Mobile flash is discontinued. And then there's the fact that Flash is buggy, resource intensive and just plain shit.Looks nice but no flash
html5 is even worse... less powerful and buggy too.... (ex. youtube html player is bs)
Hardware Wii U Browser details: tabs, screenshots, HTML5, no Flash
html5 is even worse... less powerful and buggy too.... (ex. youtube html player is bs)
I don't think one example of embedded video protocol is an accurate way to measure the efficiency of an entire set of standards...Mobile flash is discontinued. And then there's the fact that Flash is buggy, resource intensive and just plain shit.Looks nice but no flash
html5 is even worse... less powerful and buggy too.... (ex. youtube html player is bs)
As a programmer, that just reeks of "BS", in fact.
As a programmer too, still think html5 is still not mature enough.. flash may be more resource intensive but it's still much more powerful and stableI don't think one example of embedded video protocol is an accurate way to measure the efficiency of an entire set of standards...Mobile flash is discontinued. And then there's the fact that Flash is buggy, resource intensive and just plain shit.Looks nice but no flash
html5 is even worse... less powerful and buggy too.... (ex. youtube html player is bs)
As a programmer, that just reeks of "BS", in fact.
The problem with HTML5 is that it does not work the same on each browser. Everyone makes his own interpretation of this or that API and you end up spending hours, if not days making your code compatible with every browser, only to end up with dirty hacks everywhere... Which is not the case with Flash. Plus there's no real effective workflow or tools to develop HTML5 game easily, as opposed to Flash. And JavaScript can't really compete with AS3...I don't think one example of embedded video protocol is an accurate way to measure the efficiency of an entire set of standards...Mobile flash is discontinued. And then there's the fact that Flash is buggy, resource intensive and just plain shit.Looks nice but no flash
html5 is even worse... less powerful and buggy too.... (ex. youtube html player is bs)
As a programmer, that just reeks of "BS", in fact.
(inb4 "bullshit javascrept is awsum, flash iz dead blablabla", I'm a developer and work with both HTML5 and Flash everyday)
http://www.cvedetails.com/vulnerability-list/vendor_id-53/product_id-6761/Adobe-Flash-Player.html
Flash's stability and security are a travesty.
D
Deleted-185407
Guest
OP
I work with HTML5 everyday, and I've honestly had zero cross-browser issues unless it's something to do with obscure APIs like History or Fullscreen API. With more commonly used functionality such as canvas I have yet to encounter a single problem when it comes to cross-browser compatibility. Heck, surprisingly enough, IE9 runs my canvas web apps the best and most reliably. Spending days making sure your code works in multiple browsers is a thing of the past, unless you're targeting ancient browsers like IE8.
As for tools, that's entirely up to yourself, you're not limited to anything. Personally I'm happy enough using Notepad++ and GIMP for developing all of my web apps. Working on the low level means I have much more power, no compile times, and overall I can develop at a fast rate. If you're wanting a tool to develop HTML5 games specifically, you can always look into applications like GameMaker which recently added the ability to export to HTML5.
And if a HTML5 feature you've seen somewhere is buggy, blame the developer, not the language. Blaming HTML5 for being buggy is like blaming C/C++ for being the cause of a developer's ignorance of buffer overflows.
They're not obscure, they're simple features that should work out of the box with the same couple of functions on any browser, and it's not the case... I'm sick of mozSomeFunction, or having to have 8 lines of the same property on a css file with -moz, -o, -webkit, etc...
I also worked with WebSockets a lot. Different drafts implemented in different browsers, responding differently to different errors, and most of the time little to no way of correctly debugging it, especially on mobile browsers. It's a nightmare. Also had to code a C++ websockets server, that has to deal with all those different personalities... Couldn't they do REAL sockets like everywhere else ?? And more importantly, when is everyone gonna drop JavaScript for a real language with balls (and by balls I mean classes, real objects, imports and all that jazz...)
I wonder who you worked for, but our clients always want IE7/Firefox 3 compatibility...
D
Deleted-185407
Guest
OP
It doesn't. I guess there'll be another app for porntube or adult-comics or things like that.
...which will make the miiverse all the more awesome: all your friends will be able to see where you're spending all your "gaming" time.
(pick-up line of the future: hi there, lady. I see you're over 18. Can I invite you to my fetlife-app?
")
can you tell me what problems you get with flash player?? -.- as for security, it is sure not that secured but if you develop carefully, it should be no problem
When I say "obscure", I mean not often used at the moment, or in high demand, or whose specification hasn't been fully decided yet. That's why Microsoft doesn't implement a lot of new HTML5 features because they refuse to implement features that don't have a finalised specification yet. WebSockets being one of those features. Naturally you're going to have lots of issues if you're using experimental protocols. Steer clear from the experimental aspects of HTML5 and you shouldn't have any problems at all. As for those CSS vendor tags, not much you can do about it, but it's certainly not going to add "days" onto your development time. The only downside is that it might consume a little more bandwidth to send that CSS file down to the client.
JavaScript is just a functional language as opposed to an object orientated language. Take C for example, still very commonly used and very powerful, and it doesn't have classes at all. You can easily simulate classes in both JavaScript and C though, with JavaScript containing several different approaches. If you really want imports, take a look at something like require.js which encourages modular code. JavaScript has gotten so popular and powerful, that server software like node.js uses JavaScript as the language of choice, and Windows 8 allows developers to create "metro" applications in HTML5/JavaScript. It's a ridiculously flexible language. If you want to keep it functional-orientated, you can. If you want to make it object-orientated, you can. If you want to make it strict, you can. I believe the next revision of EMCAScript is going to add a lot of new features to be more similar to other languages anyways.
The company I work for will only support the latest browsers unless it's an internal tool (because internally, IE7 and IE8 are still being used). We want to be able to provide modern content, and to do that, we can only support up-to-date browsers. We haven't had a need for anything like WebSockets yet (Comet is working perfectly well). Don't want to say too much though for obvious reasons.
javascript is pretty good imo... one of my favourite scripting language.
D
Deleted-185407
Guest
OP
The problems are in flash player itself, meaning that the security issues affect the end-users who have it installed, not specifically anything a developer would make.
The link I posted has a good list.
http://www.cvedetails.com/vulnerability-list/vendor_id-53/product_id-6761/Adobe-Flash-Player.html
type html5 vulnerabilites on google and you can also get a list.. sure flash player has its cons but i still think flash player is still better, more mature and more powerful than html5 at the moment.. it will probably change in 1 or 2 years as everyone is shifting to html5
No you don't, because "HTML5" is a specification, not a single product.
- "Flash Player" is a program installed on the computer that can run arbitrary code and modify the user's system. If you'd look at the vulnerability list I linked to you'd find it's a real list of actual, existing vulnerabilities. Seven of them were entered into the database this month alone, and range from things like possible DoS attacks, to code injection.
- "HTML5" is not a program, in fact HTML (by itself) is not even a programming language. It's a specification that browsers will support, so any security holes would be in an individual browser... the same browser that's currently used with flash. The only thing you'll get by googling "HTML5 vulnerabilities" are theoretical vulnerabilities based on overarching designs, not actual security holes.
Getting rid of flash and sticking with HTML5 will reduce the vectors of attack.
Similar threads
