Re:We Need to Save What Made Linux and FOSS Possible
by anonymou2 on Thursday May 09, 2019 @04:24AM
(#19866368)
I, I, I, I, I, all I care, .... that's really the problem that we face.
Re:We Need to Save What Made Linux and FOSS Possible
by Crinus on Thursday May 09, 2019 @06:17AM
(#19866842)
> Who cares.
When the "new" tool is worse than the "old" tool, i care (and yes, the "new" tool can be worse - and often is - yet displace the "old" one, not because of its quality, but because of external reasons - like the developers of the "old" tool being unable to sustain its development).
Re:We Need to Save What Made Linux and FOSS Possible
by detaro on Thursday May 09, 2019 @04:59AM
(#19866527)
> If WordPress goes there's five million other blogging platforms I can switch to.
Have you done a full migration of a grown Wordpress blog to another system, without breaking stuff? It's not something you do on a weekend or two. Changing away from a tool that holds lots of data and configuration is expensive.
Re:We Need to Save What Made Linux and FOSS Possible
by kazinator on Friday May 10, 2019 @02:26PM
(#19880738)
Or, regarding his other remark, a migration of hundreds of thousands of lines of code from gcc to something else.
Re:We Need to Save What Made Linux and FOSS Possible
by ahartmetz on Thursday May 09, 2019 @04:38AM
(#19866435)
By the way, IRC doesn't look like anything. It's a protocol. It looks like your client software.
Re:We Need to Save What Made Linux and FOSS Possible
by pjmlp on Thursday May 09, 2019 @04:40AM
(#19866443)
Yes it does, because someone has actually to do it and given how much FOSS developers get paid back from the community, we end up having lousy tooling, because it always gets implemented from scratch.
Edit:
I'm speaking from the perspective of an upper 20something. I'm part of a generation that jumps jobs when the opportunity is better, or just because "it's been too long", not the one of years past where I'd be expected to work my way through the same company my entire life. With that said: if my new job says "we use Slack" then I use Slack, end of story. If they say "we use IRC" then I'd Google for how to use IRC because I have never ever used it in my entire life, never read up anything about it in my entire life, and I definitely don't hold IRC in high reverence like many posters here do. All I can see when I google IRC is that it looks ugly and honestly, that's what's most important to me these days because I have to look at, and interact with, the thing for 8+ hours a day so the least it could do is work out of the box, look modern, and doesn't need me to waste hours fussing with some dotfiles to get it to look the way I want, which is exactly how most modern chatting apps look (again: to me it's a waste of time, when I can just grab a off the shelf solution).
I appreciate that there is open source, and that there are free programs out there. I appreciate all the libraries that make my life easier. But the thing is, these are all tools I use to do a job. I don't care at all about the history of say gcc. All I care is that it works and compiles my programs, and if it does, then so be it. And if it doesn't? There are other options, icc, llvm, etc. My point is that at the end of the day, all I want is a tool to achieve a solution, and who makes that tool, or the history behind that tool, doesn't matter to me at all. It's not even part of the equation.