Capra, Cribl's Design System

Cribl’s big reveal is basically this: the company got tired of holding its app together with digital duct tape. After years of leaning on an outside tool kit for buttons, menus, and other interface bits, the cracks started showing. Pages looked inconsistent, teams were building the same thing in different ways, and—most seriously—parts of the app were hard or impossible for some people to use, especially with a keyboard. So Cribl built its own design system, Capra, to get everyone following the same visual rules and to make the product more accessible.

But the comments? That’s where the real plot thickens. One camp reacted like this was a familiar tech breakup story: the quick shortcut was fun at first, until the maintenance nightmare arrived. Commenter christophilus swerved into full "back to basics" mode, talking up a stripped-down, old-school approach inspired by the UK government’s famously plain design guides. Translation for non-tech readers: less flashy code, less browser chaos, more speed—and maybe a little accidental time travel. That sparked a subtle but delicious tension under the surface: are modern apps overcomplicated, and should everyone just calm down and make simpler websites again?

Then came the futuristic counterpoint. Another commenter dropped a link to getdesign.md and pushed the idea that design rules shouldn’t just help humans—they should help AI tools too. So yes, beneath Cribl’s very practical cleanup operation, the crowd quickly split into two very internet-era vibes: "bring back simple and sane" versus "feed the robots better instructions." Not exactly a flame war, but definitely a nerdy style showdown with strong opinions and a whiff of meme energy.