If AI tooling starts to seriously chip away at those foundations then it puts a large chunk of their business at risk.
Yes, but it was never more private than the law decided for. Any judge could lawfully have the police tear the envelope apart and read the contents during an investigations. In this sense, the only private communication that ever existed was from mouth to ear.
Today's technology enables actual privacy any anonimity online, and any good and bad deeds can be hidden behind the screen, and nobody should be offended, nor surprised, that civilised societies may want to have a say in the matter.
This is more like a judge ordering phone book providers not to list a phone number for a public organization known to engage in criminal activity. It would be prima facie unconstitutional in America, while the police opening a suspect's envelope can be an authorized legal search.
The link you provided says:
In 1942, during World War II, Congress created a law to grant President Franklin D. Roosevelt or his successors the power to temporarily shut down any potentially vulnerable technological communications technologies.
The Unplug the Internet Kill Switch Act would reverse the 1942 law and prevent the president from shutting down any communications technology during wartime, including the internet.
The House version was introduced on September 22 as bill number H.R. 8336, by Rep. Tulsi Gabbard (D-HI2). The Senate version was introduced the same day as bill number S. 4646, by Sen. Rand Paul (R-KY).
The bill did not pass and did not become law. So what are you referring to?
Deleted Comment
I’ve seen teams waste many months refining k8s deployments only to find that local development isn’t even possible anymore.
This massive investment often happens before any business value has been uncovered.
My assertion, having spent 3 decades building startups, is that these big co infra tools are functionally a psyop to squash potential competitors before they can find PMF.
The mental gymnastics required to express oneself in yaml, rather than, say, literally anything else, invariably generates a horror show of extremely verbose boilerplate, duplication, bloat, delays and pain.
If you're not Google, please for the love of god, please consider just launching a monolith and database on a Linux box (or two) in the corner and see how beautifully simple life can be.
They'll hum along quietly serving many thousands of actual customers and likely cost less to purchase than a single month (or at worst, quarter) of today's cloud-based muggings.
When you pay, you'll pay for bandwidth and that's real value that also happens to make your work environment more efficient.
You can literally get a Linux box (or two) in the corner and run:
curl -sfL https://get.k3s.io | sh -
cat <<EOF | kubectl apply -f -
...(json/yaml here)
EOF
How am I installing a monolith and a database on this Linux box without Kubernetes? Be specific, just show the commands for me to run. Kubernetes that will work for ~anything. HNers spend more tokens complaining about the complexity than it takes to setup.The mental gymnastics required to express oneself in yaml, rather than, say, literally anything else
Like, brainfuck? Like bash? Like Terraform HCL puppet chef ansible pile-o-scripts? The effort required to output your desired infrastructure's definition as JSON shouldn't really be that gargantuan. You express yourself in anything else but it can't be dumped to JSON?
re: the cloud specifically see these GitHub issues:
https://github.com/dagger/dagger/issues/6486
https://github.com/dagger/dagger/issues/8004
Basically if you want consistently fast cached builds it's a PITA and/or not possible without the cloud product, depending on how you set things up. We do run it self-hosted though, YMMV.
chef's kiss