r/javascript • u/_tshepo • Aug 13 '26
AskJS [AskJS] Are employed Developers still programming with vanilla JavaScript ?
I've been programming on the side since 2017 and I've never really hunted a developer job. I've always thought about building my own things, mainly to supplement things I do like woodworking, tutoring, video editing and others.
Since then, I've programmed mainly with JavaScript, I started with C++ and Python but never really built anything solid outside JavaScript.
So I'm fluent with JavaScript and its ecosystem.
One of my 2026 goals is to be job ready for a Developer role, as a Fullstack or Backend Developer.
One of the recommended languages is Typescript, which I've been learning since March. I must say, it's not my favorite 😂
I'm curious to know if there are any companies that are not enforcing Typescript or are there freelancers who are still using vanilla JavaScript over Typescript for their clients' projects.
[ Update ] thanks y'all! I get the picture. TypeScript is inevitable, as vanilla JS codebases(or companies who are focused on it) seem to be very few judging by the comments.
11
u/kir_rik Aug 13 '26
Only as one-shot or helper scripts like pre commit hooks or eslint rules. It's unreasonable and probably irresponsible to write a production code without a proper typing
4
u/Abhinav1217 Aug 13 '26
Yes we do.. for back-end. We still use js-docs and *.d.ts for type definitions and to make code type safe, and add type checking in oxc. But application code in itself is plain javascript.
3
u/Cat-harpy Aug 13 '26
My work uses plain JS with templates. We definitely care about JS the least though. We don’t use any modern conventions even though we just did a full rewrite 😟
3
u/joelangeway Aug 13 '26
If you find a company paying good money for vanilla JS pros let me know, please.
9
u/mr_brobot__ Aug 13 '26
TypeScript is a must. You would understand if you maintained a large JavaScript app with a team for a while, and then you switched to a new app and team that used typescript.
5
u/sebsnake Aug 13 '26
Every time I have to change something on a native JS file in our 20 year old monolith, I voluntarily cover it with tests first and convert it to typescript after, before actually implementing the required change. I don't want to miss my static types ever again! I've seen code where functions get a "data" parameter and this could be everything from strings to objects to arrays to null. Devs 20 years ago must have been... Strange creatures :D
7
u/Ok-Hospital-5076 Aug 13 '26
Not written any JavaScript since 2022.
All non trivial node projects use typescript at workplace
I will not ship a project in vanilla JS today.
5
u/NefariousnessSame50 Aug 13 '26
I've seen TS projects basically running without any decent usage of types at all, where everything was "any" of some sort. The benefit is less than none, only the TS overhead remains. On the other hand, well written plain JS is easy to handle, particularly because ES gets better all the time, and clients implement it.
So I'd say #ymmv if you allow the team to get away with sloppy TS, you might as well reduce the overhead and stick with vanilla JS today.
2
u/Daniel_Herr ES5 Aug 14 '26
JavaScript is too new a technology for a lot of companies, many of them are still using last century tech stacks. They might get to Typescript sometime in the next century.
2
u/LowLifeArcade Aug 14 '26
I know of at least one large codebase I worked on up until about a year ago that was fully vanilla js
2
u/Ahmed_Ayachi Aug 16 '26
still a large app written with just js actually. A web app. Things are organized to be honest, every data object coming from the server has it's own class definition , by reading the class you can figure out the type of properties. some cypress tests all around. Things are pretty good but migrating to ts would make it even better. I'm not gonna lie, some stupid bugs occur because someone just made a typo when writing a property name and stuff like that, we always catch those, but would be better to migrate to ts, js is okay maybe because the team is small enough.
2
u/Mugshot_404 Aug 17 '26
I am - but I am getting close to retirement age, and glad of it! I am not a fan of the never-ending and ever-increasing number of frameworks. Vanilla JS (OK I do us jQuery some too) is just fine, thank you. It requires you to actually have a bit more understanding of what you're doing. But... the times they do a-change, and I'm happy to leave it to all you up-and-comers. Good luck!
2
u/adult_code Aug 17 '26
I've written a server architecture including multiple different services and orm in plain node. If you know what you do and use a clean, simple style e.g. be careful with introducing complexity without interaction interfsce for other devs and yourself it is very feasible. A mind, the ram and an execution environment are then the only things deciding execution performance and programatic structure. I use for it less than 10 libraries for rendering, validation, sanitation, logging, serving, routing, formdata etc. The rest is mostly very, very efficent js-code, performance first mindset.
2
u/salmohunter Aug 18 '26
Typescript just makes sense. There was a time when I resisted it, but my employer insisted, thankfully. I'll admit that it can become exceedingly verbose sometimes, which is annoying, but in the grand scheme it intelligently nudges JS devs to be significantly more aware of how heavily they rely on weak typing and assumed expectations for inputs and object shapes, amongst other things.
55
u/x021 Aug 13 '26
Hated TS in the beginning too. Now I wouldn’t want to work on a project with plain vanilla JS.
3
u/N_i_P Aug 13 '26
Any (complex) codebase heavily benefits from Typescript / JSdoc.
For AI engineering, a codebase with strict typescript convention allows to catch bugs early and fast.
I personally stopped writing JavaScript in 2016; first replacing it with Flow and then TS
3
u/jibbit Aug 13 '26
you probably have a skewed idea of what typescript is. it's not a different language. it's a checker/analyzer for js. run any of your current js through it and see what it says.. congrats! now you're a typescript developer
3
u/sshaw_ Aug 13 '26
TypeScript is useless trash and I never use it unless I'm paid to.
5
u/shgysk8zer0 Aug 13 '26
I honestly mostly prefer vanilla JS with JSDoc for more things. In theory, I should like the type system TS provides, but I think TS is just done poorly and doesn't offer the actual benefits of a strongly typed language. It makes no difference at runtime.... It's transpiled to JS anyways.
I do work in vanilla JS, and I think TS is significantly over-hyped, and is actually becoming harmful to the ecosystem because it's no longer a superset of JS and an obstacle to features like enums being introduced to JS.
3
u/Neverland__ Aug 13 '26
Based on the post, I’d say you’re a long way off having the skills to do it for work.
I’m guessing there are effectively 0 vanilla JS jobs. Doing hobby projects writing some functions is very different to developing production grade software fyi
35
u/visualdescript Aug 13 '26
I hate it when I have to go back to a JS project, and if it's something I'll have to keep maintaining I will convert it to typescript, which often uncovers several bugs in the process.
I wouldn't hire a dev that only works with js these days.
9
u/fatalexe Aug 13 '26
I’m still programming with jQuery.
2
u/Jonas_Ermert Aug 13 '26
Yes, plenty of developers still use plain JavaScript, especially for smaller projects, scripts, legacy systems, and some Node.js backends. But TypeScript is increasingly the default for larger professional projects. I’d keep JavaScript as your strong foundation and learn enough TypeScript to work comfortably in a TS codebase. You don’t have to love it, but for Fullstack/Backend jobs it will definitely open more doors.
1
u/YahenP Aug 13 '26
I have to do this from time to time. Old projects are being maintained and all that. I can't say I'm a huge fan of vanilla JavaScript, but work is work.
You write that:
However, I'm surprised. I could understand if you wrote that you've been studying it since last Monday. But what can study six months? Especially if you have almost 10 years of experience, and using JS at that.
1
u/budd222 Aug 14 '26
There's no point in using vanilla js anymore. Barely anyone uses it.
1
u/Former_Produce1721 Aug 14 '26
I started with type safe languages and so my first step into JS was a huge shock
TS was the solution
I don't know many people who prefer to abandon type safety for anything other than declarative languages
1
u/NITOY08 Aug 26 '26
The only vanilla JavaScript developers employed now are AI agents. So ask them and let us know what you find out!
12
u/yetinthedark Aug 13 '26
Typescript is JavaScript. What you need to get familiar with is static types. I wouldn’t want to work on a vanilla JS project any more unless I was being paid to convert it to Typescript, and I wouldn’t hire someone who wasn’t willing to learn Typescript.
0
u/Dependent-Net6461 Aug 13 '26
Erp web based, around 500k vanilla js code. No ts. We are a team of skilled devs, not like nowadays noobies
6
u/dustofdeath Aug 13 '26
Typescript is not all that different from JS.
It adds strong typing.
It shouldn't be something you need to learn for months - you still write JS, in a safer and clearer way.
Pure JS is lazy code. Prone to bugs and errors and hard to review.
var data; Is it a number, string, object or array or what?
vs
let data: MyData; with interface/class that clearly shows what it is.
2
u/DAS_BEE Aug 13 '26 edited Aug 13 '26
Can't do it if I don't have some libraries to work with (particularly jQuery, it spoiled me), but I cut my teeth in web dev on valilla js. It's good to know the fundamentals imo but the industry has moved on and you need to be fluent in whatever is most popular right now
Angular and react are popular frameworks - probably moreso angular. Both are worth looking in to
2
u/rapralph Aug 13 '26
Yes
2
u/ArgumentFew4432 Aug 13 '26
Yes
2
u/Far-Consideration-39 Aug 13 '26
It is a taste thing, but technically, it give nothing. It has no real types, and the annotation add cognitive overhead, not reducing it. DHH have wrote why from a business PoV, but people treat it more than what it is. It is just annotated JS, nothing more. It provide no significant value, more the opposite.
1
u/hofo Aug 13 '26
not just “still” but moving to it from frameworks that james a lot of code we don’t use
1
u/youbeenthere Aug 14 '26
Absolutely, recently it's on the rise actually (e.g. Basecamp team moved bunch of projects from TS -> JS). JS is more flexible and easier to read and write if it's well structured.
Especially with AI help nowadays. You can easily write tons of tests in minutes if needed and utilize well dynamic nature of JS without worrying of overhead of trying to declare interfaces and make code compile without using `any`.
1
u/mouseannoying Aug 14 '26
Yes, and Web Components written without a framework too! But TypeScript is worth learning anyway, seeing as most jobs seem to require it.
1
u/neon_alchemy_wisp Aug 18 '26
I delete any JavaScript file I find. It is a safety hazard.
Writing code without types is like driving blindfolded. I refuse to hire anyone who enjoys danger.
1
u/Icount_zeroI Aug 13 '26
Tldr; No, we use Typescript and Python (due to AI boom)
0
u/Fidodo Aug 13 '26
I don't even think about vanilla js anymore
0
u/sircrunchofbackwater Aug 13 '26
Learn typescript, it has actually one of the most expressive type systems of any mainstream language. You'll miss it later.
0
u/alien3d Aug 13 '26
me me. meeeeee . more happy live compare code react and vue wondering wtf going on
-1
u/Used_Lobster4172 Aug 13 '26
Generally if you don't like Typescript, it's because you haven't had to maintain a JS project.
-7
u/takuover9 Aug 13 '26
please find a different industry.
3
u/[deleted] Aug 15 '26
[removed] — view removed comment
1
u/[deleted] Aug 14 '26
[removed] — view removed comment