More relevantly: I've spent way too long rolling my own issue tracking systems (plural!) over the years, and it's good to see someone else share my intuition that dependencies and tagging are by far the most important part of solo-ish issue trackers. You'd be shocked how many massive tech companies publish issue trackers where dependencies are an afterthought (or worse: a paid upgrade).
My only tiny, soft suggestion would be mention "Unix Philosophy" rather than just the MVP link, tho it is indeed cute. As I alluded to above, the former has a dedicated cult behind it already ;)
These days Python is almost as universally available, and I've seen few systems ship without Perl. Both provide excellent backward compatibility; I have many scripts that still run unchanged on Python 3.6 (2016).
(Pebble founder)
But honestly I've had Macs that still work 15 years after I bought them, and iPhones that work for easily 6 or 7. That's not because AU or EU require a somewhat longer warranty, I don't think.
2002 PowerBook user checking in. Not great for "modern" work, CPU gets really hot compiling "simple" stuff like git or libressl, but OSX 10.5 is a superior user experience to macOS 15. Still great for lightweight web browsing (disable JS!), some coding (Python 2.7.14!), classic games (StarCraft! from a *box*!).
Stop alarm is presumably one of those basic actions.
But it doesn’t support custom actions that the app developer might have registered.
You can't COW two different libraries, even if the libraries in question share the source code text.
If you mess with the logo, the console locks up during boot. If you don't, you're violating the trademark.
For example, the Passat 3B and later platforms introduced proprietary screws for the wheels and brakes, so you weren't able to change them yourself.
Same for all kinds of sensors that will go rogue when the car is turned off and you change a sensor on the engine. All firmware gradually was modified each generation to allow less modifications and less self repairs, and less repairs by third party workshops.
Also, the Golf 2 platform for example had a very sturdy engine running beyond 1 Mio km easily. What do you think happened with the Golf 3 engine design? They made the camshaft structurally weaker, so the engine will blow up more easily. The rest of the engine is almost identical. Talk about being bad at hiding planned obsolescence.
There's many more examples like this, acrosd every manufacturer. The real reason why there is so many people on race tracks driving old cars is because they're easier to modify, easier to maintain, and easier to buy replacement parts for.
It's ridiculous if you think about it, and really frustrating that there is no legislative intervention against this.
This should be illegal. You're supposed to do what, stay on the roadside for 20h before an authorized repairman can reach you? What if the weather is harsh, and you run out of basic supplies like food or your medicine?
The only non-generic word you see in the crash message is "SQLite".
You look it up, find SQLite, and you bother the developers for help.
The problem is as old as labels.