I currently have hopes / am watching Apostrophy who are building on top of Graphene but at least they acknowledge that people need Google Play and are attempting to support that while not sacrificing the entire device to privacy issues. https://www.apostrophy.ch
Only Android needs Google Play. The thrust of this post is that there's a third alternative which is neither iOS nor Android - and that's a killer feature.
Now it's up to capricious EU leadership whether to support a sovereign OS, including mandating that banks and other institutions open up their requirements to use solely US-controlled devices.
Ah FireShip, I forgot that channel existed at all. I asked YouTube to not recommend that channel after every vaguely AI-related news was "BIG NEWS!!!", the videos were also thin on actual content, and there were repeated factual errors over multiple videos too. At that point, the only thing it's good for is to make yourself (falsely) feel like you're keeping up.
Hey if you enjoy it, go for it. I used to like it a couple of years ago too, but I found that more and more lately, it was neither entertaining nor reliably informative. The jokes/memes were lazy and recycled a lot, the tech content was often poorly researched, and it started feeling like content produced for the sake of having content.
It is interesting to watch them try to grow so quickly. At some point they'll need to turn more profit to hold all this scale up. We'll see if they can stick to the privacy claims or start to sell out.
Unless your project is small and for learning, or won't be around for very long, Yes. You absolutely do or will end up in a technical debt world of hurt. I have worked on systems without them that are 15+ years old and the vast, vast majority of fixes and refactoring were self inflicted wounds like this. We added FK's and indexes where necessary and wound up faster and safer.
That sounds awful. My first instinct would be to see where an FK constraint would fail, and then ask the business what it should be. There is no guarantee that every business case from way back needed an FK, or that anyone in the business knows which FK value should be there. It sounds absolutely miserable.
In my experince, adding proper constraints will not only ensure code can never write invalid data to disk, it will also help you realize when business rules are lacking or failed to consider edge cases.
My pain threshold was crossed this past week when Edge added a Bing search bar to the middle of the Windows desktop. Even though the default search bar 4 inches away already searches Bing, and the Weather applet by the clock now has sensationalist news forced into it.