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

> Part of the importance is due to the fact that while the space shuttle was a technical success in terms of being able to build and operate a reusable upper stage, it was hella expensive.

This is a complete apples to oranges comparison.

A more apt comparison would be the space shuttle being a kin to Vasco da Gama's discovery of the sea route to India. After that point, the concept was demonstrated and the challenge was in optimizing cost-savings of commercial endeavours.

I mean, orbital lift services have been a thing for how many decades?


> The community-driven quest for "panic safety" in Rust is the same curse that befell C++ in terms of "exception safety", maybe worse because at least more C++ shops are sensible enough to disable exceptions.

You seem confused. The "exception safety" topic in C++, which clueless people often cite Google's style guide as an appeal to authority, is that it's undesirable to modify old legacy code that does not use exceptions to call libraries that do. The sole reason this is not desirable is that calling code that throws exceptions introduces code paths that the legacy code was not designed to consider and cleanups that leave it in a state it was not designed to be in (i.e., all stack unwinding and RAII cleanup in surprising points with surprising implications).

And project managers tasked with a project that involves legacy C++ code can't simply spare time and resources to redesigns legacy project to accommodate for these changes, or the risk of having stable production code one day crash just because someone linked to a library that now throws.

Therefore, the "exception safety" discussion in C++ is not a technical one. It is a project management one, and one which involves high reliable legacy code.


> Just because emotions seem to be always boiling whenever Rust is mentioned, I want to clarify for people who only follow casually that there is nothing unusual or scandalous about these finds.

Rust unfortunately is renowned for it's toxic community (see actix-web). Within that community, some clueless but vocal members routinely attack people who have the audacity of not rewriting all their projects in Rust, and they parrot cargo cult mantras such as memory safety as their main attack points.

Consequently, discussions on memory issues plaguing Rust often draw these types, with the expected consequences.

Yes, Rust also suffers from memory safety issues. Yes, there are CVEs caused by Rust code. Yes, using Rust obviously does not make your code better or bug-free. But these discussions are not grounded on a technical ground.


This is an interesting comment which mostly seems to aimed at causing outrage? For the last many years I see more people with an axe to grind whenver Rust is mentioned rather than the other way around.

The issue with actix-web, which played out in 2018-20, was that it played very liberally with memory safety, prioritizing speed over everything else, with the author closing PRs solving memory bugs.

Basing your definition on "techinical ground" you can dismiss anything that isn't perfect.

Rust's solution is the human response. Memory unsafety are treated as bugs, listed and fixed. Some fast, some more slowly. Depending on impact and how deep they go. C and C++'s solution is listing them in the specification, or having it be implementation defined, and telling you to not step on the land mine.

Given the research on this area introducing Rust in some of the most battle hardened codebases globally leads to far fewer memory issues and high impact vulnerabilities in the Rust parts. And the parts converted to Rust often are the ones which has had an history of bugs and vulnerabilities becuase they are non-trivial.


Here is another one, the attack on ThePD, the end result being that Rust still has no reflection support, while C has been getting several goodies caused by him moving away from Rust back into C and C++ ISO work groups.

Thanks to that Rust community behaviour, C23 has several nice improvements, with several others to possibly land on C2y.


It does have reflection support on nightly (via comptime aka const only fn see https://goals.rust-lang.org/2026/reflection-and-comptime.htm...), but it's a much more complex feature than was presented in the ThePhD report.

Until it actually lands on stable it does not count, it may take years, if ever.

I lost track how many features have been on nightly, there is even a website to keep track of them,

https://doc.rust-lang.org/unstable-book/index.html


So by that logic we don't count C23, until all C implementers decide to follow it?

If Jean Heyd went and implemented it, I wonder how far we'd be into actually having a decent alternative. Because his implementation did the hacky thing via trait abuse, while this actually changes compiler to allow const-only functions. The trait abuse would have exploded Rust's already long compile times.


> So by that logic we don't count C23, until all C implementers decide to follow it?

It seems you are confused and emotionally involved, to the point you're trying to grasp at straws to have something to shout back.

C is specified by an international standard, which then is used as integration target by countless implementations.

Languages such as Rust are different in the way they have no formal specification. Whatever went into the reference implementation is what counts as "the language", bugs and all. At best a specification can be derived from the reference implementation.

The key difference is that a C compiler that doesn't implement a feature and/or deviates from the implementation is considered a buggy implementation, whereas Rust is whatever is currently in rust stable. If something is not on rust stable, it is not rust.


> It seems you are confused and emotionally involved, to the point you're trying to grasp at straws to have something to shout back.

Not really. If you count when practically you can use a feature then it makes sense to wait till all major implementers use it. For example you can use `type_info` feature on nightly right now. Same way you can use some C23 features on some compilers but not others.

It's more of a light hearted jab at how I hear things work in C-land. "Wow, that feature is amazing!", "It's in C11, so it will be widely used by {current_year + 5}" (keep in mind this is an exaggeration for comedic effect).

Truth is the nightly features ship as fast as there is demand for them and depending on roadblocks encountered. E.g. specialization is highly sought after but effectively unsound until some nasty unsound cases are dealt with. Type_info doesn't seem to have these sort of roadblocks.


ISO standards don't have a reference implementation like Rust, there is no nightly before something gets added into the standard, unfortunely some papers even follow a waterfall model.

Getting the PDF out is the equivalent of landing on stable.

We will never know now, will we?


> So by that logic we don't count C23, until all C implementers decide to follow it?

I mean. I'd sure be reluctant to depend on it until it had trickled out through the ecosystem


> This is an interesting comment which mostly seems to aimed at causing outrage?

No, unfortunately Rust's toxic community tends to flock to these topics to flood them with their blend cargo cult claims. Topics which happen to question and even refute their claims is like their bat signal.

The actix-web episode is a good example of how far these types can take even the most harmless claim, at the expense of everyone.

Meanwhile, anyone who actually works in the field for a living is hardly surprised by this. When this sort of news pops up, we check if we need to start an unplanned update and that's it.


It is a quite interesting take that it is acceptable for the, at the time, most popular web framework, to have memory bugs in the name of speed. Especially in this day and age of vulnerabilities being discovered left and right.

> It is an quite interesting take that it is acceptable for the, at the time, most popular web framework, to have memory bugs in the name of speed. Especially in this day and age of vulnerabilities being discovered left and right.

You sound like you're trying to gaslight everyone with this story. The problem with actix-web was not "memory bugs". Not the slightest.

The problem was that it was a high-profile project in Rust, and Rust's toxic community felt entitled to relentlessly harass it's maintainers with vacuous claims regarding the use of what they chose to frame as unidiomatic Rust to justify their campaign of personal attacks.

To the point where they forced the maintainer to outright quit.

We are talking about Rust's toxic community being so toxic it even leads high-profile members of the Rust community to burn out and give up.

This was the problem. Not "bugs". It's the community.


It is rather ironic to accuse others of toxicity and personal attacks while opening with accusations of gaslighting and calling an entire community toxic.

The claim that the problem was "not memory bugs. Not the slightest" is demonstrably false.

The issues were serious enough to receive a RustSec advisory and three separate CVEs covering memory corruption and potential use-after-free.

https://rustsec.org/advisories/RUSTSEC-2018-0019.html


Additionally those toxic vocal evangelists keep forgetting that without C++ there is no Rust compiler.

Their beloved language is most likely decades away from ever having a fully bootstraped reference implementation.

Which even if it ever happens, projects like Linux would most likely never adopt, as that new reference implementation has to provide the same hardware support guarantees as LLVM and GCC.


This is pretty funny from my perspective because I have some use cases for Rust in mind where LLVM and its entire optimization architecture is completely backwards to how an ideal Rust compiler backend would look like for the types of architectures that I intend to target.

The mutable aliasing ecosystem is holding more advanced hardware back.


> Additionally those toxic vocal evangelists keep forgetting that without C++ there is no Rust compiler.

You say "vocal", yet they remain eerily silent in this and every other thread about Rust on HN, as well as /r/rust over on Reddit.

If you didn't know better, you could almost think they were imaginary.

You seem to have a mental picture of a raging Toxic Rust Evangelist consumed by shame and rage over Rust's Dark Secret: It's using the best codegen backend on the planet (with a compatible license), LLVM, which is written in - gasp - C++!! Dun dun dunnnn!

What a dramatic plot twist! I understand how that might feel very engaging.

The boring truth is that everybody is pretty fine with LLVM, because no reasonable (or real) person believes that this is a problem. As long as it generates pretty decent code in a reasonable amount of time for all the important architectures, it's a great choice.

We're trying to get work done.


What is the point of inventing some sort of existential conflict between Rust and C++?

Why must Rust have "a fully bootstraped reference implementation"?

This is weird, dude.


> Is a language only memory-safe if its implementations are completely bug-free?

What do you call a programming language which claims to be memory-safe that has memory safety issues in it's standard library?


Software with bugs in it. Or shorter, Software.

> Software with bugs in it. Or shorter, Software.

Yes, that's the whole point. Rust is used to write software. Not memory-safe software. Let alone bug-free software.

But somehow that's the extraordinary cargo cult claim that Rust proponents make. Is that claim valid?

That's the point. Isn't it?


As pointed out above, this same logic applies to virtually every trait every language claims to have. And it's purposely obtuse and combative. You are implying the sentence "Rust is used to write buggy software" by saying "Rust is used to write ... not ... bug-free software" which is again the case for every language ever. Do you also write comments complaining about cargo culting proponents of seatbelts, fire alarms, and electrical breakers since people still die as a result car crashes, fires, and accidental electrocutions?

And no reasonable people are claiming that rust is used to write 100% bug free software. And yet people like you imagine such people daily apparently. It's certainly not a claim made anywhere upthread of your comment so if it's your claim feel free to take full ownership of it.


I would rather take the 0.1% lie that Rust is memory safe than the 99.9% lie that competent C and C++ developers can properly deal with the UB they sprinkle throughout their code base without causing severe security vulnerabilities.

> The systems analyst analyzed the problem that needed to be solved and designed a solution involving a computer, including system modules, inputs, outputs, etc.

This is a holdout from the time when the whole software development field was still stuck with the idea that waterfall/big design up front was an adequate way of doing things.

The belief was that, like any engineering field, systems would first be designed in detail before anyone could even open an IDE.

This approach was quickly proven to be wrong, expensive, and fruitless. Agile started to emerge as an effective approach to the problem of developing and maintaining software systems. The uselessness of the system analyst role, when contrasted with the fact that mere programmers could easily implement features without guidance from an enlightened individual far removed from the problem domain, was readily noted.


> Are they? I'm on a macbook M5 pro 48GB (so, much better hardware than most users), and the speed alone is a problem, qwen 3.8 27b is ~10x slower than opus 5.5.

That's hardly relevant. I can use any local model through providers such as OpenRouter and get blazing fast prompt response times, and you're charged a small of what an OpenAI/Anthropic prompt costs.

What makes local models extremely competitive is the fact you do not need a huge data center to run them. The hardware they require is far from impressive. Check Mac studio benchmarks and how some models output >200token/second.


Local and open-weights are different things

Also, open-weights models are more expensive per task than Haiku and Luna


> Local and open-weights are different things

Yes they are, but you should understand what is the defining feature of a local model. Being able to run them locally is a consequence of that defining feature, not the defining feature. And it turns out that it makes them cheaper to run.

Moreover, you can run both local models and non-local open weights models through providers such as OpenRouter. They evem have Qwen2.5 7B.

> Also, open-weights models are more expensive per task than Haiku and Luna

You should really check your notes. Luna only remained competitive because OpenAI was forced to halve its cost just to avoid being dominated by open weight models. I seriously recommend you check out OpenRouter's benchmarks.


I seriously recommend you check out the cost-per-task Pareto frontier, which not a single open model is on

https://artificialanalysis.ai/


> I seriously recommend you check out the cost-per-task Pareto frontier.

I checked. OpenRouter provides their own. They use their actual cost, which is what they charge users, and their benchmarks results. Please, spend a few minutes to browse it. You'll notice that the likes of Luna is dominated by quite a few entries.


Subscriptions are actual costs to users. And Openrouter doesn't consider that. If you're talking API prices, those aren't actual costs to inference providers.

> Subscriptions are actual costs to users. And Openrouter doesn't consider that.

You seem confused. OpenRouter provides access to models from Anthropic and OpenAI, and they both have clear pricing.

See for example:

https://openrouter.ai/openai/gpt-6-luna

Don't you agree that the cost that OpenRouter charges it's users for using these models don't reflect their cost?


does not consider subscription subsidization

Compared with subscriptions, I don't think open models are that cheap. You can get an incredible amounts of API dollars for $20.

look at the S1, the subscription revenue is a small chunk of the stated revenue. they are not getting the 1.4T valuation by subscriptions.

until it is being subsidized.

We should check it in few months after IPO


I mean the person you are replying to has a fairly capable Mac, and even the smallest generally-agreed capable model is still too slow for their liking.

We don't all have 10k lying around for hardware. A $200/month subscription would take you 4+ years to cost $10k.


> For some reason they need the $100B today at the cost of dilution, rather than additional private rounds and/or using cashflow+profits to continue the advancement.

Both Anthropic and OpenAI seem to be burning cash as if it was a game of startup chicken. Of course they all desperately need cash.


> They pay a LOT of money, have some high level of “nerd” prestige for solving interesting technical problems, have good outreach with things like problem of the month, and have not been impacted by massive layoffs.

I never heard of them.

If not for HN, I would never know they existed.

I don't think the remark about "nerd prestige" holds, but beyond that your points boil down to marketing.

And how an unknown company changed its hiring practices is hardly front page news.


Paying a lot of money and hard technical problems are not exactly marketing.

Like I said, they are relatively small but they are definitely not “unknown”. Out of curiosity, could you name any quantitative trading firm, or trading firms in general? You specifically may happen to just not be paying much attention to this sector.


They are unknown because they choose to be unknown. The first rule of finance is that, you never tell anyone how you make money. Even more so if you make billions of dollars annually.

Your ignorance of something does not mean the thing you are ignorant of is inconsequential

> It feels like people are still trying to bet on the horse that will achieve gAI.

I think that at this point gAI is just a marketing blurb, and the actual race is to dominate current practical applications involving basic RAG and ReAct loops. This can go from anything between software development, business intelligence, and market research. A company whose top brass can use a team of agents to do what nowadays they assign to mid- and top-level management is an executive with tighter control over the whole business process. For this you don't need gAI.


> There's a third option: allow bots and give them access as efficiently as possible.

Why?


To make your data more accessible AND reduce server load. More and more people are using AI, so there will be more and more bots as the trend seems to be accessing data with your AI, and maybe, only sometimes, actually reviewing what it found. I'm afraid that if you don't at least start to consider how we might accommodate the bots, you'll be walling off more and more real users going forward.

> To make your data more accessible AND reduce server load.

Wait, how do you reduce server load by allowing traffic from bots?

> More and more people are using AI, (...)

That's specious reasoning. Sites provide data for their users to consume, and in some cases their business model relies on real people consuming their content.

If you replace "bots" with "scrapers", which is a specific kind of bot, what conclusions do you draw?

> I'm afraid that if you don't at least start to consider how we might accommodate the bots, (...)

Wait, you think this problem is new? What do you think companies do with crawlers and scrapers?


what does the site get out of ai users? it doesn't seem like they have a strong incentive to let you not actually visit the site

shopping makes some sense if the bot can still buy things at least, but a lot of other ad dependent sites really have little reason


A wide portion of the Internet is not ad supported. Consider a user searching for product support: the company benefits from the user self-solving the issue without having a ticket filed.

This, may, however be to the detrimental of discussion platforms, but if that drives people to self hosted discussion platforms instead of relying on reddit, then it is a net positive.

Discourse's most recent blog delves into this and is an interesting read, I will submit that I think.


I'll look for that - I'm thinking about small forums and community sites a lot lately with ai stuff.

I'm with ya, but I'm not sure what the solution is. Just pointing out a reality the internet's going to have to cope with.

My cynical take is we'll just start putting ads into the text that targets agents.

I just told you why.

> I just told you why.

No, not really. Is your opinion too hard to defend?


Third paragraph, right there

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

Search: