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

The annoyance comes from the fact that your kind of _reasonable_ discourse on safety is always thrown when there is a bug, but never when there is a claim that rust is 100% by construction. I.e. It's always a defensive argument, but I never see someone step up to mention it on overly optimistic claims.

I can't be defending the statements of whoever says this, but I do think that the reasonable way to understand it is that the fundamental model that the Rust compiler and standard library attempt to implement is safe and correct by construction, rather than as a statement about the concrete implementation.

Among software developers, we shouldn't need to provide a "assuming there are no bugs" caveat with every statement about how something works, because we know that bugs are essentially unavoidable at scale. We can say that Rust makes it much easier to avoid bugs, but nobody serious has ever claimed that they are 100% eliminated.

It's not like C or C++ compilers are bug free either, despite implementing much weaker models.


> the fundamental model that the Rust compiler and standard library attempt to implement is safe and correct by construction

This comes up a lot as a defensive argument too, but it's also pretty frustrating, because Rust's "fundamental model" is not a thing that really exists. There are project proposals to create one (such as https://goals.rust-lang.org/2026/roadmap-project-zero.html#), but at the moment it's just a vague set of vibes people gesture towards to dismiss all the problems with Rust-as-actually-implemented.


Calling it "vibes" is just so unserious.

If you would like the Rust language to have a formal specification, I would suggest you look at ways to help that happen. There is already the Ferrocene[1] project.

The safety model of Rust is extremely well described in detail. It's not particularly hard to understand, either. Are you worried that there is some kind of fundamental flaw in the design, we're just waiting to discover it, and it will all come crumbling down? My suggestion would be to start by understanding Rust's type system and why it works the way it does, and you will very quickly build an intuition ("vibes") that it obviously works.

[1]: https://ferrocene.dev/


If your intuitive understanding of Rust is that its type system "obviously works", then you have developed an incorrect understanding! There are many documented cases where it does not work, and there is an active project to change its design so it works in more cases.

I don't think we should accept this kind of vibes-based reasoning from C programmers who are confident their programs don't have any memory bugs, and we shouldn't accept it from people trying to sell us programming languages either.

I think it's reasonable to say that Rust successfully prevents a lot of memory issues, and that it's it's a good choice for lots of projects. But it frustrates me when people try to dishonestly argue that it's perfect and then retreat to arguing that the implementation is flawed but the design is perfect, because neither statement is true but they take a lot of oxygen away from efforts to improve the situation.


> There are many documented cases where it does not work, and there is an active project to change its design so it works in more cases.

Are you referring to the implementation or the model? Because there are several bugs in the implementation, but they are very clearly bugs.

If you're aware of any actual holes in the type system as it is designed, I think the Rust lang team would be very interested in hearing about your paper!


I am referring to the one that exists in material reality, and not just the collective imagination of the people making this dishonest argument.

Wait, so you believe that unless the program's behavior is described by an ISO standard document, bugs cannot exist?

"It's a feature, not a bug!" taken to the next level. I guess I admire your dedication to obstructing reasonable discourse.


The problem isn't that Rust doesn't have bugs in it. The problem is when people try to say that Rust is an "implementation" of some thing that does not have bugs. This is only true because it's not possible for there to be bugs in a standard which does not exist. It creates the impression that the Rust team did design work that they have not actually done yet.

"But my mental model of Rust is not detailed enough to notice the bugs!" That's great, but that's also true of every bug, including the ones that are caused by major design defects, so it's not really saying much.


I mean it would be nice to make one of those, but I also don't really see the point of doing so besides shutting up the guys who like to talk about how Rust doesn't have a spec, most of whom do not even seem involved in the language really? Nobody really has an issue with the current situation, they are all clearly bugs and they more or less get triaged appropriately.

Right, but the GMs you see online are often "super GMs". They are on a category of their own in the ultra tail.

No, I watch plenty of "regular" GMs, as well as some IMs and even FMs who all consider way more moves/positions than I do.

I’m around 1800-1900 and they don’t consider more moves or positions than I do at all. It’s just that their analysis is correct and mine is not even close.

I actually don’t know this for sure, I should say that they don’t verbalise more moves than I think about. It’s plausible and perhaps even likely that they have a lot of moves or positions they do touch on but immediately discard so don’t even verbalise.


I'm fairly certain that GMs often consider many more moves than what they verbalise. If you look at Naroditsky's speedrun episodes, there are many moments where he verbalised a few of the opponents responses, and sometimes said opponent plays something else and he goes "I looked at that, but thought that wouldn't work" (or something along those lines). I've also seen these sorts of things in clips from Levy who is a "mere" IM.

Man, I miss Naroditsky. Such good content and such a sweet person.

Some folks on internet are not representative of a nationwide issue...


They cut the whole country's internet when people are playing football, to make sure nobody is live pirating the football

This is your country. This is your country on intellectual property rights.


Yeah right, they also eat the dogs.


No, they don't eat the dogs but they do cut off the internet during football.


I love books as well, but I find it hard to keep my physical library growth comparable to my physical books.

The majority of the books and authors I follow are now on Patreon, and there is just no easy way to get a hard copy, or even a digital copy for that matter. I read book 11 on Patreon while Amazon is publishing book 8...

Now that is good for authors I guess, they have a better, more stable revenue source. But I don't own books anymore, can't read them offline, which is very annoying.


What form does a book take on patreon if there's no file to download - is it just one huge text post?


No, usually authors publish 1 chapter every . Some publish 1 chapter per week day, some 1 chapter per week.

Once there are enough chapters for a full book, authors usually publish them on Amazon, and remove them from Patreon because of the exclusivity clause.

There is usually a 2/3 book lead on Patreon vs Amazon.


- Because USD is the main trading currency, much more liquid than anything else

- Also for physical resources, you want geographical diversification, and America is far enough that to be orthogonal to e.g. European conflicts


That canot happen if the market becomes monopolistic, with every bigtech out there buying every startup worth a penny. The erosion of anti trust in the US created this monstrosity.


Solex got used much longer than post WWII, the engine is very easy to service. I had one when I was 15, and most of my friends did as well. Everyone in the village had either a "solex" or an old "mobilette".


This drives me mad as well. Electric bikes should be limited to 25kph and non throttled in Europe, yet half the bikes I see are both, and drive recklessly.


The other day I was passed by one which kept up with the cars on the main road, which has a speed limit of 80km/h. Most cars don't go full speed there, but will reach at least 60km/h . On it were two young boys without helmets. It's insane.


I don't really get that logic. Cars can do way over 100 yet no one calls for limiting all cars all the time, because some drivers drive reckless.

And if we want to limit cars - you know, the number one thing that actually kills a lot of people directly - then I don't think it helps artificially limiting alternatives like E-Bikes.

The only difference is with enforcing the rules, but there are solutions for that. Police on E-Bikes doing patrolling, mandatory number plates, E-Bike driving licence, .. not that I want all those things, but I much rather have that and not crippled bikes so cars stay the norm.


You are being confused, vehicles by themselves are not limited, their category is.

You can have an electric vehicle that runs at 100kph if you want, but that is not a bike, that is a motorcycle.

The problem here is people having vehicles assimilated as ebikes, but with radically different specs.

I have no problem with these guys driving their vehicles on the car lane, like motorbikes do, but that's not what we're talking about here.

These vehicles are running on the bike lane, drivers are without helmets, they cross pavements, and enjoy all the slow vehicles perks, while being far more dangerous for their surroundings.


Ok, but I am talking about being able to drive in city traffic and keep up with cars and not be a blocker - and then go to the forest with my e-bike where I do mind the other people walking around there and drive adequate. Not possible with current legislation.

I can only drive my E-Bike with my car to the forest (like to many people do), or drive slowly there myself.


In Europe a class 1 ebike can't have a throttle and assist must be limited to 25km/h (it's 32km/h in the US). They can be faster and have a throttle, but then they are more like scooters in terms of licensing and insurance. If you go to most bike shops in Western Europe they will only have class 1 e-bikes. A class 1 bike is generally allowed everywhere a bike is.

