dosourcenotcode

5 ms·

1.
by dosourcenotcode 2y ago
And not just options but base command names too. I wrote a tool to partially mitigate this in some cases: https://github.com/makesourcenotcode/name-safe-in-bash
2.
by dosourcenotcode 2y ago
Agree that long options should be used. But there is one caveat to consider: portability. Sadly to this day not all BSD distributions have GNU style long options. And the ones that now do only got them fairly recently. So if you want portab
3.
by dosourcenotcode 2y ago
Definitely agree with the article that engineers should be more aware of scenarios where those interacting with the systems they build have slow internet. Another thing I think people should think about is scenarios with intermittent connec
4.
by dosourcenotcode 3y ago
A cool tool to be sure. However I feel this tool is a crutch for the stupid way browsers handle web pages and shouldn't be necessary in a sane world. Instead of the bullshit browsers do where they save a page as "blah.html" f
5.
by dosourcenotcode 3y ago
I absolutely stand by my claim that FRT is the Next Generation of FOSS for several reasons. To begin with even now in the 2020s billions of people alive today have never once been on the Internet. Source: https://www.un.org/
6.
by dosourcenotcode 3y ago
Good search and offline docs are not mutually exclusive. Grab the HTML version of Python's docs for example. You can search through them totally offline thanks to a bit of JavaScript they include.
7.
by dosourcenotcode 3y ago
As glad as I am that things like DevDocs and Zeal exist I feel like ultimately they are a crutch and indicative of a much larger problem in Open Source which I'm trying to address. Now as a FOSS maintainer I don't owe anyone any p
8.
Help bring about the Next Generation of Open Source [pdf](makesourcenotcode.github.io)
1 points by dosourcenotcode 3y ago|1 comments
9.
by dosourcenotcode 3y ago
I've been working on what I hope is the Next Generation of the Open Source movement. See here to read about how Open Source fails in certain serious ways to be properly open and what I propose be done about it: https://makes
10.
Freedom Respecting Technology Definition [pdf](makesourcenotcode.github.io)
3 points by dosourcenotcode 3y ago|0 comments
11.
Freedom Respecting Technology: Next Generation Open Source and Open Knowledge(makesourcenotcode.github.io)
64 points by dosourcenotcode 3y ago|9 comments
12.
The next generation of Open Source and Free Software [pdf](raw.githubusercontent.com)
2 points by dosourcenotcode 3y ago|1 comments
13.
by dosourcenotcode 3y ago
This in my opinion is what Open Source should have been.