Linked by Thom Holwerda on Mon 11th Jun 2012 00:38 UTC, submitted by judgen
Windows "Microsoft recently extended 'It Just Works' compatibility for Visual Basic 6 applications through the full lifetime of Windows 8. Visual Basic 6 first shipped in 1998, so its apps will have at least 24 years of supported lifetime. Contrast that with the Microsoft .NET Framework 1.0 (2002), which is incompatible with Windows 7 (2009)."
Thread beginning with comment 521817
To view parent comment, click here.
To read all comments associated with this story, please click here.
Alfman
Member since:
2011-01-28

galvanash,

"Not modern ones. There is virtually no reason to 'run' UI code on the server anymore. You may host it and serve it to clients, but you certainly don't need to run anything except your data layer."

It's probably not worth my getting involved here since I do agree with your overall message - leave bad legacy code behind when possible. However I'm not sure why you made the above claim? You must know that the overwhelming majority of web apps do generate UIs on the server instead of the client. Even modern frameworks like ASP.Net have done very little to shift UI generation to the client side.

It's technically possible to shift all UI code to the client side by using ajax and eliminating postbacks, but that's the exception rather than the norm.

Reply Parent Score: 2

galvanash Member since:
2006-01-25

You must know that the overwhelming majority of web apps do generate UIs on the server instead of the client. Even modern frameworks like ASP.Net have done very little to shift UI generation to the client side.


Well maybe I went a bit too far with that... I should have said "Not all of them". A combination of backbone.js or knockout.js with jquery on the client side can handle the UI and all the business logic - all you need on the server side is a data layer. There are other ways to do the same thing, ASP.NET has Atlas for example.

I wasn't really trying to say that this was the only way to do it, rather that server side generated UI code isn't the only way either. Web development does not necessarily involve server side complexities created by the UI code. The backend of a backbone/jquery web app is generally nothing more than a thin REST web service for fetching and retrieving your data. The nice part is you don't have to care much what the server side is (ASP.NET, python, Ruby, whatever) - it doesn't much matter.

Reply Parent Score: 2