Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Guide to JavaScript Frameworks

javascriptreport.com

Post reply on HN
Print view View original

121–130 of 244 posts

Re: Guide to JavaScript Frameworks

#121

Post by amerkhalid »

joaodlf wrote: post #44

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 backend programming experience with a little bit of jQuery and Bootstrap experience.

I run into similar experience when trying to learn new JavaScript frameworks. Documentation for these frameworks is usually written as if you already are expert in another JavaScript framework. And then it is really hard to understand benefits of tooling they have. I could do simple apps or tutorials but trying to use any of these technologies in a real project is such a hassle that I end up using good ole jQuery. Sometimes, i feel like these frameworks and their extra tools have no real purpose but to help one pad their resume.

Only reason I keep diving into these frameworks is because I worry that if i don’t learn new technologies, I ll be outdated soon.

Re: Guide to JavaScript Frameworks

#122

Post by ByteCastle »

joaodlf wrote: post #44

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…

My biggest struggle is knowing why a certain thing is done. I don't want to simply build on a layer of magic, I want to know why I am using a particular framework or library. But without much experience having done it prior, it is hard to evaluate why the current trends exist at all.

Re: Guide to JavaScript Frameworks

#123

Post by debaserab2 »

LeoNatan25 wrote: post #90
debaserab2 wrote: post #79

Earlier quoted context omitted.

What is pure HTML and when does it become impure?

When you build a browser insider a browser (aka React), it’s impure.

So JavaScript dom manipulations are pure? but one specific technique of dom manipulations are not?

Re: Guide to JavaScript Frameworks

#124

Post by sloxy »

yomly wrote: post #101
joaodlf wrote: post #44

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…

From what I see, we are moving away from a heavy server which does the heavy lifting to thin server layers that just send data and feature rich UIs that process the data. This is possibly because the browser has become a widespread means of distributing general software. As a result, the domain of "backend" engineering has bled into the frontend and thus frontend engineering has gotten more complex. If you purely wan…

your comment contains as much value as this comment.

Re: Guide to JavaScript Frameworks

#125

Post by hobofan »

dsego wrote: post #94
Kiro wrote: post #64

Earlier quoted context omitted.

I've used Vue for larger project and like it but the things you list are the drawbacks IMO: - Don't need to know jsx! But you need to learn Vue's template DSL. JSX is just HTML and JavaScript. - v-for looping is saner than reacts mapping - v-if allows v-if statements without renderIf component or multiple render statements in react (antipatterns boo!). Strongly disagree! - two way data binding with vue-model I sugges…

JSX is NOT just HTML and JavaScript! If it was just html I could write and not , I could write instead of . It's not even just javascript, or I would be able to write a simple if-else statement. JSX is a DSL, a minimal one, but still. I mean, you could say it's even worse, because those subtle differences can cost you hours of looking for mistakes.

> If it was just html I could write and not , I could write instead of

In case you don't know (and I also didn't until recently), those namings come from the HTML DOM Javascript API, and not from React. So having that naming in React+JSX is more a consequence of operating on that abstraction level, than a quirky decision of the React developers.

Re: Guide to JavaScript Frameworks

#126

Post by orangecat »

Kiro wrote: post #64
_fol8 wrote: post #7

Reasons why Vue will rock your socks off - Don't need to know jsx! - Sane way of scripting puts the script in an object and each component is html javascript css - Event buses allow sharing of variables between child components without either redux or pushing variables down one child at a time (finally!) - v-for looping is saner than reacts mapping - v-if allows v-if statements without renderIf component or multiple…

I've used Vue for larger project and like it but the things you list are the drawbacks IMO: - Don't need to know jsx! But you need to learn Vue's template DSL. JSX is just HTML and JavaScript. - v-for looping is saner than reacts mapping - v-if allows v-if statements without renderIf component or multiple render statements in react (antipatterns boo!). Strongly disagree! - two way data binding with vue-model I sugges…

I suggest anyone thinking of using two-way binding for anything to rethink their choice.

v-model isn't two-way binding in the AngularJS sense; it's just a shortcut for binding a "value" property and updating it on "change" events. See https://vuejs.org/v2/guide/forms.html.

Re: Guide to JavaScript Frameworks

#127

Post by expertentipp »

megous wrote: post #116
boubiyeah wrote: post #112

Earlier quoted context omitted.

I don't know... not all web standards worked well in the past: xhtml, appcache, etc. I wouldn't be surprised if web components never got success. Why should anyone use this standard when a library is 10 times better? Being the standard is not enough.

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.

(HTML) DOM is performant, snappy, and cross browser compatible as never before. One of the reasons why jQuery is becoming irrelevant is that DOM finally works.

Re: Guide to JavaScript Frameworks

#128

Post by perpetualcrayon »

joaodlf wrote: post #44

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 think about it like this:

The number of projects is simply a sign of how popular the language / platform is (is becoming).

When you start to understand / recognize the different "types" of projects you'll see they all (generally speaking) fall into probably less than 10 total categories of projects.

Your goal is not to understand all of them well, but to understand them well enough to know which ones fit their use cases the best. When I think of these things in this way I can generally dismiss ~90% of the projects after I've read a handful of pages of their documentation to know whether they're on the right track or not.

Then, for the ones I've dismissed, if I start seeing those projects pop up more and more on forums like HN I might reassess, but other than that once you get over the steep edge of the learning curve it's no longer intimidating to see so many projects popping up in the ecosystem.

EDIT: Or just get your skills to a point where you're confident enough that you understand the fundamentals well enough that you can fit into any project no matter what front-end libraries / frameworks they're using.

Re: Guide to JavaScript Frameworks

#129

Post by codingdave »

joaodlf wrote: post #44

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 came from the same background, and got hired onto a team that uses a modern stack, and it really wasn't that painful to pick up. A few weeks of working day-to-day in such a codebase, and you'll get it. You might not like it, you might prefer the old school ways of coding, but feeling sorry for devs who move to such platforms isn't necessary. We're doing fine.

Re: Guide to JavaScript Frameworks

#130

Post by avip »

celim307 wrote: post #84
joaodlf wrote: post #44

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…

That's how I feel configuring networking and load balancers and other backend stuff. I know its essential but for some reason front end and all its quirks makes more sense to me

It makes little sense to us as well, that's why we've invented the term "DevOps", and offloaded the real work to those (mostly bearded) dudes.
Post reply on HN