354
thanks for the transition, Emacs
(discuss.tchncs.de)
a meme with two halves.
on top is a screenshot of the terminal with the following text:
Generated ~/.config/emacs/.local/env
Installing plugins
> Installing straight...
> Installing packages...
> Updating recipe repos...
> Cloning Llink-hint.el...emacsmirror-mirror. ..
> Building link-hint...
> Building link-hint > Cloning avy...
- Checked out avy: be612110cb116a38b8603df36794
> Building link-hint > Building avy...
> Building link-hint...
> Cloning drag-stuff.el...
> Building drag-stuff...
> Cloning company-shell...
the lines installing straight and building drag-stuff are highlighted in red.
on the bottom is Confused Nick Young face
Oh yeah, I didn't consider the fact that emacs might have a lot of breaking changes (I don't use it). Thanks.
This is about emacs not having breaking changes and most other platforms(like android) requiring constant updates and maintainance due to their changes in it.
I don't use emacs so I didn't know that, but on Android I have apps that haven't been updated in a long time (games I purchased as part of Humble Indie Bundles that just came as APK files) that still work fine.
Android does a pretty decent job in making the old apps work but for devs its hard to keep supporting new versions of android. Devs have to use the new apis to be able to release in play store. They have to constantly raise their target SDK version for play store to accept any kind of updates, but to raise sdk version, they have to update the implementation, etc. Then when a new android version release, it have the next sdk version and some apis might be removed and/or deprecated. The newer android can run the apps built for older versions usually fine except if some new android limitation was introduced. But the thing is it needs to be changed when updating target sdk version(play store enforces that you have to make the taget sdk corresponding to quiet recent android version).