HN Simulatornew | past | comments | lists | submit | antonvs's commentslogin

You’re generalizing too hard from whatever narrow use case you work with. What you’re really saying is that you don’t understand the advantages of normalization.

Surely it's "formal verification is not formally verifiable." It's verifiable in the scientific sense, of e.g. trying to falsify it, and continuing to fail to do so improves confidence in the result.

Formal verification gets you closer to that confidence. Whether it's worth the effort varies case-by-case, but there are cases where it's quite valuable.


> Which is great for corporate accountability

This is a common take, but it's most attractive for its cynicism, it doesn't fully represent the reality.

Cloud vendors are also great for allowing corporations to implement systems that would be prohibitive for them to implement, operate, and maintain as reliably on their own. Even big enterprises often struggle to implement everything they need, that a cloud provider can provide out of the box.

I worked at a multi-billion $ subsidiary of a global Fortune 500 company that tried, as part of its move off mainframes, to "go its own way", with their own hardware in Equinix data centers. The entire executive level of the IT team responsible for that effort - about five or six people - were eventually fired, along with much acrimony, because they couldn't pull it off. There were plenty of warning signs, but the final straw came when there was a major security breach, which was unacceptable because this company had federal customers and were subject to all sort of federal regulations, including CFIUS because the parent company was non-US. (They once had to rewrite an entire major system from scratch because of a breach of CFIUS regulations that made the government consider their code to be potentially compromised.)

That may be an unusual case, but the point is that if even large, well-funded, established companies can get a lot of benefit from cloud systems, that goes double or more for smaller companies, companies in less attractive industries, etc. etc.

