It’s nice to see that Acorn isn’t the only app with this bug. Notice the baseline of the text (and box) in Keynote as it is resized from the top. It shakes, which is caused by the canvas not being viewed at 100% scale, which in turn causes rounding problems somewhere along the chain.
Acorn has had versions of this problem for years, and it always drives me a little crazy when I see it. But this is Apple's Keynote, so I get to laugh this time.
The relationship between consumers and developers is symbiotic, one cannot exist without the other. If the Mac App Store is a hostile environment for developers, we are going to end up in a situation where, either software will not be supported anymore or even worse, won't be made at all. And the result is the same the other way around – if there are no consumers, businesses would go bankrupt and no software will be made. The Mac App Store can be work in ways that's beneficial to both developers and consumers alike, it doesn't have to be one or the other.
"I’ve been doing Hazel for over seven years and I think it’s fairly safe to say that I’ve been successful doing it. I’m making more money than I did employed at other companies and I’m much happier with my job."
"One thing that I did learn is to have a healthy respect for randomness. Luck plays a huge role and you can’t always attribute one’s success or failure solely on their decisions and actions. … The point is that a good deal of your app’s success depends on luck. That doesn’t mean you sit back and just let fate decide; you still need to work to improve your chances. Just realize that there’s a big chunk you can’t control and that on some level, you need to be ok with that."
The longer I'm indie, the more I realize this is true
Robert McGinnis is one of the greatest paperback cover artists of all time. McGinnis has painted over 1200 paperback covers and over 40 movie posters, including Breakfast at Tiffanys and several James Bond films. In 1993, he was voted into the Society of Illustrators’ Hall of Fame.
The two previous books on McGinnis (publishing in 2000 and 2001) are both long out of print and command premium prices. So a new monograph on the artist is long overdue. With 176 pages and a large 9x12 format, this promises to be the biggest and best of the three volumes.
Limited to 1000 copies, minus the one I just ordered.
"We have seen problems with apps not being updated in a timely manner. We have seen issues with crashing, devices rebooting, rotation glitches, keyboards playing up, touch screens not responding. Indeed I'm typing this while babysitting the full restore of an iPad that one pupil "broke" - through no fault of their own - while updating to iOS 8."
There's been a bit more grumbling than usual about the quality of Apple's software recently. And I can't help but feel like things have changed for the worse. Random crashes, system instability, background processes crashing and having to reboot to fix things. I'm sure I've said it before, but I really think Apple is trying to move too fast. They are already light years ahead of their competition, it would be great if we could all just stop and take a breath of air and look around and enjoy what we've got for a little bit. A little break until the next great thing comes out.
"The v1.0 release of Swift has come and gone, and v1.1 is right around the corner. My thoughts so far can be summed up as this: the hype of Swift is over for me - I want my ObjC 3.0 language. I’ll keep trucking along in Swift for the projects I can, but at the end of the day, I’m, on the whole, fairly disappointed in the language.
"The truth of the matter is that I really, really, wanted to like Swift. Much of the Objective-C syntax is clunky, bolted on, and downright infuriating at times (I’m looking at you block syntax). However, the power and flexibility the language provided in its relatively minuscule ruleset should not be overlooked.
"But it is."
My thoughts on Swift are still evolving. I have gut feelings, but I can't trust them until I spend more time using Swift.
If you're not familiar with SES, it's a simple service and API from Amazon that makes sending out mass emails (like newsletters) to thousands of folks super easy. I've been using it for a couple of years from a custom Python script I wrote, but it looks like Woosh would have been a better solution.
Why use SES over anything else? It's amazingly cheap, and it was well worth my time to switch from Campaign Monitor to it.