Microsoft built a web-based platform for the Internet, but they should have bulilt a Windows-based one
InkaSoft 7/1/2026 4:28:08 AM
Before the web, there were Client-Server network applications. The browser is a sort of thin Client. But Fat Clients were viewed out of favor over Web Browsers and Web Servers.
Client-Server is defined by its always connected network, unlike web ones which are stateless. Clients are also defined by their Windows interface. Windows applications always run faster than web browsers, because web browsers have to retrieve the entire UI and data every request (the UI being HTML). In a Windows application the controls are hard-bound to the data source for example to a server across the internet.
Microsoft never tried building Fat Client and Servers for the Internet. I think it was a mistake, they should have. Like I said the performance is many times faster than web based connectionless system. Many more things can be done with a fat client as it can access the operating system.
AOL is an example of a company that had Fat Clients. AOLs UI was a Fat Client, had instant news and weather updates because it had a connection to the AOL Servers,.
I am/was a .NET developer. I don't know if I will continue to be if Microsoft continues with the stateless thin-client model. I may try to reach out to the via blogs or something and see what they think.