The Irony is Strong with W3 Schools
-
A colleague just bought my attention to point (1), (2) was discovered very quickly: 1. They're still running on classic ASP! (At least judging by the address bar). 2. View Source reveals a shed-load of CSS styles defined directly in the HTML file. A classic case of do as we say, not as we do.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
A colleague just bought my attention to point (1), (2) was discovered very quickly: 1. They're still running on classic ASP! (At least judging by the address bar). 2. View Source reveals a shed-load of CSS styles defined directly in the HTML file. A classic case of do as we say, not as we do.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
Might not be as obvious as it appears.. [w3schools.com/ Technology Profile](https://builtwith.com/?https%3A%2F%2Fwww.w3schools.com%2F)
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
-
A colleague just bought my attention to point (1), (2) was discovered very quickly: 1. They're still running on classic ASP! (At least judging by the address bar). 2. View Source reveals a shed-load of CSS styles defined directly in the HTML file. A classic case of do as we say, not as we do.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
A company I worked for 15 years ago and I helped build their e-commerce sites still is using classic ASP and the topography of the web pages and querystring values look the same. Only thing that's changed are the images, HTML, and CSS. I expect W3Schools has a money maker with little growth; so they much the same as my former employer, they don't invest in a mature but profitable asset and could care less about security and performance.
-
A colleague just bought my attention to point (1), (2) was discovered very quickly: 1. They're still running on classic ASP! (At least judging by the address bar). 2. View Source reveals a shed-load of CSS styles defined directly in the HTML file. A classic case of do as we say, not as we do.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
A colleague just bought my attention to point (1), (2) was discovered very quickly: 1. They're still running on classic ASP! (At least judging by the address bar). 2. View Source reveals a shed-load of CSS styles defined directly in the HTML file. A classic case of do as we say, not as we do.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
it's a classic case of why change something that is already working! ;)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
A colleague just bought my attention to point (1), (2) was discovered very quickly: 1. They're still running on classic ASP! (At least judging by the address bar). 2. View Source reveals a shed-load of CSS styles defined directly in the HTML file. A classic case of do as we say, not as we do.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
My Saturday job requires me to use an e-commerce site that still uses classic ASP, at least according to the address bar. An upgrade was promised about 4 years ago to make it compatible with IE 10/11. It used to drive me crazy that the M-F manager cleared the IE cache on Friday, unwittingly also clearing the compatibility list. I would get to the payment screen and realize that I was unable to select a payment option due to outdated javascript/css! :mad: Luckily F12 lets me emulate IE9 to get through it! This is a pretty major US business web application that still can't take payments from Safari, Chrome, Edge or IE > 9 browsers! :wtf: I have a fairly large task coming up dealing with an inventory and ordering system I wrote in classic ASP. (started before .NET and maintained until about 5 years ago) The project had been unused for a few years, then a new customer came on board a few months ago and wants it. It still works great, but it will be much better in .NET! :) Personally, I always found classic ASP easy to understand...mostly just building a page from top to bottom. Debugging was another matter. X|
"Go forth into the source" - Neal Morse