5 ms·
Just curious, what's the vanilla JS niche? Is there any particular reason a company would go with it instead of frameworks like React, etc (not saying I agree w
by Nextgrid 7y ago
Just curious, what's the vanilla JS niche? Is there any particular reason a company would go with it instead of frameworks like React, etc (not saying I agree with those decisions, just an observation based what's happening on the job market)? Do you do server-side or client-side JS?
- username90 7y agoA lot of people don't want to set up a whole new environment just to run some javascript in their front end. I know you can put react and angular code in plain js files and serve those files directly, but if you hire a typical frontend guy chances are he will need to add a whole slew of dependencies and steps to deploy your solution. Take a simple site like HN, there is no need to make maintenance many times more expensive by doing all of those things when a hundred lines of javascript will do the trick while still being simple enough that any programmer could read it and understand how it works.
- hombre_fatal 7y agoThen 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.
- deleted 7y ago[deleted]
- austincheney 7y agoI can not speak for other peoples' opinions. Here is the reason I would pitch it in one word: scale. An application written with original logic directly to the requirements provided will be smaller, execute faster, and require less overhead to maintain than something written with a giant framework provided your developers know what they are doing. One of the biggest selling points to using a large framework is precisely because many developers don't know what they are doing and many businesses are not willing to invest the money in training and documentation. There are also specific demands that require original code that a framework is not ideal for. One of the employers that contacted me from HN was wanting me to write and maintain a Jabber based chat client that runs the browser with high concurrency like a high volume IRC room. Performance was critical and so they didn't want to deal with the overhead of a large framework. Also, large frameworks are generally there to supplement developers' insecurity with the DOM and general architecture in the browser. That doesn't solve for writing a Node.js application. As for myself I do both client-side and Node.js work. I enjoy working with Node more because that space is less opinionated. Developers' have all kinds of irrational opinions that they are willing to bet their careers on when it comes to working in the browser. Compared to most of that foolishness I am a 10x developer, and its not because I'm great at writing software. What is super frustrating though is talking through these concerns during a job interview and dazzling the interviewers virtually ensuring my selection for the position. This is super frustrating because it isn't my intent. I am not trying to impress anybody when I go down that risky path of laying all my cards on the table. I am trying to voice my concerns as directly as possible to ward off a future bad relationship. Then once I get hired and go to work on the team sure enough all my apprehensions that I attempted to illuminate during the interviews are present ensuring that everyday at work will be a slow death trying to sprint though an ocean of tar.
- cwackerfuss 7y agoNot sure what type of sites you're building on the web, but building nontrivial feature-rich web applications does not scale well with vanilla JS. Frameworks like React and Angular give you the power to manage state, respond to state updates with performant and predictable UI rerendering, and share components and logic in an opinionated way that buys engineering teams consistency and speed of development. Maybe the 10% of companies that aren't deterred by this opinion simply don't have websites that necessitate a "web application," but having an applicant say this would personally have me looking the other way 100% of the time.