4 ms·
I think if the web apps we were working on were marketing landing pages, you'd be right. For any real application that software engineers are hired to work on,
by d357r0y3r 3y ago
I think if the web apps we were working on were marketing landing pages, you'd be right.
For any real application that software engineers are hired to work on, "learning HTML" would do very little. Most high-level front-end engineers do know HTML. There's not that much to know.
The web today is basically a universal desktop client. Apps like Figma, Slack, Airtable, and thousands of others are not really websites, they're hosted applications that have a mind boggling amount of interactivity.
- kethinov 3y agoAttitudes like that are why so many "real applications" have things like progress bars assembled from divs and JS instead of using a progress element or show/hide toggles assembled from divs and JS instead of using details/summary elements. Turns out there are so many HTML elements for a reason.
- d357r0y3r 3y agoAttitudes like what? How do you build Figma using "semantic HTML"? Everyone likes the idea of keeping things simple and using web native constructs. The problem is that web native constructs can't do the things people them to do. Even the progress bar example is a good one. Yes, there is a minimal progress indicator element shipped in the browser. It is completely useless for all but rudimentary cases.