4 ms·
No they aren't, that is the point made when: the deprecation is announced, preprocessor flags are added to cordon off the code and throw compilation warnings, f
by sennight 5y ago
No they aren't, that is the point made when: the deprecation is announced, preprocessor flags are added to cordon off the code and throw compilation warnings, finally - the code is deleted. The burden is then shifted onto the hardware producer to maintain their now disconnected code, and adapt to breaking changes blindly made by anyone not accounting for the situation (basically everyone). This obviously doesn't happen, because maintaining code for hardware they no longer sell isn't profitable. At most, the manufacturers will offer a few pre-compiled blobs for the most popular system configurations - which really sucks for anyone who actually subscribes to the ideals originally espoused by free software proponents.
- znpy 5y agoyou can fork stuff and keep rebasing things around and/or maintain your own fork, I guess. > which really sucks for anyone who actually subscribes to the ideals originally espoused by free software proponents. the ideals of free software is for software to be free (according to the four fundamental freedoms) and not to work on all and every hardware and to maintain software indefinitely. anything besides the four foundamental freedoms is BS.
- sennight 5y ago> the ideals of free software is for software to be free (according to the four fundamental freedoms)... No, it is to ensure that people are free - as software doesn't know the difference. Would you deny the existence of business strategies that endeavor to curtail such freedom, or do you view those as okeydokey 'cause SaaS wasn't explicitly mentioned by the FSF in the 80s?