302 karma · joined October 27, 2009
ryan@cotangent.org https://ryanspradlin.com/
[ my public key: https://keybase.io/ryanspradlin; my proof: https://keybase.io/ryanspradlin/sigs/0jSBscyoeoewWnJ_WZn5hRrwldzUbSpyFxtQm-mlra8 ]
Overall, it strikes me as a nice idea; I know I would appreciate having a first day like this.
[1] http://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Chang...
My anecdotal evidence from helping friends and family is that Macs don't suffer from "Windows rot" [1] the same way that PCs do. My hypothesis: due to differences in the developer communities for each platform.
How about: "Web 3.0"
More likely: a partnership with Adobe involving Flash/AIR as a development platform option for Windows Phone 7.
[1] http://arstechnica.com/web/news/2009/07/are-those-photos-rea...
Looks like the improved version erases just the previous frame's ball, instead of clearing the whole canvas (just my best interpretation -- I'm not familiar with the canvas API).
EDIT: This link details what's going on here:
One important optimization rule to follow is to reuse as many pixels as possible between frames. What I mean by that is the fewer pixels that need to be processed each frame, the faster your program will run. A good example of this is when erasing pixels with the clearRect(x,y,w,h)method, it is very beneficial to clear and redraw only the pixels that have changed and not, for instance, a full screen 1920x1280 sized canvas. Unlike the Flash Player’s redraw regions, this management of "dirty rectangles" needs to be done manually for canvas. [http://www.kontain.com/fi/entries/94636/]
Apparently Flash Player optimizes the reuse of pixels automatically, and MobileSafari does not.
"Looks like the new policy would allow to have VM included in the app itself. Why not focus instead on the VM instead of this as3 to native code conversion (sure the innovation in one can already help the other but still it’s the VM which since in need of a bit more love)." [1]
Now that Apple allows interpreters (as long as they run code packaged embedded in the app), I wonder if this approach would be easier for Adobe to maintain than the AS3-to-assembly compilation they do now. Arbitrary SWFs could be paired as data with a standard interpreter app.
EDIT: I suppose this would make the packager a lot more like AIR for Android( http://labs.adobe.com/technologies/air2/android/).
[1]: http://blogs.adobe.com/conversations/2010/09/great-news-for-...
Maybe it's just me, but I've almost completely forgotten about MySpace when I think "social networks".
I think the phone manufacturers can blame Apple for this -- they set the expectation for mainstream phones to get regular and significant software updates. Now customers feel slighted if their phone doesn't get upgraded.
[1]: I mean "does what I want" in the "my mom can make a photo slideshow without tech support" sense, not the "I can install Linux on my iPhone if I want to" sense
"Apple’s policy allows for employees to have apps on the App Store if they’re developed and published prior to their start at Apple."
[1] http://www.engadget.com/2010/07/23/microsoft-wants-employees...
[1] http://www.networkworld.com/news/2007/102907-iphone-ipod-tou...
To an outsider, it feels like there is a mountain of material to wade through before you can really get going with a Java webapp; for Python and Ruby, the perceived barrier to entry is much lower.