Ohh we had a similar experience with Google Cloud. Added our organization and Domain into their Auth system and suddenly all users were migrated into a (invisible / transparent) workspace and could no longer use their calendar or google drive as the workspace had no free usage like you have on a normal free tier.
Apple was clear that they were offering the safety of a walled garden from the start.
Apple didn't lie about supporting a user's freedom to run anything they like, only to execute a rug pull after they successfully drove the other open options out of the marketplace.
> Apple didn't lie about supporting a user's freedom to run anything they like, only to execute a rug pull after they successfully drove the other open options out of the marketplace.
They did execute a rugpull, and they aren't offering safety anymore.
The rug pull is ads in the app store. If I go to the app store now and search for my bank's name, the first result is a different bank. If I search for 'anki', the first 3 results are spam ad-ware tracking-cookie trash.
If I search "password store" I get 4 results before the "password store" app.
I had a family member try to install one of the google-docs suite of apps, and the first result was some spamware that opened a full-screen ad, which on click resulted in a phishing site.
My family can't safely use the app store anymore because they click the first result, and the first result for most searches is now adware infested crap because of apple's "sponsored results".
What's the point of charging huge overhead on the hardware, and then an astounding 30% tax, and also a $100/year developer fee, if you then double-dip and screw over the users who want your app by selling user's clicks to the highest bidder?
Don't forget that Apple is spying on their users even more then Google does (which is gross in its own). Apple controls much more user data then Google does.
At the same time Apple keeps telling their users some fairy-tales about "privacy".
> Apple was clear that they were offering the safety of a walled garden from the start.
This is a red herring. Is Google a hypocrite for lying about it first? Sure. But suppose Android dies and gets replaced by something that never claimed to be open. Or gets replaced by nothing so there is only iOS. Is that fine then?
Of course not, because the problem is the lack of alternatives, and having your choice glued to an entire ecosystem full of other choices so that everything is all or nothing and the choices you would make the other way are coerced by them all being tied together into something with a network effect.
> If Google actually takes away the ability to run unsigned code, my next phone will be an iPhone. And I rarely even run unsigned code.
Same here. If I must be in a walled garden, then I will choose the better kept garden and it sure as hell isn't one of Google's crappy platforms.
The only reason to put up with the shittiness of Android is freedom. The same freedom they keep eroding with their constant, never ending attempts to force remote attestation and sideloading limits.
GrapheneOS is the last hope for Android as far as I'm concerned. Hopefully Google won't find ways to screw that up.
> it might finally result in me fully exiting the Google ecosystem
Don't wait for them to push you away. Start exiting now. Setting up mail on my own domain and distancing myself from gmail is one of the best things I've ever done. Highly recommended.
I've noticed with GrapheneOS, that more recent builds are exhibiting weird issues. This isn't their fault, it's upstream ASOP issues. For example, just in the last few weeks:
* The date has now gone missing from my lockscreen, only showing the time.
* I can no longer see signal strength on my phone for mobile, if wiki is off. I turn wifi on, and now I can. I use a larger font, but it used to be just fine.
There are all sorts of little changes like this I've noticed recently.
It makes me wonder if Google is slowly mangling default ASOP so projects like GrapheneOS will have a crappier daily build experience.
And GrapheneOS doesn't have time to manage features changes like this, they focus on their key security improvements and fixes. If Google is doing this on purpose, it has real potential to seriously degrade ASOP as usable without lots of fixes and changes.
They already rug-pulled security updates or whatever it was a few months back.
And it really seems like the sort of sneaky, underhanded way Google would handle things.
Odd, I don't have those issues (date is on the lock screen, network signal strength when wifi is off is there). Played around with font settings but that changed nothing. Up to date stable version of Graphene on an 8a. Are these beta versions? Or maybe it's phone dependent.
Do you have 'Receive security preview updates' on?
Google stopped publishing any info about security updates until (I think) quarterlies come out. GrapheneOS had to sign some sort of non-disclosure for them, in order to roll them into updates.
If you don't have that on, then you're not fully up to date with security updates. This could be the difference.
> GrapheneOS had to sign some sort of non-disclosure for them, in order to roll them into updates.
So doesn't this mean GrapheneOS is effectively controlled by Google now?
Also, how is keeping anything secret under NDA possible at all if you want to know what's in a security update and be actually able to build that update yourself from source?
Buy a cheap unlocked smartphone and run GrapheneOS[0]. I want my smartphone to be like my linux computers where I run them for as long as the hardware works and is still relevant. My iPhone 12 is getting close to its end of life support, yet it is still working well. We should expect better from trillion dollar companies. So I'm not supporting them with dollars wherever I can afford not to. That and I think it's more enjoyable to run something off the beaten path. I like to explore the space a little.
I swapped out my MBP for an Asus Pro Art running linux last year and that's been working out pretty well. Hopefully my cheap motorola phone will be supported by GrapheneOS soon and that will work out too.
GrapheneOS will support future Morotola phones that meet a subset of their requirements, rather than existing phones. Less likely to be budget lines for now.
The cheap Motorola phones won't support GrapheneOS because they are missing some of the security features that GrapheneOS requires. The Motorola partnership is for some new phones: hopefully at a lower price bracket, but likely to be flagships or 2nd tier.
Just to switch to an even more aggressively monitored and tightly controlled walled garden?
People sometimes act as if the one would be an viable alternative to the other. Even both are effectively the exact same shit for the exact same reasons.
Which increases the limit to whatever time is left on your current payment period. After which the app will stop working and need to be reinstalled by an authenticated developer who has a current Apple Developer Subscription.
EDIT: Edited the above which previously said 90 days incorrectly. Not sure where my brain pulled that from but I posted the correct details here prior: https://qht.co/item?id=45743615
Notably if you install a month before your subscription expires you need to reinstall the app in 1 month.
As a non python dev I really thought UV and TY are great tools and liked their approaches but I don't know how good it is that they are privately held... no a fan
Technically the tools are not privately held, they're OSS with a permissive licence. It's just that the bulk of work was done by them. The acquisition (ostensibly) changes none of that
Yea absolutely. I am using GPT 5.2 / 5.2 Codex with OpenCode and it just doesn't get what I am doing or looses context. Claude on the other side (via GitHub Copilot) has no problem and also discovers the repository on it's own in new sessions while I need to basically spoonfeed GPT. I also agree on the speed. Earlier today I tasked GPT 5.2 Codex with a small refactor of a task in our codebase with reasoning to high and it took 20 minutes to move around 20 files.
Also (at least in germany) their burger patties are nearly twice as expensive as groundbeef. I really like them but since I am neither vegan or vegetarian I either opted to groundbeef or to haloumi or something as a replacement. I think the substitutes could work well when they are reasonably priced or actually cheaper than what they want to replace so people are more likely to try it.
Same goes with soy milk. Alpro costs like 2.80€/L while common dairy milk is less than a euro per liter.
> Alpro costs like 2.80€/L while common dairy milk is less than a euro per liter
Sure if we are cherry picking the "premium" brand this comparison works. Store brand soy or oat milk are 0,95€[0] and 0,90€[1] per liter respectively, so about what cow milk costs. For milk and milk alternatives there hasn't been a financial differentiator between them for about 5 years now.
With meat replacement patties there is still a significant price difference, though there Beyond Meat is also one of the more expensive ones (which is bold, as they've also been lapped by the competition in taste and variety of products).
It's because the meat industry is a welfare queen. In my local supermarket last year I could buy pork for ~8 EUR by kg, but champignons costed 10 (Nordic country).
I now wonder if it'd be a good idea to move our end to end tests to a pretty slow vm instead of beefy 8 core 32gb ram machine and check which timeouts will be triggered because our app may have been unoptimized for slower environments...
For blocking presubmit checks, getting the fastest machine you can is probably reasonable. Otherwise, the advantage of the craptop approach is that it needs basically no infra work and gives an immediate impression of the site, and not CI, being slow.
If you’re willing to build some infra, there’s probably a lot more you can do—nightly slow-hardware runs come to mind immediately, browser devtools have a convincing builtin emulation of slow connections, a page displaying a graph of test runtime over time[1] isn’t hard to set up, etc.—but I don’t really have experience with that.
I kid you not a few jobs ago I found several race conditions in my code and tests by running them at the same time as a multi threaded openssl burn test. :)
a stranger i once talked to at the gym told me "every workout is better than the workout you are not doing" and that kinda changed my perspective on that topic.
reply