Skip to main content

Technology discussions today and tomorrow

For as long as I can remember, developers(but also all other kind of IT people) have religious descussions about ‘there’ technology; Java vs .NET, stored procedures vs dynamic SQL, client side vs server side and so on.. And just when you think people start agreeing the next discussion knocks on your front door.

One interesting discussion I followed closely last year(it already seems so long ago) was ASP.NET WebForms vs MVC. I especially liked the post by Scott Guthrie showing some common sense on the debate. I totally agree with Scott’s point about the nature of technical debates, and the acceptance that some technologies suit better for some problems.

However with the emergence of new web technologies like CSS 3 and HTML 5, the growth of REST and the renewed interest in Javascript, I want to re-open the discussion. I think that architecting ASP.NET MVC applications will have a lot more potential than WebForms. Just think for a second what you have to do to transform your current ASP.NET MVC applications to an HTML 5 enabled application… not so much. Now do the same thing for ASP.NET WebForms… this will be a lot harder! As long as Microsoft doesn’t release a new version of WebForms where the server-side controls can generate HTML 5, it’s just not possible.

Why HTML 5 makes the difference?

No matter which web technology you use, in the end all you get back is an HTML response, but HTML has its limitations in that it is static. You need to post a request to the server each time you want some new action to occur. In some cases this ‘complete form and submit’ model works, but we have become used, from smart clients, to a more dynamic model that provides feedback as we make selections. Customers expect that web applications behaves like smart client applications. And it’s their that HTML 5 can really make a difference! It extends the browser capabilities to a full client side experience in a much simpler way than is possible today.

And this brings us to the next discussion, which technology will drive the smart client behavior on the browser? The question of Webforms vs. MVC is already an irrelevance. That is yesterday’s fight and victory has been declared despite a few units continuing to fight on. The next war is already happening between Silverlight and Javascript for ownership of the smart client…

It are interesting times…

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more