21–30 of 70 posts
2- For every company you acquire how many companies do you look into and end up not buying?
Hey Kenneth: I watched your two M&A announcements today with keen interest, because I've been watching the overall market change and we're kind of trying to figure out where Adobe fits into things. Where we used to use flash, we're using HTML5 for web and mobile, and where we used to use Adobe SMS, we're now using brightcove, kaltura, and others. We're phonegap hackers as well. I'm trying to figure out if Adobe is mo…
Contracts aside, what is the normal expectation regrading how long founders & employees of the start up remain with the acquiring company?
Does Adobe have a strategy to fight HTML5 or make good progress with open standards b/c of the Typekit purchase? We don't want Adobe to shut down Typekit by any means b/c of how awesome it is and I'm afraid Adobe is resistant to HTML5 as an open standard. Please don't throw money at solutions to killing amazing products which enhance HTML5.
I would like to down-vote this question as it makes no sense given everything Adobe has done to the contrary of these concerns over the past year. I'm not a huge fan of Adobe, but I can appreciate their efforts regardless. I advise the author to review the adobe labs and check out what has been done re:HTML5 and CSS3 over the last year. http://labs.adobe.com/ http://labs.adobe.com/technologies/edge/ http://labs.adobe…
Very good question, but one that needs a responsible answer. Adobe wants the web to live on using its proprietary formats like Flash while a growing minority is resisting this and switching to HTML5. Adobe's efforts are a good start but have a long way to go. Muse, for example, has good intentions but in practice is a horrible product with extremely convoluted code.
I'm not a Flash hater as I love the fact that YouTube grew on this standard and many fun games are because of Flash but I also see the reason why HTML5 is a much better standard to get behind and why technologies like Flash will ultimately die unless they become more open.
How important is conflict resolution during these deals?
(This one is really broad and shows some ignorance) When you are driving acquisitions, do you treat the deal like a developer would treat a large project? Do you have a set of requirements that you work toward? Do you have to track changes and perform QA?
Does Adobe have a strategy to fight HTML5 or make good progress with open standards b/c of the Typekit purchase? We don't want Adobe to shut down Typekit by any means b/c of how awesome it is and I'm afraid Adobe is resistant to HTML5 as an open standard. Please don't throw money at solutions to killing amazing products which enhance HTML5.
Adobe has shown no contempt for HTML5, while HTML5 pundits continually rip Flash. Adobe has repeatedly stated that their Flash product and their Web products serve different goals and markets, and they are in the business of providing cross-platform solutions wherever there is a demand. If you watched the keynote today, you would have seen that Adobe itself is creating some of the best HTML5 / CSS3 dependent applicat…
Does Adobe have a strategy to fight HTML5 or make good progress with open standards b/c of the Typekit purchase? We don't want Adobe to shut down Typekit by any means b/c of how awesome it is and I'm afraid Adobe is resistant to HTML5 as an open standard. Please don't throw money at solutions to killing amazing products which enhance HTML5.
Adobe is strongly supportive of HTML5 and open standards. In fact, we've recently released two tools, Edge and Muse, that are built on HTML and related technologies. We intend to help Typekit continue to grow and continue to leverage open standards.
I see decent intentions with products like Muse but its faults outweigh its benefits and I do not expect this particular product to see much life unless its vastly improved or changed.
As a web coder, I heavily rely on products like Photoshop and am disappointed with bloat and inefficiencies I've experienced over the years, so I really have hard time believing the same fate won't happen to Typekit. That said, I am going to try to keep the skeptic in me quiet as I watch what happens to this awesome product.
Do you have any recommendations for teams with lots of Flash-based content, to prepare for the transition to an HTML5 environment? Can we continue creating Flash content as we always have, trusting that Adobe will provide a means to migrate/recompile our existing FLAs or SWFs to HTML5 when the time comes? Or should we take any preparatory action to ease the transition? For instance, authoring our graphics using SVG, writing our code in an intermediate scripting language that may be compiled to ActionScript or JavaScript, etc?
I realize you might not be the best person to ask about this, but in your position it seems probable that you'd be aware of the roadmap for Flash. I realize the roadmap is confidential, but any tips or recommendations would be greatly appreciated. Alternatively, if you could recommend someone for me to talk to about this, I'd be grateful.
EDIT: Any sort of response would be great. There seem to be a lot of folks here who are interested in this issue.