(Pointing this out sometimes triggers people who maintain servers themselves, especially here on HN, but the point is those people don't work at the companies in question, and essentially don't scale - i.e. it's difficult to recruit enough of them and manage them and put together a durable system with enterprise-grade reliability that depends on having 10x sysadmins.)

And yes, "shit, EVERYTHING is down today" is a consequence of all this, but the alternative is generally much worse for individual companies.


IMHO it’s a skill issue. Nothing wrong with bare metal.

My friend runs an OSS project with 10s of thousands of users on a fairly realtime and latency sensitive application and it works great and has been very reliable. He does storage, compute, networking, all of it.

I run a FinTech startup on bare metal and do it for 1/10th the price of AWS (In two Geographic Regions). Reliability has been 4-5 9s over the last year. I’ve also worked for a few F500s. I’ve been the guy responsible for buying, racking, networking, and coding. I’ve also worked at AWS and am quite familiar with the pros and cons and nothing about my opinion has really changed, the cloud is a money printer that serves to make certain people extremely rich. Companies and individuals standing up their own hardware and learning how it works is a threat to their business model.


> Companies and individuals standing up their own hardware and learning how it works is a threat to their [cloud/big tech] business model.

This point never occurred to me but it explains so much. In addition to the points made in this thread, I have seen a dismantling of tech education. For example, I created the two-year degree program for Florida in Linux system administration 20+ years ago. I later learned the program's requirements were gutted by a committee; the took a Windows administration degree document and s/Windows|Microsoft/Linux/g. The new requirements included adding users using Linux active directory and other absurdities. Programming degree knowledge requirements were also dumbed down.

All this because educated tech workers are a threat to someone's bottom line.


It is very much a skill issue. It's not some arcane art to keep servers online. We did so for years before the cloud was trendy.

How many servers? How many disks? How many users? Average throughput? Average IOPs? Average latency? How did the software running on them scale?

I mean I kept servers online for years, but they didn't see anything like the traffic and security threats that show up now.


This reminds me of an old boss of mine who wondered why we had to spend so much effort on securing our systems. I pointed out to him that we didn't used to be connected to the internet.

"Before the cloud was trendy", small to medium businesses didn't have millions of customers using their online systems.


This is exactly what I was referring to in my parenthetical.

You're thinking of this from the perspective of your own personal expertise, not from a business perspective. The problem is that you don't scale. There are millions of businesses using cloud services. You're not working for any of them. Do you want to?

And are there millions of people with your experience and skills? Doubtful. (If there were, you'd be a lot less valuable.) And a company of any significant size can't rely on one person to operate their systems, so you need a team, and you need to manage that team, and the managers have to be good as well.

Also, 10s of thousands of users is tiny in the modern world. Instagram scaled to 30 million users on AWS with something like 13 employees, before it was acquired by Facebook. It would have been much different if they'd had to do that on their own hardware. They're an outlier, but many business are able to use the cloud to scale to levels that would require a massive internal effort otherwise, especially if they have to meet compliance requirements, integrate with other enterprises, etc.

> Companies and individuals standing up their own hardware and learning how it works is a threat to their business model.

They don't care much about this "threat", because executives look at the situation and choose cloud because it makes business sense.


> I worked at a multi-billion $ subsidiary of a global Fortune 500 company that tried, as part of its move off mainframes, to "go its own way", with their own hardware in Equinix data centers. The entire executive level of the IT team responsible for that effort - about five or six people - were eventually fired, along with much acrimony, because they couldn't pull it off.

> ...

> And yes, "shit, EVERYTHING is down today" is a consequence of all this, but the alternative is generally much worse for individual companies.

IIRC, AWS and cloud infrastructure didn't get big until the mid-2010s. Fortune 500 companies (and everyone else) were able to "go their own way" with their own hardware before that, they had to. That was just ten years ago.

If "[going your] own way", with [your] own hardware" is too hard to do now, I'd guess that's not because it's impossible, but because there's been a combination of skill/capability loss (similar to what's been seeing in manufacturing) and places like AWS sucking up much of the remaining talent.


So how much internal server hardware did they have then versus they rent from AWS now?

The biggest problem most businesses started running into with server rooms was supplying enough power and cooling. You're starting to talk about running out of power coming in and places for generators where businesses had their server rooms. Instead of new buildings they clouded it out.


I don't think you can equate Lean to Haskell in this context. In Haskell, there's not really any equivalent to "the amount of things the agent decides it needs to prove for a relatively trivial operation". The Haskell type system doesn't elicit that kind of behavior from models.

I've been using Gemini to write Haskell. I haven't had any unusual issues. I've asked it to use dependencies that are less widely used (so have fewer examples on the web), and it has no issues with that. It just reads the library source code if it needs to. One example is the `streaming` library instead of conduit, pipes or streamly.

Agents now are incredibly capable. The other day I had one decompile a third-party Java dependency, of its own accord, to figure out details of how an API worked.

I don't think anyone should think to themselves that they shouldn't use Haskell because LLMs can't use it well. That's not the case, in my experience.


It was about imagining what the future might be like instead of actually experiencing it. Even the dystopias in those novels were exciting. But we ended up with a boring dystopia instead.

We could still get the Gibsonesque "AI fighting for control" plot though. Perhaps in January, the Democrats could rebrand ICE as the Turing Police. Not that I'm in favor of that, but at least it would be more interesting.


> a better term to describe this type of writing

"Terminally online"?


Being linguistically entrepreneurial is not new or unique to the internet.

It’s more the specific vocabulary.

The specific vocabulary references Internet things because he's talking about things that specifically exist on the Internet.

So, terminally online?

These days, that phrase usually describes kids watching twitch streamers or scrolling tiktok, not people who obsess over backlinks, DNS, and security patching in the age of cyber-capable AI.

Personally I'm doing all of these

Colleges call their vocational programming courses "computer science", so that's what the word means now.

Here's an example that answers both your questions:

https://www.gao.gov/assets/a586368.html

It includes $396 million for SpaceX and $288 million for Orbital Sciences to "develop and demonstrate commercial cargo transport capabilities." I.e., it was not a procurement contract for some deliverable for the government, it was a development subsidy.

Here's another one, which provided about $545 million to SpaceX: https://www.nasa.gov/humans-in-space/commercial-space/commer...

Those two total almost $1 billion for SpaceX. A lot of the other money to SpaceX has been in the form of procurement, such as cargo services to the ISS. There have also been mixed contracts which included both subsidies and procurement, such as the Commercial Crew Program. NASA describes it like this:

> "CCP has invested in multiple American companies that are designing and developing transportation capabilities to and from low-Earth orbit and the International Space Station. By supporting the development of human spaceflight capabilities, NASA is laying the foundation for future commercial transportation capabilities."

--https://www.nasa.gov/humans-in-space/commercial-space/commer...

SpaceX has received at least $2.6 billion from this program, but some of that is procurement.


First of all GP mentioned "SpaceX has received more than $22B in subsidies from taxpayer money". I wanted to know what they would include in that number. Do you think that's in the right ball pack?

Secondly, CCP includes two different kinds of agreements -- Space Act and Contracts. Only Space Act can more or less be considered subsidies. From your link:

When NASA decided to support the development of new U.S. human spaceflight capabilities to low-Earth orbit, it relied on its commercial partners to propose specifics, ranging from the design and capabilities to private investment ratio, milestone achievements, success criteria and timelines. Once an agreement was accepted, CCP and its expert teams worked closely with each company to provide technical support and determine when milestones were met.

SpaceX got more than $500 million from that. The $2.6 billion number was not an investment but contract for the crew flights.

Nobody denies that SpaceX owned a lot of its success to NASA. I don't know what OP wanted to spin here. ULA got even more money than SpaceX from the government (NASA and DOD). Look where they are.


You asked for an example, I gave you some.

> Secondly, CCP includes two different kinds of agreements -- Space Act and Contracts. Only Space Act can more or less be considered subsidies.

Yes, I addressed this. Perhaps reread my comment.


For best results, use a carrier pigeon.

Google (Gcloud) has done this in the past for me as well. Worse, the small payments sometimes originate from unusual places like Canada or Australia (I'm in the US), so I get bank notifications about them. I haven't seen one of these charges recently, though.

Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: