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.
Apple is incentivized not to solve this because presently app creators can hijack these links to open in their own native code app, provided:
1. they have paid to join the apple developer program
2. they have validated ownership of their URL's domain with apple
3. they have submitted to all of the censorship requirements of the apple App Store (failure to do this one is what destroyed Tumblr and the Hong Kong anti-police protester app, you may recall)
4. they pay apple a cut of their sales
5. they buy mac workstations for all of their iOS mobile developers, to run xcode
Apple actually has a vested interest in apps supplanting the web, and has little incentive to improve web security features because Apple would prefer that new businesses simply use native iOS apps for everything (which sells more iPhones and locks both development investment as well as user eyeballs to their hardware).
The other-people's-apps-opening-your-site-in-their-custom-webview-and-adulterating-it problem doesn't go away if you onboard with Apple, build an app & register your domain for Universal Links. The custom webview is quite capable of blocking ULs.
The app would have to get much larger if they have to bundle most of a browser with it to avoid using the browser components on the phone. But sure, they could do that.
But to be in the app store an app has to comply with the rules. Google could decide to require compliance with that header. It's no loss to them, because the consequence would be that almost all Android users would use Chrome, and the tracking in the browser would still be controlled by Google.
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.
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.
Well, it's a little more complicated. The M1 MacBook Air now sells at $999; $899 for education. And you can drop more than $1000 on an iPad Pro with an M1 processor.
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.
