5 ms·

Oh please stop. Apparently the author has always worked on their own projects, with its own (or its team’s) discipline. Let me state this: old-school front-end

by yuchi 6y ago

Oh please stop. Apparently the author has always worked on their own projects, with its own (or its team’s) discipline. Let me state this: old-school front-end is a mess once you have to mantain an enterprise-grade application. npm is pure joy to work with, in comparison with a huge mess of copy-pasted files in a “vendors” directory (if you are lucky enough to have such a directory! currently I’m working on a project where developers copy-pasted the content of JS libraries one after the other in a single “lib.js” file… for years!) Front-end development has now reached a very fine situation regarding code hygene and modularity — and this makes me very happy to be on the front-end side.

411111111111111 6y ago
Yes, the grass on the other pasture is always greener. I especially found his hand-waving wrt language funny. > The language doesn't matter much to me, I know enough of them to know that they are all very similar and thus easy enough to learn. If thats what he thinks, then he really only experimented with very similar languages... And the quantity of strangely applied software patterns like using statemachines to hide a simple switch-case... it would be hilarious if it wasn't so sad.
- wizzwizz4 6y ago
  The difference between MIT Scratch and FORTH is superficial; it's all just mutable LISP when you get down to it.
paul_f 6y ago
Not every application needs to be "enterprise grade". Yet, many design teams seem to approach them all the same way. Stop the needless bloat!
chrisjs95 6y ago
This. The quality of developers has gone down in the past 10 years and it's really hard to teach maintainable Javascript to developers. They just don't understand even delegation and how to do complex UI's in plain Javascript. Either way you wouldn't really want to because it just turns to crap. The frameworks have been great for companies.
- r45tio2 6y ago
  > The quality of developers has gone down in the past 10 years Well, there we go. Why would that be? It seems a very sad state of affairs. A genuine question: what has happened here? Constructively, we need frameworks for different skills - why are we expecting designers and UI experts to deal with dependency management? Let's let them do what they are good at. "Developers" is too wide a term, for a start. Cutting through the abstraction and thinning down the frameworks so we can achieve the same thing with less is a very different discipline to making a site look nice. Let's all work together.

by yuchi 6y ago

411111111111111 6y ago

Yes, the grass on the other pasture is always greener. I especially found his hand-waving wrt language funny. > The language doesn't matter much to me, I know enough of them to know that they are all very similar and thus easy enough to learn. If thats what he thinks, then he really only experimented with very similar languages... And the quantity of strangely applied software patterns like using statemachines to hide a simple switch-case... it would be hilarious if it wasn't so sad.

wizzwizz4 6y ago
The difference between MIT Scratch and FORTH is superficial; it's all just mutable LISP when you get down to it.

paul_f 6y ago

Not every application needs to be "enterprise grade". Yet, many design teams seem to approach them all the same way. Stop the needless bloat!

chrisjs95 6y ago

This. The quality of developers has gone down in the past 10 years and it's really hard to teach maintainable Javascript to developers. They just don't understand even delegation and how to do complex UI's in plain Javascript. Either way you wouldn't really want to because it just turns to crap. The frameworks have been great for companies.

r45tio2 6y ago
> The quality of developers has gone down in the past 10 years Well, there we go. Why would that be? It seems a very sad state of affairs. A genuine question: what has happened here? Constructively, we need frameworks for different skills - why are we expecting designers and UI experts to deal with dependency management? Let's let them do what they are good at. "Developers" is too wide a term, for a start. Cutting through the abstraction and thinning down the frameworks so we can achieve the same thing with less is a very different discipline to making a site look nice. Let's all work together.