4 ms·
Good god, JIT for CSS... I thought this was one of those joke articles about insane complexity of front-end development.
by sakopov 6y ago
Good god, JIT for CSS... I thought this was one of those joke articles about insane complexity of front-end development.
- qbasic_forever 6y agoEhhh, systems outside frontend are just as complex. Think of a backend service--you've probably got a low-level TCP/HTTP handler written in a fast systems language like C/C++, then your business logic written in a higher level language like Go/JS/Ruby/etc., and that's interacting with your data layer using a completely different logic-based SQL language (and extra complexity to translate that SQL to your high-level language with an ORM layer), and on top of that you probably have a rules engine for authorization because you realized the systems language was too slow to update and deal with fast-changing business requirements. This is really not that different from the frontend world where you've got a markup language to define semantics of the view, a logic layer in JS to pull in data with web requests to populate the view, and CSS as a style layer to make the view look good.
- Lapsa 6y agoDon't forget to add CSS type safety with TypeStyle!!!11eleven
- mhd 6y agoI downloaded the tailwind-jit repository, and after a good coffee break and "npm install", it's 120 megs. But I'm not that worried, give it a few cycles and we get esbuild for tailwind, which should bring it down to a simple barebones 8 mb Go binary.
- tiborsaas 6y agoWell, they needed to fix a serious issue they created in the first place. Wait till they fix the issues with this too :)