There are dozens of us. Dozens!

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.

Just zoning out for a bit, cozily with a hot cup of your favourite drink is a lofty dream these days.

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.

Not in my functional language with no nulls :P

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.

• Fixed volume jumping to 100% upon removing 3.5mm headphones

THANK YOU!

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.

Ahh that’s gonna be a real hard find.

I thought OpenRGB would be able to give some starting point so I looked it up, but there’s a grand total of 11 supported gamepads, half of which are the PS controllers. So we’re out of luck there.

What sort of configurations are you looking to do with the controller that Steam Input wouldn’t cover? Cause if you don’t actually need specific features from the 8bitdo config software, it works just fine with Linux. In fact, I’m using one right now, and have been using it for years.

Oh! That’s somewhat interesting to know.

But it’s worth noting that while word of mouth is one way, we can always just try launching the game without Steam to find out.

Again, you’d be forgiven for that. The design language around these sorts of license purchase has been frequently framed as a straight purchase by many companies on the Internet that it’s become essentially the norm that many don’t question. DRM is also proposed without ever stating that it essentially makes the end user purchase a license, as it frames itself as a way for the publisher to retain some control over the product that’s in their interest, and that the end user don’t even need to really know until the rights are exercised. It’s an infuriating piece of technology that is straight up designed to be a rug pull from the get-go.

But, again, to be fair, not all games on Steam have DRM from some info I’ve gathered before. It was impossible to tell, but I think Steam actually shows a little info box now to clarify that DRM is in place or not.

Welcome to the painful world of DRM that we live in :’)

And to be fair to Steam, they did recently issue a statement and tried reflecting it in their stores to say that you don’t actually outright own all the games you “bought”, as, for some, you are merely purchasing the license to play games that the publishers have decided to put behind a DRM. This has always been the case since the dawn of DRMs, and it was implied that people should understand it, but recent events have made it clear that a lot of people aren’t even aware of it. So you’d be forgiven for not knowing.

As many others have said, this is because you’re using the same account on both devices, and Steam’s DRM policies will stop you from being able to do what you described. So I won’t go into re-mentioning the many suggestions others have talked about.

What I do want to mention, however, is that this isn’t a problem that comes from having the Deck itself. Set up a separate computer in your living room and use your Steam account there, and you would have the same problem. Does that mean you should be turned off from buying a new computer that’ll run parallel to your main gaming rig?