seandougall
Joined 16 years ago
Joined 16 years ago
(Edit: that’s assuming you’re asking about a derivative work, which I may have misunderstood)
Everyone's definition of "useful" is different. I personally run into far fewer last-mile issues with Metro Rail than I did with BART when I lived up north. Heck, BART had to run a bus service to OAK until just a few years ago, and they've had a lot more time to sort this out.
> They squandered a huge opportunity to do it right, to dig subways and put the rail on a grade-separated medium. Instead they opt for light-rail that shares the same surface roads as cars, thereby ensuring that the system is a failure.
No, they did dig subways where needed (and where geologically feasible). And they opted to use existing right-of-ways in other areas, so that the thing could actually get built. Look at the Gold Line going through South Pasadena; it cuts diagonally through a fairly dense, wealthy residential area, which it can do because the neighborhood was built up around tracks that were there long ago. Without that existing right-of-way, the whole line would have gone the way of the 710 connector.
(Side note: My kids' grandma is a retired software developer. So I guess maybe it's just that the average grandma is more sophisticated than we are?)
I mean, if Apple says airplane mode turns off the cell radio, that’s a falsifiable claim, so you don’t have to take it entirely on faith. It might be possible to hide it in the UI, but you can’t hide a radio signal.
(edit: and if you accept their four-degrees-of-game-of-telephone translation at face value, as sibling comment points out)
I think you may be referring to the promises of ABI stability? They kept promising that "soon" starting around Swift 3 (IIRC) and kicking the can down the road for a while there, but it is stable now on Apple's OSes. But I don't recall seeing promises of source stability back then; they were pretty open about the fact that the language was still evolving.