hashmash

18 ms·

1.
by hashmash 2mo ago
Low pause collectors like ZGC and Shenandoah must be enabled explicitly. G1 is still the default. It should also be noted that the low pause Azul C4 collector was available in 2010, but it was a commercial product.
2.
by hashmash 9mo ago
Just say "tracing garbage collection" to avoid the usual referencing counting arguments.
3.
by hashmash 10mo ago
Because none of the existing software would work. The idea of running a Rosetta-like feature on an 8-bit CPU isn't feasible. The Apple II eventually received an upgraded processor, the 65816, which was compatible with the 6502.
4.
by hashmash 10mo ago
It wouldn't have happened because the 6809 wasn't binary compatible with the 6800.
5.
by hashmash 11mo ago
Yes, I'm familiar with these. Many of the earliest problems were to due bugs in the verifier, and there were several different vendors with their own set of bugs. The bulk of these problems were identified and resolved over 25 years ag
6.
by hashmash 11mo ago
The Java runtime isn't any more inherently insecure than the JavaScript runtime, and JavaScript seems to work just fine for the web. The key reason why applet security failed was because it gave you the entire JDK by default, and so ev
7.
by hashmash 11mo ago
The post is pretty much bullshit. Variable names have no impact on performance.
8.
by hashmash 11mo ago
This adds an extra level of friction that doesn't happen when the set of primitive types is small and simple. When everyone agrees what an int is, it can be freely passed around without having to perform special conversions and deal wi
9.
by hashmash 11mo ago
Sometimes I'd like to have unsigned types too, but supporting it would actually make things more complicated overall. The main problem is the interaction between signed and unsigned types. If you call a method which returns an unsigned
10.
by hashmash 11mo ago
The first official JIT became available in JDK 1.1, in 1997. The Symantec JIT was available as an add-on sometime in mid 1996, just a few months after JDK 1.0 was released. Even better performance was possible with GCJ, available in 1998. T
11.
by hashmash 11mo ago
If JEP 401 is ever delivered (Value Classes and Objects), then this sort of problem should go away.
12.
by hashmash 11mo ago
At the time the feature was added, there was no way to make a parameter to a function be lazily evaluated. Something like `assert(condition, "error: " + stuff)` would eagerly concatenate the string even when the condition is alway
13.
by hashmash 11mo ago
Directly or indirectly many (or most) projects ended up depending on something which was using an unsupported backdoor API because it provided a marginally useful capability. The module system restricted access to these APIs and everything
14.
by hashmash 11mo ago
What's the elevator pitch? If I'm already happy with the OO language I'm using today, why should I use Nod? What does it do better?
15.
by hashmash 1y ago
> The biggest current knock against Java I see is JNI, which unlike the core language is absolutely horrible. JNI was only ever designed to be good enough, and it is. The new FFM API aims to replace JNI in most cases, but it's desig
16.
by hashmash 1y ago
I guess it depends on what "just fine" means. What happens when a conversion is applied? Is there silent data corruption (C), or is there an exception (Ada, D) or perhaps a panic (Rust, Zig)? Is the behavior dependent on compiler
17.
by hashmash 1y ago
The problem with having unsigned integer types is that it introduces new type conversion issues. If you call a method that returns an unsigned int, how do you safely pass it to a method that accepts an int? Or vice versa? A smaller set of p
18.
by hashmash 1y ago
The main problem with the keyboard was the non-standard size of the kepcaps. The standard distance between keycaps is 0.75 inches, and the standard top width is 0.5 inches. The Atari ST keycap distance is standard, but the top width is 0.62
19.
by hashmash 2y ago
Were you only testing on x86 or any other "total store order" architecture? If so, removing the volatile modifier has less of an impact.
20.
by hashmash 2y ago
When using the `-XX:+PerfDisableSharedMem` workaround, VisualVM cannot attach to the running process anymore.
21.
by hashmash 2y ago
Why is an async model better than using OS threads for an I/O bound workload? The OS is doing async stuff internally and shielding the complexity with threads. With virtual threads this work has shifted to the JVM. Can the JVM do threa
22.
by hashmash 2y ago
The OS scheduler is still there (for the carrier threads), but now you've added on top of that FJ pool based scheduler overhead. Although virtual threads don't have the syscall overhead when they block, there's a new cost cau
23.
by hashmash 2y ago
But that same benefit was always available with platform threads -- a simple API. What is the real gain by using virtual threads? It's either going to be performance or memory utilization.
24.
by hashmash 2y ago
The problem with the naïve design is that even with virtual threads, you risk running out of (heap) memory if the threads ever block. Each task makes a bit of progress, allocates some objects, and then lets another one do the same thing. Wi
25.
by hashmash 2y ago
William Anders never walked on another world.
26.
by hashmash 2y ago
The CoCo 3 had a custom chip which provided an MMU and a few other features, but the maximum amount of memory it supported was 512KB. Page size was fixed at 8KB.
27.
by hashmash 2y ago
With Java, the default encoding when converting bytes to strings was originally platform independent, but now it's UTF-8. UTF-16 and latin-1 encodings are (still*) used internally by the String class, and the JVM uses a modified UTF-8
28.
by hashmash 2y ago
There's no hard guarantee that freeing an object runs in constant time. Reference counting tends to provide more predictable performance, but I don't think the phrase "hard guarantee" is appropriate.
29.
by hashmash 2y ago
PRQL has some very nice features, but the syntax also has some not so nice features that you don't see in the examples. There's special parsing rules for parenthesis and newlines, and a special word wrap character is needed at tim
30.
by hashmash 3y ago
PRQL is actually a first class functional programming language, with syntax for supporting readable query processing pipelines. The documentation for PQL is a bit light, so I don't know if it's as powerful as PRQL.

More ›