wistlo

Yes. "We all" add it. Every time.

/s

Many years ago, I standardized on Journal in Microsoft Outlook.

Well guess what. Microsoft created Notes and Journal bceame a "legacy app." It was not possible to migrate. The deprecation of the .PST file in Exchange Server left me no way to transfer when I lease-rolled to a new laptop.

Enter Notes. As in, "notes.txt", which is exactly the same idea as todo.txt described here. Works. If this text file ever becomes machine unreadable, file compatibility will be the least of our worries.

This is so much better than reading the news.

Favorited—I'll be coming back to absorb more, as my aging semi-fluency in engineering physics and SQL doesn't help much with the notation I last saw in the 1980s.

When I click the link for this story, Edge (stop laughing. Please.) pops up "uBlock Origin works on Microsoft Edge." (It's already there, Edge, but thank you).

Edge is based on Chromium, so would that mean this breakage will eventually apply to Edge as the Manifest changes, uhm, manifest to Chromium-based products? Or is this just a Google Chrome thing?

FWIW I keep Firefox around but I have to admit I like Edge's smooth sync of bookmarks and settings across machines and even different platforms. I switched about two years ago when Edge was clearly faster and lighter. It's no longer as lightweight and there are slowly accumulating annoyances coming mostly from some Microsoft Clippy-esque attempts to make some tasks "easier" (mostly via Copilot) but I still prefer it to Firefox. My former employer/retiree benefits site, for example, won't open at all in Firefox. I've considered other Chromium based browsers like Brave but haven't (yet) been sufficiently motivated to switch. (Give Microsoft some time, I expect they'll eshit Edge eventually).

Funny thing, I didn't any trouble finding gasoline on January 19, 1981.

"A generation from now, this solar heater can either be a curiosity, a museum piece, an example of a road not taken, or it can be a small part of one of the greatest and most exciting adventures ever undertaken by the American people,” Mr. Carter said. Reagan removed the panels in 1986."

All you need to know about the respective legacies of Carter and Reagan.

A worry about the incoming American president has nothing to do directly with the proliferation of sports gambling nor the harms it brings, but the sudden absence of formerly available data that might-just-might contradict the narrative of an industry that's unzipped its change purse and let Trump have at the mic stand inside (a horribly multi-mixed metaphor, but apt).

"That data set you got there, UC Consumer Credit Panel. Sure would be a shame if something happened to it, you know, if, say, somebody decided to publish a post tying bankruptcies to our donor's lil $300 billion enterprise here. Capiche?"

That's happened with climate data during his previous term, so expect more (of less).

The OG cloud email service, AOL, still revive it for testing now and then, from 1993.

Yahoo! account established July 17, 1996. I know the exact date because I remember a hyperlink blue headline across the top of the gray Yahoo! home page, "TWA Plane Explodes Off Long Island"

I tried a variety of configurations. The E-series was one of them, as it's advertised as "Great for relational database servers, medium to large caches, and in-memory analytics." Premium and Premium V2, tried those at larger capacities I didn't need just to get higher IOPS.

None came within an order of magnitude of a Ryzen 7600/nVME mobo sitting in my son's old gaming case.

An option I did not try was Ultra disk, which I recall being significantly more expensive and was not part of the standard corporate offering. I wasn't itching to get dragged in front of the architecture review board again, anyway.

I may have the "Ebsv5" series code incorrect. I'd look it up, but I don't have access to the subscription any longer.

What I chose ultimately was definitely "nVME attached" and definitely pricey. The "hypervisor-adjacent, very low latency volume" was not an obvious choice.

The best performing configuration did come from me--the db admin learning Azure on the fly--and not the four Azure architects nor the half dozen consultants with Azure credentials brought onto the project.

At my job at a telco, I had a 13 billion record file to scan and index for duplicates and bad addresses.

Consultants brought in to move our apps (some of which were Excel macros, others SAS scripts running on old desktop) to Azure. The Azure architects identified Postgres as the best tool. Consultants attempted to create a Postgres index in a small Azure instance but their tests would fail without completion (they were string concatenation rather than the native indexing function).

Consultants' conclusion: file too big for Postgres.

I disputed this. Plenty of literature out there on Pg handling bigger files. The Postgres (for Windows!) instance on my Core I7 laptop with an nVME drive could index the file about an hour. As an experiment I spun up a bare metal nVME instance on a Ryzen 7600 (lowest power, 6 core) Zen 4 CPU pc with a 1TB Samsung PCIe 4 nVME drive.

Got my index in 10 minutes.

I then tried to replicate this in Azure, upping the CPUs, memory, and to the nVME Azure CPU family (Ebsv5). Even at a $2000/mo level, I could not get the Azure instance any faster than one fifth (about an hour) of the speed of my bare metal experiment. I probably could have matched it eventually with more cores, but did not want to get called on the carpet for a ten grand Azure bill.

All this happened while I was working from home (one can't spin up an experimental bare metal system at a drop-in spot in the communal workroom).

What happened next I don't know, because I left in the midst of RTO fever. I was given the option of moving 1000 miles to commute to a hub office, or retire "voluntarily with severance." I chose the latter.

Reads like the materials coming out of AT&T, a very different company but with the same need to obfuscate massive cuts from investment community.

Or better yet, a registry flag to enable browser choice.