3 ms·
Then again, HN doesn't need a Javascript developer to maintain their 2kb of JS, either. I mean, by virtue of being a client-side Javascript developer, you're s
by hombre_fatal 7y ago
Then again, HN doesn't need a Javascript developer to maintain their 2kb of JS, either.
I mean, by virtue of being a client-side Javascript developer, you're surely going to be working on client-side applications large enough to demand a client-side Javascript developer.
Frankly, avoiding jobs that use frameworks seems like you're choosing for nothing more than legacy spaghetti-code messes, not some sort of back-to-basics enlightenment. But I'm not here to judge what somewhat likes. :P
- username90 7y agoI looked up his post, seems like he codes complicated systems in Javascript rather than being a typical UI developer: https://news.ycombinator.com/item?id=20589013 https://news.ycombinator.com/item?id=20589013 I can see a lot of companies being willing to hire a person who can do that even if he doesn't want to use a specific UI framework. Just write down the javascript and you can integrate it in whatever codebase you have, so he is a lot easier to work with than your average JS dev.
- Nextgrid 7y agoFrom my experience the modern framework-based project are spaghetti messes with thousands of unaudited (and unauditable, due to their quantity) dependencies. To me it doesn't look much better than the old-style "spaghetti mess". At least the old-style one is usually self-contained and will keep working, where as the new one will randomly break once someone pulls a package or a repo is temporarily unavailable. Maybe there's just something I don't get and clearly frontend developers somehow manage to make all of this work, but to an old-school backend guy like me the modern JS ecosystem seems horrifying, needlessly complicated, over-engineered and brittle.