Building using no frameworks, am I in the wrong?
So currently the platform im building has two parts. Both of which i have made strides with the first one being the reader for the graphic novel reader im building being the furthest ahead in development.
I have done so much research in frameworks, deciding between using React, Preact, Vue, Angular andBecuase i am planning on using a mobile device as one of the souces of viewing things, the overhead of all the clunk that comes with most of the frameworks bother me.
I am well aware they do thhings right and have a strong community but in my case, i have thought about using a framework for the editor i will be building as that will require alot more componetized content but the reader i am more comfortable building in vanilla JS and i manged to get to a good spot and used alot of ideas around functional programming to keep the code organized.
Note that I am not planning on changing the reader much after its build but the editor hense the reason for the framework there and maybe getting a helping hand but the reader for me s minimal, and i worry alot about performance, caching with service workers and making progressive experiance to the user from the ground up.
Question: everyone says using a framework is ideal but i feel becuase i am not using the though and info which i feel is biased is more of a distraction. Do any of you have a process to determaine at what point a framework is needed? or do you actually use a framework from the get go just in case?
(note that the application has two parts and i have no issue using any but i feel at peace using vanilla and it might be becuase i use react on a daily and i need a break from the overkill which is being used way to often even for the slightest thing in my opinion, and all because of social norm from what i can tell)
Frameworks can definitely get you going quicker if your problem fits into them, so they can be a cheap way to validate an idea.
One thing to keep in mind: if your needs diverge from the framework's in some way you could end up fighting it. Many big companies end up developing their own frameworks not necessarily out of ego but because depending on someone else for such an important component is a liability.
I suggest being liberal with the libraries you use, and prefer a library over a framework if you can, but be very thoughtful about the frameworks you use.
I like this idea, i am all for both and dont mind but at the moment i do value getting things out and from there deciding and hopfully not having too much extra to worry about if it comes that i need to rebuild a few parts. I try and avoid libraries as much as i can as i do intend production code to be using a FE framework that has a modular and component approach, this makes it easier for me to transpile code between if im not locked into using a framework while making things to validate
Frameworks are here to help you code faster as well as make some abstractions. Also, the community and packages behind them help you to move forward even faster.
I would not be able to create couple of side projects a month if I would do it in an e.g pure JS. But it all depends...
Using vanilla JS is more performant and your bundle size will be smaller. Main thing is that you are transpiling your JS bundle for browser compatibility.
For me If my app is JavaScript heavy to the extent of fetching from a REST api, doing transformations on that data, forms which need validation, etc... i will go for a framework because its just quicker ( productivity wise not performance wise) and my code will have less bloat. i.e no document.querySelector everywhere, just React components. For example, there's already a bunch of accepted ways to do state management, but with vanilla JS I can come up with anything I want which is fun but at the same time can be a massive time sync. If I need to do routing frameworks like React have good ways to do that.
If my app is extremely small, a single form, or is based off a dynamic html website and Im just enhancing it I will use vanilla JS, otherwise I will just use React. You are right that JS frameworks get used too often, but that doesn't mean they do not have their place. Yes its - imo- silly to use React for a blog, but what you are building sounds more like an Application that would actually benefit from a framework. At the end of the day its up to you, your users probably aren't going to care.
I think you should use what you're most comfortable with.
I'm working on a project right now with no frameworks and it feels easier to progress/learn. I've tried a few frameworks and it never felt right to me.
Frameworks tend to make development faster. So I always use a framework and set of libraries from the get go. Wait, how do you handle a database? I doubt you write to the file system and wrote your own locking mechanism
I get this, especially because this is one of the reasons why i wanted to use one for the editor i am building as that will be something that will require specific modular structure making it easier and quicker to develop alone or with others. Regarding the data base, well this is something i have not started yet as am still in the process of deciding what to use, I have used mainly a node stack for that but i was planning on thinking through and getting some info here once i get to that part regarding questing i come across as i research what might work out well for me.
Note: I have done planning around the structure of what i expect the payload for certain things to look like but that is as far as the database goes and i think because of speed and comfort, i might end up going down a route that uses a document-based data base (maybe mongodb?) but havent stuck to anything yet and this was more related to the FE and my head running in circles for no reason as always