5 ms·
> The BSDs run off of good old fashioned ego driven software development done by people who care deeply about software. On the other hand, ego driven software
by oblio 7y ago
> The BSDs run off of good old fashioned ego driven software development done by people who care deeply about software.
On the other hand, ego driven software development can also freeze technologies or development processes to what the main ego(s) want(s).
Case in point, FreeBSD, NetBSD, OpenBSD and CVS. And even they will admit CVS is sub-optimal for development, see: https://wiki.freebsd.org/VCSWhy https://wiki.freebsd.org/VCSWhy, https://wiki.freebsd.org/VCSCvsProblems https://wiki.freebsd.org/VCSCvsProblems. Note: I'm not saying Git is the solution, but CVS is bad. They should at least use SVN or any of the many systems that have learned from CVS' mistakes.
TL;DR: Pick your poison regarding development practices.
- messe 7y agoFreeBSD has used SVN since ~2012-2013 I believe.
- oblio 7y agoThat's good to know, but that wiki article was last modified in 2018. It's a bit confusing...
- irishsultan 7y agoI believe it was moved to a "Historical" category at that time
- tachion 7y agoVery recently (last few days) the FreeBSD project formed an internal group with a task of reevaluating, planning and testing the migration from SVN to Git.
- bojanz 7y agoAnd a migration to git is being evaluated: https://twitter.com/lattera/status/1132084341213933569 https://twitter.com/lattera/status/1132084341213933569 DragonFly BSD, a FreeBSD 4.x fork, has also used git successfully since early 2009, I believe.
- tachion 7y agoI'd refrain from using this person as any indication on what's happening in FreeBSD - he's known to be openly hostile against FreeBSD and making many repetitive false statements about it, after feeling hurt by the project rejecting his low quality and poorly written 'security' patches.
- anjbe 7y agoThat’s certainly an interpretation. George Neville‐Neil, president of the FreeBSD foundation, recently gave the keynote at AsiaBSDCon. During his presentation he derided Sean Webb/Lattera for its focus on security (https://hardenedbsd.org/content/easy-feature-comparison https://hardenedbsd.org/content/easy-feature-comparison), simultaneously deriding OpenBSD as “basement dwellers” (this in a talk asserting that the BSDs need to present a unified front to succeed in the world). He also made excuses for the fact that FreeBSD finally—finally!—implemented ASLR in 2019. (For reference, PaX developed ASLR in 2001, OpenBSD implemented their own in 2003, and mainstream Linux got it in 2005.) His excuse, that ASLR is “broken anyway,” was called out by the very first commenter for betraying a complete misunderstanding of what ASLR defends against (GNN trumpeted ASLR attacks on JIT engines, but executing malicious JavaScript on the host is out of ASLR’s scope and always has been). https://youtu.be/7kShjboN6ek?t=2820 https://youtu.be/7kShjboN6ek?t=2820 I don’t know the full story between Sean Webb/Lattera and FreeBSD, but I do know FreeBSD has a poor track record when it comes to security mitigations, and if the presentation above is representative of how the president of the FreeBSD Foundation behaves at an ostensibly cross‐BSD conference, I know which side I’m immediately inclined to disfavor.
- busterarm 7y agoCVS may be "bad", but it's clearly working for the OpenBSD project and they have released roughly every six months like clockwork.
- oblio 7y agoThings can go on for very long periods of time until they suddenly burst. What happens when the current developers retire? I doubt there's any software dev born in 1990 and later that wants to touch CVS, especially for a hobby project.
- busterarm 7y agoExcept OpenBSD gets new contributors all the time. A decent number are in uni or grad school, which basically contradicts your suggestion entirely. We contribute to OpenBSD because we care about the goals of the project and that motivates learning and dealing with CVS.
- Crinus 7y agoYou make it sound like CVS kills children. People worked with CVS just fine for decades and OpenBSD has made their own tools for CVS to improve their development experience and, frankly, if a developer - regardless of age, lets not get into age discrimination here - finds CVS a roadblock to working on OpenBSD, they are simply not a good developer.
- microcolonel 7y ago> If a developer - regardless of age, lets not get into age discrimination here - finds CVS a roadblock to working on OpenBSD, they are simply not a good developer. While we're at it, if a developer finds ed (the standard text editor) a roadblock to working on OpenBSD, they are simply not a good developer. Why is somebody "not a good developer" if they don't want to work with tools which are an insult to the priorities and humanity of the user†, for no good reason, when they could go to Linux and have 99% of what's good about OpenBSD, without the cult of GCC 4.2-justifying, CVS masochists? I love OpenBSD, but the self-defeating goober decisions clearly reduce the number of people willing to become the experts needed to push the project forward. So much of OpenBSD is user-friendly, as long as that user reads the manual; but CVS is among the most user-hostile version control systems any living developer remembers using, and even if you know exactly what you're doing CVS is still an inconvenience because of centralization, and because of the amount of clerical work required to get it to operate properly. † In the context of a world full of spectacular alternatives; obviously this doesn't apply to a time when CVS was a cut above.
- upofadown 7y agoChanging from CVS to something else would mean updating a lot of documentation ... which perhaps is an example of a downside to the BSD way of doing things (the way things are built from source I mean, actually having documentation is good).
- oblio 7y agoThey wouldn't be the first open source project to migrate their source control. There's some which switched a few times, even.