The Death of an HTML5 Game Breeds an Open Source Project
colinneagle writes "German social gaming company Wooga has thrown in the towel on its HTML5 project after seeing little return on the increasing amount of effort put into its Magic Land Island game. Some early success convinced Wooga to devote additional resources to the game, which was launched in October of last year. However, 'As the project continued to progress, so did the industry. Whilst the benefits of an open platform future are clear for games developers, it became clear halfway through Magic Land Island's development cycle that the technology wasn't yet ready for mainstream exposure.' The announcement sheds some interesting light on HTML5, as Wooga hardly holds back on any of the details behind the game's failure. The biggest barriers to HTML5's entry to the mainstream include internet connectivity and limitations on sound. The consensus? The time for HTML5 will come; it's just not quite there yet. In the meantime, Wooga has made the game open source so other HTML5 developers can learn from it."
Nethack 3D! 8^)
A feeling of having made the same mistake before: Deja Foobar
Didn't they get Steve Jobs' memo?
What political party do you join when you don't like Bible-thumpers *or* hippies?
The time for HTML5 will come; it's just not quite there yet.
I've been saying this for awhile now. HTML5 is neat, but it's still not anything more than that right now.
What do I know, I'm just an idiot, right?
So there is the Facebook icon but it isn't mentioned in the summary at all. Is it a game that was targeting Facebook?
Sound in web pages has been an abomination since the moment it was introduced. I never want to have to go searching through dozens of tabs looking for the one website that thinks its so important that it needs to blare audio at me. Anything that plays audio without the explicit consent of the user is incredibly impolite.
Give me Classic Slashdot or give me death!
You can't run C++ from a browser using any sort of standards
You can if you code to SDL (the de facto standard for 2D games' I/O), compile it for Windows, Mac, X11/Linux, and Android, and then offer binary packages (msi, dmg, deb/tgz, apk) through standard HTTPS. The only browsers you won't hit with this method are Safari for iOS, IE for Windows Phone 7, IE for Windows RT, and browsers for game consoles.
Flash is dead, yes. It didn't run on all devices like HTML does
Flash's media capture API runs on a lot more devices than HTML5's. So do Flash vector animations, without having to bloat them by a factor of ten by rendering them to cosine-transform-based video.
Using apps ensures literally 100% compatibility with the target device
And 100% more headaches with the device manufacturer's screening process, as the article points out.
I don't see Microsoft, Mozilla, or anyone other than Chromium rebranders implementing support for the Pepper API used by Google Native Client applets any time soon: "Mozilla is not interested in or working on Pepper at this time."
When you go to youtube, you're asking for video. When you search the web for information on bananas, you're not asking for "I'm a banana" repeating in the background as you read up on the cultivation and export of the fruit.
I'm hyping my own projects here, but over the past weeks I've been porting free software games over to Android. Specifically, games that use the Simple DirectMedia Layer (SDL) library. Most of the games are written in C++, and the OpenGL (OpenGL ES in the case of Android) functionality is handled via the SDL library. I have had a good response so far for some of the games.
I have the games as different branches from my tree on Github. My tree is a fork of Sergii "Pelya" Pylypenko's port of SDL 1.2 to Android. One branch is a (partial) port of the popular educational game Tux Math. Another branch is of the game Circus Linux, which I felt did not translate well to Android (at least as I did it) so I never published it to Google Play. I should be putting a few more branches up on Github soon - ports of Ri-li, Hex-a-hop, Ice Breaker and so forth. The Ri-li source will probably be the next one that I will put up.
Good god yes! Just because I click through to a video doesn't mean I want to watch it immediately. I often middle click through half a dozen links to open them in new tabs, and then watch them one after another.
This is why I keep youtube blocked in noscript, to enforce click to play.
Give me Classic Slashdot or give me death!
Technically C++ runs on those devices, but the ability to execute native code is cryptographically locked down so that only a few developers selected by Microsoft can code in C++. Everyone else has to use C# or another statically typed, verifiably type-safe CLR language. DLR languages such as IronPython require Emit, which is not present in the .NET Compact Framework, and P/Invoke raises a security exception.
But Chrome took over the top browser spot from IE.
That's a plurality, not yet a majority.
So who gives a fuck what a bunch of wannabes think?
Any web developer that wants to reach a three-fourths supermajority of PC users, for one. At this point, Google Native Client runs on as many distinct browser engines as ActiveX. Or how do you expect to get people to install Chrome just to run one web application?
Theoretically a native executable can be just as secure as a JavaScript engine: run it in its own user account. The trouble is that home PC operating systems provide no one-click way to make a dedicated user account for a single application.