4 ms·

> A lot of that complexity isn't actually necessary. I don't understand this take. Client-side JavaScript is hard because of cross-browser / cross-platform / c

> A lot of that complexity isn't actually necessary. I don't understand this take. Client-side JavaScript is hard because of cross-browser / cross-platform / cross-device challenges. Server-side JavaScript is hard because of the nature of the language and the runtimes, the lack of standard library and the myriad attempts to "fix" it, ranging from inventing new languages to transpilers to runtime rewrites. May be you mean to say, a lot of complexity could have been avoided? Unfortunately, that ship has sailed.

userbinator 3y ago
Client-side JavaScript is hard because of cross-browser / cross-platform / cross-device challenges. Is it really? Or is it hard because people are under the impression that it's hard and thus jump into the quagmire of others "selling" grossly overcomplicated "solutions" hoping it'll be easier (when in fact it isn't)? When I can replace something that a team of about a dozen needed several months to create using a few MB of frameworks that work only in the latest version of Chrome and somehow needs multiple seconds to load over a gigabit LAN (internal tool) with an HTML form and a few lines of JS written in an afternoon that will work in any browser newer than ~IE5 (and will mostly work even without JS at all), I don't think that's the answer. I don't understand this take. As the saying goes, "It is hard to get a man to understand something when his salary depends on him not understanding it." I think that's ultimately what it comes down to: Developers justifying their existence. They're all enamored with the new and shiny, resume-padding crap that they forget the problem they were hired to solve and instead create more problems that they then solve to show how "smart" they are. ...then they all get thrown out when the company downsizes. That's why I ended up having to do some JS work. I don't normally work with JS but I can use it if I need to. I never had a need to do server-side JS so I won't comment on that in specifics, but I suspect it's much of the same situation.

userbinator 3y ago

Client-side JavaScript is hard because of cross-browser / cross-platform / cross-device challenges. Is it really? Or is it hard because people are under the impression that it's hard and thus jump into the quagmire of others "selling" grossly overcomplicated "solutions" hoping it'll be easier (when in fact it isn't)? When I can replace something that a team of about a dozen needed several months to create using a few MB of frameworks that work only in the latest version of Chrome and somehow needs multiple seconds to load over a gigabit LAN (internal tool) with an HTML form and a few lines of JS written in an afternoon that will work in any browser newer than ~IE5 (and will mostly work even without JS at all), I don't think that's the answer. I don't understand this take. As the saying goes, "It is hard to get a man to understand something when his salary depends on him not understanding it." I think that's ultimately what it comes down to: Developers justifying their existence. They're all enamored with the new and shiny, resume-padding crap that they forget the problem they were hired to solve and instead create more problems that they then solve to show how "smart" they are. ...then they all get thrown out when the company downsizes. That's why I ended up having to do some JS work. I don't normally work with JS but I can use it if I need to. I never had a need to do server-side JS so I won't comment on that in specifics, but I suspect it's much of the same situation.