|
|
Subscribe / Log in / New account

KernelCI now testing Linux Rust code (Collabora blog)

KernelCI now testing Linux Rust code (Collabora blog)

Posted Dec 11, 2022 13:53 UTC (Sun) by pizza (subscriber, #46)
In reply to: KernelCI now testing Linux Rust code (Collabora blog) by khim
Parent article: KernelCI now testing Linux Rust code (Collabora blog)

> Time required to push update matters, too. What good is you “good source” if you can not obtain what you want/need from it?

Over the course of my career, I've noticed the folks who complain the loudest about regressions are also the same ones complaining about updates taking too long.

Ask them to prioritize "speed" or "stability", and it will always be the opposite of what they currently have. If "cost" is also included in the mix, they'll _always_ complain that it's not zero.


to post comments

KernelCI now testing Linux Rust code (Collabora blog)

Posted Dec 11, 2022 14:50 UTC (Sun) by khim (subscriber, #9252) [Link] (1 responses)

> Over the course of my career, I've noticed the folks who complain the loudest about regressions are also the same ones complaining about updates taking too long.

IOW: some people loudly complain, some people silently suffer.

And I'm proud to admit that I complain about both. Why? Because the way to reduce problems with regressions is to make updates less painful!

It's not a big deal for me if rustc or any other fast-moving component intermittently regresses: I just report the issue, roll it back for a few days and after few days (if regression is fault on the rustc side) everything is fixed.

Even if it's my fault (for using some unstable feature or something) I don't spend too much time on these regressions — because they are limited.

On the other hand every time I need to upgrade gcc or debian or any other project which releases updates once a year or, even worse, once per 2-3 years… it's a pain: regressions are numerous, I hit them all at once and even if each one, individually is “not a big deal”… cumulatively they are a problem.

> Ask them to prioritize "speed" or "stability", and it will always be the opposite of what they currently have.

It's because of false dichotomy. Once upon time MS IE was both a pinnacle of web browsing and epitome of stability. There was very stable steam of articles (and even books!) which described its various bugs and deficiences.

Today that literature genre have mostly dried up: if something is crazy bad then you report it and it's easier fixed or, at least, acknowledged.

I don't perceive it as a problem, although some people miss time where they both needed to collect pile of hacks needed for MS IE 6 and could afford to collect such pile because MS IE 6 was destined to stay with us for decade or more.

> If "cost" is also included in the mix, they'll _always_ complain that it's not zero.

Again: they are no saying anything others are not thinking, do they?

KernelCI now testing Linux Rust code (Collabora blog)

Posted Dec 11, 2022 17:31 UTC (Sun) by pizza (subscriber, #46) [Link]

> Once upon time MS IE was both a pinnacle of web browsing and epitome of stability.

Those were never simultaneously true. I'm not sure if the former was _ever_ true in anyone's eyes but Microsoft's.

> Again: they are no saying anything others are not thinking, do they?

They're not willing to acknowledge, much less pay for, the price of what they want.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds