3 ms·
How would my quote apply to people who do that kind of work? The whole article is about people that <<don't>> do that.
by oblio 5y ago
How would my quote apply to people who do that kind of work?
The whole article is about people that <<don't>> do that.
- md8z 5y agoIt's pretty rude to insult someone by calling them an "attention deficit teenager" regardless of what they're working on. I would recommend against quoting that article.
- bmn__ 5y agoI see you chose to ignore what prompted the rant. Is it deliberate?
- md8z 5y agoI generally try to avoid responding to rants because every time I do that, the author gets angry and starts complaining at me. In my experience, people who rant are just frustrated and blowing off steam, and are not trying to be taken seriously or start a constructive dialogue. If a person actually has some leadership/direction and a solid grasp on the full picture then there is no need to rant. But you may want to read my comment here: https://news.ycombinator.com/item?id=28856907 https://news.ycombinator.com/item?id=28856907
- PaulDavisThe1st 5y agoWhere we put our attention says a lot. People like Takashi get almost zero attention, because so many people spend their time blabbering about people doing "sexy" stuff. JWZ does this too. I believe we'd be much better off if we tried to do more ignoring of the flashy stuff we don't like and instead support and laud the unflashy stuff and the people who do it.
- sho_hn 5y agoI'd say what's interesting is that the people who don't do that are probably overrepresented within the Linux community. The average tenure of devs there is in excess of the average tenture of most tech employees of today. It might be more meaningful to measure continuity as provided by organizations (i.e. communities vs. corporations, for example) as they address turnover, but I'm not so sure. Frankly tech churn seems to be about equal on both sides. Other systems have revamped their audio stacks on occasion as well. It's the economics/business models that favor certain kinds of finish, especially backwards compatibility. I'd further submit the Linux story there has improved over time. For example PulseAudio didn't attempt to provide much of an upgrade path to apps using aRts and ESD (its predecessors), but PipeWire provides continuity for apps written against ALSA, PulseAudio and JACK. And as PulseAudio and JACK were difficult to run side-by-side at times, it actually reduces fragmentation as well. By aligning audio and video device access within one system it also generalizes system behavior.