Readit NewsDon't get me wrong. Number of C++ libraries is far bigger than number of rust libraries. But number of modern c++ libraries is still not that high i feel. So once you have integrated legacy code into your project, there's a lot of scope for newbies to create memory leaks/double free/etc ...
Ladybird is an outlier and there are probably a few more project like it, but anyone looking to be employed should pick up the new skill that is rust. Contribute to ladybird and learn c++ if the project interests you, but don't learn it for a career.
The advice about career is very geography and industry dependent. Almost no one hired Node.js developers in my city back when i started.
Samsung has been doing this for a while now.
Which are the devices/vendors that still allow / encourage this?
Even Graphene OS reported that they're in talks with some vendor... Have there been any updates towards that?
The main reason i used to root devices are:
* Get longer support/OS updates than what the vendor provided
* System level adblock using adaway
* Titanium backup
These days firefox/brave browser gets me half way through adblocking and i lost interest in the ad filled apps..
Syncing gets me good level of syncing for backup on my NAS etc .
And a little video on youtube that made me rediscover this nostalgia recently: https://www.youtube.com/watch?v=zHgcrdv8zpM
Are Linux desktop projects still run mostly by volunteers these days anymore?
The kernel itself is heavily funded by, contributed to by so many large companies. A lot of user space projects are all maintained by companies or maintainers who work for companies like Redhat, Canonical, Suse etc ...
Didn't Wayland itself get popular during Nokia/Intel Meego days? I remember there being automotive compositors, Jolla Phone all using wayland.
- Battery life. One of the main reasons your phone lasts as long as it does is because it severely restricts the ability to run always-on things. A phone of course can run an email server, but the battery life will immediately tank to the point where the device becomes largely unusable for its original purpose.
- Phones make extremely poor servers because connectivity is intermittent. This is fine for software that's 100% local, but a lot of the most useful software needs to talk to the internet - or more importantly, has to allow the internet to talk to it. Imagine losing an email because you walked into the subway and your phone was unreachable the moment an SMTP server tried to connect to it.
> Imagine losing an email because you walked into the subway and your phone was unreachable the moment an SMTP server tried to connect to it.
Dont SMTP servers already retry a few times before giving up? Plus it is not like you're using the phone to host content for the whole of the internet. It would be just for your close circle usually.
I am not saying phones make the perfect servers for all kind of applications but for certain kind of workflows... I think Phones are pretty good. Our network infrastructure (NAT, firewalls etc... limited data plans etc..) is the main headache for most of these use cases. But the network infrastructure is a problem even for our laptops, home computers etc..
Phones are amazingly powerful. Why not "self host" apps on phones?