Fjax? What’s that about?
Ajaxian has a post covering the much hyped Fjax alternative to Ajax. Off course the major flaw I see in Fjax is the F (which is the only “new” thing in Fjax anyway), Flash. I personally hate Flash, not because it’s not powerfull and you can’t do a lot of things with it, but let’s be honest, Flash scales horribly.
The point of Ajax becoming so popular is the fact that it required no extra plugins, add-ons or whatever you may call it, it just runs out of the box. If now we switch over to a Flash based solution we loose one of the major drivers in Ajax’s short history.
As Ajaxian puts it:
Jay and Steve McDonald didn’t like traditional Ajax (the libraries, the XML parsing (even though you can use JSON of course)) and decided that they could create “smoother, more desktop-like web experiences that AJAX promisesâ€, as they said in an interview at juxtaviews.com. What is Fjax? Website: “Fjax is an open, lightweight, cross-browser methodology for Ajax-style web 2.0 development Fjax is a technique focused on drastically streamlining the XML handling layer of web 2.0 applications. Picture Ajax’s XML parsing and handling with less than 65 lines of code! It’s not a replacement for toolsets that provide presentation-layer visual gizmos. Think of it as a new engine to put under the hood of all the great widgets that are already out there.â€Now, the image I draw may be a bit too dark, but we are moving away from all the REST-Architecture, service modelling, and other great things Ajax has brought to use, exaclty like the comet stuff some months ago. I’ll give Fjax a chance to prove itself but it is has no killer feature that might justify the hype about it right now.
