|
|
|
|
|
|
by lifeisstillgood
2490 days ago
|
|
|
I disagree. JS should be like SQL - everyone's second language and a standard that can be taken from job to job and company to company and still be effective. But while I this week used my decades old SELECT skills for a quick two day job, I have also been utterly stumped trying to modify react codebases. JQuery is probably the closest thing to SQL in the JS world and it is fine - but there appear to be few technical reasons not to use it and lots of fashion reasons. And so while I could just stick to JQuery and some widgets, the weight of development seems to be in the morass of change that is so very hard to stay on top of. Yes this feels like crotchety old timer moaning, even to me. But there is something there. I am having trouble expressing it however. |
|
|
I don't think SQL is a great example either. Your next company could be using any database where you aren't even writing SQL. And you're expected to know more than standard SQL to, say, use Postgres. Your rant here to me is like getting mad that "just SQL" isn't enough because you constantly have to learn more at your next job that uses Postgres, DynamoDB, etc or that "just <language>" isn't enough because your next job uses a different framework than you're used to. I don't think your rant is consistent, so it just comes off as confused anger towards JS client development.
Maybe you don't have the stomach for client development where code must run on a machine you don't control? That isn't a disparaging remark either, it's very reasonable to prefer the cozier environment of writing code for machines you do control (like application servers).