nu11ptr

7 ms·

61.
by nu11ptr 8mo ago
While unfortunate, to me this just says any user requested features aren't going to get merged anytime soon. As is, it already runs on windows/linux/mac, and will need to do so maturely for Zed to function. Therefore, to me,
62.
by nu11ptr 8mo ago
IMO, as long as Zed uses it, we are safe. If it doesn't, we aren't. I'm keeping it that simple.
63.
by nu11ptr 8mo ago
Yeah, running just gpui is kinda like writing a react app without a component library. It is going to be on you to implement all your components. All of those are handled. Run the "story" app. It is very impressive IMO. Components
64.
by nu11ptr 8mo ago
I remember when that came out, but I'm not sure I understand the concern. They use GPUI, so therefore they MUST keep it working and supportable, even if updating it isn't their current priority. Or are you saying they have a close
65.
by nu11ptr 8mo ago
Really? It seems better than ever to me now that we have gpui-component. That seems to finally open doors to have fully native guis that are polished enough for even commercial release. I haven't seen anything else that I would put in
66.
by nu11ptr 8mo ago
From the PR, it sounds like the switch to WGPU is only for linux. The team was reluctant to do the same for macOS/Windows since they felt their native renderer on those platforms was better and less memory intensive.
67.
by nu11ptr 8mo ago
If I recall, Arrow is more or less a standardized representation in memory of columnar data. It tends to not be used directly I believe, but as the foundation for higher level libraries (like Polars, etc.). That said, I'm not an expert
68.
by nu11ptr 8mo ago
> If we look at segment 0800, we see the smoking gun: in and out instructions, meaning that the copy-protection routine is definitely here, and best of all, the entire code segment is a mere 0x90 bytes, which suggests that the entire rou
69.
by nu11ptr 8mo ago
I feel like the title is a bit misleading. I think it should be something like "Using Rust's Standard Library from the GPU". The stdlib code doesn't execute on the GPU, it is just a remote function call, executed on the
70.
by nu11ptr 8mo ago
Exactly what I was thinking. I mean how can you produce something, esp. in bulk, when the exact ingredients and quantities aren't known? Assuming it is made in a typical factory, the machines would have to be programmed and that would
71.
by nu11ptr 9mo ago
I am a pretty serious "Rustacean", but I like to think "for the right reasons". A rewrite in Rust of the main project would make very little sense, unless there is some objective the project wants that can't be met
72.
by nu11ptr 9mo ago
> by reading that the memory safe Rust language has and can cause undefined behaviour Only unsafe blocks can cause undefined behavior. The memory safe portion of Rust that most program in cannot cause UB. If you use "forbid unsafe&q
73.
by nu11ptr 9mo ago
Thank you to those who continue to develop Miri. It is a great tool for those of us that have crates that need to use unsafe. While nothing will give 100% confidence in the lack of UB, Miri is a great start.
74.
by nu11ptr 9mo ago
> You've created a logical justification for a myopic, misanthropic world view. Nobody said it wouldn't be nice, but that it does not confer "obligation". This is the key word. I would argue a world where people do th
75.
by nu11ptr 9mo ago
Go is one of the simplest languages there is. Not always easy to create something at scale IMO, but certainly simple.
76.
by nu11ptr 10mo ago
True, I forgot about unsafe package. They would probably have to make it a Go 2 thing and add indirection to raw pointers or a need to "pin" them. Since pinning would already exist for CGo I suspect that would make more sense and
77.
by nu11ptr 10mo ago
A better route for something like Go IMO is to move to a compacting collector, this would allow them to move to a bump allocator like Java for super fast allocations and would make deallocation effectively "free" by only moving li
78.
by nu11ptr 10mo ago
It is also equally odd to me that people want to cling so hard to C, when something like Rust (and other modern languages for that matter), have so much nicer eco systems, memory safety aside. I mean C doesn't even have a builtin hasht
79.
by nu11ptr 10mo ago
I haven't use Calibre in several years. What does it use AI for?
80.
by nu11ptr 10mo ago
> You could have done that in Rust but you wouldn't, because the allure of just typing a single character of ? is too strong. You could have done that in Go but you wouldn't, because the allure of just typing two words
81.
by nu11ptr 10mo ago
> Go has full automatic memory management and Rust doesn't It doesn't? In Go, I allocate (new/make or implicit), never free. In Rust, I allocate (Box/Arc/Rc/String), never free. I'm not sure I see the d
82.
by nu11ptr 10mo ago
Interesting. It is semi-rare that I meet someone who knows both Rust and Go and prefers Go. Is it the velocity you get from coding in it? I have a love/hate relationship with Go. I like that it lets me code ideas very fast, but my resu
83.
by nu11ptr 10mo ago
> I don't find that to be the case. It may be slower for a month or two while you learn how to work with the borrow checker, but after the adjustment period, the ideas flow just as quickly as any other language. I was responding to
84.
by nu11ptr 10mo ago
I disagree. I've been writing heavy Rust for 5 years, and there are many tasks for which what you say is true. The problem is Rust is a low level language, so there is often ceremony you have to go through, even if it doesn't give
85.
by nu11ptr 10mo ago
> you sort of come to understand "this goo at the end of the expression is just coercing the return value into whatever alternate goo the function signature dictates it needs", which is not at all the same thing as careful erro
86.
by nu11ptr 10mo ago
> And yet somehow the internet went down because of a program written in rust that didn’t validate input. Tell me which magic language creates programs free of errors? It would have been better had it crashed and compromised memory integ
87.
by nu11ptr 10mo ago
Nah, you just need to use `map_err` or apply a '.context' which I think anyhow can do (and my crate, `uni_error` certainly can otherwise).
88.
by nu11ptr 10mo ago
That isn't apples to apples. In Rust I could have done (assuming `anyhow::Error` or `Box<dyn Error + Send + Sync>` return types, which are very typical): let mut file = File::create("foo.txt") .map_err(|e|
89.
by nu11ptr 10mo ago
> might as well have used C, the dollar cost is the same. When your unsafe area is small, you put a LOT of thought/testing into those small blocks. You write SAFETY comments explaining WHY it is safe (as you start with the assumptio
90.
by nu11ptr 10mo ago
> I would assume trivial means the default approach works for most cases. Perhaps mutable global variables are not a common use case. Unsafe might make it easier, but it’s not obvious and probably undesired. I'm a Rust fan, and I wo

More ›