You are viewing a single comment's thread from:
RE: Official Announcement - Steem fork will be called "Calibrae"; DNS will be calibr.ae
It's absolutely going to be an ironclad rule of Calibrae, that API changes require really solid reasons. It is best to treat APIs like immutable values, like tuples. You can add to them, but you can't change them. This allows people to keep legacy code working while permitting improvements. When the old API needs to be rebooted, then you need to also develop a roadmap for migration, or you should just leave it the hell alone.
It's the fastest way to lose developers in Open Source projects, switching around API's. Programmers hate having to relearn stuff for no good reason.
An API should stay the same yes, the fundamentals underneath can therefore change.
I was talking about iOS.. That went very fast...
ah, ok. Well, the changes I bumped into with this porting process I was doing, were handling boundary conditions. I think compiler coders can be a bit wishy-washy about these things.
Especially when it comes to such a poorly specified and complex grammar as is used in C++. This is one of the reasons why a simple, and consistent grammar is always important in a language. It can be very hard to learn languages that have complex grammars. Human or otherwise. Bulgarian has such fuckery in its verb mutations. I still hardly know which way to express tenses and persons in non-present forms.
I was outraged when I was in highschool at the lack of Grammar in the English syllabus. Basically, if you ever wondered why most people barely speak better than a 13 year old, it was when I was 14 that they stopped teaching us any new grammar.