4 ms·

Whenever I see OO[something] in the world of programming, I have that face my mother would be ashamed of. I have jumped on and off of web development in the la

Whenever I see OO[something] in the world of programming, I have that face my mother would be ashamed of. I have jumped on and off of web development in the last 8 years. Everytime I jump back in there are changes. I ended webdev around 2011 being pretty good with jquery, using ajax to load part of web pages. Did some cool stuff for its time. Came back to webdev in 2014 using knockoutjs. Seemed like bloat but did not question decision outside my control. I did like the idea of changing a value and it automatically applied the change on screen. Came back to webdev in 2018 using angular. This was my decision and only because "it was popular" so anyone could take over hte project. Felt like duplicating my work to be honest. Now, its 2022 and back on web dev. React. npm. Seriously... WTF! One site was using npm and grunt JUST TO MINIFY FILES!! Again... WTF! Maybe there is something good about this OOHtml and missing the point entirely. WOuld not be suprised using this requires over 1000 npm dependencies.

trollied 3y ago
There's no reason why you can't still dev the "old" way. It'd be nice to actually have a nice clean, fast site for once that doesn't present you with a load of spinners or other nonsense while the content actually loads. Before your face gets DDOSed with adverts. The modern web is a disgrace. I sometimes wonder if some devs actualy use the sites they create.
- masfoobar 3y ago
  > There's no reason why you can't still dev the "old" way. Absolutely. It's just when you jump back in the webdev world and you see changes you end up learning them to keep yourself relevant. As the years have passed, since starting with knockoutjs (for me) the back of my mind was slowly accepting the "old ways" are the best way to simplify and solve the actual problem. I was slowly moving back to using jQuery.. and, in the last year, have been moving over to htmx.

trollied 3y ago

There's no reason why you can't still dev the "old" way. It'd be nice to actually have a nice clean, fast site for once that doesn't present you with a load of spinners or other nonsense while the content actually loads. Before your face gets DDOSed with adverts. The modern web is a disgrace. I sometimes wonder if some devs actualy use the sites they create.

masfoobar 3y ago
> There's no reason why you can't still dev the "old" way. Absolutely. It's just when you jump back in the webdev world and you see changes you end up learning them to keep yourself relevant. As the years have passed, since starting with knockoutjs (for me) the back of my mind was slowly accepting the "old ways" are the best way to simplify and solve the actual problem. I was slowly moving back to using jQuery.. and, in the last year, have been moving over to htmx.