monogon VS Tailwind CSS

It's somewhere in my git stack :).

Until I get to publishing it, the proto/gRPC definitions for node management are a good enough start: https://github.com/monogon-dev/monogon/blob/main/metropolis/...

And the top level API to actually deploy workloads is plain Kubernetes.

Monogon, a fully remote, self-funded and engineer-led technology company, is hiring software engineers to work on Metropolis, an open source [1], secure, distributed cluster operating system based on Linux and Kubernetes.

Metropolis runs on a fleet of bare metal or cloud machines and provides users with a hardened, production ready Kubernetes - without the overhead of traditional Linux distributions or configuration management systems. It does away with the scripting/YAML duct tape and configuration drift inherent to traditional deployments, and instead provides a stable, API-driven, secure and vendor-lock-in-free platform for companies to build their products upon.

We're looking for senior candidates who can design, implement and verify complex systems that will make up part of Metropolis. We offer a kind and honest work environment in which we prioritize quality over quantity. You'll be the fourth member of a team working on an ambitious, industry-challenging product.

Our ideal candidate is a generalist with deeper knowledge in one or more of the following areas:

- Distributed systems;

- Software engineering of systems built to last;

- Security engineering, especially experience with secure boot chains;

- Low-level programming and debugging (C, Linux Kernel, …);

- Kubernetes, especially practical experience of running bare-metal production deployments;

- Platform development, ie. running a 'Company A' style infrastructure/DevOps team [2].

Our codebase is mostly Go (including pid1!), so knowledge of the language is a plus, but not a requirement (given the seniority of the position, we expect any candidate to be able to ramp up on Go within a few weeks).

To get in touch, email me at at nexantic.com.

[1] - https://github.com/monogon-dev/monogon

[2] - https://rachelbythebay.com/w/2020/05/19/abc/

- Platform development, ie. running a 'Company A' style infrastructure/DevOps team [2].

Our codebase is mostly Go (including pid1!), so knowledge of the language is a plus, but not a requirement (given the seniority of the position, we expect any candidate to be able to ramp up on Go within a few weeks).

To get in touch, email me at at nexantic.com.

[1] - https://github.com/monogon-dev/monogon

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.

First, you need to make sure that you have a working Tailwind CSS project…

Tailwind CSS

With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.

This app was built with Svelte Kit, Tailwind CSS, and many other technologies. For a full rundown, please visit the GitHub repository

Unlike Tailwind, which has over 77,000 stars on GitHub, Mojo CSS has about 200 stars on GitHub. But the Mojo CSS documentation is fairly good and you can find most of the information you’ll need there.

JavaScript React Flowbite Tailwind Firebase - Auth, Database, and Hosting Vite

- Performance is a feature.

Another common interpretation of brutalism is aesthetic, reacting to overly complicated user interfaces by creating simpler, more direct ones. Tailwind CSS (https://tailwindcss.com), one of today's most popular CSS libraries, promotes this approach in its component examples. There's also a neat library I've seen recently called "Neobrutalism Components" for React that I like (https://neobrutalism-components.vercel.app), providing components with a similar look and feel to Gumroad. This might more accurately be called 'Neo-Brutalism,' as noted in the comments.

A more engineering-centric interpretation of Brutalism focuses on form, structure, and efficiency, drawing significantly from brutalist architecture principles. Apart from the user interface itself, most mobile, desktop, and web applications are extremely bloated and often perform worse than sites from 10 years ago did. While one HTML file might be "less brutalist" than the original HN site, it is substantially more brutalist than any HN mobile app in existence, and offers nearly identical functionality.

A broader interpretation of brutalism, which could be termed 'Meta-Brutalism,' is embodied in the overall experience on this site through UX flows. Yes, in the strictest sense, the original HN site is more Brutalist in many ways, but it only shows 30 articles at a time and does not function as a PWA. For this site, the experience of reading 10 stories is arguably less brutalist, but for quickly browsing through several pages and skimming articles (which is how I read HN) it is a lot faster, and in my opinion, more Brutalist.

My primary inspiration was addressing software and tool bloat in UIs rather than strictly adhering to every principle set forth by David Bryant Copeland. I don't find it convincing that this site "isn't brutalist" compared to really any other experience apart from the Main HN site, and I would argue the overall experience is more brutalist in its performance and scrolling behavior.

As a side note: I generally don't like Brutalist architecture that much although I believe it is unfairly maligned. I visited the Salk Institute once and enjoyed it though (https://www.archdaily.com/61288/ad-classics-salk-institute-l...).