141–150 of 178 posts
Earlier quoted context omitted.
1. Ever thought about using class caches, AOT compilation e.g. OpenJ9, GraalVM,...? 2. Most of the time, a signal that the wrong algorithms and data structures are being used Amazon isn't rushing to rewrite their infrastrure from Java into Go.
Why would they rush? Customer will ultimately pay for infrastructure not Amazon.
Earlier quoted context omitted.
The usual Java bashing from Go folks, meanwhile Google keeps mostly using Java, Kotlin and C++, with only a couple of key projects using Go, like Kubernetes or Google downloader.
I work in cloud and every single one of our new projects is in go
Anecdotes.
Earlier quoted context omitted.
The usual Java bashing from Go folks, meanwhile Google keeps mostly using Java, Kotlin and C++, with only a couple of key projects using Go, like Kubernetes or Google downloader.
I was a witness to a decision on whether to migrate an old Java project to Go. A proof of concept (a Go rewrite of a core part of the engine) convincingly showed that the Go version would be somewhat more performant, would have vastly better startup time, and would have a smaller and simpler codebase, since the Java version's caches and latency-hiding complexity would not be needed. The decision made was to stick wit…
As someone building my startup [0] on Rust (and a fan of the language since ~2014) I don't think this is a very compelling list of points. > Rust is overhyped People are excited about Rust! Not sure why this is a reason you _shouldn't_ use the language. > Rust projects decay The text doesn't match the headline here; Rust takes backwards compatibility very seriously, and rust code I wrote in 2016 against Rust 1.10 sti…
"Rust makes you think about everything you're doing ... overhead for people who just want to move fast." Honestly, I find it much easier to move fast in Rust because for explorative code, I just bang out the code and used copy/clone liberally and once I have a skeleton it's usually a few iteration until rustc agrees to compile my code. Strong types makes it very easy for me to move fast. Doing this in C/C++ never wor…
As a Haskell fan this is very interesting! What sort of things do you write where you find Rust is a better fit? No code that I write in Haskell would be much better off without GC so I struggle to think of reasons Rust could be a better fit.
Earlier quoted context omitted.
I question this myself as bun.js is approaching golang speeds.
I highly doubt it's doing type checking though so you aren't going to be eliminating tsc from the picture even if you are using bun.js unless you want to just cross your fingers and hope for the best.
In what world is Go more reliable or faster than Java? Especially modern Java (or other good JVM languages like Kotlin). It compiles faster but that is about it. Which is a good thing too because it's verbose AF and heavily reliant on code generation even after generics shipped so that compiler lines/s actually matters. The only knock you can put on Java for reliability is null-safety but lets be real, nil pointers,…
I'm so sick of these half-arsed "features" that somehow get adopted into Java code bases.
Stop what you're doing and go write a unit test for @NotNull (or @NonNull). Watch the null value happily bypass those "checks".
Or, use (or write) a notNull() method (I happen to use commons-lang3) and watch it actually work.
Earlier quoted context omitted.
I work in cloud and every single one of our new projects is in go
Also work in cloud and we only do .NET, Java, and node, coupled with C++ when needed. Anecdotes.
In what world is Go more reliable or faster than Java? Especially modern Java (or other good JVM languages like Kotlin). It compiles faster but that is about it. Which is a good thing too because it's verbose AF and heavily reliant on code generation even after generics shipped so that compiler lines/s actually matters. The only knock you can put on Java for reliability is null-safety but lets be real, nil pointers,…
> these days with @NotNull and powerful editors like IDEA stopping you from doing dumb things I'm so sick of these half-arsed "features" that somehow get adopted into Java code bases. Stop what you're doing and go write a unit test for @NotNull (or @NonNull). Watch the null value happily bypass those "checks". Or, use (or write) a notNull() method (I happen to use commons-lang3) and watch it actually work.
I mean you can literally assign nil to a "func" type, and then call that func and it'll panic at runtime. Neither the compiler nor the JetBrains IDE will warn you about that, and there are no @Nonnull type annotations you can add (even if they're not ideal as you rightly point out).
That literally happened to me last week, just a stupid coding mistake, but took quite a while to find. In Java IntelliJ would have probably warned me about that, and certainly if I'd added @Nonnull annotations.
In what world is Go more reliable or faster than Java? Especially modern Java (or other good JVM languages like Kotlin). It compiles faster but that is about it. Which is a good thing too because it's verbose AF and heavily reliant on code generation even after generics shipped so that compiler lines/s actually matters. The only knock you can put on Java for reliability is null-safety but lets be real, nil pointers,…
That's going to need some justification. I work with Java and Go. I haven't worked with Virtual Threads yet but my understanding is Go's approach to goroutines and Java's approach to Virtual Threads are pretty much equivalent. (Channels, however, are quite different.) Let me know if I've missed something.