Adobe, HTML5

Introducing Adobe & HTML

With so many exciting things happening at all levels of the web “stack”, Adobe wanted to create a single place where everything they are working on can be shared with the community to improve what is possible on the web and simplify how wen professionals work with HTML, CSS, SVG and JavaScript. It is here that you can find up-to-date information about all of the different HTML projects Adobe is working on, discover which events that will be worth attending, and find out how you can join Adobe in making the web better.

You can read the introductory statement…
http://blogs.adobe.com/webplatform/2012/04/23/proudly-introducing-adobe-html/

…or you can head directly over to the new site… more resources will be added in the near future making this a very promising portal to learn about Adobe’s HTML initiatives…
http://html.adobe.com/

One I personally find particularly interesting is the statement under Tools & Services…

Code
We think there’s a need for a different type of code editor – we’re working on something and will have more to share soon.

UPDATE on May 3rd 2012: Check out this announcement on the emergence of “Adobe Brackets”
https://blog.petermolgaard.com/2012/05/02/introducing-adobe-brackets-a-new-htmlcssjavascript-code-ide/

However, check it out… its all good stuff and could potentially make your life as a web professional easier and more fun…

Adobe, Flash Platform

Adobe roadmap for the Flash runtimes

For the past decade, Flash Player and, more recently, Adobe AIR have played a vital role on the web by providing consistent platforms for deploying rich, expressive content across browsers, desktops, and devices. Beginning as a platform for enabling animation, the Flash runtimes have evolved into a complete multimedia platform, enabling experiences that were otherwise not possible or feasible on the web.

Today Adobe published their latest vision for these platforms in the form of a whitepaper… check it out…
http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html

Adobe, Flash Platform, Google

Adobe and Google Partnering for Flash Player on Linux

Adobe has been working closely with Google to develop a single modern API for hosting plugins within the browser (one which could replace the current Netscape plugin API being used by the Flash Player). The PPAPI, code-named “Pepper” aims to provide a layer between the plugin and browser that abstracts away differences between browser and operating system implementations.

This is GREAT news for Flash and Flex folks out there, ever since Adobe decided to discontinue their effort to support Air for Linux in favor of focusing more on Android, its always been a thorn in the foot regarding Linux support…

Check it out…
http://blogs.adobe.com/flashplayer/2012/02/adobe-and-google-partnering-for-flash-player-on-linux.html

ActionScript 3.0, Adobe, Flash Platform, Flex, JavaScript, Open Source, Tools

Adobe’s view of Flex and its commitments to Flex in the future

Its no secret that Adobe has been going through a turbulent patch the recent months while they have been implementing their new adaptive strategy to an unruly future.

Its included layoffs and new hirings, internal repositioning and new layouts of their many divisions within services and products and they have taken a deep look at the business in terms products and offerings in the process of optimizing their market profile…

Its been painful, not only to see beloved team members leave Adobe but also to see that this major company refurbishing has not really been successfully communicated to both community, but also to users of the software and companies using services based on Adobe partners… even investors has been confused by the lack of diligence in the communication, however, its increasingly behind us as the new changes are settling in and the changes to the teams is stabilizing…

One of the massively controversial changes was the dealing with the future vision for Flex and the Flash Platform… I will not go into details with what has transpired over the past months, its well documented on every blog and site relevant to the community and product ecosystem and its not with a great pleasure I’m looking back on the past months… so let’s leave it behind and instead focus on the most recent statement from Adobe on their vision for Flex…

Now, there is not a lot new statements under the sun, however in contrast to the scrambling messages and divergent directions we have been seeing until now, its nice to see that Adobe has taken a deep breath and made a firm statement which would be difficult to misinterpret either positively or negatively…

If you are in a hurry and not interested in reading the entire writeup, I’m sharing with you the conclusion in a nutshell which confirms some of the more positive statements we have seen over the past months…

Adobe believes that Flex is the best solution for enterprise and data-centric application development today and is moving Flex into a community-driven open source project to ensure the continued development and success of Flex for years to come. We are currently in the process of contributing the core Flex SDK, automation libraries, AIR SDK binaries, and documentation to the Apache Flex Project. We will also be contributing Falcon, Falcon JS, Mustella, and BlazeDS.

In addition to these contributions, Adobe is providing a team of full-time Flex SDK engineers who will contribute to and support the Apache Flex Project. These Adobe engineers will work directly with the highly skilled Flex developer community to maintain, support, and evolve the Flex SDK. We remain committed to enabling the success of all existing and new Flex projects.

Thank you Adobe, for setting the record straight and for sharing with us your intentions and vision for Flex… its a privilege to be on the team…

Adobe, Arbitrary Thoughts, Flex, Open Source

A Saturday Night Status in the World of Flex

Upon a week of drama across the world of Flex, the past week proved to be business as usual… and thank heavens for that.

In case you have missed it, the Flex team at Adobe has amended their original statement regarding the future of Flex in the context of Adobe.

We are preparing two proposals for incubating Flex SDK and BlazeDS at the Apache Software Foundation.
In addition to contributing the core Flex SDK (including automation and advanced data visualization components), Adobe also plans to donate the following:

  • Complete, but yet-to-be-released, Spark components, including ViewStack, Accordion, DateField, DateChooser and an enhanced DataGrid.
  • BlazeDS, the server-based Java remoting and web messaging technology that enables developers to easily connect to back-end distributed data and push data in real-time to Flex applications.
  • Falcon, the next-generation MXML and ActionScript compiler that is currently under development (this will be contributed when complete in 2012)
  • Falcon JS, an experimental cross-compiler from MXML and ActionScript to HTML and JavaScript.
  • Flex testing tools, as used previously by Adobe, so as to ensure successful continued development of Flex with high quality

