love the part about the dependencies, what a waste of time when trying to clean the home folder, and once you get an error it seems nothing can solve it but delete node_modules from your system (feels like dark ages). Svelte and Next are my top choices. You made some excellent points here.
First of all, I would like to say, "great video!" I respect your thoughts and options and hope that my comment doesn't seem too harsh in anyway. My opinion comes with a web dev background, as I'm an ex IBM employee. I have some agreements and disagreements with you. As a person who was crazy enough to code SPA's with both vanilla JavaScript and later Vue (both min js file and the one with the npm install), I can say that Vue has a way where it can be used without installing it with 10000000 npm dependencies. In the case of SPA, it can be optimized to not load everything at once... so then maybe one will think, "What's the point if not everything is loaded at once"? Good question for those who think it... the point is, for example, suppose that someone is using an SPA that teaches English and the SPA provides like 2500 lessons with audio, video, text, etc. In order to have this SPA work properly (even if everything wasn't in proper databases and storages, though assuming that the files would still be within the some directory related to the app), that kind of data for a specific source (view) can be pulled and rendered even with vanilla JavaScript. The major difference in this case for Vue would be that one can cut out a lot of steps for making the same thing happen. I'm not saying that in that situation, working things out in vanilla JS is wrong, but some people (and companies) have hard established the workflow of using such frameworks in order to have the thought of a "more unified codebase". Some may see this as an excuse to use a framework, and I do agree. However, in this world, it's hard to get someone to jump off something they are used to using. Before I was coding in Vue, I nearly almost coded in Vanilla JavaScript because when I was told to learn React and Angular, it just didn't sit right with me. The syntax at the time, didn't make me happy and yes I admit that React is truly a dependency hell. Sadly, nodeJS has became the same way, Even though I would had loved for it not to be like that. The main problem with nodeJS in my opinion is that nearly nobody truly knows nodeJS without using Express and then one is encouraged to learn mongoose to make schemas. What a mess. Is Dino a thing now? Who knows... I love JavaScript for what it is and when I'm not coding using Vue, I indeed can quickly code in vanilla JavaScript. Most of the time, it's even easier to get projects updated when a project don't have to rely on a framework or library to be a specific version and debugging is a lot easier o do when the bug didn't come from a dependency. Well, that's my option and I appreciate you giving me a chance to express myself. May God bless you.
Modern front end development has failed. The user experience is crap, the development experience is crap. I'm looking at getting out of development all together and doing something else because it's just so bad.
@@astroid-ws4py You're right, I used to work backend. It's much easier to work with and doesn't feel like some hack patched together with ducktape. Javascript frameworks seem to solve one problem but create 10 new ones.
Yeap. It's funny because I think a lot of us watched the old shows like Star Trek or Star Wars, or even played space-based video games, and thought "wouldn't it be cool if we could create apps that are like that"? But it hasn't happened. The frameworks out there are just lipstick on a pig, they create overhead, just to do the same thing you can do yourself.
If you can make that JS framework so that it can be installed in a single folder along with the website, then that would be incredibly. Currently, I think all frameworks give you two options: * use a CDN which means the provider could go belly-up or just decide to remove it * have to have some compiler installed elsehwere on the machine
@@atlantic_love it’s been a year since I wrote this. I finally am building my framework. It’s gonna be amazing. But it is not meant for websites but for data intensive business applications (think forms driven applications for the office).
@@paulholsters7932 Your reply has nothing to do with my reply. Also, spend more time programming and less time conjuring up "artist mission statements for programmers". I've no interest in listening to someone blabber on and on with buzzwords.
@@atlantic_love cool how you know how many hours i spent programming. What buzzwords did I use? Data intensive webapplications? It is a type of application moron, not a buzzword where performance and loadtime is less important than with a regalor website and users mainly do CRUD via forms and tables. Since performance and loadtime is not a dealbreaker it needs a different approach. Ok so you don’t care. Then why bother answering? I spent a lot of time thinking of such an approach since it is way more difficult then only having to care about speed and usability.
jquery is a bad thing ? you mean like what ? And isn't javascript just bad anyway ? I'm looking into PHP (yeah I know , It's a dinosaur right ?) and maybe Python (script kiddie ?) "just kidding" lol [ignore the lol] ha ha ha .
@@carriagereturned3974 I don't think so . That's like saying PHP or C is obsolete . You can still use JQuery . You can still use CGI . You can still use PERL , FORTRAN , ASM. Just because IT's not cool means nothing !
@@carriagereturned3974 The thing it works great for most people, unless you're looking for a job or working in an environment where all the other sheep are bleating framework buzzwords.
