I completely agree. Think of it this way, if you make a "program" that only increments an INT by a number, but then someone asks you to increment by 0.5 :confused:. Originally it was an INT. The no code says the same, I can only work with INTs, so don't change the parameter. No code = More Work = Hype = forgotten in 1 Year. :zzz:

Thank you for your input. Yes I am aware that it is a cross-browser/device supported language, but why not add one more? If I do a project with a framework in c#, I have to use an interop to get to DOM. If I use another framework, I have to always go back to JS. Seems a limitation rather than having the frameworks access DOM directly. It may seem that I have apples and oranges, but if we want to keep cross-browser/device functionality as you speak for one language applied to devices itself, then let us all use only Linux, or only Apple, or only PC. That is a whole different battle, but the heart of it all is the same. I like Apple, I use Apple; I like PC, I use PC. On that thought, for this example only, I like C# and am using a framework for developing a webapp, I use C#, but I also have to include JS. I am forced to include JS for DOM. So, I have to get another nuget, or addon, or plugin, or interop to have my C# code communicate with JS which then communicates with DOM and then DOM through JS give the desired response to my C# request/call/etc. What if I want to use C++, or the famous python? Plugins, nuget, addons galore. All browsers if they want to truly be cross/multi-platform should also be cross/multi language APIs to allow DOM access to what you are developing. Then you would be platform AND language independent thus giving the freedom to develop apps within the language that you choose.

Just needed to rant and to open for discussion. MS - Monopoly split, AT&T - Monopoly split, MCI/Worldcom - Monopoly split, Google - Monopoly...... Ect. We can go on and on about what has been taken down and split. Now I ask why is it that JavaScript is the ONLY language left on most browsers for DOM access? Why can't we use C, C-script, C#, EMCA-XXX, CGI, PHP, or any other? MS was slapped with lawsuit when they added classes to Java. I can understand why they won't touch JavaScript/DOM. But please, as new frameworks and Web Technologies rise, we need to ALWAYS turn from the network choice of language that we use, back to JavaScript in order to access DOM elements. We are forced to use JavaScript, oh and only JavaScript to access DOM. Mind you there are DOM Implementations, APIs and other AddOns, but they are just that, AddOns. If you want to access you have to use JavaScript, or as other frameworks call it, an interop with JavaScript. WHY? :confused:

I find that not one methodology fits for all needs, hence the need for various. SDLC, Agile, SCRUM, etc... depending on upper management and what they "understand" as being the methodology that will save them money is what they will implement and use/force down to us pawns. In my humble opinion, albeit all have their benefits, I think that the system chosen should be flexible to accommodate what you are managing. Production line manufacturing, down to simple app design for the latest in-style/market hype. Some may like agile boards to see where the stage of development is, yet others like Gantt charts, while still others like simple list of tasks completion and percentages with charts. For now, management will decide which we follow. This gives me an idea for an app.... :-O