While there are a lot of people riding more powerful bikes in Europe illegally, at least some countries are trying to crack down on them. In the US, it seems easier to buy class 2 and 3 e-bikes, and there seems to be a higher proportion of illegal bikes. It's an open secret which "class 1" bikes you can buy and then overclock easily.

So in Europe you mostly have class 1 e-bikes and obviously illegal (as in you can tell just by looking at them), but in the US you have these plus a lot of class 2 and 3 e-bikes, and overclocked class 1 e-bikes. The end result is most mountain bike trails in Europe allow class 1 e-bikes only, but in the US it's impossible to enforce class 1 only, so a lot of regions are trending towards banning all e-bikes from all trails. So be careful about wishing for a more powerful e-bike you can drive in traffic and mountain bike trails.


The point of PoW access is not that its hard to bypass, it's that you cannot bypass it at scale.


>it's that you cannot bypass it at scale.

Define "scale". For any reasonable wait that you're willing to impose on your users, any PoW scheme heavily favors attackers. They have unlimited time and can be scraping even while they're asleep. Your visitors on the other hand don't have that luxury. You might argue that's not the point and it's only to stop dumb scrapers that are effectively ddosing your site, but if it's just dumb scrapers, you could've stopped them less onerous measures like tls or javascript fingerprinting.


If algorithm used is static and GPU-friendly, then what stops bypass at scale?


It's more or less designed for it, it's SHA256 with a break in the middle for midstate compression to be effective, and the difficulty system is based on a misunderstanding of how bitcoin PoW works ("number of zeros" is never, ever a consideration in bitcoin, it's a match to a floating point target).

sha256(challenge + ascii(nonce)) means that the first compression round of the function can be cached and the second compression round is just the nonce plus the cache. This is the same trick used in Bitcoin mining and would have been avoidable by putting the nonce first, so immediately any non-naive code has to do half the proof of work as the vanilla solver.


> Leveraged funds are the safest way for the average investor to get access to leverage

I... do not agree that leveraged funds are somehow a safest way to access leverage.

Every product including leverage has inherently a non-linear P&L. And from my experience, non sophisticated investors always struggle to grasp the implications of that. It makes returns (on capital) very path dependent, and very nasty during volatile regimes. It breaks the naive assumption of "well I could always hold and wait for the dust to settle".

> unlike margin there is no risk of margin calls

This is a bit of a weird statement. Leverage implies margin, you cannot make it disappear, the funding and associated risk has to come from somewhere, it's just that it is continuously applied, instead of fixed timings.

I do agree that it simplifies planning and reserve management though.

> even Warren Buffet made his biggest early wins on all-in bets.

This is a bit disingenious, note that Buffet did not use leverage...


> This is a bit disingenious, note that Buffet did not use leverage...

In a way, but Buffet wasn't making those investments exclusively using his own money. Effectively there's a degree of implied leverage when you get a performance reward from investing other people's money.


Buffet funded his investments with insurance float


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

Search: