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

How it feels to learn JavaScript in 2016

hackernoon.com

Post reply on HN
Print view View original

41–50 of 236 posts

Re: How it feels to learn JavaScript in 2016

#41

Post by forthefuture »

It's so interesting to me that so many people complain and no one does anything.

If Javascript is so bad just make any other JIT compiler run in browsers. Defeat the argument with action.

I'm comfortable with my build process. I have a package.json and a gulpfile.js. I run npm i, then gulp dev. For every new project this is automatic.

Don't follow trends if you don't want to, but I don't believe anything in the OP was difficult if you understand why you're doing it and learn it properly.

Re: How it feels to learn JavaScript in 2016

#42

Post by raverbashing »

marrs wrote: post #32
raverbashing wrote: post #26

Earlier quoted context omitted.

> We're professionals, after all, and TypeScript and React were not build by some teenage hackers. Overall correct > The reason is that we started to build complex applications instead of enhancing grandma's blog using jQuery.animate, get over it. And this is where we disagree Complexity is needed sometimes, needless complexity only brings the overall value down If I want to do a website using Django I need to get: D…

and that's how you can use express.js to run a service that uses a different protocol to HTTP. Express is one of the easiest libraries to learn in any programming language. It's certainly much easier to learn than Django, at least in part because it doesn't include the kitchen sink

> and that's how you can use express.js to run a service that uses a different protocol to HTTP.

Excuses, excuses. Good defaults are important. 99.99% of developers won't care about it.

Getting form data is Web development 101

Re: How it feels to learn JavaScript in 2016

#43

Post by grabcocque »

forthefuture wrote: post #41

It's so interesting to me that so many people complain and no one does anything. If Javascript is so bad just make any other JIT compiler run in browsers. Defeat the argument with action. I'm comfortable with my build process. I have a package.json and a gulpfile.js. I run npm i, then gulp dev. For every new project this is automatic. Don't follow trends if you don't want to, but I don't believe anything in the OP wa…

The proliferation of frameworks is people's attempts to do something about it. But then XKCD 927 applies.

Re: How it feels to learn JavaScript in 2016

#45

Post by Eire_Banshee »

forthefuture wrote: post #41

It's so interesting to me that so many people complain and no one does anything. If Javascript is so bad just make any other JIT compiler run in browsers. Defeat the argument with action. I'm comfortable with my build process. I have a package.json and a gulpfile.js. I run npm i, then gulp dev. For every new project this is automatic. Don't follow trends if you don't want to, but I don't believe anything in the OP wa…

We cant force browsers to support other front end languages. JS is the only reasonable choice for front end development, Dart didn't end up going anywhere.

Re: How it feels to learn JavaScript in 2016

#46

Post by kzisme »

grabcocque wrote: post #43
forthefuture wrote: post #41

It's so interesting to me that so many people complain and no one does anything. If Javascript is so bad just make any other JIT compiler run in browsers. Defeat the argument with action. I'm comfortable with my build process. I have a package.json and a gulpfile.js. I run npm i, then gulp dev. For every new project this is automatic. Don't follow trends if you don't want to, but I don't believe anything in the OP wa…

The proliferation of frameworks is people's attempts to do something about it. But then XKCD 927 applies.

Link for the lazy: https://xkcd.com/927/

Re: How it feels to learn JavaScript in 2016

#47

Post by forthefuture »

Eire_Banshee wrote: post #45
forthefuture wrote: post #41

It's so interesting to me that so many people complain and no one does anything. If Javascript is so bad just make any other JIT compiler run in browsers. Defeat the argument with action. I'm comfortable with my build process. I have a package.json and a gulpfile.js. I run npm i, then gulp dev. For every new project this is automatic. Don't follow trends if you don't want to, but I don't believe anything in the OP wa…

We cant force browsers to support other front end languages. JS is the only reasonable choice for front end development, Dart didn't end up going anywhere.

Why would you force anyone to do anything?

Just do it. You've got dozens of these threads full of competent software engineers and no one can put 10/100 people together and fix this?

I think it's easy to not want to learn something. It's hard to read this article and say "hey I want to learn all of that". But because it is hard it is valuable.

Re: How it feels to learn JavaScript in 2016

#48

Post by jbrauer »

TamDenholm wrote: post #6

I'm a web dev, been doing this 11 years. But i totally feel past it, granted i code less and less nowadays so i havent kept up with new technologies. I've hired people that are much better at web dev than me and let them accomplish a task with pretty much whatever tech they want to use, because i believe you shouldn't constrict a developer if you dont have to. Even for a simple app that it'd take me 20 - 30 hours for…

> I still feel like a bad coder because i'm not doing it their way. :(

I've only been at it for about 2-3 years, and I must say, I feel this exact same way. Started on the LAMP stack in school and now I know nothing because what I know is "uncool" and outdated since MEAN and all of the encompassing JS libraries have become popular.

I caved and started to dabble in MEAN (even though I haven't perfected LAMP by a long shot yet..) and must say it is the most fun I have had while coding and setting up projects ever, however I can't help but feel it is like you say, "a frigging nightmare to maintain and deploy". Nothing seems intuitive...

Re: How it feels to learn JavaScript in 2016

#49

Post by oolongCat »

In my experience the whole complex JavaScript comes when you try to build the entire thing using JavaScript.

If you are developing a web app, restrict JS to the client side only, get something like react to do it.

On the server side I stick with Go(lang). This separation helps me and my team think of these two separate problems, well.. separately. Isomorphic this isomorphic that is when things start to go all in sane.

tldr; JS for front-end. Go for back-end.

Re: How it feels to learn JavaScript in 2016

#50

Post by vcarl »

throwmenow_0139 wrote: post #20

It's easy to show how complex those systems are. It's easy because they are complex. And that's pretty normal. Let someone talk about Java Enterprise development, the symptoms of your body and their diagnoses or just try to explain how to build a pencil ( https://en.wikisource.org/wiki/I,_Pencil ). We're professionals, after all, and TypeScript and React were not build by some teenage hackers. I think the problem is…

> We're professionals, after all, and TypeScript and React were not build by some teenage hackers.

On the other hand, Babel was :) He did a great writeup of his life during babel's explosion of popularity.

https://medium.com/@sebmck/2015-in-review-51ac7035e272#.nmef...

Post reply on HN