Isn't editable diagram to text more useful?

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

You probably know this already but I’ll leave it for posterity.

https://mermaid.js.org/syntax/entityRelationshipDiagram.html

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

Java 8 is an antiquated runtime that under performs in all categories against other modern runtimes.

> 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.

It is fixed. Go download the EA release.

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

FX is under the same license as OpenJDK (GPL) and available on Github.

>non open-source JavaFX

Is there a non open-source JavaFX? The only version of JavaFX I know of is GPLv2

https://github.com/openjdk/jfx

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

I don't know, there are quality of life improvement that I quite like in more recent versions.

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

JavaFX is GPL with a classpath exception, what are you talking about?

> Make your own encryption.

Why? That's generally considered bad advice.

This.

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.

Me too, HTTP/1.1 for life.

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.

When ever I watch someone coding C(++) all they do is compile and then add remove * and & or change between -> and . when the compiler complains.

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

Interesting, I did different choices:

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.

> The browser is dead,

Yea. Nah!

That obit is a bit premature

So you're telling me you write Java professionally?

Funnily enough, in a world with WASM, we might actually have Java in the backend and C in the frontend rather than vice versa as it would've been likelier in the 90s.

The irony of half world backed by VC money, trying to reinvent Erlang, Java and .NET application servers, while pretending to be innovative.

WASM is adding GC... recreating the wheel of the applet but without escaping the problem of javascript glue.

Go is just Java without the WM.

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

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

Good morning Troll

I'll give you "complains a lot."

Corrective upvote from me - the comment is too funny

You had me all the way up until the rust bit.

You can very simply do this with javascript.

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.

HBM is slower than DDR per pin, the speed gain is from a hugely parallel bus.

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

The smallest transfer done from memory is a single cache line, which on most desktop machines is 64 bytes, or 512 bits. You could imagine a memory bus that was 512 bits wide and transferred a cache line per clock, and this would improve latency when compared to a serial bus with higher clock speed. HBM doesn't do that, though, instead every HBM3 module has 16 individual 64-bit channels, with 8n prefetch (that is, when you send a single request to a single channel, it will respond with 512 bits over 8 cycles).

DDR5 has a 16n prefetch, so a single transfer from a 32-wide channel moves 64 bytes.

I think linux would be the obvious choice.

VR is being gatekept by Valve and Meta.

How likely is Valve to use Android?

> How likely is Valve to use Android?

Not likely, unless they make a headset which doesn't do much of anything by itself and is just meant for streaming from a PC. To make a standalone headset which can draw on the Steam catalog they would almost certainly want to use a variant of their SteamOS Linux distro.

Valve already has its own OS for a mobile device: Steam OS (based on Arch) on the Steam Deck. My bet is that they'd just modify that for a standalone headset.