stm8ef VS Tailwind CSS

Thanks, GitHub URL: https://github.com/TG9541/stm8ef

I'm a fan of the STM8 line, nice peripherals, and nice programming model if you are writing any assembler. Much cleaner than 8051. You can do debug with the STLink. There are free toolchains from ST as well as the open source SDCC compiler. There is even a nice Forth. Even if Forth does not interest you that set of pages has a lot of info about various STM8 devices.

This past week I've been on a mission to find the cheapest microcontroller that I can reasonably learn to program. I've gone down the STM8S 001 rabbit hole and found this https://github.com/TG9541/stm8ef/wiki/STM8-eForth-Example-Code

An example: eForth for the STM8 lets you fit an interactive development system including compiler onto an mcu with 8Kb flash and 1kB ram. Very useful for testing and exploratory development in systems that are otherwise far to small to support it.

Eventually you're going to need someone to help explain what on earth is going on here. Fortunately Thomas Göppel the maintainer of STM8 eForth has done that in a very readable explanation of FOR .. NEXT and how to use it.

It's always a multi dimensional spectrum of cost, performance, peripherals, development support, availability, family reach, etc. I personally really like STM8 microcontrollers for their simplicity and very low cost (can be less than 30 cents). There's actually another project that brings Forth to STM8: https://github.com/TG9541/stm8ef It has very good documentation and I recommend anyone to take a look

I used the discussions feature to express my thanks a few days ago. Might be better than opening an issue? https://github.com/TG9541/stm8ef/discussions/386

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...).

- Staff Software Engineer ($275k/yr): https://tailwindcss.com/careers/staff-software-engineer

We're small, independent, and profitable, with a team of just 6 people doing millions in revenue, and growing sustainably every year. You'd work directly with the founders on open-source software used by millions of people.

If you like the idea of working on a small team that cares about craft and isn't trying to achieve VC scale, I think this is a pretty awesome place to do your best work.