Nissan Leaf
nissanusa.com
nissanusa.com
That said, for nearly every other aspect of developing thick client RIAs and complex visual experiences, flash/flex/as3 wins by a mile. From IDEs to the display api to as3 apis in general to the true object oriented architecture to lack of browser inconsistencies to client side storage to sockets and networking options to modular applications.
Say what you want about flash. It certainly has its problems and it has certainly been abused, but let's not ignore all the areas where js is still playing catch up and will be for a long time (even it's just IE). Flash has been a lead innovator in web-based interfaces for many years. Even if it's true that it's in decline, completely discounting such an important technology only shows ignorance.
I mean, I can block JS, but it's irritating to have to. That's generally used for useful things like navigation. Flash marks something up as useless pizazz.
As HTML5 takes over we will see more unstoppable content - pop-up panels, intrusive advertising etc.
I just wish we could pay for the web without all this crap.
Maybe Adobe's next ad campaign will feature this idea: Flash is better because you can turn it off. In fact, if you turn it off, you remove 99% of all truly annoying ads on the web.
Thinking ahead, maybe we need a ClickToJS...
1. File -> Preferences -> Show Develop menu in menu bar
2. Develop -> Disable JavaScript
There are certainly a few corner cases left in which flash remains a better fit, but it's losing territory, fast. Good work Nissan.
That Nissan example ran pretty clunkily on my laptop and another desktop I checked in the office.
(That said, gradient transparencies always seem to doom Flash pieces to slow-hell for me.)
Anyway, the quip with rendering performance is only a matter of time. With every browser release, CSS and HTML rendering performance is increased, for example, by leveraging GPU acceleration.
Flash will be beaten soon, I'm sure. And at least that works for every platform, not just the ones on which Adobe decides it's important.
I've had a bad day dealing with HTML email newsletters so I'm probably a bit more pessimistic about it than usual, but all sides of working on the web are a serious pain in the arse!
It has been said before: not Flash is the devil. It's people who program but who have no clue how it's done. They have destroyed the reputation of a not-too-bad platform.
edit: Just saying, people who knowingly choose Linux don't expect to use Flash.
Note: I use Windows / OS X on the desktop.
When the web relies on a technology where the "protocol" is "first install this proprietary plugin, if it's available for your setup, and if not, screw you," it is antithetical to the protocol-based approach.
Look at how much browsers have improved in the last few years, making new things possible on sites. This happened because anybody can write a browser that conforms to HTTP protocols, Javascript specifications, etc. Do you see the same kind of improvement in Flash players? No. Because there isn't competition.
The web is better off without Flash. Or anything else that can't have 100 competing implementations.
And how can you say JavaScript "will never" kill Flash? Aren't Apple and JavaScript already hurting Flash's market share? Doesn't every major browser release leave less and less that Flash alone can do? Aren't we looking at an example of a major, mainstream brand avoiding Flash for a site? What is going to change over the next few years to reverse these trends?
<video ontimeupdate="sendXHR(currentTime)" src="myvideo" controls></video>
...where "sendXHR()" is a five- to ten-line wrapper around XMLHttpRequest.
One of these days, a "must have" killer app is going to come around--that could have been written in flash--that will force me to buy an Apple. At a ridiculous premium.
I don't think that's too hard to understand, predict, or dislike, given that people have been bitching about a similar strategy from a similar company for many years.
This seems really, really simple to understand, but let me know if it's still confusing.
On top of all of that, you are confusing how Apple is trying to kill Flash and replace it on the iOS devices (which is not entirely accurate).
So, while you thought you were clear, you weren't. You were confusing, incoherent, and frankly, even after I tried to give you the benefit of the doubt, I still find your arguments weak.
> This seems really, really simple to understand,
Context. You cannot join a conversation talking about something completely unrelated and expect to be understood.
The topic is flash. Everybody is saying that it should be replaced. Its replacements include 'X' and 'Y'. The fact that I reference 'Y' rather than 'X' is a completely natural context switch.
It took reading through multiple comments that were out of context from the original discussion. Your original comments weren't clear.
> I'm pretty sure that everybody else understood me, even if they claimed otherwise, because we're not idiots here.
That's your sign. =)
We generally aren't idiots here. So if people are having a hard time understanding what you mean, assume the problem lies on your end and that you are failing at communicating. Again, context is important, especially in threaded conversations.
> It's a cheap tactic to pretend that I'm "incoherent" when I am certainly not.
But you were. You're believe that you were perfectly clear hinders your acceptance of that.
And please understand I say this with the hope of helping you see how you weren't clear. I mean, I took the time to read your comments, which meant I had to highlight them, even though they were voted down. I could easily have ignored them.
> The topic is flash.
Flash on the web and JavaScript, CSS and others replacing Flash. That's the topic. It's not just flash.
> Everybody is saying that it should be replaced.
Yes, everyone is saying Flash on the web should be replaced.
> Its replacements include 'X' and 'Y'. The fact that I reference 'Y' rather than 'X' is a completely natural context switch.
It's "replacement" on iOS devices is not part of the topic, for several reasons.
The technology being linked to is not limited to iOS devices. In fact, it has nothing to do with Apple. Apple, in truth, has little to do with the desire to remove Flash from the web. However, they did put a spotlight on it.
So, if the technology being linked to and discussed (JS, CSS, HTML, etc) has nothing to do with Apple, but rather open standards, then it's fair to assume when you talk about proprietary devices, you're referring to iOS devices and the apps there. This is confusing. Flash has never been on iOS, meaning it's not being replaced. Also, Flash isn't being replaced on the desktop either. Flash is the one trying to be the platform to develop desktop applications on.
But that's mostly irrelevant, because you said this:
"I really don't want to be forced into paying the 50-100 percent Apple premium for hardware just because they managed to "kill" a technology everyone decided to hate for no reason."
You won't be forced to pay Apple premium for hardware. In fact, costs will only go down, because what is replacing Flash is open standards. If Flash dies today, nothing changes in terms of your choice of computer to use.
In fact, by keeping Flash alive, you are forcing others to pay a premium. By replacing Flash with open standards, you essentially level the playing field.
Anyways, this has gone on for quite a bit.
However, it in no way stands as example of either good design or the strengths of Flash.
The push here is to eliminate an unnecessary layer from the web stack. And I would point out that while apple has taken the steps to rid flash from their mobile platforms, they aren't leading the charge per say, they are just a very large player in this space.
Finally, just because flash dies, doesn't mean you'll have to buy an apple computer, last I check FF / IE / Opera and even gasp Safari run on non-apple platforms.
That a company with such incompetent programming and slimy marketing can come to be so ubiquitous -- this indicates something is broken in the functioning of our software market.
The last time I visited my sister, I asked her why she had Adobe Reader installed on her new 15" Macbook -- AFAIK, she doesn't need it, and Preview, which comes pre-installed, is so much more responsive. (Yes, I was watching her wait for a PDF to come up.) She just pretended I didn't ask. I wonder what trick they pulled?
Once, a few years ago, I started snooping around my old work laptop. Some background process was soaking up large amounts of CPU, even when I had no applications up. I found it was some Visual Basic background process polling so it could instantly spring into action with some Adobe Suite thing. After I deinstalled Adobe and installed Foxit Reader, my machine was much snappier!
First, I don't own a single apple product. Thinking back, I don't think I ever have. When I worked at Yahoo they gave me a macbook, and I traded it with one of the Indians when he visited (Yahoo india got HP laptops which run linux, and were kinda okay copies of the thinkpad T series. My boss was okay with it, but Yahoo India made us trade back the next time the guy came to America.)
I'm a linux guy; I don't use flash. Security hazard, you know, if you compromise my workstation, it's damn hard for me to stop you from compromising the systems I admin.
but you know what? that website? works great on chrome in Linux.
Me, I don't like apple any more than you do. I like it less, most likely. I'm extremely unlikely to buy any of their hardware (if nothing else, the macbook keyboards and trackpads just feel /wrong/ somehow. I mean, it's just preference, but they just do not work for me. I've been using ThinkPads with the little eraser head pointers for well over half my life. Not switching now.)
But we can all cheer for the death of flash, that is, if you can do everything you can do in flash with something more open and less buggy.
* Silly animations are a bad idea in Powerpoint, a bad idea in Word, and a bad idea in web documents. Word seems to be the only place where most people avoid them though.
* Running a program in a web page breaks statelessness.
* Support for disabled readers will get lost.
I understand that gopher - just text and a list of links - is a little too minimalist. But the other extreme (setting up a GUI just to show a document) is worse.
When I read a title like this, I pretty much assume that I'm not going to get any decent semi-objective information from the post.
It's flame-war fodder if you ask me.
Aside from technical issues, I think the above is valid philosophical argument per se due to closed nature of Flash.
From the very beginning, the Web evolved as an open system; no special tools are required for content creation and every browser has equipped with a "view source" feature.
Namely, video, and site navigation.
For other things it could be used - but you could also use HTML5 like the site in the example to do anything you'd do in Flash, and not lock out iPad, iPhone, Android users. Plus, it's open.
So it looks like it will use Flash if you have it.
I'm guessing that you mean 40% of visitors to sites (not the one for the Nissan Leaf) use IE. (Or more specifically IE 6.)
I think it's probably a pretty safe bet that folks who are visiting the Nissan Leaf site, and ESPECIALLY folks who would be early adopters and buy an all-electric car, are probably also not rolling around using IE6. (At least, I'd hope not.)
Conversely, someone being on an iPad or Android device is probably a pretty decent leading indicator that they're in the demographic that would consider buying a Nissan Leaf.
Seriously though, if you were building this site, I'd suggest you'd probably worry a lot more about how it looks on an iPad than a WinXP box running IE6.
The site I work on doesn't even cater to early-adopters the way the Nissan site should, and we have lots more iPad / iPhone / Android traffic than IE6 these days. (And I mean each individually, not in aggregate.)
<desc>Created with Raphaël</desc>
http://raphaeljs.com/reference.html
Awesome stuff.
http://www.nissanusa.com/leaf-electric-car/js/js.swf__v2.0.2...
I agree that it's nice that the browsers are now supporting new features that allow so much well needed functionality across the board - but they're really just now catching up to what Flash has offered us for years.
Forget all-flash websites. Seriously, forget them. I like the OP's site about as much as I liked flash intros from 2001 before they started adding "Skip This" buttons. I'm referring to media players, socket clients, file uploading tools worth using, vector animation, a decent programming experience that worked across the board (AS3 is actually a fun language if you give it a real shot).
Where would the web be without Youtube? Where would Youtube be without Flash? How about last.fm? or Pandora? Do you remember what the web was like before flash? Real Player, anyone? Java applets? I'll take a flash game over a Java applet any day. Regardless if you use these media-centric sites personally, they changed the internet as we know it - making it accessible to normal human beings. To disregard Flash's place in that history doesn't make any sense.
And it's far from over. The browsers STILL haven't gotten media playback right across the board. Everything's a big fat beta right now and IE is dragging us behind as usual. It would be nice if everyone could at least agree on a codec or two, but no. Meanwhile, flash-based media players still work just about everywhere.
I'm happy that the browsers are catching up with Flash - truly. I loved developing in Actionscript, and I'll love replacing it. But these claims that Flash is somehow the bane of the internet is to deny some of the very foundations of how successful the internet has become.
> To disregard Flash's place in that history doesn't make any sense.
Nobody is saying that Flash wasn't worthwhile, ever. It's just nice that something that used to be a large part of the web can be taken out of the hands of a company, and returned to us all.
> But these claims that Flash is somehow the bane of the internet is to deny some of the very foundations of how successful the internet has become.
Ehhhh I'd disagree. I certainly agree that until very recently (and not quite yet for everyone), Flash is no longer needed, and that that's a good thing. Flash is a threat to the Internet: it's in the hands of Adobe. The web should be open, and for everyone. But that's precisely _because_ the internet has become so successful. It's far too important to be left under corporate control.
So what you're saying is that without Flash, YouTube wouldn't have existed until 2009 or 2010?
So not quite true.
I have click to flash set up and before I could click, it replaced.
Changing the underlying technology will not change the people who use it.
Don't be silly! everyone wants faster horses! EVERYONE!
Keep me posted when RTMP media, video/webcam/audio capture, audio analysis, content protection is supported cross browser in HTML and JS.
This site is as much about marketing and generating appeal as it is about information. I don't see anything wrong with how it was done. Someone enlighten me please.
Edit: And somewhat off-topic - is it a requirement that production electrics cars have to hideous? Tesla and Chevy (Volt) seem to be the only ones that have made them actually nice to look at.
Why? Because people who are choosing to buy a hybrid or electric usually want EVERYONE ELSE to know they got one. That's one reason the Prius has no "regular" version - if you see a Prius, and its distinctive shape, you immediately know the person bought a hybrid. With other cars, (including the Tesla) you have to see the badges on the back to know. So part of the "moral reward" for buying hybrid, paying more and sacrificing some performance is lost.
It also works on my iPad. The 360 is a bit slow but it's there.
I wouldn't have visited Nissan's web page today, or any time soon. But I did, Nissan owes that guy a nice bonus.
Big brands like Nissan have a large budget to spend on the latest and greatest, and they do it. The studios that do the development are allowed to try new things, and they do. For Nissan, they get a site that looks fantastic, comes in on budget, and garners responses like this thread. The studio that does the work gets to add a site like Leaf to their portfolio of work, and their designers and developers learn a new skill that can be transferred to other high paying work. A win for everyone really.
It's talent that matters, not the platform.
Counterexample: http://blog.phono.com/2011/02/17/how-to-build-a-voip-based-b... (browser-based VOIP, Flash under the hood)
Bizarrely, Chrome has support for speech input on text-based forms which translates microphone input to text on their servers, but it doesn't expose direct access to the audio. Argh!
If you believe that advertisers can live without animation, you have your head in the sand.
The thing that really struck me the most about this is that as little as 2 years ago there would have been absolutely no chance of deploying a huge brand interactive experience without Flash.
This is the first time I've seen a site that I thought was obviously Flash only to right-click and not see "Zoom in". I was pretty gobsmacked.
Those menus are rather distracting and complicated for an average consumer site.
ps. OT but the "Leaf" is not available in green ???
Which is funny, considering in many cases it's probably Flash handling the audio for this, and thus the title is inaccurate.
Javascript by hand?
No flash there. It will fall back to flash in Internet Explorer.
Replicating what Flash does in HTML, CSS, SVG & JS is not the way forward.
Plus you don't lose on search engines and history management can be left to the browser.
Never mind.
I don't think thats a very common requirement: there are other, much more straight forward barriers to replacing flash with html + js, such as lack of dev/designer skills (ie. number of people whom can do that in flash vs whom can do it in html + js).
Or it seems that CSS is supporting animations and maybe that is a better choice over javascript? (because the browser, I presume, can optimize CSS a lot easier than javascript which can have arbitrary functionality.)
it will not work on 100% of the devices. but at least they got some clicks from us that they wouldn't otherway.
Continuing with this rationale: if done in flash, it would have take the team 10x the time to that instead of plain html. or 200x the time if done in a simpler html format, like a wikipedia article.
it would work on 100% of the devices... you would be able to use back/forward buttons, you would be able to translate on google translator and still see the site... wouldn't use all the cpu... it would load instantly for the user (well, it would be loading the rest bellow the fold while the user was reading/looking at the top part)... it would hopefully play well with screenreaders... i would still be able to use the left menu even after increasing font size... but you wouldn't have buttons that jump around.
the facts to support that are all the posts here in HN talking about A/B testing on landing pages. What gives more conversions, to good products? flashy shiny things, or to the point information about the advantages and simple call to action?
The brand is the quality. Branding is just reminding you of the quality.
anyway i doubt the comercials for MB then were pointing out the quality of the engine instead of being just empty branding marketing.
> it probably took the team 10x the time to do that this way instead of flash.
If so, that's only due to the maturity of the tools out there. Imagine creating this in Keynote and being able to export to HTML5.I bet folks here would love it too.
The fancy stuff is like a 4 color brochure. Always skippable if you want information. http://www.catb.org/jargon/html/F/four-color-glossies.html