Urr, I don’t think that’s it. I’m not sure stereo sound for vinyls has ever worked so that something like this would be necessary, and it wouldn’t really make sense – why would they have to put vocals on one channel and instruments on the other?
A stereo vinyl player just has the needle moving up and down in addition to left and right, so that the left-right axis is the sum of the waveforms of both channels and the up-down axis is the difference – which means that a regular mono player can play stereo vinyls
Far as Swift’s syntax goes, I really like argument labels too, but it’s just that there’s SO. MUCH. SYNTAX. Lots of sugar, yes, but sometimes that’s part of the problem in my opinion, because it often adds to the syntactic and semantic “noise.” Also, there’s 98 keywords (more if you count eg.
try
,try!
andtry?
as different keywords, and this count is missing eg.sending
and other new keywords) – compare this to say Rust’s or or Python’s 35. Java’s got 68, while C++ also has 98 and it’s notorious for having way too many of them. And then there’s all the symbols – some of which have different meanings in different contexts.It’s true that ARC only applies to reference types, but even with value types you can often get some fairly surprising performance problems due to implicit copies, for example in getters and setters – and the
_read
and_modify
accessors that can sometimes help with that due to returning (well,yield
ing) a borrowed value instead of a copy aren’t meant for “public” use (which doesn’t mean many libraries etc. don’t use them, much to the consternation of core devs).