Apparently, its current purpose is a demo for their "Copilot" AI technology.

With all of GitHub's great new AI features, it writes all your code for you! It doesn't matter whether the site is up at any given moment; just download your newly completed app at some point then the site is online. You're free to kick back, relax and scroll your social feeds because you don't actually have to do anything anymore. This is truly a golden era!

This is why NASA always packs a tin of Bondo with the mission supplies.

So you prompt the LLM to "find all the bugs".

Even if the LLM can find every last bug (which in turn assumes that this type of problem isn't NP-hard or has some issue that Godel would point out), just defining to the LLM exactly what a "bug" is seems to be pretty much the same thing as those formal specifications that you just convincingly dismissed as inadequate.

I don't think that there's anything magical about LLMs that would let them get around fundamental mathematical roadblocks.

It would mean that there's an 83% chance that the rest of us would be spared from more posts expounding on your silly line of reasoning.

If that's the case, the next time you play Russian roulette, why don't you go ahead and put in 5 bullets?

If what you say is true, then why is everyone freaking out over the prospect of Iran obtaining nuclear weapons?

From now on, I'm only drinking soda in October.

To me the hoops that smoothbrains will jump through to avoid IPv6 and stay on legacy IPv4, especially when hosting, is pathetic. NAT, port forwarding, tunnels, blah blah blah blah.

I have something like ~1.2 trillion times the number of routable addresses that the entire IPv4 space has. Not all are reachable, of course, just the services that need incoming access and they're each on their own isolated DMZ.

Forgot to add: if you enable IPv6, be sure to use the browser extension IPvFoo. It shows a small 4 or 6 in your URI bar to let you know what protocol you're connecting to. Once enabled, you'll see just how much stuff out there actually is IPv6.

Started the move about 18 months ago when I decided to get off my lazy ass. My ISP gives out a /56 prefix, so that lets me run 256 /64 subnets/VLANs in the house, currently there are ~10 in use. Everything get a GUA through SLAAC and I use RAs (Router Advertisements) to give ULAs to everything. Any external facing services get their own VLAN and /64 for the system(s) as needed. Firewall blocks all incoming as they usually do by default and I punch a hole for the external-facing systems. They can't reach back into the network, they only answer the phone. All the systems update DNS dynamically if the prefix or full address ever change.

I have an SSH bastion set up. In all this time there has not been a single SSH attempt from the internet. On IPv4 it was constant background noice.
For those legacy IPv4-only systems on the internet, I set up NAT64. I have an IoT VLAN and IoT 2.4 GHz wireless network that are only IPv4 because a lot of IoT network stacks are junk.

I'm still farting around with it, but man oh man, there's no way I'd go back to IPv4. It was one of the best moves I've done in ages.

Ignoring the fact that you don't seem to know what a laptop battery is, it looks like you could have a promising career as a data center site planner.

Not to mention, blocking more ads and other unnecessary stuff == better performance on the stuff you were actually trying to view. It very likely comes out as a net performance win even with a ~20% disadvantage in raw CPU speed.

If you dig deeper, you'll find that AMD originally reverse engineered the *8080*, not the 8086. The two companies had entered into a cross-licensing agreement by 1976. Intel agreed to let AMD second-source the 8086 in order to secure the PC deal with IBM, who insisted on having a second source vendor.

There would have been no Intel success story without AMD to back them up.

(That actually would have been for the best. IBM would probably have selected an non-segmented CPU from somebody else instead of Intel's kludge.)

I once worked at a place that had a clean room process to create code compatible with a proprietary product. Anybody who had ever seen the original code or even loaded the original binary into a debugger was not allowed to write any code at all for the cloned product. The clone writers generally worked only off of the specifications and user documentation.

There were a handful of people who were allowed to debug the original to resolve a few questions about low-level compatibility. The only way they were allowed to communicate with the software writers was through written questions and answers that left a clear paper trail, and the answers had to be as terse as possible (usually just yes or no). Everyone knew that these memos were highly likely to be used as evidence in legal proceedings.

I highly doubt that any AI tech bros have ever been this rigorous, and I'd bet that most of these AIs have been trained on the exact same source code that they are cloning.