51–60 of 64 posts
Written in Rust and yet when I downloaded it — admittedly a few months ago now — it segfaulted within a minute of me opening it for the first time. 0/10, not inclined to try again.
Segfaults shouldn't happen in Rust, but there is widespread use of `.unwrap`
Written in Rust and yet when I downloaded it — admittedly a few months ago now — it segfaulted within a minute of me opening it for the first time. 0/10, not inclined to try again.
People who think the programming language magically makes bugs disappear don't know what they're talking about. Yes, Rust makes a few categories of bugs disappear, but there's a vast number of bugs that you can still easily create even using Rust with all linters you can find enabled... just saw on another thread someone complaining a Gemini (poor man's internet) server responded with a Rust panic coming from an `unw…
In Rust’s case, I take it as a promise not to do anything memory-unsafe. Lapce did not keep this promise when I tried it.
Earlier quoted context omitted.
If the operation can fail, that should really be represented in the type, right?
No necessarily. Rust doesn't do that for array indexing (though bound checking is enabled at runtime and will panic if out of bounds), division by zero, numeric overflow and probably many cases where it was deemed to be just too cumbersome.
Earlier quoted context omitted.
> the staying power of a language has implications for the staying power of the project So Emacs' staying power is due to being written in LISP ?!
A affects B, doesn’t mean B only depends on A.
The big lie of open source is "you have the source, so you can extend it and fix bugs yourself". Of course in theory (with enough expertise and motivation) you can do these, but in practice most open source users don't contribute to the project, so the language it is written in is entirely irrelevant.
When was the last time (if ever) you submitted a bug fix (not a report) for an open source tool you are using, let alone joined the project as a contributor?!
Earlier quoted context omitted.
I like knowing something is written in Rust because (1) the staying power of a language has implications for the staying power of the project (how many Ada projects do you see nowadays?) (2) I write Rust so I'm more likely to contribute to this, (3) I care about the safety and speed implications of language choice, but most of all (4) building from source usually isn't a pain with Rust's Cargo, but it is for most oth…
> the staying power of a language has implications for the staying power of the project So Emacs' staying power is due to being written in LISP ?!
My argument is that Rust is certainly going to remain relevant for the next 20 years or so. When this project is no longer maintained, it probably won't be because Rust is no longer being developed, and it probably won't be because nobody writes Rust around.
If Lapce were written in something like Zig or Crystal, I wouldn't feel so certain about that. (Not a knock to Zig or Crystal.)
Earlier quoted context omitted.
> the staying power of a language has implications for the staying power of the project So Emacs' staying power is due to being written in LISP ?!
I don't get the point you're making. Yes, the popularity of technologies is impacted by the popularity of related technologies. My argument is that Rust is certainly going to remain relevant for the next 20 years or so. When this project is no longer maintained, it probably won't be because Rust is no longer being developed, and it probably won't be because nobody writes Rust around. If Lapce were written in somethin…
Just that Emacs was written almost a half century ago, and is still thriving despite being written in a language (LISP) that is basically obsolete.
> My argument is that Rust is certainly going to remain relevant for the next 20 years or so
Maybe, maybe not. Look at how quickly Perl (so promising to begin with) disappeared to be replaced by Python. Many new languages have tried, and continue to try, to replace C++ as a better alternative, and I'm sure the next 20 years will see more popup too. Is Rust the one?
If the likelihood of being around in 20 years with a still up-to-date library/tool ecosystem was the main decision making factor, then Java would probably be a safer bet.
Written in Rust and yet when I downloaded it — admittedly a few months ago now — it segfaulted within a minute of me opening it for the first time. 0/10, not inclined to try again.
Did it crash or actually segfault? Segfaults shouldn't happen in Rust, but there is widespread use of `.unwrap`
Earlier quoted context omitted.
> the staying power of a language has implications for the staying power of the project So Emacs' staying power is due to being written in LISP ?!
A affects B, doesn’t mean B only depends on A.
“Irrelevant” is a very strong statement. It claims no effect at all. A single example does not justify the claim. You need at least some statistical evidence to support that claim.
For your last question, yes I do. I sometimes take over the abandoned project to maintain it too. Some open source users never contribute in any way, some do. I’m not sure why there’s a need to dismiss the existence of the latter kind of users. No one is claiming all users should be like that.
Earlier quoted context omitted.
A affects B, doesn’t mean B only depends on A.
No, of course not, but the example does show that programming language is pretty much irrelevant. The big lie of open source is "you have the source, so you can extend it and fix bugs yourself". Of course in theory (with enough expertise and motivation) you can do these, but in practice most open source users don't contribute to the project, so the language it is written in is entirely irrelevant. When was the last t…
Earlier quoted context omitted.
A affects B, doesn’t mean B only depends on A.
“Has implications” is a very weak statement. Even if it is a very small effect but measurable fits that description. “Irrelevant” is a very strong statement. It claims no effect at all. A single example does not justify the claim. You need at least some statistical evidence to support that claim. For your last question, yes I do. I sometimes take over the abandoned project to maintain it too. Some open source users n…