Quote:
Originally Posted by tonypa
"Only fools and idiots and stagnant developers not seeing the bright future of AS3 would use Flash and write code in timeline. "
that is nonsense. Clever people would only use AS3 where it makes more sense and use something else where that makes more sense and leads to better results in shorter and more enjoyable dev cycles and also to the content being visible to more people or run in better performance or allow more functionality.
So for 3D stuff many would use other technologies, even for going for other devices (flash runs on mobiles but way worse than java , its not available on iphone right now which already dominates 30%+ of the US mobile market and is climbing to similar numbers in other markets for example). For flash content creator people looking for really high penetration numbers, not faked statistics showing over 90% penetration in less than 6 months they´d use what´s more widespread, so older plugin versions. Also older flash/AS versions allow way faster rapid prototyping and in general quicker content creation so yeah, quite professional groups like nitrome interestingly still have most of their games in flash 6-8 creation way setup and churn out games in a speed barely possible with as3 workflow.
Besides that i totally agree with your comment, its Adobe´s own fault when flash ide sells worse and worse, they don´t add enough new features to it to make it interesting for pure designers (many newer features aren´t even integrated in graphical editing workflow) and they broke workflow between flash ide created graphical content and the codeside so much that with AS3 it really makes most sense to best use flash ide created graphical as few as possible in a project, so yeah, they leave fewer and fewer reasons to use flash ide.
One has to differentiate there between two things:Quote:
Originally Posted by The Helmsman
1.: Things one can only do in AS3 thanks to content written in it in average having better code execution performance
2.: Things one can only do with it thanks to new syntax elements only available with AS3
to 1:
this is due to Adobe´s unwillingness or inability to propperly make use of the gpu with flash, if they did that propperly one could code things in AS1 and they would run at a ton better performance overall (code execution + graphical side combined) than the laughable performance flash now achieves overall when coding in AS3.
to2:
this is due to Adobe´s inability or unwillingness to propperly integrate the language versions and api enhancments in sensmaking way.
Which would for example be that all new snytax/api additions are also made available in AS1 and AS2 syntax. Also that they integrate things like in mono so one can use all language versions inside the same project.
So yeah, it would be totally feasable to allow doing things in AS1/2 that right now are only possible in AS3 thanks to the made up limitations by Adobe.
I don´t say oop and AS3 are all bad, it makes sense to do certain things in such workflow and mindest, usually reoccuring programming side only tasks one can then reuse and share in easier way than a fla with the code in it or also when its about doing massive frameworks for longtime reused code bases and projects.
That is just not what the majority of flash projects is about. The majority of flash projects is about doing flash content in short timespans which are in average at most updated 1-3 times after their release.
Also small game developers are usually about getting their content out quickly and to the biggest possible audience, bigger ones doing higher end content are often about performance and functionality not available with flash and also when you look at their code its mostly tailored for performance and their workflow, not readability or best oop practices.
Which zinc and other wrappers allowed ages ago and with tons more functionality needed and used in propper desktop apps.Quote:
Originally Posted by The Helmsman
Sure air would have in theory lots of custom nice sides like not having a machine specific binary but instead deliver a file type that can be experienced on all machines if they have a specific runtime. Well, that all is mostly unrealized future potential right now, you have to bet on Adobe spreadig the air runtime well and also working out all the kinks nicely and propperly improving the functionality in the coming versions. If you want to just make a desktop app today and spread it as much as possible and have most functionality at hand today you´re well better suited with other stuff than air. Also with their security and other thoughts based limtations they introduce in each technology i wouldn´t wonder if one still doesn´t have half the functionality/api commands when doing air apps in 5 years which one can use with zinc etc now.
One can structure things well when doing a flash/code combination inAS1/2, too (besides the point one can actually combine timeline animation, movieclips etc with code which is very limited with AS3) and also its not that much more fun either to work on someone else´s AS3 project and you first have to see how he did things,which workflow he used and which editor(s)/ides.Quote:
Originally Posted by The Helmsman
I´ve worked on othes AS3 stuff which was a combination of flas, flex component stuff and code files, AS and mxml mixed where they guy thought each made more sense, that wasn´t particularly fun to work with either.
Overall Adobe did a great job in totally convoluting the workflow with their apps/languages to the degree where its almost always a mess when you open someone elses or even your own project (after a while not having worked on it and maybe having changed your workflow some or using their newer apps) no matter which apps and workflow you had before.
"kick ass interactive websites" as presented by FWA is not what 99% of the web cares about. FWA mostly pushes advertising crap. People doing advertising websites often try to sell the newest en vogue toy to their clients in attempt to have a made up edge over a competitor or ask for more money. PV3D content for example is not what drives the web though and looks sucky to most people not caring whether it was made in flash and that´s why one should amazed by way outdated slow running,leading to the computer chugging crap.Quote:
Originally Posted by The Helmsman
no, it doesn´t, hackers, as they always do find loopholes still and Adobe´s "security measures" limit developers and lead to millions of existing content sites breaking. Also with changes breaking old content Adobe puts a very negative image on using the flash platform for any longer time used content, it is a very important side to be able to say this is backwards compatible when its about a plugin and Adobe messed that up.Quote:
Originally Posted by The Helmsman
