Hacker Newsnew | past | comments | ask | show | jobs | submit | yellowviking's commentslogin

I'm inclined to think there might undiscovered evolution advantage that we still have two kidneys today. (Most of our parts have two for good reasons)


It's... not undiscovered, they screen you for kidney stuff before they let you donate because there's a negative health impact on kidney function from only having one.


As much as I love rust. Its just shocking to learn these newer languages like go didn't take any learnings from jvm and dotnet world for something simple as dep/package management


JavaEE has been using similar pattern for decades, somehow nodejs developers it's world changing and every startup on the planet is onboard with its ecosystem.


Why would you shoehorn practices from Java on Nodejs? A lot of those patterns would be unnecessary on JS.

At the end of the day, those patterns were created to keep things maintainable, not just use them for the sake of it.


Rust, FTW


Frontpage. Anyone?


Sounds all interesting work. Like above is saying. Please your comp range to save for everyone


Excel online at last back in 2015 was writing in script#. Not only c# IDE support was just miles ahead (that's per vscode, typescript days), the biggest thing was the ability to author unit tests that leverage lots of work from at the time dedicated testing organization. (Who wrote unit tests in js 10yrs ago, anyone? )


:raises-hand: - I was certainly writing unit tests in JS in 2012. Jasmine came out in 2010 and was already widely adopted.

Also, Jasmine wasn't the first test runner by a long shot (John Resig wrote one for jQuery before Jasmine was a thing and there were earlier ones too).


I think rust should also forge the path where Java 21 takes (Virtual Threads) https://docs.oracle.com/en/java/javase/21/core/virtual-threa...


Not sure if trolling but, Rust had green threads before Rust 1.0. Like everyone sane before them they figured N:M scheduling is not the way forward and they ripped it out before going stable. That decision impressed me a lot and made me look into the language, I'm loving the journey so far.


If they are trolling then Erlang is also trolling with its legendary scheduler.


> Like everyone sane before them they figured N:M scheduling is not the way forward and they ripped it out before going stable.

Why do you think Java recently went from N:M scheduling? Surely there's something to it?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: