3 ms·

> That's true. The biggest takeaway, though, is the assumption that people will care to port mainstream software to OpenBSD when virtually nobody using that sof

> That's true. The biggest takeaway, though, is the assumption that people will care to port mainstream software to OpenBSD when virtually nobody using that software runs OpenBSD & their community discourages amateur programmers. It's not a wise expectation. Instead, they should expect to have to port it all themselves to their particular OS of choice while being thankful when people do it for them with great portability. You got it a bit wrong or didn't read the linked github issue in detail. I run OpenBSD and I ported Dart to OpenBSD. I tried to work with upstream (Dart team at Google) to incorporate my changes or work on a way that allows them to take the changes and for me to maintain the code long term. In this specific case the upstream works behind closed doors which makes it hard to cooperate on things like this.

nickpsecurity 10y ago
Oh, I read it right: " I ported Dart to OpenBSD. I tried to work with upstream (Dart team at Google) to incorporate my changes or work on a way that allows them to take the changes and for me to maintain the code long term. " You wanted them to work so that your unpopular OS is supported. My claim was that you'd have to fork it and do the work yourself in many cases since the OS project is for benefit of you and small niche of developers/users. The irony is that comments like that deride non-OpenBSD FOSS for not going through trouble of OpenBSD support while the LibreSSL commits mocked and stripped OpenSSL's support of VMS, etc. as crap that's not worth the effort users be damned. Same attitude in place. The Dart team is probably targeting Windows, Mac, and Linux (w/ Android). Those are THE desktop OS's in terms of uptake and capabilities available. Adding PC-BSD, OpenBSD, eComstation OS/2, Syllable, BeOS, MorphOS, MenuetOS... these could benefit someone but represents lots of work with almost no gain due to near-zero market share. So, for niche projects, it's on you to get the work done if your goals and theirs aren't compatible. They're doing nothing wrong even if a bit non-optimal given benefits of portable code tested on many toolchains.

nickpsecurity 10y ago

Oh, I read it right: " I ported Dart to OpenBSD. I tried to work with upstream (Dart team at Google) to incorporate my changes or work on a way that allows them to take the changes and for me to maintain the code long term. " You wanted them to work so that your unpopular OS is supported. My claim was that you'd have to fork it and do the work yourself in many cases since the OS project is for benefit of you and small niche of developers/users. The irony is that comments like that deride non-OpenBSD FOSS for not going through trouble of OpenBSD support while the LibreSSL commits mocked and stripped OpenSSL's support of VMS, etc. as crap that's not worth the effort users be damned. Same attitude in place. The Dart team is probably targeting Windows, Mac, and Linux (w/ Android). Those are THE desktop OS's in terms of uptake and capabilities available. Adding PC-BSD, OpenBSD, eComstation OS/2, Syllable, BeOS, MorphOS, MenuetOS... these could benefit someone but represents lots of work with almost no gain due to near-zero market share. So, for niche projects, it's on you to get the work done if your goals and theirs aren't compatible. They're doing nothing wrong even if a bit non-optimal given benefits of portable code tested on many toolchains.