Sure. I didn't want to directly link it without being asked because I didn't want to seem like I was promoting anything or anyone, but it's this one:
https://www.youtube.com/watch?v=fXGjwf6zUWY
I don’t think it was every one or the other. Ruby wa/ hot around 2005 and Apple experimented with language bindings for AppKit (and osascript?). I did a bunch of prototyping using MacRuby and then would rewrite in Objective-C.
Ruby’s object model is relatively similar to objc - no direct member access outside the object, everything is loosely coupled messages with dynamic runtime, you could get away with duck typing in some cases in objc using `id` types (at the expense of getting type checks from the compiler).
I don’t think it was ever intended at the next system language, though. It was just a convenient binding and optimized runtime (many of its core types were Core Foundation types - NSString, etc. IIRC).
There was a brief window when it was possible to do some really cool stuff with MacRuby, such as inspecting and even monkey patching core OS X classes. Probably one major reason why Apple killed the project in the first place. Being able to interact with the operating system on a low level through macirb was an absolutely mind blowing experience.
Sadly, those days are long gone, and I just don’t think Swift brings the same kind of flexibility or joy that MacRuby did.
This seems wild. Ruby and Swift couldn't be any further from each other. I struggle to believe that Apple ever seriously believed that Ruby was their ideal language for app development on their platforms.
That’s what MacRuby was. There was a time when you could develop native, compiled Mac applications using Ruby as a first-class language. For a while, MacRuby was looking to be the lightweight alternative to Objective-C. Unfortunately, the project was killed around the same time Apple released and started promoting Swift. I don’t know that there was any definite reason given (not that there ever is) but my understanding at the time was that Apple wanted a language developed in-house rather than adopting something developed somewhere else.
most of the views (in the iOS app at least, idk about android) are asynchronous, in that they will always prefer to load data from their servers over using locally cached stuff.
meaning that, if you have a bad internet connection and tap on eg an album, it'll open the view for that album and you just have to look at the progress indicator for in some cases up to 20+ seconds, even if you have downloaded that album and all the info is there in the local cache.
this happens annoyingly often, e.g. when leaving an area where you're connected to wifi and your phone hasn't yet switched over to celluar data.
the total volume of all oceans is roughly 1.335 bn km^3. the volums of this sattelite is ~6.612m^3, which is about 4.952*10^-16 % of the total ocean volume.
i could be completely wrong here, but i do seem to remember something about there being some physical chip in the machine that needed to be present for e.g. iMessage to work. this was a while ago but iirc they also somehow incorporated local Apple ID account management into that system.
given that the galaxy is moving, i'd say yes.