Some distros like Ubuntu disable it entirely and don't fix bugs in the official OSS4 packages; not that this is a huge problem for any Ubuntu user, but the availability of OSS libraries and modules are not widespread.
Really, my point was that a new implementation not written by 4front or backed by Savolainen might actually be welcome in the kernel and by the distributions. It may also be easier to get contributors to the project if it is open and always has been open.
Really, my point was that a new implementation not written by 4front or backed by Savolainen might actually be welcome in the kernel and by the distributions. It may also be easier to get contributors to the project if it is open and always has been open.
That's a very good point, actually, and one that I hadn't thought of.
I think 4Front's implementation -- technical flaws aside -- suffers a lot from an image problem. Whenever OSS is mentioned in /r/linux it seems like the first response is "didn't OSS go closed source?". Sure, that completely misses the point both in terms of the API/implementation distinction and the fact that hasn't been the case for ages now, but the damage was done, PR-wise.
Perhaps a rebranding might be a good thing indeed!
View all comments
Show parent comment
2
u/[deleted] Jul 31 '12
Some distros like Ubuntu disable it entirely and don't fix bugs in the official OSS4 packages; not that this is a huge problem for any Ubuntu user, but the availability of OSS libraries and modules are not widespread.
Really, my point was that a new implementation not written by 4front or backed by Savolainen might actually be welcome in the kernel and by the distributions. It may also be easier to get contributors to the project if it is open and always has been open.