161–170 of 244 posts
Earlier quoted context omitted.
So JavaScript dom manipulations are pure? but one specific technique of dom manipulations are not?
It's not specifically the DOM modification but the way those frameworks are designed. With React you have hundreds of dependencies, which have hundreds of dependencies. You lost me right there.
I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…
I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…
Earlier quoted context omitted.
But that shows some kind of misunderstanding, because you can literally build single page applications in 50 lines of code and a JS include in an html file. None of this stuff is that much work. People are really overestimating how hard it is, and you realize it once you try it. It's just people aren't familiar. https://mithril.js.org/simple-application.html Here's another app in another framework. Hard to get easier…
No, no misunderstanding. I was being snarky and referring mostly to the laundry list of items that most FE devs have running or install just to start building a FE. To me that seems ridiculous and shows me that FE devs have either not paid attention to the bloatedness that is Enterprise style development or have and walked away with all the bad habits.
We have paid attention. We're doing the best we can. Until we get HTTP/2 everywhere, ES6 modules and we fix the tire fire that is global CSS... this is what we have to do to make it work.
Earlier quoted context omitted.
But that shows some kind of misunderstanding, because you can literally build single page applications in 50 lines of code and a JS include in an html file. None of this stuff is that much work. People are really overestimating how hard it is, and you realize it once you try it. It's just people aren't familiar. https://mithril.js.org/simple-application.html Here's another app in another framework. Hard to get easier…
No, no misunderstanding. I was being snarky and referring mostly to the laundry list of items that most FE devs have running or install just to start building a FE. To me that seems ridiculous and shows me that FE devs have either not paid attention to the bloatedness that is Enterprise style development or have and walked away with all the bad habits.
The web doesn’t look so bad now, does it?
Earlier quoted context omitted.
You're just assumming the library is 10x better. One reason to use web components would be it allows for a much more lightweight abstraction over DOM.
But when you need to polyfill an entire browser’s worth of functionality, at some point you need to ask if it’s worth the trouble.
You can still compare idea of React and idea of web components, ignoring everything else, and come to some conclusions.
I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…
If you want to learn Vue, here's a great 3 hour starter that doesn't use any fancy setup - just specifically about Vue: 1. https://www.youtube.com/watch?v=utJGnK9D_UQ 2. https://www.youtube.com/watch?v=ulHt78ad890 3. https://www.youtube.com/watch?v=ez0y_XKtEIc
But the last time I needed something a little complicated I ended up using VueJS. If you don't want to do it the "right" way (ie, a whole build system and such) you can just toss the file onto the page with a script tag and get to work with your scripting wherever you feel good about doing that.
Earlier quoted context omitted.
I'm coming from a similar background and mindset but over the past few months I've been doing a lot of prototyping and some production using Vue without the build tools. I just include vue.js and use x/template scripts for the templates. It's definitley saved me hundreds of hours already.
Does this mean you use regular js and not es6?
I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…
I'm pretty sure it will remove the dread.
[0] https://medium.com/the-node-js-collection/modern-javascript-...