Canadian Cybertech assists with Clean Technology adoption ranging from software systems architecture, system design and advancement of user experiences/security. We have over 25 years of experience helping companies gather the full and auditable requirements for IT projects to ensure success.
Tuesday, June 08, 2010
Open Source Media Framework Webinar Wed June 10
Lisa is a speaker not to be missed! On top of this, there is a chance to win a copy of CS5!
Register now (I have)
http://www.eventsadobe.com/osmflaunch/invite.html
Thursday, May 01, 2008
Yes Virginia - Adobe does listen to Slashdot
“The mere idea of higher ups at a previously assumed Big Evil Company paying attention to discussions on Slashdot (with critiques here often ruthless, multifaceted, and heavily biased towards consumer interests) is pretty shocking, and heartening.
If this signals a major shift in Adobe's operating culture, I think it's cause for celebration.”
http://slashdot.org/comments.pl?sid=539834&cid=23263596
Yes - it is true. In fact, we regularly peruse Slashdot to find out the latest, brutally honest opinions from the hardest to please tech-heads. I doubt we'll ever satisfy everyone but to recap, Adobe is definitely on the right track. PDF to ISO, The ActionScript Virtual Machine (VM behind Flash PLayer) open sourced via SourceForge, the Open Screen Project, The Flex Compiler open source project and BlazeDS are just a few examples of Adobe putting community and developers ahead of corporate greed. So what does this mean?
- Anyone who complains that Acrobat Reader is bloated is free to (try to) write a new PDF reader that works faster.
- Anyone who thinks the Flash Player is too slow is welcome to help.
- Anyone who wants a bug fixed in the Flex SDK can fix it for themselves and others.
- We all get to work together to build a cool technology stack that works for us.
What's next? Flash on the iPhone? Please already!!!
;-)
Tuesday, February 26, 2008
Adobe joins SQLite! More Open Source/Standards moves!
As reported at http://opensource.adobe.com, Adobe has joined with Mozilla and Symbian to support the work of the SQLite Consortium to help ensure free, open access and development of SQLite. Adobe uses SQLite within many of its products and recognizes the importance of providing support for technology and tools that are open source because of its value to the entire developer and software communities.
This follows on the heels of a rash of Open Source and Open Standards initiatives by the software company in the last few years. Adobe donated the PDF standard to ISO which is now ISO standard 32000. Adobe has open-sourced the core Flex SDK and Blaze Data Services under various GNU based licenses. It was less than 24 months ago when we also donated core Actionscript Virtual Machine code to the Mozilla Tamarin project. We have also pledged to contribute back to the Webkit HTMl engine project when we work on that code base.
All of this makes me proud to work for a company that understand the importance of the software community.Friday, December 28, 2007
Adobe Top Ten in Open Source
Excerpt:
Adobe Systems was one. It's long been a powerful proprietary-software company, but its acquisition of Macromedia led to a new sharing ethos. Shortly after a major donation of script-execution code to the Mozilla Foundation last year, Adobe announced in April the open-source release of its Flex tool for Flash programming.
As an Adobe employee, I cannot overstate the importance for Adobe of being open. As our Linux strategy has been greatly improved in 2007, we have also become aware that the next generation of the Internet (what some are calling Web 2.0) will be largely built on open technologies. I mentioned this in a recent German interview with Die Welt.
This group of technologies, to me, is comprised of the following:
1. Open Source - software you compile and can modify to do what you want. Bugs fixed when you want them and nightly builds.
2. Open Standards - software and protocol specifications designed to integrate systems and enable interoperability. Such standards must not only be not controlled by a single vendor in the end, but also be part of a free and democratic process, have multiple implementations to verify the standard, and be pervasive.
3. Open APIs - sharing the functionality. The basis of the new web is SOA, an approach to architecture to match needs and capabilities amongst disparate domains of ownership.
4. Open roadmaps and bug databases - to help us help ourselves.
I am proud to work for a company that recognizes the importance of these aspects and listens to its developers and users.
Happy new year!