3 ms·
I was accutely annoyed by the planned obsolescence of some critical (for my computer usage) software components. I started to write heavily derived/alternatives
by sylware 3y ago
I was accutely annoyed by the planned obsolescence of some critical (for my computer usage) software components. I started to write heavily derived/alternatives directly in assembly (I realised that even lean and simple C was not enough in those cases). This de-facto cancels planned obsolescence based on compilers and some language syntaxes but the work is beyond reasonable.
I don't know why, I am so mad about it, I am doing it anyway.
- sp_c 3y agoSounds fascinating, what are some examples of the things you are building?
- sylware 3y agoI figured out only recently that lean and simple C was not enough, namely, no real assembly stuff published yet. In lean and simple C I have some (easy to port to not gcc and not clang, namely tinycc or cproc/qbe etc). Since it is a big component (for the wrong reasons), I will show it on HN when it is actually working and published, coze it is so much toxic to write (it is not the assembly which is toxic, but the standard on which it is based is completely obsolete/broken/toxic) I may send everything to hell and drop it. I guess I have still months of coding, a lot of them.