Ada actually trades blows with C in Debian shootout game. It is the language of choice for automotive and aviation safety certification. You cannot get safer than that. and it doesn't have oddities of Rust.
Game streaming technology has been ready for a long time now. It is not the technology or leadership of companies that make game streaming; it is the game studios that block game streaming from becoming main-stream.
This is the first time I hear about Ada package manager. You can always download GNAT, an Ada fronted for GCC, and start coding in terminal and a text editor. You don't need package manager and all of the other stuff.
Apple could solve this problem in Webkit. But Android is more complicated. On Android, third-party browser engines are allowed. Google cannot prevent an app from shipping its own browser engine for in-app browsing experience.
As the tidbits article says, only the client is proprietary. I am sure that eventually a fully open-source Linux version of this is going to be developed and integrated into Seahorse.
rclone already provides such a client and it is fully open source. In general, to have a zero-trust system, you need to have client and server developed by independent parties.
If it is output of some other tool, then it is a build artifact and there is no need to check it in.
I have this argument with people all the time and the conclusion is always like: "it is too hard to integrate the generator with the build system so we check them in".
The big problem with generated files is merge conflicts. How do you resolve a merge conflict on generated files. especially if they are binary.
Apple is already in [casual] gaming, they have Apple Arcade and hundreds of high quality games on app store. They also have "console" called Apple TV. Evey Apple store sells Playstation controllers.
Apple still considers Macbooks as trucks: they are for developers and professionals, not gamers or everyday users. They want non-developers to buy iPad and that is why there is no sub-$1000 MacBook.
We had to put so much effort to just run things on Rosetta because all of our compiled code had AVX enabled. We also needed to chase down pre-compiled binaries and re-compile them without AVX, we still haven't finished this work.
This sounds like a hype that is going to die at some point. SQLite has its own uses in client devices and small webservers, but it is not built to scale to millions of transactions per second.
It is possible to build all kinds of cool things on top of SQLite, but most of these articles sound like it is going to replace PostgreSQL or MySQL.
I always use Ethernet at the office because Wi-Fi sucks when everyone is connected to it at the same time. Even though they use commercial grade routers.
At home switching to Wi-Fi 6 has solved some f dead zone problems. I notice a stark contrast between performance of Wi-Fi 5 and Wi-Fi 6 devices.
This kind of initiative could take off. Only if it is backed by a big player. Basically Apple Google and Microsoft.
WebAssembly is not a stand-alone application development package. It doesn’t have many of the functionalities of Flash, Applets, Silverlight or even NaCl. It has no API on its own to interact with display or keyboard and mouse. and none of the features you find in a VM such as multi threading or a memory allocator
The physical attack Microsoft worried about is hacker extracting information from a stolen laptop. It only takes a single laptop (out of thousands) to infiltrate the company network and steal source code or whatever.
For enterprise users, this attack vector is a real threat. Microsoft definitely wants to dog food this technology to their own employees to avoid getting hacked.
One of the main advantages would be hardware accelerated encode/decode, but because every manufacturer supports it differently most software refuses to use it. And once you go to software encoding, why not use a more efficient and open codec.
I cannot figure out if Bellard’s creations are hobby projects or serious production libraries.
This one has a couple of issues: browsers have already settled on AVIF. And HEVC is patent encumbered which makes it not a good choice for deploying on devices.
It is just the simple fact that the user land API of all current operating systems is C. A programming language need to support at least C ABI for this purpose.