4 ms·

> Swift where things get added at a frightening rate. Things are always added at a frightening rate when a language is young. Happened for C#, happened for Sca

• airless_bar 10y ago
  The difference is that Scala devs didn't push for immediate adoption while they were still working things out. Apple's Swift message is more or less "Stop writing Objective-C if you can and start using Swift – oh and by the way – you will have to rewrite your code with every major Swift release which we will be releasing at a rapid schedule". It will be very hard for Swift to get rid of all the cruft they accumulate. In Scala every major release addresses one or two pain points and migration is very smooth – no "rewrite all your stuff".
  • incepted 10y ago
    > In Scala every major release addresses one or two pain points and migration is very smooth – no "rewrite all your stuff". Yes, the Java way. Take ten years to implement basic stuff. I much prefer Swift and C#'s approach to this: first major version bump, things get deprecated. Second bump, they get removed. It worked great for C#, it's going to work great for Swift, which has already seen incredible adoption on iOS. Scala is moving at a glacial pace in comparison, really not worth bothering with.
    • airless_bar 10y ago
      Oh come on Cedric. You managed to troll better in the past. As you surely know it already, the deprecate-remove cycle is pretty much how a) Scala works and b) C# doesn't work.