Live data from Hacker News

What if JavaScript wins?

medium.com

81–88 of 88 posts

Re: What if JavaScript wins?

#81
post #17

For me, as a founder of a young startup, the overarching benefit of being proficient in modern JS and sorrounding tooling is that I can use the same language for my whole stack(servers, web, Android, iOS), and spend more time thinking about the product and business. In the possible future where the company grows enough where it needs a distributed server software, the only part of the product that'd be changing would…

Clojure plug: You can cover server, frontend & mobiles with Clojure as well - mobiles with the Re-Natal, leveraging React Native.

(This is also part of the "JS wins" story since two out of those three are ClojureScript, using JS as a compile target)

Re: What if JavaScript wins?

#82
post #19

I used to hate JS because the language is objectively badly designed, but then I realized that the merits of the language provide a glimpse of the future of programming. Most programming problems people have are highly generic, often looking to implement something completely off the shelf as far as problems go. Wheels can only be reinvented so many times in so many ways. To me the JS ecosystem offers a level of high…

Not to attack you personally, but it seems like you have never written software professionally. All the available packages you mention quickly become useless as soon as you have a use case that is not in the package's, often very short, README. More often than not, you need functionality which is at the intersection of what is provided by 2 or more packages with no easy means to make them work with one another nicely…

You did attack them personally.

The JS module ecosystem is far ahead of most other languages for web stuff. Most of the time the modules are perfectly sufficient, and if not, patching them is also easy.

Sure there's a lot of glue code required, but that is a reality in every language.

Re: What if JavaScript wins?

#84
post #53
post #12

Earlier quoted context omitted.

> manually reviewing WASM You should not write code in WASM. You should not review WASM. In the same way that most Java developers don't have a clue how bytecode works in the JVM.

But... Java developers should have a clue how bytecode works in the JVM. Otherwise I agree.

Honest question, why? Surely some would benefit, but the average java dev hacking on a spring app? Not so sure. Would love to hear your thoughts tho

Re: What if JavaScript wins?

#85
post #80

Earlier quoted context omitted.

> I hate imperatively constructing "types" through prototypal inheritance You hate objects... basically?

While objects are overrated, that's not what I'm talking about here. I didn't say "imperatively constructing objects of a type", I said "imperatively constructing types". This has likely changed since I last used javascript, but in the bad old days, if you wanted to specify a "type" (in the structural sense- a common set of fields that you might construct instances of), you build that type with statements rather than…

Likely you'd like the modern class syntax then.

You declaratively specific the "class" (it's just an Object under the hood, it's mostly sugar for prototypes) and then you could just to instanceOf to test if it's your "type".

I mean in JS basically everything is an object so if you're constructing a "type" you're constructing an object no matter what.

Re: What if JavaScript wins?

#86
post #53

Earlier quoted context omitted.

But... Java developers should have a clue how bytecode works in the JVM. Otherwise I agree.

Honest question, why? Surely some would benefit, but the average java dev hacking on a spring app? Not so sure. Would love to hear your thoughts tho

I agree totally that most will do fine without, but the parent comment cited the fact that few devs know about bytecode/jvm to support not knowing wasm. But descriptive statements don't imply prescriptive statements. So just because most have no clue, doesn't make it "right", or able to be used as justification.

I wouldn't call myself a Java dev - I mean I know Java like 99% percent of the world does - so I may have a terrible perspective on this anyways. Although knowing the basics of how Java source code -> running process would certainly help any Java dev.

Re: What if JavaScript wins?

#87

Earlier quoted context omitted.

I mean... he's not wrong.

But it's also got nice folks! :D

Absolutely! But there’s a reason a lot of professionals avoid here and call it The Orange Website in a derogatory fashion...

... and it’s not because it’s overfloeing with kindness & tact.

Re: What if JavaScript wins?

#88
post #13
post #7

Earlier quoted context omitted.

Given the popularity of Node.js, I doubt this. JavaScript is still winning when people have the option to use C# or C++ or Scala or whatever else.

The type of organizations I work on, node.js is only used as requirement for Web frontends. Which I anyway avoid thanks the bundlers in Java and .NET frameworks.

Unless you're disputing Node.js' popularity I'm not sure how your anecdote is relevant...
Post reply on HN