On this day 14 years ago, an anonymous 4chan user posted a RollerCoaster Tycoon 2 thread showing a 30,696-foot coaster that took four in-game years to finish, complete with riders screaming “I want to get off Mr. Bones Wild Ride” and a looping exit where “the ride never ends.”
In the source code for minecraft legacy console edition, xbox profiles can be found including profiles relating to:
- Notch
- 4J Studios Devs
- Deadmau5
- An account called "minecraftcheat0"
theres also save data of a developer world!
Super Mario 64 texture match.The side texture for Bowser in the dark world stage, is actually an edited photo of a rock formation found in VisualDisk M1 Stones CD.Spotted by roovahlees @Leonard85026417
windows 11 is just like a vm running on a thin windows 10 hypervisor. too much legacy junk under the hood and a shell that’s basically a website running in a borderless window.
the win11 shell is just an electron app and it can’t handle vertical orientation without crashing the entire display driver.
win10 taskbar being resizable in 26H1 is because it’s the only part of the os that actually respects the manifest file. win11 taskbar ignores it because it’s not even a real win32 app.
microsoft developers forget to delete the old code before shipping the new one, that's what happens when you use too much of ai to write your code.
microsoft claims win11 is more secure. then why does it still rely on the win10 ribbon ui binaries for file operations in 26H1? if it was a real os, they would have ported everything to rust by now.
fun fact: the only reason 26H1 hasn't deleted the legacy win10 code is because the entire office 365 installer still relies on the old shell hooks to show progress bars. if they deleted the "buggy" old code, you literally couldn't install excel. the world's most "advanced" os is being held hostage by its own spreadsheet software.
New Super Mario Bros.(New スーパーマリオブラザーズ) Screenshot (Nintendo E3 2005 Press CD).The sky texture is an edited image from VisualDisk N-2 Clouds CD.Spotted by @B_squo
Story time about the worst code I've ever seen. I am going to tell you about it, and I honest-to-God would not blame you if you thought I was making it up.
I started a new job. One of the first things they wanted me to look at was why it took several minutes for a single grid to load on an Angular page. This was original AngularJS, by the way.
When I tried to load the JavaScript code behind, every here and there it would crash Visual Studio. You had to be very careful that you didn't have anything else opened because the file was so large it ate up all the memory.
The horizontal scroll bar was as thin as it could be, and you had to be careful trying to drag to the right because it, too, could crash Visual Studio.
The page had a grid on it, and instead of data binding like you normally would do with Angular, they had written if-then statements for every permutation of every column order and visibility that there could be.
When they added a new column, they had to go in and code every possible combination of visibility and order in conjunction with every other possibility that could have ever happened.
It got worse. Much, much worse.
Again, ignoring the data binding that is built into Angular, in order to detect when a user clicked on a cell, they would take the xy coordinates of the mouse click and then calculate which column and row was probably clicked on so they could edit it.
They literally had to keep track of where you scrolled to in order to try to figure out which column was under the mouse when you clicked. It was not always correct, and by not always I mean generally got it wrong.
Once they calculated which cell you probably were clicking, they then had to do a lookup on the root data to see which field it pointed to. It would then send that data back to the server and cause the screen to refresh, taking another 2-3 minutes to load.
Did I mention the calculation of which field was clicked was often wrong? And that it would send the wrong data to be updated?
Oh, and they had assigned console to null because there were so many errors that it would cause the browser to stop responding. Which I only found out as I was trying to troubleshoot and add logging.
To this day, I do not understand how anyone ever could have written something so poorly performing and put it in front of somebody and say, "I'm done."
And yes, it was offshore.