I moved all my open source projects to Gitlab the day Microsoft announced they were acquiring Github.
(I wish in retrospect I’d taken the time to research and decide on the right host. I likely would have gone to Codeberg instead of Gitlab had I done so. But Gitlab’s still better than Github. And I don’t really know for sure that Codeberg was even around back when Microsoft acquired Github.)
Running the Windows version in Wine probably would never have occurred to me.
Arch (i UsE aRcH bY tHe WaY)'s AUR has a package for it. I just installed gpaint on a Raspberry Pi 4 just to see if it worked. It worked perfectly. (Disclaimer: I did have to update the architecture in the PKGBUILD to allow armv7h, but on an x86_64 machine, that wouldn’t be an issue.)
You could probably run Arch in Docker and install the AUR package in the Docker container if you wanted to go that route.
I don’t think anyone in that conversation is advocating against “science.” They’re advocating to (or maybe just lamenting the fact that we can’t for political reasons) do more to save real bees (and the environment in general) rather than replace bees with something robotic. And they’re commenting on how starkly this article highlights how much we’re fucking the planet.
Second, building robot bees isn’t really science. It solidly qualifies as engineering, but not science. The reason I bring this up is that while it’s arguable that there’s no science that shouldn’t be pursued (though certainly science ought to be done ethically), there’s definitely engineering that would best be not done at all. We keep engineering new and ingenious ways to extract more oil from mostly-not-oil, but that’s destroying the planet. Elon’s Hyperloop was never a good idea, and it’s fortunate it was never actually built and probably will never be built. A lot of geoengineering proposals that have been put forward are risky on the basis that we don’t understand the ecosystems involved well enough to know what the side effects might be (and that’s likely not something science will be able to solve any time soon.)
Some engineering is beneficial. But some isn’t. And you can imagine Elon or the oil industry or some reckless geoengineering startup railing against detractors calling them “anti-science” just as a PR stunt to sway public opinion in favor of their fucked-up money-making scheme.
Comparing building robot bees to measuring fly genitalia further illustrates how the poster is conflating science and engineering.
The thing about “less strain on bees” seems directly out of someone’s ass. I can’t guess their line of reasoning.
Now, being realistic, we’re so fucked that I doubt we can save the bees. And I don’t think it’s necessarily a bad thing to make robot bees. But it’s pretty fucked that we have to. Which is all they were saying in that conversation.
My mother has a fascination with Roman Dodecahedra, so I 3D printed her one for Christmas. She hasn’t knitted any gloves with them yet. (And may never, but she still likes it and has it sitting on the mantle over the fireplace.)
I also work remote and have a SAD lamp mounted just an couple of inches above my employer-issued work laptop. (I custom designed and 3d printed a mount for it, in fact.) Basically exactly above and as close to my screen as possible.
It’s quite bright (obviously) and does make seeing the screen a little harder, but I crank the monitor brightness up all the way. I don’t know specifically that it’s given me headaches, but I am prone to headaches. I’ll have to pay more attention and see if there is any correlation between headaches and SAD lamp usage for me.
I leave it on at the brightest and whitest setting from 9:00am to 5:00pm (with a break for lunch.)
I will say it’s not quite enough. This time of year, even with the SAD lamp, my (self-diagnosed, mild-ish) SAD benefits from sitting out in the sun for 10 minutes or so in the morning before work. But a SAD lamp and no sun is a lot better than no SAD lamp and no sun. I think even when it’s overcast (which it is pretty much all the time where I am as well of late) I get benefit from sitting out and getting a little ambient, cloud-filtered light.
This is the specific model of SAD lamp I use. (I’ve got two of that same model, in fact. One of the AC adapters crapped out not long ago and I ordered a replacement AC adapter from Verilux for way more than what I’d consider reasonable. Works fine again now.) The one I have mounted over my work laptop is mounted in “landscape mode.” (Sideways.) I figured that would be better than upright.
Hopefully this is all at least a little bit helpful. I have no idea if you have access to any 3d printers, but if you’re interested in my SAD lamp mount models, I’m happy to share.
So, Open Source was already kindof the capitalistic fork of the Free Software movement. And it feels like Parens’ vision of Post-Open Source is about how to marry it more to “the market.” If it’s not clear from what I’ve said already, I’m not a fan of that specific aspect of it.
It is a problem that big companies reguarly violate the terms of the GPL. I hope good things come out of SFC v. Visio that give the GPL’s requirements of distributing source code with compiled code more teeth, but we’ll have to see. I do think the courts agreeing to interpret the GPL (at least in some cases) as a contract rather than as a license is a good thing. It was a gutsy move on the SFC’s legal department’s part, but the case shows more promise now that they’d made it than it did previously. Perhaps a GPLv4 that better deals with being interpreted as a contract is in order.
Though, I worry that what Parens has in mind for new licenses doesn’t address what I’d want to see from the Open Source movement and will ultimately move (Post-)Open Source in the wrong direction.
Specifically what I want from FOSS licenses is to be able to (and to have assurance that others have the option to) write and distribute software with assurances that no one’s going to use it to restrict users’ rights down the line. The GPL has historically been imperfect at that. The AGPL is better. But the GPL has always been explicit about requiring companies to distribute source code with binaries. What we need is that but with teeth in the form of some combination of court precedent and more effective legalese.
If current licenses have the problem that big companies just ignore the terms set out in the license, I wouldn’t imagine making a new sort of license with different terms like “big companies have to pay to get the benefit of using Pots-Open Source software” is really going to work.
All that said, I’m glad to hear discussion about the future of FOSS. I’m worried about where FOSS is now and where it’s going and am glad to see more strategic thinking.