4 ms·
I'm currently building an imitation of Apple's keyboard in Swift (https://github.com/archagon/tasty-imitation-keyboard https://github.com/archagon/tasty-imitati
by archagon 12y ago
I'm currently building an imitation of Apple's keyboard in Swift (https://github.com/archagon/tasty-imitation-keyboard https://github.com/archagon/tasty-imitation-keyboard). Learning process has been pretty easy so far: a few hours with the documentation and the rest picked up along the way. Playground was great for getting up to speed. It's pretty fun to be on the vanguard of a new, evolving language and have it actually be capable of production use. Also very frustrating: there are a number of design decisions that drive me crazy (lack of auto casting between CGFloat/Float/Double/Int... usually), and the latest Xcode and compiler betas have a bunch of bizarre non-deterministic bugs, performance issues, and error messages that have nothing to do with my code and require workarounds. I'm a little too lazy to file Radar bugs for them — Apple is not paying me to write bug reports, and they'll surely get discovered by others — but I'm really looking forward to writing a brief postmortem when I'm done.
(PS the code is super messy right now. I'm in the "hack away" phase, cleanup will come later.)
- m4x 12y ago> Apple is not paying me to write bug reports, and they'll surely get discovered by others So you are happy to write a long comment here in exchange for karma, and are excited to blog later in exchange for eyeballs, but won't submit radars to improve your tools because Apple isn't paying you?
- archagon 12y agoThese are bugs that will be found, unlike most other Apple bugs. Also, I'm busy and bug reports take forever to write and reproduce, especially for the kinds of eisenbugs that I'm seeing. Why so judgey, friend?
- gdubs 12y agoFWIW, duplicates are really important to getting bugs fixed.
- archagon 12y agoIf they're not fixed in a few betas, I might file them.