estebank

20 ms·

391.
by estebank 2y ago
There are a few projects for Rust only OSes. Redox aims at the desktop, Hubris aims at microcontrollers, to name two I'm aware of. But there's a huge difference between "let's make it easier for driver writers to write c
392.
by estebank 2y ago
Are you aware that RfL is not outsider Rust enthusiasts pushing on the kernel, but rather existing Linux kernel developers wanting to use Rust?
393.
by estebank 2y ago
> This is the same as my issues with Rust, if declaring a new type to represent a number of files isn't as easy as just using a u32 then no one will use it, etc.. #[derive(Copy, Clone, Debug, Hash, PartialEq, Eq)] #[repr(t
394.
by estebank 2y ago
I don't know if "putting lesser languages to shame", but https://hubris.oxide.computer/ is professional grade, built in just a few years. But I absolutely take umbrage at the idea that "build a modern pr
395.
by estebank 2y ago
If you encounter specific diagnostics that are cryptic, file tickets. A lot of things were aware of and we improve them regularly, faster when easy, slower when complex, but we eventually get to them. We can't fix cases we haven't
396.
by estebank 2y ago
Or it could have killed it on the vine because the syntax was too esoteric and would have pushed the target demographic away before they even tried it. It's hard to test the counter factual in this case. A common topic of conversation
397.
by estebank 2y ago
> I say half problem because in my experience fixing it is also beneficial for "specialists". This is critical. Once I realized that even experts didn't necessarily have homogeneous advanced knowledge of the entire langu
398.
by estebank 2y ago
> And the entire ecosystem lacks maturity i.e. the majority of libraries I use are not at version 1. I'm marginally bothered by the reluctance to bite the bullet and accept a 2.0 will happen in the future, but version numbers do not
399.
by estebank 2y ago
> Maybe sometimes the language feels like trying to keep a piece of heavy duty machinery from killing you, but they're willing to wrestle with it for the power you get in return. It's funny because to me there's an analogy
400.
by estebank 2y ago
The same people that are against documenting their APIs when requested by the RfL project would likely reject the idea of adding annotations to C code for (in their eyes) only benefiting RfL.
401.
by estebank 2y ago
> The scenario where someone wants to drive by dump some code, then you reject it, then they offer to maintain it, kind of sucks. That's not what happened here. This was a maintainer that was CCd on a Rust wrapper to a subsystem he
402.
by estebank 2y ago
The Chesterton fence argument is that you need to understand why the fence is there. If you do understand it, and still remove it, it doesn't say that's bad.
403.
by estebank 2y ago
> It’s not like libraries accumulate new bugs and vulnerabilities by not changing. That's not actually true, for libraries that interact with the platform. For example, Mac OS changed some type definition in header files in their ar
404.
by estebank 2y ago
I don't think there was ever a 30i screen. GP probably meant 60 interlaced, which needs two full scans for a change, so an effective 30 full frames per second, but enough for 60 half images. For a Wayland compositor and the entire hard
405.
by estebank 2y ago
Yes, I missed a word. And I believe pretty much everybody else realized what I meant to say. Feel free to point me in the direction of a production grade incremental compiler that can run on Linux, GNU or otherwise.
406.
by estebank 2y ago
Yes, indeed I accidentally forgot about incremental there.
407.
by estebank 2y ago
Note that Mold has no interest in becoming incremental, so there is a big reason there for another linker to exist. I find it kind of embarrassing that MS' linker has been incremental by default for decades, yet there's no product
408.
by estebank 2y ago
I do not subscribe to the "great men" theory of history. Independent rediscovery has happened over and over again. If not him, someone else would have come about with the same discoveries.
409.
by estebank 2y ago
No tool for that exists afaik, but all the pieces to make it are there.
410.
by estebank 2y ago
I do think that there's some work that can be done to improve reporting on our side: cargo should be able to report not just "how many crates are in the dep tree" but rather "how many owners am I depending on" and &
411.
by estebank 2y ago
I see, I have a different mental model for what auditing a dependency means. Auditing is "review the code and release processes of my dependency". In my mind what you describe would be "validating my Software Bill of Material
412.
by estebank 2y ago
> the amount of effort it takes to audit dependencies scales roughly linearly With the lines of code, not the number of dependencies. 10 dependencies of 100 lines of code are arguably easier, but certainly not harder than a single depend
413.
by estebank 2y ago
> You mean like four versions... The two options for cargo here are 1) fail to compile when there's more than one crate-version in the dep tree or 2) allow for there to be more than one and let the project continue compiling. The fo
414.
by estebank 2y ago
Yet another thread where people go "Dependency number too big! Rust bad!" with the level of nuance of my dogs discussing dinner. The full list is linked in the article https://gist.github.com/tisonkun/06550d2d
415.
by estebank 2y ago
Similar thing with my wife and bread. In the US she developed/discovered/exposed a gluten intolerance, to the point that she removed it from her diet entirely, but bread in France is ok for her.
416.
by estebank 2y ago
Or arguing that a bridge shouldn't be built because people don't regularly swim across.
417.
by estebank 2y ago
> I don't know why it feels like you're jumping on me here. I think what you're sensing was terseness of response because I was writing on a phone. > What you're calling an "at grade crossing" is indeed a
418.
by estebank 2y ago
> Less visual obstructions so that oncoming traffic can be seen sooner? This is called daylighting and California passed a law for it https://www.sfmta.com/getting-around/walk/daylighting > Advance the cross
419.
by estebank 2y ago
1) it makes the travel of a pedestrian going straight become a zig zag where you have to weave into streets that you don't care about. You end up minimizing distance for cars but maximizing distance for pedestrians. It should be the ot
420.
by estebank 2y ago
If there is no way of configuring the intersection so that right on red is safe for pedestrians, then the problem is the right on red.

More ›