I hate video links. The information could have been a few paragraphs of text that I could glance. Instead this much minutes of video that you can’t search, glance over, read while listening to something else… So it’s a pass for me.

this is not cancellation. This is Google taking a step back, and regroup to attack back.

First, persistency. You data lifecycle may not be directly proportional to your applications lifecycle. You may need it even after the app is shut down.

Second, RDBM systems provide a well defined memory/storage structure and API - “structured query language”. This enables you to easily query your data and acquire suitable views that are beneficial for your applications purposes.

Third, It’s always better to outsource your data layer to a battle tested, and trustworty database then trying to reinvent the wheel.

So this paves a road for you to focus on your business logic than splitting that focus for the data layer and business logic.

I suppose it’s “confusing perspective” worthy.

Then I hope it won’t get any traction.

I hope this is a joke and not intended to be real.

I have been with Firefox, since it’s inception. Never left it. And it never let me down.

Oh glorious BSG!

Done airlines give you outside views, but shoot with potatoes. So it’s better not having that. Also there is nothing to see at most of the cruise height.

I want to see the 10x hamsters!

I never used Chrome. happy user of Firefox since it’s conception.

Google is the maintainer and biggest contributor to chromium.
https://en.m.wikipedia.org/wiki/Chromium_(web_browser) and they’ve already introduced wei into chromium without any pushback.

https://kbin.social/m/degoogle@lemmy.ml/t/255346/Google-is-already-pushing-WEI-DRM-Webpage-into-Chromium

There are forks of chromium already like Vivaldi. You can still use them. Unfortunately using them is not a guarantee that Google can’t use their usage numbers as leverage while politicing or advertising bad behaviour to other parties like social media.

Worse yet, maintaining a fork is a huge undertaking for a project in the size of chromium. This means in time the fork may struggle to keep up. Or upstream may introduce functions that depends on the bad behaviours and the fork be forced to either adopt both, or adopt none.

And that’s the problem. It gives full control power to Google. That’s the reason that popularity needs to be broken.

Here it is. Another nail in the open web coffin.

It’s not the real issue. I introduced that while anonymizing the data. It’s that a 3-5 liner code became a huge switch case by just incrementing the code and never thinking how it should be done. This was caused by like 15 engineers in time :)

Something like below would be huge improvement:

subs1 = ["cluster1", "cluster2"]
if subs1.contains(clusterName) return subs1

Telegram seem to provide the least info, not signal.