

When branches don’t check out… that’s a problem.


When branches don’t check out… that’s a problem.
Maybe we should spell it: D-A-Y-O-F-W-I-N-D ?
The competition doesn’t need to be open, they just need to motivate Google to be open.
…but could that actually happen? I’m not sure what WOULD motivate Google to be open. Even if there were three or four more major mobile players (all with equal market share), and Google had the only platform that allowed unblessed software to be installed, I’m not sure that would pressure Google to continue to be “the open choice”, but more likely to take this same action as “the odd man out”.
At a fundamental level, there is an illusion/concept planted in the human mind that “force answers everything”, and when they run out of ideas (or all the ideas that they have would require too much [re]work to their liking) the tendency is to fall back onto “just use force” as an easy “solution”.
If I had to guess, I would speculate that their motivation is a long-term play to squash the general perception that Android has more malware (and is therefor less secure) than iPhone. Just about every article I’ve seen to that effect includes (1) enable unknown sources, and (2) install this malware app; so they probably see the current hurdles as insufficient and intend to perma-ban dev accounts that they find signing malware apps.
Nope. Here’s a hint: https://www.cgaa.org/article/scam-insurance-phone-calls-and-emails-to-work-emails
Read it again, more carefully… :)


Nah, just sort by date instead of topology, or vice versa.
git gud, son
This must be a hidden menu item!
To the tune of “pants on the ground”?
I wonder if this ordeal has made people stop buying (or maybe, start panic-buying) Tylenol.


Well, I do have MBSE on the brain, but the idea here is more like a low-code/no-code environment with an ABSOLUTELY ENORMOUS “pit of success”… so large that even GenAI can reliably fall into it. Numbered tabs, you go left to right answering questions and fiddling with with prompts, paint-by-numbers for working software.


I imagine that it is theoretically possible to successfully vibe-code, but probably not with a conventional project layout nor would it look much like traditional programming. Something like your interaction primarily being a “requirements list”, which gets translated into interfaces and heavy requirements tests against those interfaces, and each implementation file being disposable (regenerated) & super-self-contained, and only being able to “save” (or commit) implementations that pass the tests.
…and if you are building a webapp, it would not be able to touch the API layer except through operational transforms (which trigger new [major] version numbers]. Sorta like MCP.
Said another way, if we could make it more like a “ratchet” incrementing, and less like an out-of-control aircraft… then maybe?!?
So even if it does not move, this pawn could get promoted by some future tile-slide… come to think of it, I guess two pawns could get promoted in the same turn via a tile-slide.
So now that the black pawn has reached “the last rank”, does it get promoted?
That stick is a fine line between order and chaos.
I would say simply to avoid buying phones from ad-companies, but more generally… if you buy hardware from vendors that respect ownership (i.e. that have user-unlockable bootloaders) then you don’t really have to worry about this kind of thing, as even if the company turns evil later, you can probably flash the phone with a 3rd party rom.
This feels like an ad.