gitua

Yes that's a fair point agreed . If every platform were like that then Mozilla would never have even existed, but Chrome gaining even more market wouldn't be great either

> I as a developer want to get work done and I don't care about ideals like "standards".

The "I'm just doing my job" mentality often gets us in very bad situations down the road (be it for Privacy, Ecology, Standards, etc.)

Totally agree that for "getting the job done" and having free tools then yes CUDA is better.

For your REST example, I understand your frustration, but now think what would it be like without standards :

You would have to pay 100$ to use Apple.iHTTP©®™ + implement a version for Google G.HTTP + implement yet another version for Microsoft Visual.HTTP™. For each you would have to get a licence, agree to conditions, you would have to buy both a windows & mac because ofc they wouldn't be cross platform, each one would only work in one browser, they could decide over a night to remove your right to use HTTP, Microsoft Visual.HTTP dev tools would be crap but couldn't use the cool one from another company because not compatible, etc.

Might seems like an exaggeration but when you look at the Epic vs. Apple, Google AMP, DirectX & Metal, Apple developer fees & conditions, Web DRMs, the lack of cross-compability, etc. Well that's what HTTP would look like if people didn't care about standard.

Also standard don't have to always be backward compatible (for e.g OpenGL vs. Vulkan) that's specific to the web, not to standardisation.

It's true, but I think that's not the point. It's not because people don't care that it won't impact them.

Many people don't care about Privacy, Ecology, etc... yet it will have catastrophic consequences down the line.

Similarly here, yes it's true people don't care about the web engine, yet given Mozilla situation and Microsoft who switched to chromium, the web is seriously not in a good shape and it will have consequences on the long term.

> I think that Backslash against Nvidia is due to it's somewhat hostile nature towards OpenSource

I would add also Nvidia's hostility towards standards. They are pretty much the Apple of the GPUs : Optix, RTX, CUDA, etc. they are screwing up the whole ecosystem by making closed APIs that only work on their platform.

If you are a graphic or ML dev you can only hate Nvidia for how they are hurting standards and making our job so much harder while we could just agree on Khronos standards.

Hopefully some standards catch up (raytracing in Vulkan coming) but some other don't (ML is CUDA only)

One to one video/audio is fine and securely end-to-end encrypted with vanilla WebRTC.

But for group conversation this won't scale because with p2p (mesh network) WebRTC, each client has to encode and decode for all users (which might be too much processing to do for the client).

For that reason many group video conf apps use a centralized router when there are several people.

Privacy then becomes an issue, and all group video conf such as Zoom, Skype, etc. are basically unencrypted (not end-to-end) and they can see & log everything (your face, your voice, chat, files exchanged, etc.) because the centralised router routes non-encrypted streams.

Jitsi is going to be an exception by adding a layer of encryption using insertable streams (https://jitsi.org/blog/e2ee/).

So in summary I'd say :

- for 1-to-1 or a few more people go with normal p2p WebRTC.

- for multiple people session, host your own Jitsi server (or rent one from 8x8 or other providers) & use the jitsi SDK/API to integrate it in your app

It would simplify development quite a bit if this solution ends up being sufficient for battery life. No need to think about onCreate, onResume, onPause, onStop, onRestart , etc. like on Android.

But RAM might also be a problem if the phone keeps everything in background & isn't allowed to kill any app when it needs to

Interesting , thanks for your answer.

How can you listen to network events while being suspended ? I thought that on linux suspend = all user processes stopped. Does it somehow wake up every nth second to check if there a new message from the network ?

I think 5Ghz is the last concern given the primitive status of Linux phones which can barely make a phone call.

I'm really curious how Push Notification, App LifeCycle, Localisation Services, Background App/Services, etc. are going to be implemented on Linux phones.

Is each app going to be killed when not in foreground ? Or are they all going to keep running ?

Is there going to be special API for background download manager, notification listening, music playing, etc. or is each app going to keep running in background and do its own stuff like on Desktop ?

For Google & Apple things are super easy : they do what they want.

But For Linux Phones, people from KDE, Gnome, Wayland, Purism, etc. will have to agree on services & APIs which might take lots of time