I felt like I was watching a visual in an art gallery commenting on the human condition. If you Ctrl+- out all the way and linger on some of the choice phrases you get a better show.
Alas, if only browsers could zoom out infinitely you could conceivably use this method to create a convincing "Star Wars"-esque scrolling text field using only plain HTML.
Ling's Cars is intentionally bad. It's part of her brand. At one stage she had a site map which was laid out like a concentration camp, with the various visitors to the site shown in different sections with a stick-figure whose head was the relevant browser logo.
You might see shitty design, I see brilliant one.
This site looks like mail order Catalogues from the nineties. Kid in me cant stop screaming "I want that, and that!"
Information density is phenomenal.
Well, hard-coded styles don't get cached by browsers, so that's probably not the best example.
That being said, there are a lot of things people can do to improve performance that they neglect to. Sometimes it's just the pressure to get things done. Still, it's worth going back to revisit these issues.
Citation needed. I've seen evidence to the contrary. Generally anything with cache-control (or equivalent) headers suggesting that it should be cached, will be.
At my uni there were a large number of profs with websites that, if you viewed the source, showed that they'd been creating in MS Word. This was a CS department. Slightly depressing.
I worked a bit in research and HTML was generally treated as a serialization format for other tools and HTTP was considered a dumb transport.
I had a presentation about REST&Caching and stepped through many of the low-level behaviours of HTTP, like the properties that verbs have and their interaction with caching.
I ended up explaining the whole HTTP verb thing for multiple days straight because it was kind of a revelation to many.
Now, the research department worked in a whole different department, web was only coming up as a topic for them and was of tangential interest.
My conclusion: CS is a vast field. Don't expect experts in theoretical CS to know practical details. Don' expect practitioners in compiler building to know how to build a website or anything about distributed architectures.
It's not depressing, it just shows how vast our field is.
Sounds like ie default header font size is absolute whilst other browsers go with relative. Each approach has benefits, but support for highly nested headers is pretty low on the list :-)
This is almost as wonderful as Subway's old website. I think that one had something like five HTML tags and a few BODY tags sprinkled randomly throughout.
Writing a HTML parser to handle everything that's out there on the web is almost as hard as writing a C compiler that tries to produce the "most accurate" executable code based on what it looks like you probably meant.
It was created on August 14, 2013. I am just glad small business like this continues to run and use technology. We should send an email and tell them to fix it. I am also glad the site didn't go down after all this traffic...
I'm actually surprised. So many unclosed h3 tags would seem to indicate it was a programming error and that the page was generated by some script rather than a visual editor.
Hilarious! Initially I was thinking "poor fellow who made this mistake" and eventually I felt like I got trolled, this almost feels like its not a mistake! PS: There are 38 <h3>s and 2 </h3>s.
There's a subtle brilliance here. The font starts out reasonably small and increases in parallel with the frustration of the individual doing the troubleshooting.
That's actually beautiful, I'd never considered this as a possible outcome of nesting tags with em font sizes. By the bottom of the page one letter was about 3000px high.
In college, one of my professor's syllabus page had this exact problem. It wasn't so bad at first, but half way through the course you had to scroll so far down the page that the syllabus was barely legible. So I downloaded the page, cleaned the markup and sent him the refactored HTML page, much to his delight.
Right at the very top of the page, they explain that. in case of "Thread Breakage" you should "try re-threading the machine", and also "make sure the thread goes through all guides".
It appears that their web designer has taken this advice to heart.
Dear God, the entire source is on one line. There aren't even spaces between tags. From looking around the website a bit, this doesn't appear to be a joke, so I'm seriously wondering how this could happen without anyone noticing.
Since the site was made in FrontPage, I’m guessing that the FrontPage WYSIWYG view showed the site as looking fine, so the author didn’t bother to visit every page on the site after mass-uploading the pages.
Seems like it's IE being a bit loose with the spec (the doctype is html 3.2 after all) or just catering for the likely hood of a rule for one element being used for another.
Wonderful! Usually when I find something hilarious, I share with my non-programmer friends who stare at me like I'm some sort of freak; and I am surprised every time.
