For developers yes. For non-developers it was a mystery.

Every Dr. Who fan knows the moon is an egg. [The Moon Hatches? | Kill the Moon | Doctor Who - YouTube](https://www.youtube.com/watch?v=pHOnGSFzd3Y&t=151s)

Compared to my bookshelf, those are practically brand new. I still have books on (MS-)DOS internals and an old 8086/8088 programmers guide that details the entire instruction set.

Android has always allowed non-Play Store applications to be loaded. It's just not as easy to do.

Yep, lowercase tends to use less space on a line when using a variable width font. :laugh:

The best optimizations are usually design changes. Any optimization that requires an architectural change is a design change.

This is actually a really good comment. It explains both the why and the what/how. I wouldn't call this a sin, but rather a reminder of why you did something the way you did.

COBOL, FORTRAN, PL/1, and various Assembly languages. It really depended on the hardware and application. What's interesting to note is that other than the Assembly languages, none of the high-level languages at the time had buffer overrun, use after free, use before allocation, and the entire host of possible memory management errors that have resulted in roughly 90% of all vulnerabilities.

The psycho path is so much more fun, though.

StarNamer@work wrote:

I have 2 slide rules.

:cool:

Oh, good. We'll finally stop having to remember our first pet's name. Obligatory [xkcd: Password Strength](https://xkcd.com/936/)

So the only problem is someone didn't profit from the suicide. Got it. /s

Stolen. That's great.

This is yet another example of Microsoft's desire to move everything from on-premise to cloud. WSUS has always had huge problems with database fragmentation, to the point that I wrote a PS script combined with a SQL Server database defragmentation script I pulled off a Technet blog over a decade ago to keep my WSUS servers healthy and responsive.

Let me know when AI can read this: [https://memeguy.com/photos/images/doctors-on-strike-397489.jpg\](https://memeguy.com/photos/images/doctors-on-strike-397489.jpg)

So did the mouse have a ticket?

The 4GB limit is a Windows 32 limit, and the default in Win32 is 4 GB with 2 GB being granted the OS, effectively limiting the application to 2 GB. There is an option to make this 1 & 3 GB but I don't remember how to do this. Exchange Server and SQL Server versions designed to run on 32 bit Windows server used this option. For Windows 64, the limits are listed at [Memory Limits for Windows and Windows Server Releases - Win32 apps | Microsoft Learn](https://learn.microsoft.com/en-us/windows/win32/memory/memory-limits-for-windows-releases). Note that 32-bit applications are still limited to 4GB simply because 2^32 is 4GB. 64 bit application limits vary by OS version, generally growing with each new version of Windows.

The Agile Paradoxon nailed how Agile has been warped by managers. The SCRUM: An Honest Ad is exactly how I feel about Scrum and Scrum masters.

If you drift an electric car, are you doing the Electric Slide?

The cattle crossings on the road headed up to Teton and Yellowstone National Parks are painted on the road. Apparently cattle can't tell the difference and won't cross them.