Would you hire me if I would use only vanila javascript ?

If you are efficient, why not? But you won’t be, so no. But who am I to judge? I am just a fresher.

Depends on why I'm recruiting.. If it's the needs, sure

If you *could* only use vanilla JS and were willing to learn a framework if needed then sure, so long as I had the time to skill you up, and confidence you'd be able to handle it.

If you *would* only use vanilla JS and take a principled stand, flat out refusing to use any kind of framework then no. No-one needs that kind of egotism in their dev team.

Can you do X in less amount of time and cleaner for future changes than doing it in framework Y?

> yes (you’re hired)
> no (fuck off wannabe)

@AlmondSauce It is not about, me not want to learn. I know angular, react, nextjs all that jazz, I just know I don't want to do it because it is bloat and hard to debug. Most websites need only sprinkle of js, so I will be happy to do that in vanilla js. I hate the, you need to update your code style to react classes, nono now react hooks, oh actually... Fuck frameworks, Browser api is stable, I will build around that. Vanila with newest standard is all you need, if you want something complicated, use some library which makes it easier to do your task. Follow good parts from funcional programming to avoid spagetti, you are golden.

@danielstaleiny Sure, but very few projects are deciding what to use from the ground up. You'll likely be maintaining and extending existing code, and they may have already decided to use Vue, Angular, React, or whatever. Even if it *is* a new project, they may well have a bunch of (say) Vue experts on staff already, so want to use that.

It's fine to have opinions, everyone does. I have opinions on various frameworks we do and don't use at my current place of work - but I put those opinions aside and do what needs to be done for the team.

It is of course your right to say that you flat out refuse to touch any JS framework because of your own beliefs - and that's fine. But it's also an employer's right to refuse to hire you as a result, and I suspect you'll find it hard to find work as a result.

@AlmondSauce Sad part about what you said is choosing technology just because you ingested time in it. (vue experts) I only dislike framework as default. Framework have their place but I think we should reduce complexities not introducem by default.

Would accesability change your mind in terms of what technology you choose ?

I can’t imagine using vanilla JS to build any project without having some sort of boilerplate code to get started. And the bigger the requirements are, the more structure you’re going to need, hence you’re going to be putting together more boilerplate unless you like writing things from scratch every time. So if you’ve managed to write some decent boilerplate for yourself you’ve pretty much created your own little framework. And maybe you’ll get to the point where you’ll want to publish it one day 🤣
I’m just guessing what it would be like to want to only use vanilla. And can only imagine it would lead to trying reinvent the wheel when you’ve got solid tools available already.

@black-kite I agree that creating SPA in Vanila is stupid, but what if we don't need SPA and you just use vanila js with polifils and some small lib when you need it. Build complexities when needed, instead of starting with framework.

@danielstaleiny I'd be perfectly open to going vanilla if it was a sensible choice - I've got nothing against it whatsoever.

All I'm saying is that for many projects, that may not be a sensible choice for any number of reasons, and you're unlikely to get the job if you take a principled stand against working with anything other than vanilla.

@AlmondSauce Could you please list some of those reasons when vanila is not suitable ? I am genuinly curios what you think. I kinda want to understand why so many people think framework is the default nowadays. I get, you might say structure and speed, but for me it is not worth compare to small bundle size and not needing to update dependency every god damn day.

I once was the guy thinking SPA is the way, but after 6years in this industry bulding and mantaining projects I just feel urge to run away from this SPA nonesence. I still think there is place for SPA but most website ain't gona need it.

In the end it all depends on requirements, but I think there is little to no promotion of going the simple road aka vanila js.