I don’t know why you think I haven’t mentioned it’s advantages at all or is trying to paint me as not wanting to acknowledge “plainly obvious advantages”. I literally said that Tailwind is the industry’s current answer to working with CSS in a way that seems to work with the current and modern economic pressures. I have literally mentioned in my other comment that its advantage is that it’s as an easier to learn, easier to collab tool. Idk what else I’m supposed to say.

You were asked to say the benefits of Tailwind, but instead of saying what the clear benefits are, you are the one who chose to answer by saying that “many industry experts use it”. I thought it was a ridiculous reply, and so I chose to be ridiculous to draw parallels of your logic to justifying for the existence of fossil fuel companies. If you do not understand the concept of similies and hyperbole, I’m sorry I can’t help you there.

And you seem to fail to see the bigger picture of things and simply treated my other comment as a “I claim that this is the right way to go”. I do not claim that it is one, and is merely lamenting on the fact that there was, and emphasis here to help you read, what I think was a better way. If you’re going by the metric that economies are efficient if only things can be made quickly, then my comment is pointing out that you are simply trapped by dogma, and is merely being a part to toxic capitalism where it’s a rat race to the bottom of the barrel.

If you think CSS with the C is “slowing down development and is increasing complexity as well as potential for bugs and side effects”, then you are part of the problem. And no, I do not agree that people have “tried to embrace the cascade for a long, long, long time”. What I see instead is that they have simply lived with it because we haven’t gotten to a point where we write SS without the C. Seriously, I still don’t understand that if virtually an entire industry just hates the cascade so much, why haven’t y’all just removed it?

I’m not sure if my message is getting across to you, because it seems like you are very much happy with the state of things and the direction it’s going at. And you don’t have to spend your energy talking to someone who’s clearly on the minority and losing side of the industry. I’m just some person who happens to like CSS with the C, and enjoy writing CSS so much as it allows me to so concisely describe what I want across an entire application, and is simply lamenting on the fact that we haven’t did much to improve literacy of CSS, thinking that better CSS literacy translates to better engineers. So save your breath and energy pal.

Doesn’t it give you pause that many very experienced Frontend & CSS developers see objective advantages in Tailwinds utility class approach?

That is not a good enough reason to justify its existence. You can very well say that fossil fuel companies should continue to exist because look at how long it’s been around with all the expertise people have. Surely they should stay around, right?

Please also see my other comment

https://vger.to/lemmy.ca/comment/20657420

IMO, the industry decided to take the wrong direction, which I would agree makes sense from an economics perspective, but man, all I see is short term gains over long term ones, where we would’ve been able to build better solutions than hacks upon hacks (not using that fully derogatorily tbh). We could’ve spent all that energy, money, and time to bettering CSS and improving education to help people understand the cascade and specificity, while building better, more computationally efficient solutions that would minimize our bundles better and make JS a lot tamer than it is.

But I’m blabbering.

That’s what I mean though, that the popular frameworks are made to fight the cascade.

Modern web development claims that apps aren’t documents and simply disregarded the cascade as an artifact of document-based design, but they’re entirely wrong IMO. The cascade is made for consistency and tempo of your websites, and that’s a universal design principle irrespective of whether you’re making a website, woodcrafting, pottery, or what have you. Tailwind itself claims to give devs the ability to be consistent, but we already have that, and it’s the cascade.

Managing the cascade is, understandably, non-trivial, especially in a large enough team. It requires discipline and a good understanding of what not to do, and can take time to practice and perfect. So I understand that in our crazy economic world where speed is everything, learning something new is treated as something that’s in the way, and so we churn out devs that aren’t proficient in CSS, and they then come to train other devs, who will also not be proficient in CSS. This all lowers the barrier of entry, which is good when looked at microscopically, but in the grand scheme of things, so much of our energy is put into fighting the cascade. Just think of all the styling solutions for CSS-in-JS frameworks that we’ve churned through in the last 10 years. Madness IMO, but economies gotta economize.

Edit: yeah sorry, I get really passionate about this topic

As someone who writes a lot of CSS, and actually like CSS (yeah, unheard of, I know; I’m some alien), Tailwind doesn’t just seem like it’s reinventing the wheel and wrapping over an existing language, which is weird when you think about those two being mentioned together, is also bad for other reasons:

• UserCSS becomes near impossible to use
• Web scraping becomes a gigantic mess; LLMs become the only viable solution, and let’s not even get started on how crazy that sounds
• Semantic HTML becomes difficult to verify and build upon due to the sheer amouns of TEXT (and if you go “But you can put your most commonly used declarations together in a class selector and use that!” then congratulations you almost just wrote CSS), and in relation to this…
• It encourages bad CSS practices and thus bad HTML practices, as if the terrible walls of text isn’t already difficult to debug when working for accessibility
• RIP traditional SEO, and thus RIP any small players who want to create and maintain their own search engine, and only large companies with a lot of resources can hire people to spend a fuck ton of time to scrape and index the web. SEO already has a ton of problems as it were, and Tailwind just adds a new dimension to the problem.

If the web industry as a whole could slow down and learn to live with the cascade (seriously, the cascade is your friend!), and stop demanding that we do CSS without the C, that’d be great.

Thanks for walking pass me standing on my soapbox that virtually nobody cares about.

I don’t claim it to be common practice, just saying that it exists. That said, it may be “niche” in the grand scheme of things, but by no means do I think it’s small and insignificant. If anything, such codebases are typically foundational libraries in the giant stack of cards most other software engineers build.

See also antirez’s article about code comments https://www.antirez.com/news/124 You’ll notice how some of the snippets would’ve easily failed your criteria.

