One killer feature for me is comptime. There's just not really any other language where these things are possible.

Also, actually I disliked how Odin handled allocator/context. It's more pragmatic, sure, but just seeing "this function takes no allocator, therefore it doesn't allocate" is so nice.

SSE has an associated data format: developer.mozilla.org/en-US/docs/W...

Not strictly necessary, but it is what makes the E in SSE. Without that it's really just Server Streaming. Which is fine, just not really that technology.

Gemini / OpenAPI have live APIs for immediate user interaction/audio.
SSE can be very fast, but what the LLM web pages usually do isn't real SSE, it's just very slowly streaming the text. Only a technical difference but yeah.

I mean that's only kind of sse, just a very slowly streamed document imo.
All the live APIs are WebSockets

Depending on what you're doing, Servo might reasonably build for Android 4.1, but it's not a complete browser.

As much as I have privacy and security questions about androids device discovery thing, it is one clean UX...
You turn on your device, and your phone just... Shows it? One-click setup and one-click play are just so nice

Yeah, issue is most server implementations are bad, it is horrible or not functional over HTTP 1.1, and in general isn't the cool thing, which matters a lot for web - the cool thing is optimized, and other features get left in the dust, of with little effort put into making them work well.

I'm a big fan of yyyy.mm.dd but I think then versioning API separately becomes important.
I'm also not against just doing build numbers, and it's just build #628 - depends on if the date has any meaningful value.

No, see image
Interesting to see that it seems to look pretty different on lots of devices?

Yeah, that's totally right. I don't see CRDTs as something an app developer should directly deal with, it's a component in a larger framework that enables the app developer to build things.
A weird comparison, but like URL parsing. A web dev doesn't have to understand how it works, just use it.

I'd strongly disagree.
You still have to implement replication, just don't deal with merges. But a stream of operation / states still has to be replicated.
Additionally CRDTs are commonly defined with a separate query layer that exposes the outside data structure.

Ah, didn't find that! Thanks, that does explain it I think.
I'm thinking this means that they get visibility into the entire TLD? Or just their specific government sites?

I think it's about the walled garden - having metal allows them to pull something like the ARM processors. Having their own Graphics API exclusively gets rid of any ugly competitors that wouldn't go along with it, and no alternative implementations either.

Replication of mutable state is the single most complicated thing to get right in distributed systems.
All sorts of distributed systems in datacenters, and lots benefit from CRDTs.
Really, a lot of existing tech is extremely similar to CRDTs, just not labeled as such.

To be fair, I did watch my dad play it growing up and spent countless hours working my way up to beating him. There's a small amount of nostalgia :D

Still, it's probably the best RTS. Ofc theres AoE etc, but that's a slightly different style of RTS. I never got into those.

Has there ever been a 3D & somewhat realistic adaptation of solarpunk? I love the concept but have mostly seen cute drawn things (not that I don't adore those)

Ignoring the Dubai bit - Welcoming the Armenian Government to Have I been Pwned? What does that mean? Is it about introducing what it is? Is there some kind of government level integration (planned?)

Is it just me or are the other points below also fucking insane?
If I save up to buy new shit, buy it on the credit card and pay it off the next month, that is still considered untrustworthy?

Classic case of "what they doin' over there?"

Still surprised git doesn't have something for this built-in, like git-bisect.
Repeatedly going back and forth doing the same changes is so time consuming on large repos