7 ms·
this was a dope & comprehensive. unfortunately we have a new class of dev's that never learned html but went straight for React. Now with LLMs they will never
by dzonga 5mo ago
this was a dope & comprehensive.
unfortunately we have a new class of dev's that never learned html but went straight for React. Now with LLMs they will never learn HTML.
hence they reach for react components where simple html would have been sufficient.
- Ancapistani 5mo agoI think that’s OK. When I first had to use XML, I had to learn the XML spec and output it manually - serialization libraries didn’t really exist yet. I’ve since seen generation of juniors come up through the ranks using XML as an interchange format (and then JSON) without ever learning it fully. It was fine, and nothing terrible happened. I’ve seen AJAX go from the hot new thing to people not knowing what it stood for, to now most people not even recognizing the term. AJAX didn’t die; it became so common we don’t need a word for it anymore.
- tyre 5mo agoKind of like JQuery. I know why it was such an incredible library and am happy no new devs I work with (a) know what it is (b) understand why it was necessary. Thank god the underlying language, libraries, and browser support have moved forward. And IE6 is dead. God, what a nightmare.
- Ancapistani 5mo agoI remember when IE6 was the shiny new solution that we desperately wanted :). IE 5.5 was much, much worse, and there was a long time there when it didn’t get any updates at all.
- dzonga 5mo agoif you learnt Ajax - it still works just like it did whether you're using the XHR api or the newer fetch api. html forms still work the same way. can one say the same for the various form libraries for react or state solutions.
- Ancapistani 5mo agoI’m aware of the entire progression, and objectively I’ve seen juniors come up without knowing “the old ways” at all. I’m not sure it’s a problem, but I also can’t quite wrap my head around the way they understand systems.
- zarzavat 5mo agoTo be honest HTML is a pain. For example the HTML approach to style parts of a control is to use pseudoclasses. Sometimes the selectors are different across browsers! Then you have to test across browsers because who knows if it will actually work correctly. React is not just easier it's more dependable. If I make something with React and some divs I know it's going to work the same in all browsers.
- recursive 5mo agoThe selectors are not different. Whatever problems you have applying styles to html elements also exist in react.
- zarzavat 5mo agoYes they are. For example, Blink/Webkit allow <meter> and <progress> to be styled. Firefox does not support those pseudoclasses so you can't style those elements cross browser. Then there is <input type="range"> Blink, Webkit: ::-webkit-slider-thumb ::-webkit-slider-runnable-track Firefox: ::-moz-range-thumb ::-moz-range-track ::-moz-range-progress If I build a meter or progress bar in React, I can easily style it and because it uses divs and not wonky pseudoclasses then it looks the same in every browser.
- anotherevan 5mo agoMy problem is I thoroughly learned HTML twenty years ago and am only incidentally aware of how it has changed and improved since. Doubly so for CSS.