News for hackers. Stuff that matters.
Re:Java record pattern matching in JDK 19 by Skinney on Saturday May 14, 2022 @03:50PM (#31381669)
> and voila, all dynamic languages suddenly started to convert into statically-typed

This is... just wrong.

Plenty of people are using JS without any sort of typing whatsoever. Other dynamic languages, like Clojure, Gradle, Elixir, Pharao (a smalltalk), just to mention a few, are still going strong.

> they have this webassembly, that runs in a schizophrenia-type VM wannabe

wasm is mostly being used as a target for C(++), Rust and even C# programs that want to run in the browser. It's there to expand the reach of the browser. Most JS projects don't touch the stuff.

Re:Java record pattern matching in JDK 19 by bigDinosaur on Saturday May 14, 2022 @10:15PM (#31384675)
Typescript is absolutely coming to dominate the field IME. Obviously I have no true idea about the relative use % everywhere but I haven't worked at a place in the last few years that wasn't at least trying to use it. There's enough legacy JS out there to provide work for people who hate static types for many years though.
Re:Java record pattern matching in JDK 19 by igouy on Sunday May 15, 2022 @12:59PM (#31388886)
Re:Java record pattern matching in JDK 19 by kaba0 on Sunday May 15, 2022 @02:31AM (#31385670)
Just a small correction, you likely meant to write s/Gradle/Groovy.
Re:Java record pattern matching in JDK 19 by jstimpfle on Saturday May 14, 2022 @04:00PM (#31381765)
> wasm is mostly being used as a target for C(++)

because... JS isn't good enough?

Re:Java record pattern matching in JDK 19 by samus on Sunday May 15, 2022 @03:04AM (#31385788)
Why should JS be used as a compilation target for C/C++?