3 ms·
>> > it is a seemingly never-ending race just to keep up with the state of the art >> It is, there is noting seemingly about it. But if you build a foundation
by phkahler 8y ago
>> > it is a seemingly never-ending race just to keep up with the state of the art
>> It is, there is noting seemingly about it.
But if you build a foundation on HTML and CSS then you have something that stays relatively constant in the face of change. All that other stuff is often just fluff and programmers thinking they know a better way.
- rchaud 8y agoThe foundation of HTML and CSS was separation of concerns, yet the most popular web app framework mixes HTML, CSS and JS together and says that it's fine. That's the first moment of confusion for students who are learning React after doing the basic HTML/CSS courses. Someone who can build a static site (not Hugo/Jekyll/whatever) in HTML and CSS and upload it via sFTP will struggle to understand loop functions in a database-driven CMS, which require some knowledge of a server-side language. Same goes with learning Git; there's a big jump in perceived complexity when you go from coding inside Sublime Text and typing commands into a Terminal.
- dmitriid 8y ago> most popular web app framework mixes HTML, CSS and JS together and says that it's fine. This was always the case. Because you could never build any reliable foundation on HTML+CSS alone.
- goatlover 8y agoAnd that's because the web wasn't meant to be an application platform. It got turned into one on top of html/css.
- root_axis 8y agoYet here we are. The internet wasn't "meant" to be the global apex of commerce and communication, yet here we are. People started making more than just static documents because running programs on the web was fun and cool and it still is.
- deleted 8y ago[deleted]
- dmitriid 8y agoAnd it’s really sad that the standards bodies never realized that. They still treat the browser as a means to display text and some pictures :(