|
Display # |
|
1 |
Magic Quadrant for Application Delivery Controllers
Gartner report: "The market for products to improve the delivery of application software over networks remains dynamic and innovative. Vendors focused on solving enterprises' most-pressing application problems have become the top players."
|
|
2 |
Why Ajax Is So Disruptive
Interesting take on Web 2.0 and AJAX by Dion Hinchcliffe, well-known business strategist and enterprise architect.
|
|
3 |
How JavaScript is Slowing Down the Web (And What To Do About It)
A short article by Alex Iskold explaining how JavaScript widgets are causing causing web pages to slow down.
|
|
4 |
How secure is secure enough?
"With a faltering economy beginning to put the squeeze on IT budgets, here are five steps to help you determine whether your company is secure enough."
|
|
5 |
Web Browsers of Tomorrow
Interesting article on "Web Browsers of Tomorrow" by Esther Schindler.
|
|
6 |
Are browsers ready for next-generation internet apps?
"Browsers were built to display documents, not deliver applications." Another good article by Esther Schindler raizing some interesting questions.
|
|
7 |
Prism
A short introduction to Prism, Mozilla's attempt at building a web application browser. Unfortunately they only managed to scrape the surface with Prism, but they do "speak our language" and mentioned things we strongly believe in. Like XUL, Prism was a good idea, but was too little, too late and missed the boat :-(
|
|
8 |
Google will define the future of software
A slightly controversial article by George Colony from Forrester research. Again, we don't agree with everything he says, but it makes for interesting reading.
|
|
9 |
Will Browsers Ever Deliver Applications Instead of Documents?
"What we need is a Web browser that doesn’t just serve up documents, but serves up applications." Ric Hardacre makes some really interesting points based on his experiences in developing web applications. Unfortunately his comments on replacing HTTP is not really practical but he still provides a good insider look at how difficult things can get when you are trying to make web browsers do things they were never designed to do.
|
|
10 |
How Microsoft Lost the API War
A mind provoking article by Joel Spolsky, an ex-Microsoft employee with an interesting take on software. It is a little bit long, but if you don't want to read the entire article, at least read the last bit from "Enter the Web". These are exactly the sort of things that the X-Appl browser was designed to solve.
|
|
11 |
Web-based Accounting
This article addresses web-based accounting solutions and seeks to answer these three questions:
1. What's the fuss all about?
2. What are the pros and cons of web-based accounting? and
3. What needs to happen for web-based accounting to take off?
(Note: Some of this issues raised here are solved by the X-Appl web app browser)
|
|
12 |
The Business Case for Rich Internet Applications
This article by Dave Wolf sums up quite clearly the issues with web applications built with HTML. Unfortunately, he fails to clearly define what his understanding of a Rich Internet Application (RIA) is and provides little proof for his claims. (Note: RIAs can add a lot of value to web applications, but should not be confused with web based applications and share little of the benefits of web based applications.)
|
|
13 |
Is the browser doomed?
The Web is evolving into a full-fledged app-delivery platform, calling into question the browser's ability to fulfill the needs of today's rich Internet apps.
|
|
14 |
Is the Web still the Web?
Neil McAllister has the following to say about Adobe Air and Microsoft Silverlight: "Applications written for these platforms don't resemble HTML in the slightest. They are binary blobs, little different from executable programs built for a desktop OS."
|
|
15 |
Fat is the new thin
"What is really beginning to force the issue, however, is the growing awareness of the limitations of the browser interface from a user perspective. The web browser was designed for navigating hypertext documents; it has adapted well to very simple business transactions, but not to more complex tasks."
A good article that identifies the main issues with browser based applications. The author clearly understand the issues, but (in hindsight) his choice of Java as a client side solution, was flawed. (Editor: Java is still often used for server side development, but is rarely used in client side solutions any more)
|
|
16 |
The other road ahead
"With Web-based applications, everyone uses the same version, and bugs can be fixed as soon as they're discovered."This essay was written by Paul Graham, creator of the Yahoo! Store (originally ViaWeb). A must read for any web application sceptic. BTW, an expanded version of the same essay can also be found in his book "Hackers and Painters".
|
|
17 |
On-demand apps demand a richer browser
Can the browser meet the demands of on-demand? On-demand apps are by definition Web apps. That won’t come as a shock to enterprises because most of the latest internally deployed enterprise apps — besides a few client/server holdouts — already rely on the browser to deliver user experience.
|
|
18 |
Top 20 Reasons why Web Apps are Superior to Desktop Apps
Vinny Lingham makes a couple of good arguments here, if you are still not convinced.
|
|
|
