brundolf

52 ms·

751.
by brundolf 4y ago
And to borrow from the classic regex saying: "Now you have two problems"
752.
by brundolf 4y ago
I used to think I hated Docker, but I think what I actually hate is using Docker locally (building/rebuilding/cache-busting images, spinning containers up and down, the extra memory usage on macOS, etc etc). I don't need all
753.
by brundolf 4y ago
But it doesn't have to be run in a runtime; it can compile directly to a platform-native binary. Internally it has limitations, as any sandboxed code would, but it lets you take native code and compile it to a native binary with sandbo
754.
by brundolf 4y ago
"Safety" means a specific thing here, and whatever bugs might happen with this, they do not make the code "unsafe" It also helps that, in practice, when writing idiomatic Rust you'll almost always be accessing array
755.
by brundolf 4y ago
Explained here: https://news.ycombinator.com/item?id=34514947
756.
by brundolf 4y ago
Indexing into an array or vec will always be checked in safe Rust, so if an overflow gives you a bad index you'll just get a panic (or an Option::None if you decided to access it that way); never a safety issue
757.
by brundolf 4y ago
That's... a long list, too long for me to read it all I think. Wish there were a summary of general trends/takeaways
758.
by brundolf 4y ago
I'm sure it varies wildly by the type of program, and I'm sure much smarter people than me on the Rust team did their benchmarking homework when they originally made the choice. Just saying that to me, it seems like a reasonable d
759.
by brundolf 4y ago
It's off by default in production because all those overflow checks add up (hah). Rust's first priority has always been low-level/systems code, where these things matter. It (semi-controversially) makes runtime bounds check
760.
by brundolf 4y ago
Maybe they're outsourcing their hiring to some third-party firm?
761.
by brundolf 4y ago
More recently: micro-transactions/subscriptions But historically I'd bet it came down to the fact that games are simply more expensive than movies; a AAA game has cost $60 for the past decade and a half, while a movie ticket is ~$
762.
by brundolf 4y ago
Right, because higher-level languages became fast enough for a lot of that stuff. Rust was born into a world where that was already true
763.
by brundolf 4y ago
It's not a browser (or even a piece of a browser), it's a method of statically sandboxing a native binary.
764.
by brundolf 4y ago
It's because the post is from 2020
765.
by brundolf 4y ago
I sometimes notice my nervous system relax a bit when I log out of this website, because I know I won't get sucked into anything (he writes on this website)
766.
by brundolf 4y ago
I'm really curious how much of a joke that was and wasn't
767.
by brundolf 4y ago
Some people probably hate it, but I really enjoy the conversational format of these posts. Very novel and interesting way to bounce around a topic
768.
by brundolf 4y ago
It would be nice if subset-structs worked like they do in TypeScript, but I would still be totally happy if they had to be an exact match. Subset matching would probably be the 80% complexity for the 20% benefit Now... a neat compromise cou
769.
by brundolf 4y ago
It wasn't very charitable, but neither is the "flavor-of-the-month language" dig
770.
by brundolf 4y ago
Yeah, makes sense. I'm fortunate that my use-case doesn't have to worry about that In general, coming from TypeScript I'd like to see a lot more "duck" types in Rust that describe shapes the compiler already knows h
771.
by brundolf 4y ago
This does need to be solved, but I came up with a pattern in a recent project I'm pretty happy with: - Create all the variants as normal structs - Create enums around different subsets of them that just wrap each struct in a variant of
772.
by brundolf 4y ago
Rust doesn't have the same goals as Python or Go. It remains first and foremost a systems language, where Go is first and foremost a web language. Also: when the package ecosystem is as strong as Rust's, it's less important t
773.
by brundolf 4y ago
Yeah, JS programmers sometimes work around this and similar language gaps by making an inline function and immediately calling it (because that gives you a statement context inside of an expression context, which isn't normally possi
774.
by brundolf 4y ago
Highly disagree on two counts: > that's a symptom of issues with React, not issues with JavaScript IMO keeping as much as possible in an expression-context is preferable, even without React, because it simplifies control-flow and av
775.
by brundolf 4y ago
A problem is that you can only declare intermediate constants in a statement context, not an expression context. And with React, more and more JS devs are spending time in expression contexts Example: return ( <div>
776.
by brundolf 4y ago
This proposal has been languishing for years and years. I'm not sure when it last made progress, but I remember waiting for it with anticipation around 2018
777.
by brundolf 4y ago
Anti-cheat is still a big problem. Most of the games I play with my friends won't run on my steam deck specifically because of that. Really hoping the industry comes together and solves linux support for it; I'm not sure it's
778.
by brundolf 4y ago
Really glad my windows computer is pretty much just for games these days, so I don't have to care too much about a GUI downgrade
779.
by brundolf 4y ago
One complaint about the original was that it was super locked into Apple's ecosystem, which seems valid to me. And the new one supports Matter, so that's an improvement
780.
by brundolf 4y ago
Apple may not want it back because they don't want to deal with refurbing and reselling a niche product, but somebody out there would certainly want it for a decent fraction of the original price. Hardware doesn't get obsoleted as

More ›