Earlier quoted context omitted.
Sadly, the development environment matters quite a bit. - I will miss being able to declare classes using a sane syntax (Coffeescript helps in this regard) - I will miss the optional type annotations, which caught many a bug for me (you can use JSDoc annotations + closure compiler, but only if you like placing a verbose comment in front of every single variable declaration ) - I will miss having an IDE that can actua…
> But have you tried doing anything graphically complex in HTML5? ... Things that Flash used to laugh at will bring Chrome to its knees. Agree. An example is graph visualization. Fire up your CPU monitor and go to http://arborjs.org/atlas/ and view this very cool physics-driven mesh visualization written in Javascript. You'll see the needle jump to 95% or more. On my relatively modern laptop, if I run this for more t…
Adobe ceases development on mobile browser Flash, refocuses efforts on HTML5
161–165 of 165 posts
Re: Adobe ceases development on mobile browser Flash, refocuses efforts on HTML5
#162Earlier quoted context omitted.
You're complaining about the development environment, which is considered to be better than JS/HTML5 by many people. However, the Flash runtime is the reason people complain about Flash. It is slow, it leaks memory, it crashes like crazy and has been a second-class citizen on every platform other than Windows since forever. JS/HTML5 on the other hand is a mess in terms of development tools. But it is getting more and…
Sadly, the development environment matters quite a bit. - I will miss being able to declare classes using a sane syntax (Coffeescript helps in this regard) - I will miss the optional type annotations, which caught many a bug for me (you can use JSDoc annotations + closure compiler, but only if you like placing a verbose comment in front of every single variable declaration ) - I will miss having an IDE that can actua…
Re: Adobe ceases development on mobile browser Flash, refocuses efforts on HTML5
#163Earlier quoted context omitted.
I still used Grooveshark when you guys moved from Flash to HTML5, despite it being a less enjoyable experience. But, when the AIR app became just a wrapper for the HTML5 site, I cancelled my subscription. It seems like a lot of work went into switching, considering the functionality is still the same as the Flash version. Did any good come out of switching to HTML5?
Hmm... Upsides: It's easier to integrate ads and other third-party content like Facebook like buttons/comments, Youtube videos, etc. Unless you want to destroy Flash's performance by using a wmode other than window, there is no way to mix flash and html/iframe content. I'm pretty sure most people's hatred of Flash comes from ads that are not only annoying and poorly coded, but embedded with opaque or transparent. The…
Re: Adobe ceases development on mobile browser Flash, refocuses efforts on HTML5
#164Earlier quoted context omitted.
That's a developer issue, not a platform issue. A glitzy HTML5 application/website will perform worse than HTML5. Benchmarks: http://www.craftymind.com/guimark3/
That's why almost no one makes 'glitzy' apps in HTML5 - and this is, actually, a good thing . However, I expect it to change once Adobe tools for HTML5 will mature and gain traction. As was the case with Flash, these will be more popular among designers than among developers and - with all due respect to our fellow artists - we all know how it ends. Hopefully better hardware, GPU acceleration and WebGL support will b…
Re: Adobe ceases development on mobile browser Flash, refocuses efforts on HTML5
#165This makes me a little sad. For all that people complain about Flash, and any problems the Flash Player runtime has, it's really a fun environment to code for. I like AS3, I like the Flash API, and I greatly enjoyed writing Flex back when that was most of my job. I don't have nearly as much fun writing HTML/JS as I did writing AS3. I liked the (optional) strict typing. I liked writing for a single target and knowing…
In case you weren't aware, Flash sites :
- Do not work on 250 MILLION iPhones & iPads. - They are unusable to 1 BILLION SmartPhone Users. - Don't fully show up on Google Search. - Content is Not Shareable on Facebook & Twitter. - Are not naturally SEO Optimized.