Mozilla Launches Browser Built For Developers
HughPickens.com writes "Mozilla announced that they are excited to unveil Firefox Developer Edition, the first browser created specifically for developers that integrates two powerful new features, Valence and WebIDE that improve workflow and help you debug other browsers and apps directly from within Firefox Developer Edition. Valence (previously called Firefox Tools Adapter) lets you develop and debug your app across multiple browsers and devices by connecting the Firefox dev tools to other major browser engines. WebIDE allows you to develop, deploy and debug Web apps directly in your browser, or on a Firefox OS device. "It lets you create a new Firefox OS app (which is just a web app) from a template, or open up the code of an existing app. From there you can edit the app's files. It's one click to run the app in a simulator and one more to debug it with the developer tools."
Firefox Developer Edition also includes all the tools experienced Web developers are familiar with including: Responsive Design Mod, Page Inspector, Web Console, JavaScript Debugger, Network Monitor, Style Editor, and Web Audio Editor. At launch, Mozilla is starting off with Chrome for Android and Safari for iOS. and the eventual goal is to support more browsers, depending on what developers tell Mozilla they want, but the primary focus is on the mobile Web. "One of the biggest pain points for developers is having to use numerous siloed development environments in order to create engaging content or for targeting different app stores. For these reasons, developers often end up having to bounce between different platforms and browsers, which decreases productivity and causes frustration," says the press release. "If you're a new Web developer, the streamlined workflow and the fact that everything is already set up and ready to go makes it easier to get started building sophisticated applications." Mozilla released a teaser trailer for the browser last week.
Firefox Developer Edition also includes all the tools experienced Web developers are familiar with including: Responsive Design Mod, Page Inspector, Web Console, JavaScript Debugger, Network Monitor, Style Editor, and Web Audio Editor. At launch, Mozilla is starting off with Chrome for Android and Safari for iOS. and the eventual goal is to support more browsers, depending on what developers tell Mozilla they want, but the primary focus is on the mobile Web. "One of the biggest pain points for developers is having to use numerous siloed development environments in order to create engaging content or for targeting different app stores. For these reasons, developers often end up having to bounce between different platforms and browsers, which decreases productivity and causes frustration," says the press release. "If you're a new Web developer, the streamlined workflow and the fact that everything is already set up and ready to go makes it easier to get started building sophisticated applications." Mozilla released a teaser trailer for the browser last week.
i already gave up on ffos development (because of the bad tool quality) a year ago.
I thought so too, but it's not. They link the previous announcement in TFS; this is the actual release.
I just kinda wish it was Chrome that came out with it.. In general I just prefer the layout of their development tools. I'll definitely give this a try though.
Hmm, the humour and sarcasm seem to have been be lost on you.
So, they're running Android and iOS on your computer to run the same binaries as those platforms? If not, it's only emulation and when someone says they're emulating another browser the result is usually not worth it and nowhere close to the actual results on the other platforms.
Get free satoshi (Bitcoin) and Dogecoins
If this stuff is mostly concerned with Java for the browser, it's probably the first application I've ever seen directly intended for JavaScript implementation.
Everyone needs to breathe in oxygen or they will die! Take a breath!
when my Firefox decided to stop starting at all.
Sure, I guess I need to be a developer to fix it now.
Whatever their plugin management does, it can and should do better.
Sorry Mozilla, you have poisoned the well for many developers. The whole Brendan Eich situation and your cowering to the social justice warriors makes me not only avoid your products, but actively remind people that you are a sleazy political organization first, with a browser tool far second. Google's heart isn't much better but at least they have tact in their public relations.
Instead of developers fixing websocket traceability, they focus on making a new theme. Firefox has clearly too much designers. It's enough that every two or three versions the color of the developer console changes (and its design), and now an extra browser? I hope they don't transport the developer features into that browser, leaving firefox as a "customer only" product. When I was at places where I couldn't install software (libraries etc) I have been always happy to debug websites with the standard browser.
that Moz/FF is still focusing on stupid features that are already covered by other tools, rather than fixing their memory leaks and other bugs. Hopefully we'll get another pointless UI facelift soon too, I've finally adapted to the last one.
Now the Firefox team can remove all the developer crap from the regular browser.
Is amazing how most of the browsers, in order to pander to developers, became bloated with developer cruft. Do not get me wrong, getting developers to use your browser as primary is important. Nonetheless, this could have been done using the add-on/plug-in interfaces using an official set of add-ons/plug-ins, instead of bloating the browser.
Here I hope that the offering of a specific browser for developers means that the consumer and ESR browser are streamlined as a result.
*** Suerte a todos y Feliz dia!
Internet browsers should be built and designed for one simple thing.
Browsing webpages.
If the site needs Turing complete code, run it server side. I don't want, nor should I have to run your program. Doing so is a huge security risk and in most cases sluggish. This whole webapps and javascript everywhere BS is really degrading the internet imo. Specially when the majority of "web programmers" are in the bottom rungs of quality.
In summation, browsers shouldn't be virtual machines. I know I'm a minority voice compared to the general consumer, but it's good to vent. ;)
Now the Firefox team can remove all the developer crap from the regular browser.
Removing even the most basic JavaScript console from the standard browser would be a bad idea. It'd encourage some developers of prominent web sites to block users of the developer browser as a "security" measure. Facebook and Netflix, for instance, already block use of the JavaScript console out of "self-XSS" worries; removing even "view source" would make it even worse.
Please don't. Even non-developers are increasingly using the basic devtools to manage the modern web (defeating right-clicks, removing elements that get in the way, etc). And far more practically, the dev tools let devs diagnose bugs with users as they happen, without having to frustrate them with lots of extra steps that might lose their session entirely. At this point it would be like removing images from the browser core just because blind people have no need for them.
If the site needs Turing complete code, run it server side.
Under your proposal, how would a collaborative whiteboard work? Would users have to reload the page in order to see others' changes, and then click-click-click, reloading the whole thing every time as a submission to a server-side image map, in order to add lines to the whiteboard? Or ought the whiteboard to be released as a native application? That would exclude users of OS X, GNU/Linux, Android, iOS, Windows Phone, because these systems can't run a Windows .exe.
Developers aren't marked from birth. The WWW took off because non-developers copied the html of various pages and made their own pages. Eventually some of them became developers. It's important to maintain at least some of these on-ramps.
I'm no web dev but I often view the page source (e.g. so I can download a video instead of viewing it in my browser) or use "inspect element" (e.g. to get rid of some bar at the top or bottom taking up too much screen or being too distracting).
Help build the anti-software-patent wiki
Will this help me write an application in C++? No? Then don't call it a tool for developers. We're not all web monkeys.
I'm most interested to see if this means the release will be without a number of firefox's more annoying features, for example will I be free to disable warnings about third party extentions, and turn off the annoying messages about apps going fullscreen? Those alone would make me consider using it full time.
I get the impression that much of this was integrated into the browser because half the criticisms of Firefox came from people who had tools like Firebug installed - itself infamous for bloating the footprint of any browser it was running in.
I seriously doubt any of the dev tools that come built-in to Firefox, Chrome, or IE are doing much if anything to bloat them. What I suspect is happening is that webdevs themselves are making use of features en-mass that are turning out to have some disastrous memory side effects - unconstrained closures due to widespead jQuery use would be a good example.
You are not alone. This is not normal. None of this is normal.
We still use a Firefox 24 install for debugging GWT.
http://www.gwtproject.org/miss...
What they have "released" is just the Aurora channel with the Dev Tools theme covering all the browser.
Everything else seems to be just the same that it used to be, the only improvement is the ability to run it side by side with another Firefox profile but if you used work with Aurora like I did, all this means that you must go back to the beta channel to keep an usable Firefox with a normal UI (after applying the Classic Theme Restorer)
Their "mobile emulator" is quite simple, I don't understand why anyone would like to use it to debug Chrome on Android instead of using Chrome on their computer as it has better tools and surely it will always be integrated better.
And for CSS tweaking I prefer to use Firebug or even the IE11 dev. tools thanks to its great CSS Changes pane.
Native applications of course.
A halfway decent programmer would make your "whiteboard" cross platform.
Use of native applications leads to three roadblocks, and I'd be interested in how you would recommend to solve each:
Or if you're a really shitty programmer, you use a virtual machine language like java.
Is there a way to get an application onto Xbox 360's Xbox Live Indie Games or Windows Phone 7 at all without using a virtual machine language?
It's imperative that when I develop, that I'm developing and testing using the same browser an end user will have. Introducing differences where you have a developer and a non-developer browser is a bad idea.
BeauHD. Worst editor since kdawson.
I use the "Inspect Element" at retailmenot to get the actual voucher code directly without letting the site track me with cookies or inform dominos where I got them from.
Just where did Mozilla break CA law? Mozilla wanted him as CEO. They made him CEO. Some mental midgets went on a crusade against him. He stepped down. Is it illegal to just let him walk away because he doesn't want to drag Mozilla down with him? Or are you really so mental that you honestly think he was "fired" by Mozilla? He's still contributing to Mozilla, just look at their bugtrackers and such. He even rejected taking back his old job. The real people to be upset about are the shameless opportunists that can't understand that destroying one man won't help their cause, it will just destroy one man. And your need to vilify Mozilla is hardly better. If you're this concerned about privacy you should have starting barking at them when Google became their primary source of income, not just when Eich stepped down. You clearly don't care about Eich or Mozilla, just getting up on your own irrational soapbox.
Actually, they hid Aurora and went back to one of the older square layouts!
I had to use Classic Theme Restorer to add back a couple of minor buttons and colors though.
My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers. Developers.
Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition.
Escher was the first MC and Giger invented the HR department.
The GUI is very bad. Black on black, nearly no contrast... I'm back to Pale Moon.
Oh, and why is there no migration path between old sync and new sync? It's just a new authentication, everything under the hood is the same. If i run Pale Moon (old sync) and Firefox (new sync) i cannot have both of them, i'm forced to choose.