Jarkko Sakkinen
jarkko
It is slow, tedious, complicated and sometimes even quite discouraging but if you are successful then you are also doing something of high measurable value. And by going through the long and hard path also the end users will get the governance of long-term support, which they IMHO deserve.
At least for me the end user is the king of the hill, not developers. We need to do the hard and nasty part.
#rustlang #opensource
1
0
2
Caleb Maclennan
alerque@mastodon.social@jarkko I'd knock a few nines off that number but in broad strokes this is true. The tendency to rush off and build from scratch in a new favored tool is not unique to Rust either, FOSS projects are plagued with the syndrome. But also some of them do just need scrapping and starting over: bad crufty code plus bad project management isn't a good foundation to build on.
1
0
1
For instance, I like that bat has syntax highlighting but I would scrape it any day if GNU's version added the same feature, and I would not tbh care if it was implemented in Rust or not. This sort of culture drives to loose commitment and saturated software ecosystem,.
This article really never gets old: https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/
1
0
0
it actually does the opposite: it improves compatibility because e.g. the same prompt translates from something like bash to something like powershell.
1
0
0
@alerque Actually (and this is literal fact) before I did one day cargo install bat, I had an alias for along the lines of cat <file> | vim -R - sort of thing so it was literally just way to shortcut that and not much else.
The way Rust community looks at a “change” is sort of “this would nicer way to do this”. The way kernel community looks at a “change” is more like “we have this alarming situation that we need to absolutely deal with right here an right now or data centers or whatnot will be doomed”.
And even my fav language C is in the end for me an opcode generator, not more or less. Rust is yet another opcode generator with static analysis built-in. I just vote for the tech first and totally disregard “language level” kind of merits. What works the stuff that goes best to the cores best WFM me best in the end :-)
1
0
0
This rapidness might work for user space but especially for core kernel features feels a bit brutal to say the least...
I'm actually just opening my views because in LKML I see "yes Rust" and "please no Rust" so trying to address "in-between-but-doubtful-of-Rust" camp's concerns :-)
1
0
0
0
0
0