5 ms·
The problem with Flash is that at some point people started using it to build websites. And then all hell broke loose. You had content which couldn't be indexed
by elorant 9y ago
The problem with Flash is that at some point people started using it to build websites. And then all hell broke loose. You had content which couldn't be indexed, broken browser functionality, severe usability issues, big load times (let's not forget that bandwidth wasn't always ample as it is today), security vulnerabilities, and a variety of other issues that made the whole experience pretty lame. So while Flash did indeed offered some unique capabilities in a friendly and frictionless package, it also hurt the web in so many ways.
- andybak 9y agoThis was the main factor that had developers cheering for Flash's demise. 1000 terrible restaurant websites plus the fear that it might catch on and supplant HTML thus ceding ownership of the web to Adobe.
- mattmanser 9y agoThis feels a bit like rewriting history, it wasn't for that long that people used flash to write websites. In my recollection there was like a 2 year window when you'd occasionally hit a flash site and groan to yourself. It was google that stopped that when people realized their sites weren't getting listed with SEO. And it seemed to be confined to mainly restaurants for some reason ;) I actually think it didn't hurt the web, it was a massive driver for change, Flash highlighted the lack of functionality in html/js and was part of the reason that forced html to finally get canvas, etc. If you're completely honest with yourself, you'll realise that html/js are still years behind what you can do in Silverlight and Adobe Air. Now it's mobile apps that are forcing the web to carry on evolving and highlight just how backward html/js is. In years time we'll have people saying that phone specific apps were terrible, but in reality, without something to show us the flaws of html/js are, it wouldn't move forward. Personally I'm no fan of the mono-culture of the web, the idea that you can only use one language, either for markup or for programming, should be anathema to all of us and instead it is bizarrely celebrated. I'd far prefer to be using Python or Ruby or whatever than javascript and in reality I think it's probably costing the world billions or trillions in wasted effort as we schlep around with javascript.
- brusch64 9y agoSomewhen around 2005 many bands had Flash websites. And this is pretty much the last time I've seen full blown Flash websites. The only thing I'm using Flash now any more is watching videos. Where I'm living it is sadly still the standard for some TV stations video websites.
- graysonk 9y agoSidenote: But I don't understand why restaurant websites that I have seen are so bad. Is there a specific, prolific company that does these? The trend of restaurants around me is to just have a single png scan of their menu and nothing else. I was talking to one owner and they were wondering why their SEO was so bad
- graphitezepp 9y agoI strongly suspect it is as simple as restaurants tend to not have much money for anything that is not strictly operations related.
- ghaff 9y agoI think in context the parent was somewhat suggesting the opposite though. The websites for (higher-end) restaurants and hotels are often this mess of sliding images and pop-ups that can, among other things, make it almost impossible to do something simple like find the address, make a reservation, or look at the menu. And a lot of this was done in Flash at some point. I suspect it just became a sort of arms race with everyone competing on sizzle rather than usability. What you're describing is pretty much small businesses everywhere. Presumably this is a lot of Squarespace's target market.
- noxToken 9y agoUnless its a national chain, the ones in my area are either building it from scratch or using a template. The made-from-scratch are painfully obvious in that they look like some high school student with a touch of experience cobbled it together. And that's probably what happened - the owners child or niece/nephew did it. The template sites are obvious because the owners chose a feature-filled template with all of the bells and whistles but have no use case for all of the frills. There are empty carousels, tons of extra white space, empty link slots, and a halfway responsive mobile experience. Considering the above, a static, zoom-able HQ image of the menu is not a bad option. It's not optimal, but it's not bad. It tells the restaurant's name, phone number, business hours (possibly), address (again possibly), plus the entire menu. That ticks all of the major boxes for information that a customer may need.
- crummy 9y agoThe restaurant websites that required flash were a pain in the ass, for sure. But there were some amazing experiments in pushing the boundaries of what I considered a website to be. This is an archive of one of my favourites, the Requiem for a Dream website: http://archive.hi-res.net/requiem/ http://archive.hi-res.net/requiem/
- _pmf_ 9y ago> You had content which couldn't be indexed, broken browser functionality, severe usability issues, big load times (let's not forget that bandwidth wasn't always ample as it is today), security vulnerabilities You're describing modern, client rendered web applications.
- pritambaral 9y agoAt least one of those things is significantly reduced with modern client rendered web applications: security vulnerabilities. I wholeheartedly agree the host of power than Flash brought, but I'm glad for its demise because — among other reasons — of this: that rich interactivity on the web is now largely standardized and open.
- Nekorosu 9y agoThere were a lot of flash sites with marvelous experience. The site size was controlled by its creator. There is no difference in this regard between bloated flash site and bloated site built with standard browser APIs. Indexing was fixable by some additional effort and it's the same with these days SPAs. Basically most of those complains apply to a lot of modern web sites.