2,389 karma · joined July 3, 2018
Wasn't Diablo IV the best selling game for Blizzard ever?
I wouldn't worry too much about post-quantum algorithms for any production code in the next couple of years (decades?) myself.
WSDL comes to mind
Honestly the same issue with versioning has been my primary issue with XML Schemas in the past. XSD 1.1 for example came out over a decade ago, but is still very badly supported in most tooling I tried out.
> When we are talking about a client program calling a server API with JSON/XML, why do we care about the format of data exchanged?
We shouldn't care much, beyond debuggability (can a developer easily see what's going on), (de)serialization speed, and bandwith use. JSON and protobuf tend to be a decent chunk smaller than XML, JSON is a bit easier to read, and Protobuf is faster to (de)serialize. This means they should generally be preferred.
In the case of a client program calling a server API I'd personally have the server do the required validation on a deserialized object, instead of doing so through a schema. This is generally easier to work on for all developers in my team, and gets around all the issues with tooling. The only real reason I use schemas is when I'm writing a file by hand, and want autocompletion and basic validations. In that case versioning and tooling issues are completely in my control.
While Vulkan has been slowly replacing OpenGL, it's also more complex than OpenGL is. This means that OpenGL is still great for many simple use-cases, as you won't be overwhelmed by the complexity that Vulkan can bring along with it.
It's currently still a stage 1 proposal, while we've been waiting for years for other proposals to be merged. The last time a proposal was actually finished was over 2 years ago.
https://github.com/WebAssembly/proposals
https://github.com/WebAssembly/proposals/blob/main/finished-...
Not having internet connectivity is never a problem for me, the entire region where I live is completely covered by 4G.
https://microsoft.github.io/TypeChat/blog/introducing-typech...
https://public.wmo.int/en/media/news/simultaneous-heatwaves-...
> Soon, we are planning to make Threads compatible with ActivityPub, the open social networking protocol established by the World Wide Web Consortium (W3C), the body responsible for the open standards that power the modern web. This would make Threads interoperable with other apps that also support the ActivityPub protocol, such as Mastodon and WordPress
> We’re committed to giving you more control over your audience on Threads – our plan is to work with ActivityPub to provide you the option to stop using Threads and transfer your content to another service
https://about.fb.com/news/2023/07/introducing-threads-new-ap...
https://discord.com/blog/server-activities-games-voice-watch...