I like the philosophy of the REST style, but I also have a major beef with it. Before getting in to that, let’s first define what REST is. Right now, there are two flavors of REST. One is the real one, as described by Dr. Fielding in his dissertation. The other one is what is merely any web service that uses HTTP, URIs and Json as its mechanisms.
The latest and greatest from Microsoft when it comes to web development is Microsoft MVC. Although the acronym is new to many young web developers, MVC was actually quite popular in object oriented UI development in the early eithies. Back then, the best implementation did not only have one Model, they had two.
Imagine if Toyota trying to forbid anyone to publish information on how fast it is from 0-100 km/h (0-62 mph) or how much petrol it consumes per mile. Consumer activists and governments would not have it. But hear this! Some database engine vendors actually do just that!
The web browser is taking a giant leap forward. The average user has yet to see the difference it will bring, but on every smartphone and desktop, there is a roaring tiger waiting to come out of its cage. The most important change is that the biggest player, Microsoft, had to change its stance.
The countdown has begun for the real time web. The technology is out on iPhones, Androids and desktop users having Firefox or Google Chrome. Now we are holding our breaths for Internet Explorer 10, the final piece of the puzzle. What I’m talking about, of course, is WebSockets.
Software people are bound by trends and tradition. Although some of us wants to think of ourselves as forward thinking and open minded, we are no better than our peers.
Applications that Create, Read, Update and Delete are should be so simple, and yet, they create so much headache. Writing a local application for a single user is simple. Writing a scalable multiuser system is hard.