3 ms·
> She says that strict adherence to the FSF’s Respects Your Freedom program means that you’ll be using only obsolete and probably broken hardware. Old, like fr
by kazinator 4y ago
> She says that strict adherence to the FSF’s Respects Your Freedom program means that you’ll be using only obsolete and probably broken hardware.
Old, like from a time when it respected your freedom more?
I don't like the insinuation here, which is that we have lost; if you want the shiny new hardware, just shut up and fork over your freedom.
Just because you put up a white flag and surrendered doesn't mean that those who haven't are fighting the "previous war".
If Stallman is "fighting a war that’s no longer going on", why can't you have your freedoms respected on new hardware?
> If you’re particularly masochistic, here’s the start of the thread on Emacs-Devel.
Here we see completely cringe-inducing, uncivil exchanges such as:
RMS> Is it possible to do this with call-process
or by running a shell command [instead of the do-applescript function]?
H. Melman> I think so, though I have to figure out the right
incantation to get stdout returned as a string. I might be
nice if call-process' DESTINATION arg had an option for this.
A. Schwab> See shell-command-to-string for how to do that.
It's like not being able to look away from a trainwreck, these uncouth, unconstructive GNU diatribes.
- aidenn0 4y ago> Old, like from a time when it respected your freedom more? Old and broken as in "You can't update the firmware" because updating the firmware with proprietary software is Bad, but using the proprietary firmware that ships with the product is A-OK.
- kazinator 4y agoThat position is crystal clear and makes sense. If absolutely nobody can replace the firmware (without desoldering chips and such), then the playing field is level; the firmware is effectively part of the hardware, like a voltage controller chip on the circuit board. If the firmware is flashable, then until someone actually flashes it, the situation sort of resembles the above, which is why the original firmware image is acceptable. Would you prefer that Stallman declare unacceptable any proprietary factory firmware that can be overwritten? Basically the FSF concerns itself with things that are programmable: who controls that. If only some privileged players can produce images for the device (like the original manufacturer or some parner or other cohor thereof), then the user is disadvantaged: the field is not level. A device with a nonprogrammable ROM could be be harmful, and that could be due to code. But it is not fixable by programming, just like a harmful toaster.
- dathinab 4y ago> then the playing field is level; But it's not, because it only affects a small number of devs with a lot of conviction. A number small enough to be mostly irrelevant for any company with relevant market share. The rest of the world does just ignore the FSF of today.
- naasking 4y agoThe rest of the world has always ignored the FSF. They were quite influential nonetheless.
- giantrobot 4y agoA place where this idea falls down now is many devices do not actually contain a ROM. They only have RAM and get their firmware loaded into them at initialization. Functionally they are little different from a device with a flashable firmware. This is a weird situation for Linux distros or any FOSS operating system. In order to use this hardware they need to ship closed binary blobs. Even if the license on the blobs allow redistribution shipping non-free software is often against a groups internal rules.
- kazinator 4y agoPeripherals requiring firmware from the host are not new. In the consumer PC market, software modems (or "winmodems") appeared in the early-to-mid 1990's. A device with only RAM that gets proprietary software loaded into it from a storage device on startup is the description of any computer booting a proprietary operating system. The GNU Public License contains an exception allowing GPLed programs to link to the libraries of an existing installation of a proprietary system. The situation that is different with firmware blobs is that you have to redistribute them. Even if you get rid of the proprietary OS from the host machine, your free OS has to supply those blobs. Indeed, weird situation as you note.
- mindslight 4y agoI personally wish they'd revise this singular obtuse rule in favor of talking about specific processor domains. A peripheral running proprietary software, whether from ROM, flash, or loaded into RAM by a Free host, has a similar level of non-freedom. But it is ultimately still a peripheral with limited purpose and limited privilege - it does not harm my freedom in the main computing domain. I'd say the FSF isn't so much "fighting the previous war", but rather new fronts in the war opened up and they've had a lackluster response. But there is of course much money to be made by convincing people to just give up on freedom entirely, to sell them flashy computationally-disenfranchising gadgets and services.
- dathinab 4y ago> Old, like from a time when it respected your freedom more? No. - Old like people took years to create alternative drivers and reverse engineer APIs. - Old like hardware which was phased out due to security flaws which also happened to allow free firmware. - Old like the producer doesn't care about it anymore and therefor some employees feel safe to leak some details needed for creating free drivers.
- yuhong 4y agoPart of the reason why I pay attention to Marginalia search is the hardware problems it shows. There are now some good papers on SSD based search engines.