Adobe will also have a team of Flex SDK engineers contributing to those new Apache projects as their full-time responsibility. Adobe has in-development work already started, including additional Spark-based components.

You can read the entire post here:
http://blogs.adobe.com/flex/

Eventually, its a much more positive and inspirational variant of the post after the update compared to the original one, so thanks to Andrew and Deepa for taking the time to make the effort to apply the amendment.

In retrospect, I found the entire experience of having the bag shaken in which we have placed our faith to be motivational and a reminder to update my skillset. This last point is something we can all take away from this experience.

Upon talking with dozens of Flex developers over the past weeks, it became clear that some of us had forgotten to stay updated and expand our toolset, and regardless of what happens to Flex, this is an important reminder. A professional is only as good as his tools allow him to be and the quality of the output depends on both the skill of the professional as well as their ability to choose the right tool for the job.

We should use Flex when it makes sense and remember to stay tuned to what is going on in other areas or our industry for the moment when Flex may not be the optimal tool for the job.

Another reminder I have taken away from this experience is my old commitment to continuously contribute to at least one Open Source project at any given time… obviously I will be contributing to Flex once it hits the repositories… why don’t you join me ?

Adobe, Flash Platform, Open Source

OpenSource AVM… Tamarind

Project Tamarind, once so promising and bespoken project… was co-owned by Adobe Systems and Mozilla Foundation, and has been discontinued for more than 3 years now…

However, the sad state of this cool OpenSource project is that it hasn’t been touched since March 2008…


The members from Adobe are mostly names I have never heard of so I sincerely wonder what have become of them (perhaps they are still engineering in the dungeons of San Jose), anyways check the names out for yourself…

If anyone knows the obituary belonging to Project Tamarind, please do share… it seems to have been a massive Adobe effort that apparently ended up in a fruitless archive of The Mozilla Foundation.

Anyways, you can check out the archived project home page here…
http://www-archive.mozilla.org/projects/tamarin/

Adobe, Adobe Flex

Quick Pointers about Flex (and Flash Platform)

A lot of confusion has arose triggered by the recent announcements by Adobe… among one was that they would hand over Flex SDK to Spoon and leave updates and maintenance to the community, in this case including the way it has been done, imho. means the very rapid departure of Flex as a viable application platform.

Even in the upcoming 4.6 release, its far from feature complete to make it a viable mobile platform (Native Extensions is a half-baked poor solution to lack of resources to implement what should be part of the platform) and general performance remains ludicrous despite the effort put in to improve it in addition to the UI control which should be the force of Flex is far from complete.

Adobe Flex’s ultimate force was as an enterprise platform, however Adobe has in the past week announced that they are replacing Flex as the recommended enterprise application platform with HTML, please read Deepa’s blog post describing the change in focus of Adobe Flex…
http://blogs.adobe.com/flex/2011/11/your-questions-about-flex.html

The fact that the Flash Runtime is lost on mobile in general with the last weeks announcement to discontinue Flash for Mobile and the fact that it will not be running in Windows new Metro browser system makes it a no brainer that Flash Platform is going down as well, now its just a count down which we eventually dont know how long will take before Flash will disappear as a platform… the proposition that Flash Platform should survive as a casual gaming platform is difficult to have any sincere faith in, but perhaps time will show that there is a market to support it as a gaming platform, however as a RIA platform Flex and Flash Player Runtime is now officially not viable anymore anymore than ActiveX and Java Applets are…

Soon we will see Adobe taking all their hard earned knowledge and experience building Flex and putting into something equally useful, but based on the Web Standards stack and not a closed source proprietary platform such as Flash Player…

This is good news, it will make applications and experiences build using Adobe technologies generally better software system citizens by using the same technologies as the other members of arena, and now Adobe can focus on providing tooling and framework and not focus on maintaining a runtime as well…

We are already seeing some of the directions the tooling will take us, you only have to look at Adobe Edge, PhoneGap, jQuery Mobile possibly Adobe Muse (if you want to be aMused) to see that they are already way ahead on this and soon ready to release the first tools to facilitate making the initial experiences and small app’s using Web Standards Stack in replacement of Flex and Flash Player…

We are still far from having the strength of ActionScript and the Flex Framework, not to mention Flash Builder and the SDK itself, however it will come and we will be even better positioned for creating great experiences and apps for our markets than we were with Flex and the Flash Player runtime…

Following a comment to the post, I wanted to add this except from my response as its essential for the understanding of my point here (and to address the things I on purpose didn’t address in this post):

The current state of affairs is exactly that as described, Flex is no longer a recommended platform and there is no alternative available (yet) that can equalize it… thats it, in a nutshell.
However, making the decision to change focus and resources to be allocated on HTML instead of Flash and Flex is a good and sound decision, regardless how the decision may have been communicated and left us people working with Flex where the rubber meets the road hanging to dry.
The message itself and how you deliver the message is two separate things, the message is good and clear, the delivery was not exactly up to par which is causing the confusion now and the uproar in the community.
Therefore, my suggestion is that we discuss these two aspects separately from each other. In my post I was not trying to discuss the way this new change of focus and technical strategy was conveyed to the public and the community, but instead only focus on the decision itself and what it means in the long run for us working with Flex.

I agree, we are stuck right now with a very delicate situation because of this and because many people and even people close to Adobe were not made aware of this information until the public did… there are some pretty horrid stories going on backstage right about about how some people were left hanging to try on stage while presenting Flash Technologies, where people in the audience were following on Twitter how the storm hit following the Flash Mobile announcement, something the Adobe Rep on stage wasn’t informed about, and therefore were made to look like an ass on stage in front of 250+ people.

Lets keep pragmatic and keep emotions aside when discussing constructively what technological decisions have been made and what it means to us in the community, then we can always discuss the approach used afterwards when the dust has settled…