julik

10 ms·

91.
by julik 2y ago
I think it's more like "having less moving parts". In which they kinda-sorta-succeeded, except that the choice of bun seems misguided for something where you want broad adoption. And Tailwind is, by now, a product that is cle
92.
by julik 2y ago
The application is not packing the binary - it is the gem that you use to build CSS, and I _think_ it's only active during development, but don't quote me on that. In production there is a generated built asset which contains all
93.
by julik 2y ago
Yes, they run it - but for most it is melted into another bundler like PostCSS. The few of us who try to resist the "just use bundlers for everything and everywhere" do notice that there is now a bundler process firmly anchored in
94.
by julik 2y ago
I don't think CSS has failed - it's just a big and complex system for automatic layout. Automatic layout is hard, and if the age and power of CSS show us anything - is that it has succeeded. Comparing CSS of today to CSS of, say,
95.
by julik 2y ago
I hope there will be sirens... https://en.wikipedia.org/wiki/The_Sirens_of_Titan
96.
Template-Scoped CSS in Rails(blog.julik.nl)
2 points by julik 2y ago|0 comments
97.
by julik 2y ago
> You're a much more patient person than I am. That is very kind of you to say, thank you!
98.
by julik 2y ago
Most likely they decided to go for a binary so that people with other runtimes could use Tailwind without subscribing to the whole Node+npm ordeal. And it's actually neat when it works - for us RoR folks it makes things like tailwindcs
99.
by julik 2y ago
I don't even know what it is, to my shame. I do know that when you run a container it will be calling into the CPU ins directly, unless it concerns something like Rosetta 2 - but even then I don't know whether, say, the AVX2 instr
100.
by julik 2y ago
I see this is absolutely something I am not going to be using as long as I can help it (it is the same setup as importing CSS and MP4 in Webpack via the import declaration), but a good tidbit to know it exists.
101.
by julik 2y ago
No, the pre-processor has to be running continuously in "watch" mode with patterns for all your HTML (and sorta-HTML) files. When it detects a change in one of them, it chews through the changed file and emits a .css file into you
102.
by julik 2y ago
The vendor does not officially publish its dropped support. But from a brief piece of research I did, Jared dropped support for macOS 12 before Apple shipped the last update for it. And while on a formalistic, nitpicky level it is a "w
103.
by julik 2y ago
That would be nice. There was also duktape, which was very compact and very embeddable - it could have been a decent carrier for Tailwind too.
104.
by julik 2y ago
So do I, but we were told that "open source is a gift", and I can only have opinions about choices made by others, not command them "do it this way instead". I am not the inventor, owner or maintainer of Tailwind nor do
105.
by julik 2y ago
That one I try to avoid at all costs, but I hear what you are saying. The owner of the company selling Next.js and adjacent services is firmly in that list of influencers I have muted going forward.
106.
by julik 2y ago
Absolutely with you on "no build". Sometimes it doesn't work (for me - where I need NPM modules with annoying math I don't want to do myself), but the basic premise of "nobuild" is absolutely and completely how
107.
by julik 2y ago
The irony is that these days, with nested selectors supported natively, there is zero need to use this heavy of a tool for this isolation.
108.
by julik 2y ago
I know the feeling. The way it works is that Tailwind parses your HTML, finds `mb-4` and thus knows that it needs to emit the `.mb-4 { margin-bottom: some-var-calc-thing-in-4-increments-of-your-layout }. So it is not as much of a compiler -
109.
by julik 2y ago
> Why in gods name ship bun. I try to avoid that strong of a language (although believe me - when this was going about I was very, very angry indeed). I think the reason was exactly removing the "npm hell" for users and not req
110.
by julik 2y ago
The irony of my situation was that even using a Docker container would not help, because Docker does not emulate CPU instructions.
111.
A Supermarket Bag and a Truckload of FOMO(blog.julik.nl)
116 points by julik 2y ago|74 comments
112.
by julik 2y ago
There is - removing a wonk preference namespace is as easy as `rm ~/Library/Preferences/com.cheapskatesoftware.wonko.plist`. Whereas the Windows Registry is a monolithic piece of gunk you need a Microsoft editor for to zap so
113.
by julik 2y ago
Good one! I thin it will be fine.... ..exceptForThisArgumentAtTheEnd.
114.
by julik 2y ago
TIL
115.
by julik 2y ago
Fair point! It also felt clearer to me at first, but I found that I would need some "management" to avoid indexing into nonexistent indices and otherwise manage that pointer - like you are saying, the checks for that index not fal
116.
by julik 2y ago
That is deliberate, because I wanted the `past` + `future` to go in the same direction chronologically. They are separate stacks, but they represent a certain continuity in time - so I wanted to have it ordered the same (chronologically)
117.
by julik 2y ago
Something I support completely - previously https://news.ycombinator.com/item?id=35418933#35438029 If CSV is indeed so horrible - and I do not deny that there can be an improvement - how about the clever data people spec ou
118.
by julik 2y ago
That's clever and can work great if you don't hold any resource handles
119.
by julik 2y ago
To me - it does, because using an index is always this fiddly thing. Do you increment/decrement the index before doing something or after? Do you need to check that you have incremented to len or above? Do you need to check that you ha
120.
by julik 2y ago
This is very neat. Doesn't this kinda cross functuionalities with the MutationObserver?

More ›