Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
estebank
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
15 ms
·
241.
▲
by
estebank
11mo ago
One person's terrorist against the Franco government is another person's freedom fighter against the Franco regime.
242.
▲
by
estebank
11mo ago
They tried that during the Chicago development and discarded the idea due to multiple problems with how humans work. Two different UIs meant that you had to learn them separately, you didn't have a slow ramp from one to the other, one
243.
▲
by
estebank
11mo ago
There's a different question too, that I think is more important (for any language): how much of the language do you need to know in order to use it effectively. As another poster mentioned, the issue with C++ might not be the breath
244.
▲
by
estebank
11mo ago
The people writing C++ either don't need much convincing to switch because they see the value or are unlikely to give it up anytime soon because they don't see anything Rust does as being useful to them, very little middle ground.
245.
▲
by
estebank
11mo ago
For the latter, the term you want to search for is polymorphization. It is about making the compiler do the work that those manual façades do, automatically.
246.
▲
by
estebank
11mo ago
You're forgetting about the shutter angle. A large shutter angle will have a lot of motion blur and feel fluid even at a low frame rate, while a small shutter angle will make movement feel stilted but every frame will be fully legible,
247.
▲
by
estebank
11mo ago
If the only way of triggering spatial memory unsafety in C++ was vector[i] and that operation was defined to always interrupt execution, then yes, C++ would be considered memory safe. But that is not the case. The equivalent of vector[i]
248.
▲
by
estebank
11mo ago
Hell, some baggy pants could fit an entire SNES in them! https://youtu.be/rY9uitdQIpg?si=5RfMcQvFFvS_GadJ
249.
▲
by
estebank
11mo ago
This is true of almost everything: it's not that Zig or Rust are unique on most features. Most of them have existed in one shape or another before. The praise they receive is because of the level of polish their design and implementati
250.
▲
by
estebank
11mo ago
The US taxes on global income all citizens, even those living abroad. The only way to avoid that is to give up your citizenship, but then you have to pay an exit tax as if you had liquidated your assets. Even if you go to a country with a t
251.
▲
by
estebank
11mo ago
> its ugly as sin Uncalled for and subjective. Certainly plenty of people call Rust's syntax ugly. Discussing syntax and not semantics is a waste of time. > has zero use case other than mingling with legacy c code So it has a use
252.
▲
by
estebank
11mo ago
A backtrace won't give you the values of variables needed to identify that. I did specify "succinctly as possible with all the information necessary for a human to be able to solve the issue". An error that doesn't have
253.
▲
by
estebank
11mo ago
Fil-C should have a(n on by default) mode where collecting an unfreed allocation is a crash, if it doesn't already.
254.
▲
by
estebank
11mo ago
That strategy is ok if the expected user is a fellow developer. For anyone else, a back trace is spilling your guts on the floor and expecting the user to clean up. A tool for wider usage should absolutely detect the error condition and exp
255.
▲
by
estebank
11mo ago
I guess the confusion happens because MIR: the representation, mir: the stage, stable MIR: the potential future API interface for hooking into the compiler stage, and miri: the MIR interpreter all share pretty much the same name. Const eval
256.
▲
by
estebank
11mo ago
The annoying experience with the borrow checker is when following the compiler errors after making a change until you hit a fundamental ownership problem a few levels away from the original change that precludes the change (like ending up w
257.
▲
by
estebank
11mo ago
> Rust also supports reference counting GC, but that is more _verbose_ to use... It should be _simpler_ to use in my view, similar to Python. The main disadvantage of Rust, in my view, is that it's verbose. I think there's spac
258.
▲
by
estebank
11mo ago
Miri does do that? It is not aware of the distinction to begin with (which is one of the use cases of the tool: it lets us exercise safe code to ensure there aren't memory violations caused by incorrect MIR lowering). I might be mist
259.
▲
by
estebank
11mo ago
Luxembourg has had free public transport since 2020.
260.
▲
by
estebank
11mo ago
I think they meant on unstable features which might yet change their semantics. A stable API relying on unstable implementation is common in Rust (? operator, for example), but that is entirely dependent on having a good idea of what the ev
261.
▲
by
estebank
11mo ago
Generators in particular has been blocked on the AsyncIterator trait. There are also open questions around consuming those (`for await i in stream`, or just keep to `while let Some(i) in stream.next().await`? What about parallel iteration?
262.
▲
by
estebank
1y ago
The disagreement is the difference between "there's an group [the Rust community] going around pushing/bullying projects to use Rust" and "project maintainers want to start using Rust". Those two things get con
263.
▲
by
estebank
1y ago
Even if they are, they are not updating to latest Debian stable.
264.
▲
by
estebank
1y ago
Obligatory link to the in-progress forum post about the development of The Return of the Obra Dinn's dithering effect: https://forums.tigsource.com/index.php?topic=40832.msg136374... The difficulty for dithering on an
265.
▲
by
estebank
1y ago
>>> Zig is more enjoyable than Rust >> Why is that? > Zig is more enjoyable than Rust You didn't really leave the GP more informed than before.
266.
▲
by
estebank
1y ago
To expand on the sibling comments, this is why Rust doesn't do implicit type conversions that could allocate: https://groups.google.com/a/chromium.org/g/chromium-dev/c/EU...
267.
▲
by
estebank
1y ago
I would go as far as saying that 90% of managing the project is properly communicating, discussing and addressing the ways in which Rust sucks. The all-hands in NL earlier this year was wall to wall meetings about how much things suck and w
268.
▲
by
estebank
1y ago
> You are responsible for testing the code you write, not the one that actually runs. This is not correct for every industry.
269.
▲
by
estebank
1y ago
In safety critical spaces you need to be able to trace any piece of a binary back to code back to requirements. If a piece of running code is implicit in code, it makes that traceability back to requirements harder. But I'd be surprise
270.
▲
by
estebank
1y ago
The problem with advanced modes is that it is easy for a chaos monkey to get into them, and at scale that will happen all the time. A mitigation for advanced modes is to have a big bright red "get me the hell out of this to a normal st
More ›