I think comment ratio could be a fairly misleading metric. There are programs out there that requires a lot of context upfront that distills down to just a few lines of code, and especially those that are more academically interesting.

Recently got one via Clove from the UK https://www.clove.co.uk/

I was pretty nervous getting it cause did not really know how it was gonna go, and they asked for a photo of my credit card (without the secrets of course) and proof of residence, which was a bit spooky, but it’s their attempt (or so they say) at pushing back against potential scalpers.

Do check Fairphone’s community form about owning one this way though, cause there’s been other Canadians who have gotten the phone, and they have tidbits to share about. We also don’t get warranty cause we’re outside the EU AFAIK.

Yo, you just reaffirmed my idea that I thought was too wild! I have to replace this old phone of mine soon cause the battery’s dying, but I guess this thing will have to stay up for a bit, or much, longer.

Please don’t remind me. Had a colleague with a senior title who just vibecoded on our CI pipeline and it ended up blocking deployments for half a day.

AFAIK, the author isn’t anti-proprietary. His goal with the newsletter is to share news that relates to self-hosting, which isn’t limited to FOSS, which is something he mentioned in one of his recent newsletters (it’s a common criticism he gets apparently). And there’s the reality where the vast majority of the source for selfhosted software are hosted on Github.

Not in my functional language with no nulls :P

Am trying to build my first NAS here (and no I’m not buying one off the shelf, cause where’s the fun in that when I drive Linux on the daily?), and I do have some spinning drives. I wouldn’t lose important work; this is just for my personal use, but it would pain me to lose some of my personal stuff. My important docs are already backed up on a personal cloud, and my side projects are on some public git.

But yeah, my plan is to have just enough power in the event of a power outage to gracefully shut down the NAS. Would be really nice if I could automate that, in case I’m not around.

Back in university, it was an iPad mini 5, using Notability. Notability has enshittified badly though.

These days (I’m no longer in university so I do write a lot less), I write on a Kobo.

It does. I vastly prefer writing notes by hand than typing em. But my handwriting sucks when I have to write quickly, and I also don’t like lugging around giant stacks of paper. And so I settled on a digital writing pad, and just do the work to type my notes later. Acts as revision too.

Every time I see someone recommend this at work I die a little inside. Like… C’mon!

And the cat wasn’t programmed to automatically follow the LOCATION header. SMH.

I remember that at one point, someone wrote this when books started becoming more accessible:

Books are RUINING OUR CHILDREN!

Just controlling parents wanting to dictate their children’s way of life since time immemorial. It’s an eternal battle.

I was thinking of male chickens when I read that and thought I’d check it out, but this was absolutely NSFW. Lucky for me though, I’m off work at the moment.

Oh I’ve heard of this, but for a different country:

https://en.wikipedia.org/wiki/Twelfth_Malaysia_Plan (for years 2021-2025) https://en.wikipedia.org/wiki/Eleventh_Malaysia_Plan https://en.wikipedia.org/wiki/Tenth_Malaysia_Plan And you can find older ones from there. The first one started in 1966, just about 10 years after Malaysia’s independence: https://en.wikipedia.org/wiki/First_Malaysia_Plan

There’s also a 13th plan in the making from various news sources in Malaysia, for the next 5 years from 2026.

Most of these plans have some amount of controversy that come with them.

• In the first plan, they’ve been happy to even support the US in the Vietnam War, in order to get some money out from the US for economic development. It was a rather unpopular move, but here we can already see how Malaysia chooses to play in the international scene, which generally continues even today.
• Throughout many of the plans, there are sections that clearly give preference to the Malay race and the indigenous people, typically grouped under the term bumiputra; though this sort of affirmative action is actually enshrined in Malaysia’s constitution as https://en.wikipedia.org/wiki/Article_153_of_the_Constitution_of_Malaysia; and from the word of mouth passed through generations of the Malaysian Chinese, there’s a strong belief that the ancestors of the Chinese and Indians there made this concession so that their people may stay in Malaysia, as many of them left their home countries due to strong push factors back home, and they aren’t welcomed back either.
• If you’re wondering what other sorts of preferential treatment have they given to the Bumiputras over the years: a percentage of enrolment in universities, a percentage of employment in sufficiently large enterprises (from somewhere medium and up I believe), and attempts at essentially emboldening rich Malays to own even more of Malaysia’s wealth in terms of percentage (there’s a common theme where previous governments will use the word Bumiputras when they really mean the Malay people, almost as if it’s a useful facade or shield against criticisms from non-Bumiputras and sometimes even foreigners; the indigenous people are fractured and generally don’t care about Malaysian politics).

Whether these plans are inspired by Soviet Union plans, I don’t know, as no one seems to talk about that. The Malaysian government’s approach to international relationships has never really changed throughout the years, despite changing governments recently: they will deal with the country regardless of whichever side of the power struggle they’re in, be it the US, Europe, Soviets, Russian, and today, China, as long as they would throw money at it without seemingly hurting the country, as well as other Islamic countries. So there’s a good chance that these 5-year Malaysian Plans are very much inspired by the Soviets.

There’s no good reason today and in the future, period.

There are “experts” who still claim these, but they are based on a very dated recommendation from at least 15 - 20 years ago at this point. To some, such non-sensical requirements (by the fact that we should be storing passwords as hashes today) have become doctrine, rather than any fact based in reality.

And some users have been conditioned into thinking that these are good security practices as well, because governments and banks still make use of them, and these are the very organizations that should be the best-in-class when it comes to security. Some of these users become CEOs or product designers with more say than their IT and security experts in the company. The rest is history from there.