News for hackers. Stuff that matters.
Re:Ask HN: Why is everything in JavaScript changing so fast? by bloomca on Friday October 21, 2016 @10:22AM (#12760659)
The problem is that everything in JS exploded during just few years (Node was published in 2009), and it took few years to build tooling around Node to start utilising all this power.

And then everyone started to build "rich" web applications (it is called differently every year), with the "best" tool existing. I personally see two major problems – usually cool startups who can afford using the bleeding edge will die soon (or will get enough money to completely rewrite it), so 'maintanence' in idiomatic way doesn't work here – life cycle is extremely small, and it reflects in the way libraries are written in JavaScript. Also, the barrier is low, and therefore we have a lot of complex websites built by novices, running in development mode in the actual production.

Community also is very "poisoned" with the idea that you _have_ to work in your evenings (contributing to OSS, writing your own or just playing with hot technologies), and therefore new stuff is baked extremely quickly. It is usually very low quality, and you have to cope a lot in order to make it work, and often you have to dive into source code, and it is considered as normal, which is quite sick from my point of view.

Also, it is truly "hype" community, which is super excited about what is hot now – and it means that today kings will be overthrown very soon (right now stuff like Cycle.js and Vue.js is gaining traction). Nobody wants to maintain their libraries – and very often you can see projects with a lot of stars completely abandoned.

Recently, Babel.js was defined as _defacto_ standard, and it basically started transpiling era, which is not going to end in the foreseeable future. It shakes the stability, and makes extremely easy to add new features (like stage-0), and people just used to unrealiable tools.

So, all of this works as a snowball, which only speeds up. People create more and more complex web applications, and also js is going into other fields (like microcontrollers, Node.js grows in popularity, React Native is super hot now). When it will stop? Nobody knows. Maybe WebAssembly after implementing will stop it (people will spread over competing technologies), maybe no.

Re:Ask HN: Why is everything in JavaScript changing so fast? by nobleach on Friday October 21, 2016 @12:09PM (#12761591)
Having been a programmer for the past 18 years, I can say that JavaScript definitely suffers from "rock star" syndrome. There are great people in every programming community... and JavaScript is no exception. But never have I seen a community so plagued by the conference speaker, twitter famous types. (The types that refer to people not in their perceived realm of popularity as "filthy randos") It's incredibly toxic. I want to scream, "we're all geeks, just like you. You are not really a rock-star!!! No one outside of this niche community even cares what you think about anything at all!!!" Today's novice programmers have potential to be tomorrow's great inventors. That's why I can extend an amazing amount of empathy for sloppy code, bad architecture, etc. The poison that you speak of has the image of the SV archetypical, studio dwelling, hip 22 year old. None of this is the fault of the language though... or OSS. I think you're correct in mentioning "hype".
Re:Ask HN: Why is everything in JavaScript changing so fast? by erlich on Friday October 21, 2016 @12:41PM (#12761931)
Some ppl simply are rock stars. They are better than everyone else at the whole open-source lifecycle. They know how to do the marketing, manage scope, ship features, manage issues, etc.

To make a successful open-source project is not easy and is about balancing a range of factors, including balancing their work/life. Not everyone can do this, or wants to do this. I think rock stars earn their status.

Re:Ask HN: Why is everything in JavaScript changing so fast? by bloomca on Friday October 21, 2016 @12:49PM (#12762037)
Well, the thing is that in JS community there are tons of rock starts who basically do simple stuff (which was done 100 times before them), but only after their presentations it goes crazy. People retweet them, use as a credible source, etc. Also, there are a lot of people who are very opinionated and just push it and by this become famous in JS land.

Yeah, that's true, that they invest a lot of personal time in this stuff, and they do a very good job in balancing, but the problem is that people trust them in important questions like performance even despite the fact many of them don't know CS basics properly (like data structures, etc).

I don't want to say all of them are this way, there are some well-educated people who definitely know a lot and deserve all of this. But as it was mentioned earlier, a lot of them are just 22 years old hip guys who released something what became mainstream/were involved in it and became ambassadors.

Re:Ask HN: Why is everything in JavaScript changing so fast? by erlich on Friday October 21, 2016 @02:56PM (#12763462)
> people trust them in important questions like performance

I think this is part of the tradeoff that they excel at. There is a huge difference between perfecting and optimizing vs. shipping and growing an ecosystem.

Re:Ask HN: Why is everything in JavaScript changing so fast? by titzer on Friday October 21, 2016 @12:52PM (#12762087)
> I think rock stars earn their status.

I think that's mostly bunk. For every rockstar there's 100 equally talented individuals who will never get recognition because they were not in the right place at the right time.

Rockstars are incredibly lucky.

Re:Ask HN: Why is everything in JavaScript changing so fast? by erlich on Friday October 21, 2016 @03:00PM (#12763507)
And if Steve Jobs didn't build Apple, someone else would have.
Re:Ask HN: Why is everything in JavaScript changing so fast? by fsloth on Friday October 21, 2016 @01:10PM (#12762315)
As an outsider to the community, I see it as a pathology that there are people you are supposed to recognize outside of the language creator. Not that a culture is a bad thing but in a healthy technical community recognition should come from decades of hard work - not from a nice landing page and a framework of the week.

IMO, social media and blogosphere driven complex work cannot be deep, just confused.

Re:Ask HN: Why is everything in JavaScript changing so fast? by erlich on Friday October 21, 2016 @03:02PM (#12763521)
I think its democratic which is the best system we have.

Any kid with a new idea can have his ideas listened to. This means we don't get stuck.

Re:Ask HN: Why is everything in JavaScript changing so fast? by fsloth on Friday October 21, 2016 @06:16PM (#12765391)
Democracy is not about deep work, thorough understanding or the best architecture. It's about negotiating compromise in a situation where there is no shared goal. It works great for ruling countries where it's sluggishness and confusion is a feature and not a bug.

I would claim that any technical undertaking without understood goals using a process whose main design feature is not efficiency but sluggishness is a pathological one.

A computer system is far more simpler than any countrys political system - it's tractable and optimal solutions can be found. Unless, of course, unless the design process is lost in confusion and bafflement.

I would claim a place where any kid is listened to is precisely the one where everyone will get stuck. If people spend more time reading blogs rather than on CS basics they cannot understand a great ideas because they are on the Kruger-Dunning level of skill development.

Re:Ask HN: Why is everything in JavaScript changing so fast? by EpicEng on Friday October 21, 2016 @02:46PM (#12763371)
Yeah, I don't know about that. In my mind, the true rockstars are the people solving hard problems, e.g., kernel contributors, safety critical code, driverless vehicles, etc. I couldn't care less that you can quickly tape together 100 libraries and 7 frameworks to get the latest rendition of pets.com off the ground.
Re:Ask HN: Why is everything in JavaScript changing so fast? by Can_Not on Monday October 24, 2016 @09:51AM (#12778742)
Making people who are incapable of kernel work, drivers work, writing safe critical code, etc. capable of being safe, secure, and highly productive, if only by glueing hip new libraries, is a rockstar task.
Re:Ask HN: Why is everything in JavaScript changing so fast? by nix0n on Friday October 21, 2016 @01:12PM (#12762327)
> They know how to do the marketing

This is the only necessary component of stardom.

When something is actually good, it'll retain its popularity.

Re:Ask HN: Why is everything in JavaScript changing so fast? by agentultra on Friday October 21, 2016 @11:45AM (#12761360)
> Also, the barrier is low, and therefore we have a lot of complex websites built by novices, running in development mode in the actual production.

I'm not a huge fan of the "Javascript programmers are novices" myth. It's quite damaging.

Javascript is a kitchen-sink language these days in the ES6+ world. You've got the functional programming features... monads, functors, applicative and even immutable data structures are just a library. You have classes, interfaces, protocols and of course event-driven programming, prototypes, etc, etc, etc. It's not a small spec these days.

The point is that there are smart people who use the language to great effect. Enough with the "unwashed masses," story please.

Personally I'll take an ML or Lisp based language anyway... but thankfully I can have my cake and eat it too by compiling to Javascript.

Re:Ask HN: Why is everything in JavaScript changing so fast? by LeoNatan25 on Friday October 21, 2016 @11:52AM (#12761425)
Nothing here disproves the claim you try to disprove. "There are smart people" - that's a given, but how does that disprove that the barrier is low, and the vast majority of less-to-none experienced developers choose JS these days?
Re:Ask HN: Why is everything in JavaScript changing so fast? by agentultra on Friday October 21, 2016 @12:15PM (#12761631)
I was tackling the blanket assertion that Javascript developers are novice programmers. It's understood that there are programmers of all skill levels who use Javascript. However statements like the aforementioned are dangerous when people just assume it must be true.

There are novice programmers and many of them choose Javascript is more accurate. The aforementioned assertion is used as a pejorative by programmers from other languages who think, perhaps rightfully so, that Javascript is inferior to their language of choice. That doesn't make Javascript programmers as a whole inferior despite what such a blanket statement implies.

Re:Ask HN: Why is everything in JavaScript changing so fast? by fsloth on Friday October 21, 2016 @01:15PM (#12762377)
I think in general since the number of programmers grows, the majority must be novices, and the language growing most rapidly has relatively the largest amount of novices. I know it sounds like snobistry and not a statistical blanket statement, though.
Re:Ask HN: Why is everything in JavaScript changing so fast? by LeoNatan25 on Friday October 21, 2016 @02:39PM (#12763296)
"There are novice programmers and many of them choose Javascript is more accurate." - this is how I read the GP's comment.
Re:Ask HN: Why is everything in JavaScript changing so fast? by bloomca on Friday October 21, 2016 @12:53PM (#12762108)
My first "serious" programming language was JavaScript, and I didn't know a lot of basic stuff for a long time – because it is considered normal in JS community! Nowadays we have node.js, so you have to know at least a bit about your terminal, how to run server, kill processes and other everyday stuff, but back in the days it was unnecessary.

And this is not a single story; I've also interviewed some people and for some reason my experience is that JS has very low entry barrier.

Yes, with tail recursion we'll have almost full FP (only pattern matching is missing), but it doesn't mean that every novice will go and study them right after landing – in fact, the opposite, because there are much more tutorials about OOP JS.

Re:Ask HN: Why is everything in JavaScript changing so fast? by spiffyman on Friday October 21, 2016 @02:01PM (#12762913)
I'm uncomfortable with how willing I am (and others are) to just make/accept claims about how terrible the JS community is without evidence. In this thread there are tons of people saying JS devs don't understand CS fundamentals, write low quality code, and take their bearings from hype; that the "vast majority" of inexperienced people choose JS; etc. And I haven't seen any statistics on this or even a single example of such things.

I'm a Python guy who's working in Java at the moment. I don't particularly care for JS or frontend work, and I make no bones about it. But if someone were saying all this about the Python or Java communities, I'd be asking for evidence. And, frankly, I'd be pissed. So I think we should hold ourselves to similar standards -- don't just shit on a community because that's how you feel. Provide cases. And possibly even advice on how to improve!

Re:Ask HN: Why is everything in JavaScript changing so fast? by ourmandave on Friday October 21, 2016 @11:06AM (#12761022)
Soon we'll have trouble hiring Angular 1 devs to maintain legacy code, like COBOL.

Except COBOL started in 1959, not 2009.

Re:Ask HN: Why is everything in JavaScript changing so fast? by Roboprog on Friday October 21, 2016 @11:18AM (#12761114)
Angular 1.0, June 2012

https://github.com/angular/angular.js/releases?after=v1.0.4

...

And I actually prefer ng-1 to the transpiling mess that is ng-2, as well as preferring to use functional composition rather than pseudo-static classes for the controller logic.

https://github.com/roboprog/ang-prog-enh

Re:Ask HN: Why is everything in JavaScript changing so fast? by tscs37 on Friday October 21, 2016 @11:15AM (#12761091)
50 years later and we still haven't learned.
Re:Ask HN: Why is everything in JavaScript changing so fast? by rdeboo on Friday October 21, 2016 @11:47AM (#12761384)
It seems to me that many big companies are asking for Java + Angular skills these days; and that many new projects are build using that stack. This has the effect that it is still very worthwhile to learn Angular 1. I don't think it is going anywhere soon, plenty of companies are invested in it.
Re:Ask HN: Why is everything in JavaScript changing so fast? by marcosdumay on Friday October 21, 2016 @11:51AM (#12761415)
My hope is that with WebAssembly, it will stop mattering.

JS development will probably go on like if nothing changed, but people that don't like it will be able to opt-out.

Re:Ask HN: Why is everything in JavaScript changing so fast? by minitech on Friday October 21, 2016 @01:32PM (#12762577)
WebAssembly is a neater target format, but we can already compile to JavaScript today.
Re:Ask HN: Why is everything in JavaScript changing so fast? by marcosdumay on Friday October 21, 2016 @01:59PM (#12762896)
And several projects already are compiling to it. But it is not neat, what makes those projects less reliable and featurefull. Often enough for people to say "fuck it!" and go back to JS.

If WebAssembly takes too long, I can see JS compilers getting very good, but it's looming availability is discouraging that.

Re:Ask HN: Why is everything in JavaScript changing so fast? by minitech on Friday October 21, 2016 @02:43PM (#12763343)
> Often enough for people to say "fuck it!" and go back to JS.

Because having an extra compile step or language to learn is inconvenient no matter what you target.

> If WebAssembly takes too long, I can see JS compilers getting very good, but it's looming availability is discouraging that.

I haven’t seen any of this.

Re:Ask HN: Why is everything in JavaScript changing so fast? by cygned on Friday October 21, 2016 @10:49AM (#12760890)
As someone who's working in that environment every day I cannot agree more.
Re:Ask HN: Why is everything in JavaScript changing so fast? by stcredzero on Friday October 21, 2016 @01:37PM (#12762634)
often you have to dive into source code, and it is considered as normal, which is quite sick from my point of view.

For an environment that's as dynamic and open as Javascript, my POV is that one should be able to dive into library source code -- but that changes resulting from this should be an unusual circumstance, having to do with edge cases. If the normal situation is that you are always doing this, and it is always is flat-out basic debugging, then this is messed up.

The ability to dive into and debug everyone's source code should be considered a blessing. It's a great way to learn coding style and programming! It's one thing that was great about working in Smalltalk. However, the need to do so just to fix library bugs should be viewed as a symptom!

Re:Ask HN: Why is everything in JavaScript changing so fast? by planteen on Friday October 21, 2016 @02:05PM (#12762947)
Do you have more details on JS in microcontrollers? I'm curious about real-time systems, etc.

I found the Tessel (https://tessel.io/), but its hardly a microcontroller - its a MIPS SoC.

It looks like the Espurino is more of a traditional microcontroller. But the unit cost is high - $40!

Is anyone using JS on a microcontroller in a high volume product?

Re:Ask HN: Why is everything in JavaScript changing so fast? by raerpo on Saturday October 22, 2016 @06:49AM (#12768195)
I saw pretty interesting stuff with Johnny-five.

http://johnny-five.io/

Re:Ask HN: Why is everything in JavaScript changing so fast? by petra on Friday October 21, 2016 @03:02PM (#12763524)
Not sure it's low enough for volume project , but the closest today is espruino js on esp8266 ($2 wifi MCU) , or its brother , the esp32.