ChrisSD

6 ms·

31.
by ChrisSD 9mo ago
Huh, I've been using Zed for awhile now and never even noticed it until you mentioned it. Fortunately there's a setting to remove it.
32.
by ChrisSD 10mo ago
Do you have plans for handling C FFI without "unsafe"? Will it require some sort of extension module written in C/C++/Rust?
33.
by ChrisSD 10mo ago
Why do you feel uncomfortable? Why do you think anyone is trying to make you feel uncomfortable?
34.
by ChrisSD 10mo ago
It's ok to be strange. It's ok to be bizarre. Be free. I do not understand the desire for everybody else in the world to act exactly like you. Variety is the spice of life.
35.
by ChrisSD 10mo ago
For sure, there are other hardware requirements a 2017 CPU may fail.
36.
by ChrisSD 10mo ago
It's beside the point of the article but... > The hardware limitation is specifically TPM 2.0 Almost every even half decent CPU made in the last decade does have TPM 2.0, albeit for some strange reason OEMs used to ship with it disa
37.
by ChrisSD 10mo ago
To be clear, Ubuntu did nothing. This is a third party implementation that Ubuntu decided to ship in their OS.
38.
by ChrisSD 10mo ago
That study only says that most Americans think they interact with AI at least a few times a week (it doesn't say how or if it's intentional). And it also says the vast majority feel they have little or no control over whether AI i
39.
by ChrisSD 10mo ago
Windows also has uuids. E.g.: \\.\Volume{3558506b-6ae4-11eb-8698-806e6f6e6963}\
40.
by ChrisSD 1y ago
They're using slide rule users as a stand-in for serious mathematician as opposed to people who incidentally use mathematics. It makes some sense in historical context but becomes a bit anachronistic after the invention of electronic c
41.
by ChrisSD 1y ago
^_^ sucks when you actually need to talk about emoji though :/
42.
by ChrisSD 1y ago
Tbh, the rights and wrongs aside, I suspect "everyone" is complaining about it because it's the easiest thing to talk about. Much like how feature discussions tend towards bikeshedding.
43.
by ChrisSD 1y ago
That's an entirely different issue. The kb's of overhead for backtrace printing and the format machinery is fixed and does not grow with the binary size. All combined it wouldn't account for anywhere close to 1mb let alone 10
44.
by ChrisSD 1y ago
Tbh I really don't think it matters what the letters stand for.
45.
by ChrisSD 1y ago
That sounds like they were mandated to shoehorn "AI" into their description in some way. Because it is indeed a non sequitur.
46.
by ChrisSD 1y ago
More or less, yes. It is guaranteed that tier 2 at least builds so they'll be a nightly available every day though it's possible they might have a serious bug. To be honest though that's always a risk for nightlies even with
47.
by ChrisSD 1y ago
To be clear, tier 2 targets are still expected to be well supported. It just doesn't require CI to pass after every PR (meaning PRs aren't blocked on fixing tier 2 specific issues). However, the target is officially distributed an
48.
by ChrisSD 1y ago
In my experience every developer, company, team, sub-team, etc has their own "library" of random functions, utilities, classes, etc that just end up being included into new projects sooner or later (and everyone and their dog has
49.
by ChrisSD 1y ago
huh?
50.
by ChrisSD 1y ago
I think the two basic synchronisation primitives are atomics and thread parking. Atomics allow you to share data between two or more concurrently running threads whereas parking allows you to control which threads are running concurrently.
51.
by ChrisSD 2y ago
A safe API would look a lot like Windows' GetEnvironmentVariable and SetEnvironmentVariable https://learn.microsoft.com/en-us/windows/win32/api/winbase/... https://learn.microsoft.co
52.
by ChrisSD 2y ago
It can only synchronize if everything using is Rust's functions. But that's not a given. People can use C libraries (especially libc) which won't be aware of Rust's locks. Or they could even use a high level runtime with
53.
by ChrisSD 2y ago
In the Rust std, `set_var` and `remove_var` will correctly require using an `unsafe {}` block in the next edition (2024). The documentation does now mention the safety issue but obviously it was a mistake to make these functions safe origin
54.
by ChrisSD 2y ago
No but it doesn't use C library values so it doesn't matter. E.g. getting the command line arguments is done via calling `GetCommandLineW` so it doesn't use argv or argc. This is actually necessary because Rust cannot assume
55.
by ChrisSD 2y ago
That's the "vcruntime" not the "ucrt". There has been a distinction since the ucrt was made an official part of the OS. It's very easy to make a win32 program without the ucrt filesytems APIs so long as you don
56.
by ChrisSD 2y ago
Rust's standard library basically never uses ANSI APIs. The article doesn't demonstrate any attack that works against Rust. If they do have one I'd highly recommend reporting it. Of course, Rust can't control what happen
57.
by ChrisSD 2y ago
Rust 1.0 was released in 2015 making it almost ten years old. Rust, unlike Go, was largely developed in public. It also changed significantly between it's initial design and 1.0 so it feels like "cheating" to count pre-releas
58.
by ChrisSD 2y ago
> Some can try Rust does this with standard types even. "Parse, don't validate" is the answer to the question: why does Rust have so many string types? Of course you can hack around this using `unsafe` but, as you say, in
59.
by ChrisSD 2y ago
The usual complaint is that there has been little progress on async and webdev in Rust itself since 2018 so it's odd to hear the reverse complaint. Though I would add that Rust's async is not just about webdev; it has had success
60.
by ChrisSD 2y ago
On Pro it would be better to use the group policy editor. As a bonus this also ensures the setting survives updates, which is not always a given for raw registry edits.

More ›