Good frontend work is HARD. It requires both design and engineering knowledge, and it's very easy to write unmaintainable or inaccessible code. It also requires a high amount of backend work via BFFs, load balancing, hosting and serving, credential management, and more. The cherry on top is that it's basically all async code.

To be clear, I'm talking about the types of FEs used by thousands internationally, fully adherent to WCAG 2.2 (and above), and with rich interactivity. I'm not talking about someone's hobby project with a couple dozen users at best.

Seeing backend elitists diminish its worth is tiring as all hell. To me, it indicates that the person is either new to the industry or looking for a sense of superiority because they don't understand FE work. It's meaningless and exhausting to read.

Tldr: I agree

[–] firelizzard@programming.dev 5 points 7 months ago (1 children)

The first part of this article is taking about naming, and then heavily implies “CSS/HTML is not a programming language” is equivalent to devaluing front end developers. But that’s not the case, at least not for me.

Front end is hard. It is obnoxiously hard and requires both artistry and technical skill. And it’s critical to the success of anything that has a front end.

But I still say, “CSS/HTML is not a programming language”, because they’re not Turing complete. A programming language is something you can write a program in, without any other languages. It’s a matter of definition, not a matter of valuation. CSS and HTML are difficult and critical to get right but they’re a different kind of thing from programming languages.

[–] F04118F@feddit.nl 7 points 7 months ago (1 children)

And semantically, logically, you are 100% correct. But there are other, subjective, emotional, layers to language. Billionaire, business magnate, and oligarch can mean the exact same thing, but they have very different emotional meanings and associated contexts.

I think the author may have a point that by spreading the "HTML is not a programming language" meme, we may be contributing to its lower subjective status.

But this thesis is, by its very nature, subjective, of course.

[–] firelizzard@programming.dev 2 points 7 months ago

To me that ‘meme’ is like someone making an “Eggs aren’t meat” meme. Technically correct, I agree with the factual part of the statement, but the meme is dumb and pointless, like a bad joke. Unless the point is to belittle, in which case the poster deserves to be forced to do front end dev and deal with irrational user complaints until they repent or end up huddled in a corner mumbling incoherently, either or.

It’s like sexism. I don’t have time for that shit. If people were being sexist, bigoted, or belittling frontend devs at my job I’d tell them to get their heads out of their asses, or find a new job and then tell them. Fortunately I currently work with people who don’t suck.

[–] idefix@sh.itjust.works 2 points 7 months ago (1 children)

I feel like this article is completely missing my point. I've done my share of programming websites but not for the past 2 decades. And now I'm completely lost at reading CSS. I can't make sense of the code shown in the picture. And that's always been my trouble with CSS: the tendency to unnecessarily over-complicate things while reinventing the wheel. They have created a huge barrier for entry to the world of website programming and I think it's a shame.

[–] F04118F@feddit.nl 3 points 7 months ago* (last edited 7 months ago) (1 children)

That's an honest criticism that does not intend to devalue frontend. But there's an overlap where "over-complicate" may imply that frontend (tools) should be uncomplicated.

Having only done a few frontend projects in recent years, I see obvious value to new, more powerful CSS selectors and even things like Tailwind. I can't read Tailwind yet, but making intuitive user interfaces that work well on all kinds of devices for all kinds of people (screen readers?) is difficult and should not be expected to be simple, IMO. But this is a matter of opinion.

The ones most qualified to deal with that issue are, obviously, experienced frontend devs and they build these things.

[–] idefix@sh.itjust.works 2 points 7 months ago

I agree with everything you said, that's fair. But I do not remember having to much difficulties coding UI interfaces in Qt while supporting numerous end-user configurations.

[+] Skullgrid@lemmy.world -6 points 7 months ago* (last edited 7 months ago) (2 children)

I see you are a thin skinned idiot that can't understand your own fucking link

I find what most of those people actually mean is: HTML and CSS aren’t scripting languages. Which: a) of course they aren’t; and b) is not really the point at all.

my point is that css is meant to determine appearance and logic should be handled elsewhere.

[–] F04118F@feddit.nl 7 points 7 months ago

Well, ehm.. Thank you for the feedback I guess?

I appreciate your clarification: you mean that the logic part of conditional appearance should be handled by, for example, changing a property on an HTML node, and styling that property in CSS, did I get that right?

If I may offer some feedback in return, I would recommend you work on your phrasing. Insulting people can easily lead to being ignored or having low-value interactions. Asshole. 😉

[–] Strawberry@lemmy.blahaj.zone 4 points 7 months ago

CSS has always combined the styling and the logic for the styling. CSS selectors implement logic to determine where to apply styles