3 ms·
Why there was a need to make a thick abstraction over HTML and HTTP I'll never really understand. How could you want to obscure what are very easy and simple t
by pmarsh 18y ago
Why there was a need to make a thick abstraction over HTML and HTTP I'll never really understand.
How could you want to obscure what are very easy and simple tools still baffles me.
And having talked with some programmers who use nothing but ASP.NET it's amazing how in the dark it has left them.
- fauigerzigerk 18y ago"How could you want to obscure what are very easy and simple tools still baffles me" It's because HTTP/HTML is a very simple tool for what it was created to do: retrieving and displaying static pages. Everything else is not so simple. As soon as people started to move data entry forms with master detail screens, etc. onto that platform things were getting nasty. Since Microsoft is the master of master detail forms, or at least of the platform on which most of them have been built, they felt a need to come up with a solution. And the solution the "company who never understood the web" came up with was ... XMLHTTPRequest. No, seriously, it was ASP.NET. No, wait, it was both! ;-) The world is confusing.