If I learned anything from all my past mistakes in life, it's this.

The screen is some different tech and not quite as responsive as an iPhone screen and does not do multitouch, but otherwise works fine.

I don't know why. Every review always praised the previous models for the physical buttons, and literally nobody asked for them. The physical buttons were perfect, yet they've taken them away.

There must be some grand anti-button conspiracy, it just doesn't make any sense.

Stochastic parrots can code yes, but that does not make them experts. Don't trust them with your life.

The TI-200 was much more accessible and fun, creating small little programs during or after class. Only once you wanted to go assembly did it become a chore again.

To summarize: not the same.

But to be fair I've also had many issues with Lightning. A few shorted out and became unusable and burnt on one side. And those were 100% original bought in the Apple store, as were the 5W chargers and iPhone this happened with.

Knockoffs were generally terrible and might stop working. A "genuine" cable bought from big retailer turned out to be a knockoff once after a software update, resulting in annoying popups from Apple. And some knockoffs were so bad they didn't stay in.

Even certified Mfi ones from Belkin somehow felt different, like the tolerances were slightly off. Those worked though.

Overall, I think it's had a good run and was underrated as a connector physically, but on the whole I like USB-C and it's more open ecosystem more.

What's totally insane is that the modern engine rewrite Aleph One can also play back such old recordings, for M2 Durandal (1995) and Infinity (1996) at least.

I'm actively avoiding Shorts, Reels, and whatever else with those mechanics precisely because they pull you in and snap an hour is gone with nothing of value to show for it. It's so totally different from regular long form videos.

We regulate addictive substances too, even for adults and without relying on parents. The amount of productivity and quality of life lost to these platforms must be staggering in aggregation.

Thats the problem right there. The company doesn't care. No amount of personal certifications is going to fix that.

It MUST be on the companies. They should be fined out of existence for such breaches and they would quickly change tune.

I think the reason I started doing it on the iPad is that the keyboard focus is sometimes inconsistent, so clicking or tab-tab-tab-enter is slower and less reliable vs. just touching the screen. Definitely feel the gorilla arm though.

I regularly back up my Photos library using rsync to prepare for the worst. From the files I see it looks like all the originals are there under /originals, albeit renamed to some UUID hash. However the EXIF data and contents seem to be intact. The number of files and their names are also stable. The database seems to be a basic sqlite DB.

I think it might make sense to extract the files directly that way, and try to see how the DB stores the original filenames. Might not be too hard. The edits though I think are applied "live" (at least for video) so it's probably impossible to get them out this way.

That one also wasn't a hardware limitation as it ran my displays just fine in bootcamp, but macOS would just produce fuzzy output all the way.

It's infuriating.

In TFA it's set to a measly 2MiB, yet tried to allocate 2TiB. Note that the PG default is double that, at 4MiB.

What the setting does is offload the responsibility of a "working" implementation onto you (or the DBA). If it were just using the 4MiB default as a hardcoded value, one could argue it's a bug and bikeshed forever on what a "good" value is. As there is no safe or good value, the approach would need to be reevaluated.

The core issue is that there is no overall memory management strategy in Postgres, just the implementation.

Which is fine for an initial version, just add a few settings for all the constants in the code and boom you have some knobs to turn. Unfortunately you can't set them correctly, it might still try to use an unbounded amount of memory.

While the documentation is very transparent about this, just from reading it you know they know it's a bad design or at least an unsolved design issue. It just describes the implementation accurately, yet offers nothing further in terms of actual useful guidance on what the value should be.

This is not a criticism of the docs btw, I love the technically accurate docs in Postgres. But it's not the only setting in Postgres which is basically just an exposed internal knob. Which I totally get as a software engineer.

However from a product point of view, internal knobs are rarely all that useful. At this point of maturity, Postgres should probably aim to do a bit better on this front.

Doesn't help that most tuners are still dog slow, none of the beginners courses properly tell you how the guitar actually works, or what a "chord" really is. They're all just "play this and don't worry about it". To be fair it does get you going.

I noticed the "memory" too and it's turned Gemini into a useless syncophant for me, but so subtle that I almost didn't spot it.

I loved those courses, great memories.

I see plenty of tourists with winter gear that is either insufficient, or completely over the top. Whereas if you buy locally you'd generally find the right stuff.