gf000

5 ms·

31.
by gf000 9d ago
Let's not pretend that EU data laws are not far more stringent and actually enforced than whatever the US has. Like sure, the government with a jury decision may acquire some person's data. But it's not getting sold to whiche
32.
by gf000 9d ago
Just for reference, Scala actually has proper null safety. You can turn it on with a compiler flag and then use union types to denote nullable types, like String | Null
33.
by gf000 9d ago
As mentioned: var x = someFunction() waitForSomeOtherFunction() That's semantically equivalent in the two languages.
34.
by gf000 9d ago
And the first two lines are an async function as they are, without any special handling. They won't block the thread, and you can have millions of them. Like it's no accident that c# with their goldfish attention span wanted to sh
35.
by gf000 9d ago
While typing this comment I pressed/swiped on several words to finish them. One reads much faster than they write, I don't really see a problem with easily guessable auto complete.
36.
by gf000 10d ago
Comparable components, but almost every line of Rust code expresses information about the lifetime of objects - either implicitly (quite often), or explicitly. Meanwhile in java it's a constant "Arc<JavaType>", and scop
37.
by gf000 10d ago
Well, would a dissected frontal lobe in and of itself be intelligence? I think the same goes for LLMs, they may be a core part of an LLM harness, but you may still need a couple other components (e.g. it may itself write itself a determinis
38.
by gf000 10d ago
That's the way of getting the address itself, that's unrelated to how fast the actual memory read/write is. Stack is fast because it is frequently "touched" staying in cache. If you were to continuously read write a
39.
by gf000 10d ago
If the two calls are sequential then simply: var x = someFunction() someOtherFunction() If you would have written var xTask = SomeFunctionAsync(); await WaitForSomeOtherFunctionAsync(); string x = await xTask; then it
40.
by gf000 10d ago
> And thousands of manual get/set functions don't? By definition, they don't. They are verbose and hard to maintain, but if ever in the future you would want to keep the same API surface but change the internal implementat
41.
by gf000 10d ago
> data races Which are completely safe in Java > Forgetting to release a resource I know what you mean and it's definitely a tongue in cheek reply but it's almost like that's what the GC is made for :D bit less sarcasti
42.
by gf000 10d ago
Java is a very small language, all things considered. Compare to kotlin, c#, rust it's absolutely tiny
43.
by gf000 10d ago
So you compare the build tool of A and B on a short-lived job type where java is knowingly not its strongest? How is that a meaningful comparison?
44.
by gf000 10d ago
> Structured Concurrency I think the two languages mean slightly different things here. In any case, Java's model is so much more simpler that I don't think they are honestly comparable. In kotlin's case you have to be ve
45.
by gf000 10d ago
I think parent was referring to this: https://www.baeldung.com/java-14-nullpointerexception
46.
by gf000 10d ago
It just swallows errors, so you don't even know about it!
47.
by gf000 10d ago
> is notoriously verbose. A 500KLOC codebase in Java would usually be half that size in Rust Lol, no way. Especially that rust is pretty verbose all things together (which makes sense, given it's a low level language - ergo you have
48.
by gf000 10d ago
> The stack is definitely faster than anything else I have seen it mentioned everywhere, but is this actually true? I mean, of course it is faster than random cold memory, but is it actually faster than a hot, in-cache part of the heap?
49.
by gf000 10d ago
Actually, javac itself is plenty fast, pretty similar to Go's (it also barely does any optimization) It's usually the build systems that add quite some overhead.
50.
by gf000 10d ago
At the same time, all this syntactic sugar makes the language's surface area gigantic . Like it's almost C++-level complex, and then you would have to properly understand all the interactions between this matrix of features. That
51.
by gf000 10d ago
It's pretty much the opposite. A fixed release schedule makes development more relaxed so it can be properly done, no need to rush for some release date. If it's not yet ready, there is 6 more months to get it merged.
52.
by gf000 10d ago
It's one end of the same problem. int is not an Object, so just erasing is no longer a valid approach, you need to specialize the class/method itself to use int-specific byte code.
53.
by gf000 14d ago
Also, probably due to some DRM bullshit, resuming a song from the middle doesn't work most of the time. I have to seek to the beginning for it to start playing. Like that's literally the only thing it should be able to do 100%..
54.
by gf000 16d ago
Thanks, that's a great example!
55.
by gf000 16d ago
As opposed to the western ones'?
56.
by gf000 16d ago
It's foldable. You can either fold it and use it with one thumb, or have a much larger screen depending on your actual needs at the moment. Like that's the very point of foldables, otherwise they would be a tablet..
57.
by gf000 17d ago
Sure, but then you can no longer actually construct your "objects". That's what my rust comment was referencing.
58.
by gf000 18d ago
Care to refute the actual numbers? No one was talking about the ethical part (which you may or may not agree with). Carbon footprint is an actually measurable quantity that we can compare - what's your problem?
59.
by gf000 18d ago
A bit of a hair-splitting, but isn't explicit construction the only way formal theorem provers can work? Of course you can still prove stuff with them, but certain axioms that more "human" proofs use may not be available, lik
60.
by gf000 18d ago
> All in all, my point is, if you are doing anything that actually utilizes the hardware near its limits you will be tuning by quite a bit. What do you think happens in case of literally any other platform/programming language when

More ›