I still use a 13 Pro Max for travel. Incredible longevity. The only downside is it requires a battery pack to last a full day but those are slim and compact now. I intend to replace the battery soon since it still has 2-3 years left as a backup.
It will probably keep most of its value too, if hardware price inflation continues.
The good news is Apple made a more practical dual-screen device than most previous attempts. The “big square” UI was awkward for both reading and video. Apple not only made it rectangular but kept it in the magic aspect ratio that’s able to be shared by single and dual screens.
I had written off dual screen when the square layouts were the norm, but I think Apple has struck a good balance here between screen size and price+chunkiness+serviceability. I won’t be holding my breath for an iPhone Trio. (Not to be confused with Palm Treo.)
As tech became more pervasive in the past couple of decades, it became commonplace for pundits to spout nonsense on the topic. Those takes should give anyone in tech pause about how everything else is reported.
“Only a minority of people think of reporting bugs and, if they do think of it, they often fail to do so either because they think it’s too time-consuming or that they might end up looking silly.”
Most people don’t directly use open source, and reporting bugs in closed systems is rarely rewarding.
With the issue trackers that are common in open source, a bug reporter gets to watch the bug report’s lifecycle.
They can see what the developer – and others – think about the bug report. Is it a real bug? Was it reported previously? Is it worth fixing? Does the report contain sufficient detail to reproduce it?
With enough time, the reporter will learn if the bug is fixed or discarded or ignored. At the outer loop, they can become better reporters of bugs by seeing this play out enough times.
In contrast, bug reports to a typical end-user application go into a black hole from the moment they’re submitted. Even if said bug is eventually fixed, the reporter will be none the wiser about whether their submission was even looked at, let alone triggering the fix.
> In contrast, bug reports to a typical end-user application go into a black hole from the moment they’re submitted.
True, but not always, I've heard PMs saying: "this was a user-submitted bug", meaning you better fix this ASAP.
But yes, for the most part they don't like it. I recall reporting a bug and then they obfuscated their SPA bundle.
Funny enough, today I spent like an hour thinking: should I report this, should I ever report bugs at all. It was a P0 but I didn't report it, and I noted it as my first time considering giving up on my career.
Last week I reported a list of medium-bugs and I ended with: "I'm not sure if you'll ever read this, so I'm not adding more details that could help you debug, but feel free to reach out…" They responded: "We will share this feedback with the appropriate team. No further action is required on your end. Your ticket 124443 is solved. Please rate us!"
> I've heard PMs saying: "this was a user-submitted bug", meaning you better fix this ASAP.
There are certainly developers with a practice of triaging and action user-submitted reports, but unfortunately it’s opaque to the one who reported it.
Visitor’s Sunday or owner’s Sunday? It seems to be the former as the stated purpose suggests a PSA function and less about reducing owner’s burden in maintaining uptime.
If that’s the case, you could consider using pre-render JavaScript to detect what day it is in the browser. Then temporarily redirect Sunday-identifying browsers to a “Closed On Sunday” page.
I can see how the title is misleading, but I would have been shocked if it was internal Meta jargon. Execs at all the big tech companies nowadays have a culture of avoiding slogans that could be deemed overly aggressive.
Even “Move fast and break things” was technocratted into “Move fast with stable infrastructure” after Meta went public.
Wayback shows #6 as "By 2010, more than 50 percent of books sold worldwide will be printed on demand at the point of sale in the form of library-quality paperbacks."
It was removed early 2011. Is this what happens when they can't decide on who won?
Edit: note that uptimecore is still not as nice, not so flexible, e.g. I need to add a time adjuster, and the favicon, and some other details like that.
It will probably keep most of its value too, if hardware price inflation continues.
reply