kibwen

16 ms·

241.
by kibwen 4mo ago
> Therefore, the standard forces the compiler to generate "safe" code for the switch. Safety, as usual, has cost, so the switch version ends up doing a bit more per loop iteration. Safety only has a cost in this case because
242.
List of video game console color palettes(en.wikipedia.org)
2 points by kibwen 4mo ago|0 comments
243.
by kibwen 4mo ago
> Rust forces you to either (a) re-invent the wheel (yet again !) This is inherent to the domain of systems programming. One-size-fits-all solutions only suffice until you need extreme performance. So, for example, Rust provides a basi
244.
by kibwen 4mo ago
> Its limited compared to Go as well. It depends on perspective. Go is tailored for writing backends, so it's great that it provides things like net/http (we could also interpret cause and effect inversely here; Go provides n
245.
by kibwen 4mo ago
To paraphrase Mitch Hedberg, this is the sort of thing that is now possible with AI. It used to be possible, but it still is, too.
246.
by kibwen 4mo ago
If you don't actually take the time to write something manually inside the card, that's as thoughtless asking an LLM to generate a birthday message to someone.
247.
by kibwen 4mo ago
The main reason to allow users to set seeds manually is to allow players to share seeds among themselves. And the reason that players want to share seeds is because players will find exceptionally rare seeds that other players might want to
248.
by kibwen 4mo ago
Frankly, it should be a crime, a felony even, to purchase something if you haven't seen an ad for it beforehand. Think of the poor middlemen!
249.
by kibwen 4mo ago
I can assure you that Rust will never have a ++ operator. Not only is it semantically bizarre, it's entirely unnecessary in a language where iteration is overwhelmingly performed via iterators rather than via manually incrementing arra
250.
by kibwen 4mo ago
You don't need linker hacks to control what happens before main in Rust. You can disable the default runtime setup with `#![no_main]` in your crate root, and then manually designate a starting point via an unmangled function named appr
251.
by kibwen 4mo ago
> Is it the end result that matters, or the process of creating it? One of the main reasons that art is valuable is in its ability to communicate emotions. Good art has the ability to serialize emotions within the artist and deserializ
252.
by kibwen 4mo ago
You are not morally obliged to extend rights to anyone who does not respect your rights. This is tit-for-tat, the foundational principle of functional societies. Unleashing a bot on a group of people is a grievous disrespect that shows you
253.
by kibwen 4mo ago
> nobody likes to tear down the interstate Lots of urban areas in the US have been resisting, tearing down, and/or relocating major roads since the freeway revolts of the 1970s: https://en.wikipedia.org/wiki/H
254.
by kibwen 4mo ago
Whether or not the successor was a friend of Dye isn't relevant here. Let's say for a moment that Apple's design woes were a result of Dye. Dye was appointed by Apple's leadership. The conclusion would that Apple's
255.
by kibwen 4mo ago
Years ago I read the entirety of Starfish on the gloriously Geocities-ass website linked here, and I highly recommend it. Even as someone who has a hard time keeping focus, it sucked me in.
256.
by kibwen 4mo ago
> I don’t know if all the untalented hacks are gone, but the untalented magazine-designer hacks with clout and influence all left with Alan Dye. As usual for Gruber, this is fanboy cope. Dye may be a convenient scapegoat, but he was no
257.
by kibwen 4mo ago
Meanwhile, 40,000 years ago: "Me and my daughter just started to feed and befriend a wolf skulking near our camp."
258.
by kibwen 4mo ago
> smart but evil Sadly I have yet to see evidence that something can be smart without being evil.
259.
by kibwen 5mo ago
> Perhaps control flow isn't the right term, maybe non-trivial would be better? Indeed, there are plenty of valid reasons to be wary of operator overloading, such as the risk that someone might insert a network call into your vect
260.
by kibwen 5mo ago
Overloadable operators are not an instance of hidden control flow. Overloadable operators represent a user-defined function call, and thus can't influence control flow any more than a regular function. And if regular functions can&#x27
261.
by kibwen 5mo ago
> To the static typing folks: leave my dynamically typed languages alone Surely you understand that the push to add types to dynamically-typed languages comes from dynamic-typing folks, not from static-typing folks. People who are deep
262.
by kibwen 5mo ago
There's nothing about embedded development in Rust that would make it more reliant on linker scripts than any other language. Github's count is misleading here.
263.
by kibwen 5mo ago
I get the impression that even the definition of "anarchy" itself is subject to anarchy, with lots of disagreements and infighting. The more even-keeled anarchists that I've seen stress that they're not against hierarchi
264.
by kibwen 5mo ago
Better question, why would you need a CEO?
265.
by kibwen 5mo ago
Arena allocators are great for certain use cases, but they don't provide any solutions to memory unsafety; they don't do anything for use-after-free, they don't do anything for buffer overruns, they don't address any sou
266.
by kibwen 5mo ago
No. Rust is excellent for beginner programmers dipping their toes into systems programming for the first time. Imagine you have a million-line C codebase, and a brand-new junior hire. Are you going to unleash them on the codebase unsupervis
267.
by kibwen 5mo ago
Rust's library facilities are excellent for writing unsafe code with. Rust is very precise about which safety invariants must be upheld by which APIs, and does an excellent job documenting these, an excellent job at linting against imp
268.
by kibwen 5mo ago
> But unless you plan on rewriting the entire Rust ecosystem, you're going to be dealing with invisible failure points in Rust code that you would not be dealing with when writing the equivalent Zig code. That's what Rust&#x2
269.
by kibwen 5mo ago
You can certainly write data structures in Zig that swallow allocation failures rather than surfacing them. We're talking about library-level concerns, not language-level concerns. Both Rust and Zig give you the power to allocate raw m
270.
by kibwen 5mo ago
Rust doesn't stop you from checking if memory allocation has failed. Its libstd provides many operations that don't bother to surface memory allocation failure (for the reasons given above), but that's why Rust provides a lib

More ›