4 ms·
Exactly. I wonder if in the future we will more demand API stability of our host platforms so we aren't rewriting the same framework on every API change. I feel
by RubenSandwich 9y ago
Exactly. I wonder if in the future we will more demand API stability of our host platforms so we aren't rewriting the same framework on every API change. I feel like I'm always building on sinking sand, that my programs have half-lives shorter then radioactive elements. Say what we want about Microsoft but they have always valued API stability.
- MBCook 9y agoApple’s frameworks are relatively stable. Maybe we shouldn’t be building frameworks on top of frameworks on top of other languages? Maybe officially supported tools/languages are often a good choice.
- pjmlp 9y agoExperience taught me that it is always the best option for production code.
- Fappy 9y agoI understand what you're getting at and agree with the sentiment. Knowing work on the .NET framework is going to be supported (see: not broken) for years to come is a big factor for deciding on a basket for your eggs. But aren't most radioactive elements notorious for having half-lives that are long with respect to the human lifespan? Just sayin'.
- RubenSandwich 9y agoYeah, the radioactive element comment is more statement on how our products are slowly decaying. But if I was to choose one with a half-life similar to the lifetime of the products I've worked on I'd go with the isotope: Sodium-22 with a half-life of 2.602 years. Edit: Going by https://en.wikipedia.org/wiki/List_of_radioactive_isotopes_by_half-life https://en.wikipedia.org/wiki/List_of_radioactive_isotopes_b..., it seems that most of the halflives fall in the 10^(n where n <= 6) seconds category which is smaller than a human lifetime.