6 ms·
I like openbsd. I like their attitude (even if many don’t) I like what they’ve given to the UNIX-likes, and what they strip away due to complexity (removal of B
by dijit 7y ago
I like openbsd. I like their attitude (even if many don’t) I like what they’ve given to the UNIX-likes, and what they strip away due to complexity (removal of Bluetooth) or lack of decent UX (wpa_supplicant), or just potential issues (removal of Hyperthreading)
I know it’s probably controversial to mention it; but I’m also glad they didn’t buy into the code of conduct saga that waved over FreeBSD and eventually Linux.
I’ve used the OS as a daily driver, it certainly was nice, albeit slow. I would go back if I could avoid some of the Linux/MacOS stuff I really need. I still use it on personal servers and I still really love it.
I send them €50/mo but I don’t feel like it’s enough. I wish they had more resources to bring things like AC Wi-Fi to the fold. Truly impressive work to all involved.
- temptemptemp111 7y agoYep, same. I'm not ready to flee Linux just because of the CoC, though. Need to stand our ground.
- umvi 7y ago> but I’m also glad they didn’t buy into the code of conduct saga that waved over FreeBSD and eventually Linux. I'm a bit out of the loop, but I thought it started with Linux because Linus swore/ranted/"abused" contributors or something? Or am I thinking of something else?
- dijit 7y agoIt’s fair to be out of the loop. I wish I was, because dissenting for any reason is seen as being a villain or a troll. For a little context though the freebsd code of conduct was instantiated in 14th February 2018 - the Linux one was altered to be the current one on September 21st of the same year (which is when the Linux CoC controversy began).
- calcifer 7y agoHe was quite abusive actually, not "abusive".
- derefr 7y agoYou seem to be interpreting the parent as using scare-quotes to disagree with the idea that Linus's behavior was "abusive." But the parent comment was, as far as I can tell, intending to use regular quotation marks, in the way a journalist does (and as I just did)—to mention what someone else said, without endorsing or denying that opinion as their own, in order to avoid an argument. (Personally, I think more things people describe should be put in quotation marks. A lot of Internet arguments are started by people trying to argue others out of beliefs they don't actually personally have.)
- aaronbrethorst 7y agoQuotes only work with attribution
- vvvij 7y agoDo you think it would fare better under new AMD CPUs? (besides the raw increment in performance) I do hope that as long as Theo is in charge they never but into the whole CoC thing. Thankfully, from what I recall, some of their biggest backers are from China and thankfully they don't really give a crap about CoC, feelings or human decency in tech, for better or for worse.
- cpach 7y agoWhat is it that you don’t like regarding CoC?
- lone_haxx0r 7y agoI'm not OP, but: > Harassment includes but is not limited to: Comments that reinforce systemic oppression related to gender, gender identity and expression, sexual orientation, disability, [...]. -- FreeBSD CoC Why even bring in the "systemic oppression" part? I can only assume that they'll be more lenient on disparaging comments that don't reinforce "systemic oppression", i.e. they'll apply "positive discrimination", otherwise it makes no sense to include such an expression in the CoC. I refuse to participate in any project that discriminates people based on their personal traits, that includes "positive discrimination".
- YUMad 7y agoBecause 'systemic oppression' is a made up concept, just like 'Jesus'. And just like Jesus, it's a guilt-exploiting profit- and power-seeking concept.
- dang 7y agoWe've banned this account for repeatedly breaking the site guidelines and ignoring our requests to stop. If you don't want to be banned, you're welcome to email hn@ycombinator.com and give us reason to believe that you'll follow the rules in the future. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- klodolph 7y ago> Why even bring in the "systemic oppression" part? Because systematic oppression is more of a systemic problem. Individual problems are easier to solve than systemic problems, i.e, you don’t need a code of conduct to solve a problem with one or two people in your association. If you make one disparaging comment to someone, we can hope that they take that one comment in stride and move on. If you make a disparaging comment that reinforces systemic oppression, it’s no longer a single comment, but it’s part of a larger problem. The way these comments harm the group is that e.g. in response to low-level misogynistic comments, women silently leave the group. You might not even notice this happening until it is too late. One of the core freedoms which is protected by the first amendment is the freedom of association, and a key part of that is the freedom not to associate with people you don’t like. If you don’t make an explicit choice about who you want in your association, the choice will be made for you by the most toxic members. So you are basically given a choice between an open code of conduct which people can discuss or comment on, or a secret/hidden network of people who make the decisions without any clear way to understand why they make these decisions or how to appeal them. That’s just my take on it.
- hackermailman 7y agoMost OpenBSD developers know each other and meet on a regular basis so likely why no CoC is needed when there isn't dozens or hundreds of contributors that don't meet. I miss OpenBSD for the certainty of what my system is doing, these other systems I have to use for work some intelligent process comes a long and rewrites my configs or something else annoying.
- adrianratnapala 7y agoDoes OpenBSD have an alternative to wpa_supplicant? I've been using wpa_supplicant under the hood for ages, but only recently learned anything about it... and it's actually very good, except that it's CLI interface is so low-level and difficult to use.
- octotoad 7y agoIts standard ifconfig handles all the equivalent functionality.
- dTal 7y agoI don't use OpenBSD for various functionality-related reasons, but experiencing that was an eye-opener. It makes me mad that Linux doesn't use such a clearly superior system, and leads one to wonder what other needlessly complex interfaces we put up with unquestioningly.
- microcolonel 7y agoThere are things other than wpa_supplicant, but wpa_supplicant is just sorta "good enough", everything generally works. It's a different approach. For me, my OpenBSD moment was when I used the backlight brightness keys on a laptop in a vt, and it Just Worked™.
- adrianratnapala 7y agoI would put it the other way around. wpa_supplicant is actually very good at doing what it does. But rolling it's functionality into ifconfig is probably "good enough". wpa_supplicant is an application of the "do one thing" philosophy. The kernel provides a some basic hardware-abstracted plumbing which lets a specialist tool do all the complicated handshaking and what-not for wireless. This saves the basic tools (ifconfig, ip) from having to build in all that wireless complexity. But it does introduce an extra moving part that has to be configured. For this reason, just bloating it into the basic tool is likely to be good enough, and also provider a superior UX (for nerds like us).
- somacert 7y agoOpenbsd has a code of conduct. It's been there a while. https://www.openbsd.org/mail.html https://www.openbsd.org/mail.html only half joking
- microcolonel 7y ago> Intelligent people may look at the same set of facts and come to very different conclusions. Repeating the same points that didn't convince someone previously rarely changes their mind, and irritates all the other readers. This one is crucial. I see so little respect for tolerance around various projects these days.
- yjftsjthsd-h 7y agoI can support a CoC that opens with, "Plain text, 72 characters per line". Standards™!
- wrycoder 7y agoI don't think there are many who send €50/mo, kudos to you! Few of their corporate users give much back at all. I used OpenBSD as my workstation a decade ago and also ran it on a firewall box. However, upgrading the system every six months is tedious: basically, you manually download the files, overwrite the kernel and userland core, and then do a three way merge of /etc. Plus there's a bit of manual work required to deleted unused files and account for moved files: https://www.openbsd.org/faq/upgrade65.html https://www.openbsd.org/faq/upgrade65.html After that, you still have to upgrade the ports tree (which has gotten easier). Note that skipping upgrades is not supported. Security updates between the six month upgrades are handled by monitoring the security list and downloading and applying patches as instructed. If you are running a bunch of identical servers professionally, it's not much of a burden, but it is if you are upgrading one workstation and a firewall box. I got tight on time and went back to Debian/apt. Does anyone here know how to do this more efficiently? (It is a really nice system, and the man pages are superb.)
- asveikau 7y agosysmerge has made the upgrade process a lot easier in the last several years. It was a lot more painful in the past.
- jammygit 7y agoIs it easier or harder to just do a full reinstall and reconfigure it with a script (chef or something custom), while preserving your data directory?
- yjftsjthsd-h 7y agoSomewhat like sibling comment, I'd be really tempted to put /home on its own filesystem, control/configure everything else with Ansible (or Chef or Puppet or [...]), and just do a fresh install every 6 months. For bonus points, automate the install part with an autoinstall file. Keep in mind, there's setup cost here; it's easy for me to say because I'm already controlling my system with Ansible, but if you're just getting started it's harder.
- sirn 7y agoIn -current there’s sysupgrade(8) that handles the “download bsd.rd, boot bsd.rd, upgrade, sysmerge” steps automatically in an unattended manner.
- bitwize 7y agoProjects without a code of conduct are either immature or led by reactionaries, and in either case have a much higher risk of toxicity. If you want to get something done in a communitarian fashion, implementing, clearly stating, and enforcing rules of conduct is an absolute must.
- tick_tock_tick 7y agoI agree with you in principle but most of the codes of conduct being pushed during the last major wave had very little to do with that goal. They were clearly targeted at policing users online/offline conduct and values outside of the project rather than fixing any active issues for that project.
- bitwize 7y agoA person who's a dick outside the official channels is much more likely to be a dick on the official channels also. Tolerating such people is inimical to creating a welcoming community, as they pose considerable risk of disrupting development activity and intimidating people who are or might potentially be making valuable contributions.
- jim-jim-jim 7y agoDo all projects have to be "welcoming" though? Sometimes I wonder if OpenBSD (and other projects that emphasize simplicity) are as good as they are precisely because they seem to attract opinionated, blunt developers with thick hides.
- hiram112 7y agoI suppose you're right. Before the CoC craze, the open source community just wasn't able to crank out anything of technical value. But since then, things have really taken off, and there's no doubt we can attribute it to the CoC and also the non-technical community members who, more often than not, demanded we carry it.
- 7y ago