I'm an iOS engineer with 10+ years of iOS experience, the last 6 years I've been working at Meta mostly focused on the Messenger and Instagram apps.
I'm interested in building delightful native iOS experiences and have experience working with a wide range of iOS APIs and apps of all sizes.
http://www.bazqux.com/ - I paid for a lifetime subscription a couple years ago and never looked back. The interface is great is both desktop and mobile, since it’s online everything is kept in sync across devices and I can configure the interface to my liking. I tried many RSS readers and nothing came close.
Unfortunately, I don't have enough resources to optimize site for screen readers. I think that mobile/desktop apps handle accessibility better so you could use them with BazQux Reader or other service.
It's only 4D. I believe they called it 5D chess because they didn't want people to interpret this as 3D chess + time. If I recall correctly, the tutorial mentions at some point that the 5th dimension is "unused".
5. The timeline of how the game actually evolves, building out the tree. This is a bit of a stretch, since you can't move pieces through it in the same way as the other four.
It would have been nice if 4D only ever meant four spatial dimensions, and then we'd have (3+1)D for three spatial dimensions and a time dimension. (And (2+2)D for two spatial and two time dimensions :-))
My understanding is that Luigi is not in the final build of the game (which is why it was not found before). But I believe the recent leak contains the CVS repo used during development, which includes the complete change history.
A few years ago I wrote an article explaining how the chaos game works with high school level math, and a few couple of fun experiments that you can do with it. If anyone's interested you can read the article here: http://shiftingmind.com/chaosgame/
I recently worked on a production app that used Swift. It's certainly possible, but I wouldn't recommend it (yet). Writing Swift is nicer and feels much more natural than Objective-C, but the tools are not there yet.
Xcode crashes often (even more frequently than with Objective-C), the compiler will probably also crash at some point during development. Compiling Swift code is also considerably slower than compiling Objective-C code. Error messages are often cryptic and debugging compiler bugs is very time consuming.
There's also a few places in Swift where things still need some more time to settle, framework support is tricky and some very basic tasks are harder than they should be (for example, getting a substring).
The article suffers from a bit from looking at things from a strictly theoretical knowledge (i.e. the first example is not valid Swift code), but it does bring up a few interesting points.
Remote: YES
Willing to relocate: No
Technologies: iOS, Swift, Objective-C
Résumé/CV: http://linkedin.com/in/pablogom/
Email: pablo[at]shiftingmind[dot]com
-----------------------
I'm an iOS engineer with 10+ years of iOS experience, the last 6 years I've been working at Meta mostly focused on the Messenger and Instagram apps. I'm interested in building delightful native iOS experiences and have experience working with a wide range of iOS APIs and apps of all sizes.