I used to query databases and create diagrams from the metadata, but text to diagram just makes little sense to me.

Java 1.8 is good enough for eternity, so they have to break it to keep getting a salary.

Just like Google/Apple have to break HTTP/1.1 to force adoption of their "obfuscated by complexity" protocols.

What needs to be fixed in Java is the Virtual Thread pinning, and that is probably the last usable feature they will ever be able to add.

They are also trying to deprecate AWT, for their non open-source JavaFX.

The only way to not remain a slave is to break free:

Compile your own Java!

Compile your own Linux!

Buy redundant hardware that does not break easily and is repairable.

Make your own devices if you can.

Make your own encryption.

The amount of times certificates have run out breaking things is astounding.

So I work around all certificate test the first thing I do when integrating with an external HTTPS site.

Good job people that get paid by HTTPS.

The performance of these binary protocols does not scale on most server implementations.

The protocol is not the bottleneck, the parallelism and memory latency is.

Multiply that by all the C(++) coders on the planet and we have lost a billion man hours...

5-bit base-32 oi23456789 abcdefghkl mnpqrstuvw y

o = 0 i = 1 j, x and z removed.

I like that you can fit 6 characters in an 32-bit integer and still have to bits to spare... makes for compact usernames and network bandwidth.

Go is just Java without the WM.

Rust is just a native compiler that creates slow programs and complains a lot.

If you consider respect and responsibility.

The browser is dead, the only thing you can use it for is filling out HTML forms and maybe some light inventory management.

The final app is C+Java where you put the right stuff where it is needed. Just like the browser used to be before Oracle did it's magic on the applet.

Browser developers are now reaching for straws to remain employable.

That said the biggest tasks remains:

- Go back to HTTP/1.1 with "One time password" auth.: https://datatracker.ietf.org/doc/html/rfc2289

- Simplify the browser so that it can be compiled in less than many hours on the latest CPU.

- Completely remove the tie-ins to any commercial/governmental entities.

Basically go back to Netscape with some improvements to javascript performance and hardware accelerated rendering of HTML.

Everything else invented in the last 20 years is meaningless. This is valid in most domains: Raspberry Pi is the only real exception.

Parallel means latency if you have non "embarrassingly parallelizable" tasks?

VR is being gatekept by Valve and Meta.

How likely is Valve to use Android?

Remember the first weeks of coding C? It took me 4 years to not get cold sweat just thinking about using it when the compiler didn't inform you about a typo and you have to rollback the code all the time to fix problems and learn assembly (in X86, ARM and now Risc-V).

And that was without deadlines or any delivery pressure.

Today I realize C is for mad people, but I learned to respect the thing while no longer being afraid to use it in a real scenario.

Also event-based protocols with deterministic physics.

Last but not least, you need to use a language that can atomically share memory between threads; C (with Arrays of 64 byte Structs) or Java.

I mean it wont solve your race conditions but it also wont crash.

And it will be VERY fast because parallelism without cache misses!

I wish there was a Java with C struct JNI access.

"While I'm on the topic of concurrency I should mention my far too brief chat with Doug Lea. He commented that multi-threaded Java these days far outperforms C, due to the memory management and a garbage collector. If I recall correctly he said "only 12 times faster than C means you haven't started optimizing"." - Martin Fowler

https://martinfowler.com/bliki/OOPSLA2005.html