simonask

17 ms·

391.
by simonask 1y ago
> And Linux won't arbitrarily irrevocably brick your computer because of an automatic update. To the average user, it absolutely will . Unless they happen to run on particularly well-supported hardware, the days of console tinkerin
392.
by simonask 1y ago
You are reiterating the same points, and they are still wrong, I’m sorry.
393.
by simonask 1y ago
Ok, I'm going to call it here. I don't know what this comment (or account) is, and I'm not particularly interested in a bad faith flamewar.
394.
by simonask 1y ago
Whether it’s “stupid” remains to be seen. I personally would not have made this choice at this point in time, but the way some people seem to consider “Rust program has a bug” to be newsworthy is… odd.
395.
by simonask 1y ago
I suspect you miss the point. Somebody is attempting to characterize the Rust community in general as being similar to other programming communities that value velocity over stability, such as the JS ecosystem and others. I’m pointing out t
396.
by simonask 1y ago
So the problem here is that it is almost entirely wrong. There is no reference count anywhere in the borrow checker’s algorithm, and you can’t do the things with borrows that you can do with reference counting. It’s just not a good mental m
397.
by simonask 1y ago
Nobody - least of all the authors of uutils - is forcing Ubuntu to adopt this change. I personally feel like it's a pretty radical step on Ubuntu's part, but they are free to make such choices, and you are free to not use Ubuntu i
398.
by simonask 1y ago
The high level of visibility that this incident received is a great example of the point I'm making. Can you name one more?
399.
by simonask 1y ago
I agree with your points, except that "compile time reference counting" is not a thing. I'm not sure what that would even mean. :-)
400.
by simonask 1y ago
Yeah, sweeping hot takes with very little to back them up do tend to get downvoted. More than anything, the Rust community is hyper-fixated on stability and correctness. It is very much the antithesis to “move fast and break things”.
401.
by simonask 1y ago
Other people are allowed to do whatever they want.
402.
by simonask 1y ago
With current GPU architectures, this seems unlikely. Like, you would need a ton of cells with almost perfectly aligned inputs before even the DMA bus roundtrip is worth it. We’re talking at least hundreds of thousands of cells, depending
403.
by simonask 1y ago
It is the opposite of what a closure typically means, because it is precisely not “closing” over its lexical scope. It’s an interesting feature to be sure, and it enables some really beautiful things, but it also enables some incredibly d
404.
by simonask 1y ago
Have never had any trouble in Scandinavia or Germany. There are regions of Europe with less developed infrastructure, but the situation is identical for all car makers.
405.
by simonask 1y ago
That's what I'm saying: In Ruby, you can transplant code from a closure out of its lexical scope and evaluate it as if it was defined in a different environment. Should you ever do this? No. But you can. :-)
406.
by simonask 1y ago
They are closures. But Ruby can do interesting and slightly reckless things, like transplanting a closure into a different evaluation scope. It’s very powerful, and also very dangerous in the wrong hands.
407.
by simonask 1y ago
… And then you completely close all instances of the app that you need to see the changed environment variable, including any integrated terminal processes within that app. And then you relaunch all instances of that app and recover whateve
408.
by simonask 1y ago
The missing piece is that it would still force you to make even larger types in many cases, such as `Result<Large, Error>`. Essentially the problem is composability. If you are building a large type from a sequence of other large type
409.
by simonask 1y ago
I'm editing a UTF16-LE file right now. Works just fine. It does show the BOM at the beginning, though.
410.
by simonask 1y ago
There's many ways to represent it, but the "sub" in "subpixel" does tell us that someone along the way needs to deal with fractional pixels. :-)
411.
by simonask 1y ago
Spitballing here, but subpixel rendering also requires integration with the rendering pipeline, specifically that you have the infrastructure to pass fractional offsets to the rasterization engine based on the concrete screen position of a
412.
by simonask 1y ago
It’s not as if such bugs are unheard of for Windows users, and certainly not Linux users. But I’ve certainly never struggled with getting WiFi to work on a Mac, or struggled with getting it to sleep/wake, or a host of other problems yo
413.
by simonask 1y ago
As the other person pointed out, these are two different things. Sanitizers add runtime checks (with zero consideration for performance - don’t use these in productions). Static analysis runs at compile time, and while both GCC and Clang ar
414.
by simonask 1y ago
C is simple. As a result, programming in C is not simple in any way.
415.
by simonask 1y ago
This is a bit of a misunderstanding. Safe code is just code that cannot have Undefined Behavior. C and C++ have the concept of "soundness" just like Rust, just no way to statically guard against it.
416.
by simonask 1y ago
What is a “typical Linux keyboard”?
417.
by simonask 1y ago
I mean, it would be perfectly fine if it wasn’t for the fact that it’s not perfectly fine…
418.
by simonask 1y ago
The larger point is what the T stands for: Text. Tree structures just aren’t very user-friendly representations of text, and it’s supposed to be “hypertext” after all. :-)
419.
by simonask 1y ago
Interesting read. Another interesting fact is that `setenv()` is fundamentally broken on POSIX, and should essentially never be called in library code. In application code, it should be called only in the absence of any alternative, and cer
420.
by simonask 1y ago
zł has entered the chat. ;-) (The Polish Ł is typically not easily typable of non-Polish keyboards.)

More ›