dopylitty

I call it..the Wolfram Apparatus

I wouldn’t be surprised if states like Idaho and Florida that don’t have functioning public health departments start having TB outbreaks to go with their measles outbreaks once the CDC is decimated and can’t provide a backstop anymore.

Right, English is just a plain bad way to tell a computer to do something. The signal to noise ratio is too low and references are too ambiguous.

You see this with the ridiculous "prompt engineering" crap that has sprung up where people are slowly reinventing programming languages but completely unspecified. Something that could be specified in 4 lines of godforesaken YAML ends up taking 40000 words of very bizarre English and using enough energy to roast a whole pig.

There might be one case somewhere that could be found where a firm that technically counts as PE isn't shady but in general the very idea of private equity is shady so it follows that all the PE firms would be shady also.

The point of PE isn't to run sustainable businesses that provide quality products and services for customers while treating their employees well. The point is to rapidly suck all the value out of businesses by loading them up with debt, breaking laws, mistreating customers, and exploiting employees. What happens to the carcass of the business or to the customers and employees whose lives have been destroyed doesn't matter to them.

While that’s true it’s good to be vigilant.

Viruses are constantly evolving and flu can also exchange parts of its genome with other flu strains (reassortment).

It may become more (or less) virulent by chance while evolving more fitness for human bodies so past results don’t guarantee future results.

This is something I think people are missing but which is really important.

AWS is flailing now and pissing off all the competent workers. Those who have the skill will leave for newer gen cloud companies without the baggage like Fly or Tailscale or even Oxide. Or they'll start their own thing.

So do you really want your whole company's compute environment running on infrastructure managed by burnt out and low skilled people?

This might be the start of the migrations from the first generation infrastructure focused cloud services to the new more application focused services.

I gotta say don't sleep on this article thinking it's just another article about IPv6 adoption stats.

There's a lot of interesting thought in the second half about what the Internet fundamentally is and where it's going. The author argues that the use of TLS and SNI has fundamentally changed the internet from a number based routing network to a network based on DNS names and SNI where the numbers involved don't really matter anymore.

> Where is this heading in the longer term? We are pushing everything out of the network and over to applications. Transmission infrastructure is becoming an abundant commodity. Network sharing technology (multiplexing) is decreasingly relevant. We have so much network and computing resources that we no longer have to bring consumers to service delivery points. Instead, we are bringing services towards consumers and using the content frameworks to replicate servers and services With so much computing and storage the application is becoming the service, rather than just a window to a remotely operated service.

> Another thing that changed on the server side was that, thanks to AWS and the like, it became trivial to set up a massive private network. Nowadays you can have a cluster of thousands of virtual machines that communicate with one another entirely within a VPC. Only machines that need to communicate with external entities get a public IPv4 address. This kind of setup not only frees up a /20, but also has the benefit of being more secure.

This is something that people who are too deep in the weeds of legacy networking don't realize. The future is to not use IP at all within enterprise and not use the Internet at all for B2B communication. In fact the future is to not use any networking abstraction at the application layer.

To start with every device can be in VPCs with the same private /16 because they can easily communicate securely within the cloud environment via services like VPC lattice or using S3/API gateway both within and across companies. Let the cloud provider handle the undifferentiated heavy lifting of figuring out how to get data from one device to another. In time third parties will establish cross provider bridges.

Then you can start to ask yourself why your applications need the "networking" abstraction at all. If you want to send some bits to an application either within or across companies it should be just a matter of putting the bits in some location the receiving application has access to and the cloud providers can figure out how to actually make the bits accessible to the other application. Think writing to an S3 bucket using a VPC endpoint but with less HTTP/TCP/IP cruft in the middle.

As a benefit the identities on both sides will be established by the cloud providers so you don't need to worry your devices are reachable by malicious actors. Then you can start to get rid of all this cyber security nonsense that has grown up around the ridiculously insecure protocols that were developed in the 70s for connecting trusted machines and somehow are still in use today.

Internet service providers and cloud providers may or may not use IPv6 but enterprises, schools, and end users certainly won't need to.