In South Africa we refer to the papaya as pawpaw, I'm in England now, and here they just say papaya. https://en.wikipedia.org/wiki/Papaya. This article mentions papaya as a separate fruit. Is there something missing?
I find MDN to be a bit clearer, and they benefit from the in-browser runtime. All the extra detail in the Rust docs (blanket traits etc) were quite intimidating and distracting when I first started learning it.
While both of these docs are pretty good, as someone who normally much prefers API references to "how to" formats, the MDN's "how to" approach here is succinct & just enough to cover reasonable bases, while the Rust API ref list is a bit too terse by comparison (& the Read More click out is a bit annoying).
Have there been any comparisons written about Tailwind's performance vs thoughtfully selected CSS? I've been writing Tailwind exclusively for the last year or so and I haven't noticed anything in particular, but I find that using utility classes causes me to lose an awareness of the cascading nature of CSS. Aside from the filesize bloat due to the bigger HTML files, do long and highly-repetitive class lists slow down style parsing or DOM interaction? And if so, would @apply directives have an advantage over class lists?
I can't say much about selector performance besides that class selectors (.class-name) being very fast, opposed to complex selectors (like "#some-id > div a"). Of course less classes applied means less work for the browser, but the real cost is the complex selectors
With regards to bloated HTML, that might seem the case but since you reuse the same class-names everywhere in your app (and tailwind JIT removes non-used classes), compression really cuts down on the size of your bundles. It just looks bloated in the web inspector. This is a disadvantage, it is a bit hard to debug HTML with all those class-name strings around, although I would say web-inspectors should just truncate "class" attr value
With bundler performance it adds some overhead (tailwind has to go through all your .js/tsx files), but in my experience not noticeable
A lot of the comments in that thread appear to be flaming the OP for impersonating a legendary demoscene group, or something like that. I've always enjoy touristic, almost archaeological appeal of reading old subculture drama, and I wish I stumbled across them more often.
Absolutely. You can usually drop the direction though as it's the initial value. But flex is so powerful for layouts, I'll slap it on almost anything, and barely have a need for grid.
I'd say close to just works. I've spent the last 6 months developing with Rider on Arch and it hasn't been a completely smooth ride. Admittedly, a lot of my pain just came from inexperience. I screwed up permissions; it took me ages to setup the right .net packages due to the nomenclature (which, when I installed Visual Studio on Windows, is easily glossed over); function apps took a while to get working.
But it really is satisfying once you've got everything working.
