Fork me on GitHub

Tagged: flash RSS

  • britg 2:08 pm on September 2, 2008 Permalink | Log in to leave a Comment
    Tags: adobe, ajax, flash, , google chrome,   

    Who Google Chrome Affects the Most: Adobe 

    I see a lot of coverage of the new browser out by Google – Chrome.  And rightly there should be – this is pretty exciting stuff!  Javascript running on it’s own thread per tab?  Sweet!

    I’ve also seen a lot of “Should Mozilla be pissed?” or “How will this affect Microsoft?” etc.  But I haven’t seen a lot of coverage on who I think is affected most by this move: Adobe.  Why?  Because the whole concept behid Chrome is to spead up web applications, namely Google’s style of web applications which all happen to be using AJAX instead of Flash.

    So, if Google has completely revamped it’s javascript engine in Chrome so that each tab operates javascript in it’s own thread, and you can run AJAX applications like google docs, gmail, etc. continuously without worrying about your browser bringing down your entire computer, we’re likely to see a renewed interest in AJAX as a platform.  Also, we’ll see a renewed effort from other browser vendors to make their javascript engines comparible.  This is all bad news for Adobe Flex/Flash.

    How are you, as a web developer, going to build that next business app?  Using Adobe’s Flex/Flash platform that requires users have a plugin installed (although most do) but has all the limitations of Adobe’s Flash plugin running in the browser?  Why would you when for most business applications, AJAX can meet all your needs AND be optimized to run as well as desktop applications?

    No matter what the outcome, it’ll definitely be fun to see how this plays out!

    Oh, and I’m writing this blog post through Chrome – it’s so new and shiny, go get it now!

    Update: Chrome doesn’t have to gain huge market share for this scenario to play out!

    Chrome is open source and hence their Javascript Engine is open source! (http://chromium.org) So, Chrome doesn’t have to make a huge dent in market share to make a huge dent in how the other browsers support javascript and AJAX apps.

    From limited testing over about 2-3 hours I could noticeably tell a difference in performance running Gmail, Google Docs, Google analytics, and google reader in separate tabs as opposed to doing this on firefox.

    This tells me that their javascript engine technology is superior to others out there – and since it is open source, I can imagine a scenario where other browsers, especially mozilla, adopt this engine.

    So, google chrome may never ever gain market share but I’m willing to bet their javascript technology will! This is what bodes poorly for Adobe in my opinion – a new browser market that isn’t dominated by Chrome per se, but is dominated by fast and multi-threaded javascript engines!

     
  • britg 6:43 am on July 1, 2008 Permalink | Log in to leave a Comment
    Tags: flash, , search, yahoo   

    Searchable SWFs – Game Changing 

    Adobe just dropped a bomb as far as I’m concerned.  They’ve announced a collaboration between Google and Yahoo to bring fully searchable SWFs.  Ted on Flex reveals the best part:

    The cool part is that this also covers dynamic data loaded in from requests to a server, these are typically ignored in both AJAX and SWF applications.

    This is going to open the door for a lot of the cool and useful things we’ve been wanting to do for clients at Figaro, but have had reservations about because of SEO implications, and  I’m sure many RIA houses out there feel the same.

    Combine this news with a tool like swfaddress to provide deep linking into your applications and BAM! you have a killer combo.  Let’s just remember to keep our apps classy and tasteful, guys and gals.  This news isn’t cause to go hog wild with flash like the late 90s, early 2000s restaurant site debacle.

     
  • britg 6:27 pm on June 18, 2008 Permalink | Log in to leave a Comment
    Tags: flash,   

    Iphone Web Is Not The Real Web… 

    … until they add support for flash.  Period. The recent news about the whole SproutCore framework for iphone web apps just doesn’t do it for me.  Venture Beat puts it well when they say:

    Do you want a browser that lets you use hypothetical “open” applications that will be developed in the future, or one that lets you browse the web as it exists right now? You know, the web where many popular sites are built on Flash technology? Yeah, me too.

    Someone should write a dystopian story about what would/will happen when Apple creates their own little sterile corner of the web where only apps built for their framework/libraries/safari javascript engine work properly.

     
  • britg 10:51 am on May 30, 2008 Permalink | Log in to leave a Comment
    Tags: , flash, multiplayer   

    Thoughts on Massively Multiplayer Flash Gaming Infrastructure 

    I’ve been thinking a lot about the different options we could use for the Space Survivor infrastructure.  The game itself is flash based and the site uses html/css (doesn’t make sense to make the entire site flash for performance reasons) and the site-specific framework and semi state-less page views will most likely be on CakePHP.  So, if you just want to check your stats, view ships, read missions, or anything that fits into the normal webpage paradigm it’ll most likely be served from a PHP server.

    When we start talking about the technology required to provide a backend for the actual game, that’s when the choices get interesting.  Most multiplayer games on the PC or console probably use some sort of custom framework for handling network traffic, probably written in C, C++, Java or some other low-level language.  But, I kinda want to mix things up and jump on what I think will be the next generation infrastructure for networking/multiplayer in games – Erlang.

    There was an article on Reddit quite a while ago – Writing Low-Pain Massively Scalable Multiplayer Servers – that really says it all a lot better than I am qualified to.  I highly suggest reading it, but I’ll talk about concurrency here.

    Erlang is a great choice for multiplayer infrastructure because it was built from the ground up to be a high-concurrency system.  It’s trivially easy to add nodes to an Erlang cluster because there is built-in node detection; so once you create your new instance of the Erlang emulator and connect it to any other node in your system, all other nodes become aware of it.  The bottom line is, you don’t have to spend any resources creating this network effect  – it’s a fundamental part of the language!

    In the article I linked to above, Joel recommends creating a node for each processor on a machine.  It’s not uncommon for servers now to have 8 processors, definitely at least 4.  So if erlang is your platform of choice, you can immediately create 4 or 8 instances, each doing separate tasks and maximizing your CPU usage out of the box!  Amazing.

    I’ll continue this discussion in later posts as I gain more understanding of how things fit together in an erlang-based multiplayer infrastructure.

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
esc
cancel