Firefox 27 Released
mozilla.org
mozilla.org
Anyone interested should learn what continuations are (in Scheme).
[0] http://cs.brown.edu/courses/cs173/2012/book/Control_Operatio...
I always thought generators were merely a way of making convoluted iterators, but when I realized that you can put your application logic inside a generator, in my head, it immediately turned it into a "how did I ever code without this before" kind of feature.
I just hope other browsers (especially IE) follow suit in implementing this feature
We don't use JSC here, so I couldn't make a good case for extending the work to cover Safari as well. Anyone wanting to help implement them in JSC has two good blueprints to work from.
I reached out to the IE team back when Andy was still early in the implementation and let them know what we were doing and what the release timeframe was in the hopes that it would help prioritize generators on their side, but I have yet to hear a peep about IE support.
Maybe all we need are some benchmarks? :)
edit: typo
It's also quite fun that you can embed a simple prolog in languages with generators fairly easily too: http://yieldprolog.sourceforge.net/
Does this mean that we can use Task.js in ordinary web pages now?
I've decided to change it again, so I'm going to give Firefox a try during this month. For now, it looks really nice, performance seems to be quite good and the feeling of getting at least a small part of my digital life away from Google feels nice as well.
Tomorrow I'll be trying out the Firefox' developer tools.
I'd be really happy if Firefox convinced me to stay, as I really love what Mozilla is doing for the web community.
I think this dumbing-down approach Google is doing with all their apps and websites will only alienate more and more professionals out of using their platform.
I've tried to report this but you guys don't have proper bug tracker only form in the about menu.
As far as browsing habits go, I do usually have quite a few tabs open (currently I've got 38, though they're not all loaded; I don't think I often go much over this often). None are pinned. Video is disabled, and I've got no flash or plugins.
I've got three extensions (noscript, https-everywhere, duckduckgo plus). I tend to run with scripts disabled and this helps a lot with memory pressure. Sometimes I make the mistake of thinking I need to enable javascript for something (hi Google), and that's usually when memory usage skyrockets and the thing dumps core :-) But eventually it'll happen even if I don't allow any scripts.
You can ping me directly on irc, too. My handle is a literal new line character (which _is_ a valid nick), and I'd be happy to help you get the bug filed if you run into any issues. Once you have a bugzilla account, you'll see it's generally pretty easy to submit bugs and provide feedback in channels that allow us to more easily find and work on issues. We're happy to help, too!
I'd file the issue myself, but I'd prefer to enable you to see how easy it is, and for you to provide the stack trace. Even providing steps to reproduce issues makes you a part of our Mozilla community. Welcome!
[0] https://bugzilla.mozilla.org/ [1] https://wiki.mozilla.org/Performance/MemShrink
I feel like Chrome is better when rendering stuff - like we've got this plotted graph in our app's admin, rendered with Javascript and I believe HTML5 Canvas or something, with too many points on it and Firefox can't handle the rendering, it chokes, whereas Chrome can do it. On the other hand, I feel like Firefox is snappier in general.
Process per tab is _almost_ ready: http://billmccloskey.wordpress.com/2013/12/05/multiprocess-f...
You can play with it by setting `browser.tabs.remote` to true in about:config.
Mozilla guys, you really want to annoy your users again? Why?
If you love what they are doing then I urge you to stick with Firefox in the future. Firefox is the only major browser that is free software. Chrome is proprietary and sends a lot of your data to Google. Google entices a lot of programmers with their developer tools, but it's not worth trading freedom for.
Besides, if you would like take a tiny amount of market share from Google (thereby weakening their ability to set standards such as the W3C's "EME" DRM, which they support), you know that using Firefox is the right thing to do.
It also shows Google that you're not buying into their free/nonfree paradigm that discourages developers from making apps/extensions not approved by Google's stores.
Also, Chromium OS, as distributed by Google, is not free of surveillance mechanisms such as the omnibar. You'd first have to audit, hunt and remove these features, or trust a third party to do this job for you.
Besides, in my experience, there are fewer good FOSS extensions in Chromium, in particular anti-surveillance ones, but that depends on what extensions you want.
For you Windows server operators out there, I suggest IISCrypto to order your cipher selection (this works on desktop versions of Windows too).
I don't think I would trust their judgement about how my SSL is doing.
I am happy about this Firefox release; it is not just that you had to be an advanced user to get TLS 1.2 previously but that doing so would break over half the web. Now it is possible to use TLS 1.2 where available and not use it when not available.
security.tls.version.max = 3
security.tls.version.min = 1
security.ssl3.rsa_fips_des_ede3_sha = false
And it already happened few times (ex. http://en.wikipedia.org/wiki/DigiNotar#Issuance_of_fraudulen...).
Imagine what US government agency can do.
I can recommended it.
In Forefox's case, the frequent releases more have to do with rapid improvement and iteration than anything. Read the changelog and notice how it was largely a bunch of mid-moderate improvements. Some CSS goodies, some JS goodies, some security goodies.
(1) security vulnerability,
(2) performance regression
(3) new features
For a software widely used like FF, it is important that they keep the software up-to-date, make the software as slim as possible, and make the software easy to use. If you want to do some "AB" testing, frequent testing is necessary.
When was the last time you boot up Ubuntu LTS and think "oh I need to update?"
Browser tends to move fast and break fast because browser is a complex software and because the tool people use to make web application are so flexible there are so many corner cases (which can be abused to use to make things work) it is hard to have a dead version.
I look at the CentOS machine yesterday and I thought "god, where is the shiny webconsole that FF comes with?" CentOS apparently comes with old FF and I had to force to upgrade to 26.
This was not my claim. When there are security vulnerabilities I'm happy for the updates to be as quick as possible and as frequent as necessary. The problem is:
> (3) new features
Adding new features has a high chance of new security flaws, when you're operating at the speed of firefox on such an error-prone technology stack.
Different users want to meet this trade-off differently. I want fewer features, in fact I'm ok not to be bleeding-edge compatible with the latest poorly-designed HTML draft spec if it means a more secure browser. It's a question of how and where Mozilla (or other browser teams) organize their effort.
1. FF is a product, meaning if Chrome or Opera or Safari have some shiny features that a lot of developers enjoy to have, FF will very likely implement that feature.
2. Some new features are to replace the old one. For example, the original Firefox sync was pain in the ass and so there will be a new thing called Firefox Account. That's a new feature to user but it's easier to use and makes more sense to users.
3. Some new shiny features are there because of requests. People requested them and developers thought they were useful for users to have. That's inevitable. Unlike Windows, unless you cry to TechCrunch, MS won't care about your email because it's one of the 1000000 emails they receive every day.
In reality, software can't stay in the way the old OS works. Granted, we take Android fun as they roll out new features. But we can't upgrade easily because the phone manufacture and/or the service provider does not provide the stock upgrade (at least this is how my shitty phone works).
I know there are compatibility breakage and some UI decisions are really really bad. For instance, the latest nightly rolls out a different color scheme for web console which I find a huge problem for people with poor eye sight (me) or work long hours. The UI is changing to australis soon (maybe 29, maybe 30, don't remember, they haven't have a final decision yet).
It is actually quite frustrating to work in the browser side. A line of change can impact millions of websites. Often time you have to make a complex patch to make simple adjustment.
Regarding security vulnerability, I personally think they are minor compare to other more common, cheap threats. They are exploitable (and yes some are critical and severe) but when was the last time you find yourself exploited because of browser? It was probably you downloading an infected file. I know this is kind of unethical to say, but I think it is fair to say browser is quite secure these days and attackers are more likely to do things like clickjacking.
I don't remember if Firefox rolls out update (not upgrade) that includes vulnerability fixes or not. Someone correct me on this.
FWIW, that had also been fixed by the Tor Project and a newer version of TBB was available. The users who had upgraded were not vulnerable.
On Windows? Good luck with that!
You made my day right now.
Or are there still some badly behaving update apps out there?
Google's stated reason for developing Chrome was to push web browsers forward as a platform. Whatever you think of Chrome now, I think in that objective they succeeded admirably.
* Scrollbars have now changed, there are no up and down arrows. This has really confused our elder staff.
* Application shortcuts have started hanging and throwing the "Jim" screen, but the same web pages work fine usually.
* Java is awful to get installed and unfortunately we need that.
These have made me want to try Firefox even more, and seeing Generators has made me switch to the nightly build to see what else is up and coming!
Nice work Mozilla!
Take a look at XULRunner and the Chromium Embedded Framework (CEF).
If you want to see CEF in action, try Brackets:
There are some things I use Chrome for, like its JS profiling tools, but every time it freezes and forces a restart I go back to FF. Been staying with the latter more and more lately.
In contrast, I know several Firefox users who regularly have open several hundred tabs, and one guy who sometimes exceeds a thousand. (Yes, a thousand.)
(And if you're about to respond with "why would anybody need that many tabs?", please don't. It's a tired topic; just accept that there are many different and valid ways to use a web browser, and yours is just one of them.)
https://blog.mozilla.org/community/2014/02/03/firefox-27-new...
Looked up some past numbers:
Firefox 24: 43 new contributors, 32 volunteers
Firefox 25: 51 new contributors, 39 volunteers
Firefox 26: 43 new contributors, 27 volunteers
Firefox 27: 41 new contributors, 35 volunteers
Not sure if it's the addons but I recall having similar issue on a fresh install. If anyone from Mozilla reading this has any pointers, please let me know.
Edit: Also the one other thing that frequently bugs me is FF not honoring the Android intent system. YouTube and Play Store links when opened in FF give me no option of opening them in their respective apps - it goes straight to the URL. I guess I'll file a bug for this issue.
On the worse side, unlike some other browsers Firefox doesn't raise intents for redirected URLs, missing some opportunities to match appropriate apps. I believe the underlying issue is that too many redirect situations are ambiguous (especially if you might not be the default browser). I mostly deal with this with an external wrapper (Browser Auto Selector, Unshorten or the like), but it's still a weakness.
On the other side, the Firefox intnet feature that I love is that when you long-press/right-click/etc on a URL that matches some non-browser apps, you get the option of opening it in those apps (for YouTube, the Play Store, Twitter, etc.). I haven't seen any other browser with that option (though, to be fair, I spend most of my time in Firefox). It would be extra-wonderful if there were a reliable way to hit the YouTube link from an embedded video, but even without that, it's very handy.
Great find, I hadn't noticed that one before! It does make things better.
I can quibble that I wish it were a bit more obvious and that the Android icon appeared before the page started loading (next to the X), but it is still going to make many things more convenient for me.
For page load lag, addons like ABP are often especially bad because they're running the URI of each request against a bunch of regex filters to determine if the load should be allowed to begin.
Re. Play links and such, those have been showing up for me in the context menu (long press) at least with Firefox Beta.
Edit: Looks like it'll release in March: https://developer.mozilla.org/en-US/Firefox/Releases/28
Worth noting for designers since it'll implement background-blend-mode too: https://medium.com/web-design-technique/6b51bf53743a
https://hacks.mozilla.org/2013/11/live-editing-webgl-shaders...
While I'm whining, is it possible to show the console at the same time as viewing the source for files? The fact that I have to switch between the console and source tabs in FF is pretty much the only reason I use Chrome for debugging.
For the vertical split thing, opening a bug is the easiest way to get the feature in [1].
[1]: https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c... (this is a URL with the right bugzilla component. just log in, fill the blanks and submit)
This split console feature landed in 28 (so it is moving up to Beta now): https://hacks.mozilla.org/2013/12/split-console-pretty-print...
Edit: As Jare mentioned (https://news.ycombinator.com/item?id=7178225), the editor is disabled by default. Check Toolbox options.
Anyways, powerful new tools for developing WebGL.
[0] https://groups.google.com/forum/#!topic/Google-Web-Toolkit/Q...
On the IDE side, IntelliJ 13.0.2 can attach a debugger to Chrome and provide an in-IDE java debugging experience using source maps. Similar work is ongoing from James Nelson for the Eclipse plugin.
Firefox recently added support for column number support in stack traces, so eventually, Java IDE debugging using sourcemaps attached to Firefox JS debugger should be feasible.
In the mean time, GWT developers who use Firefox will need to stick to Firefox ESRs.
TLS on by default and all:unset support seem like kinda big deals to me.
Just in time to use it with nginx 1.5.10 :P
[1]https://www.mozilla.org/security/known-vulnerabilities/firef...
In short, no, they wouldn't.
"Sandboxing" and "process separation" are not magic smoke.
https://www.mozilla.org/security/known-vulnerabilities/firef...
http://googlechromereleases.blogspot.ch/search/label/Stable%...
Are you really asking me this?
Also definitions:
Firefox Critical: Vulnerability can be used to run attacker code and install software, requiring no user interaction beyond normal browsing. High: Vulnerability can be used to gather sensitive data from sites in other windows or inject data or code into those sites, requiring no more than normal browsing actions
Chrome Critical:Allows an attacker run arbitrary code with the user's privileges in the normal course of browsing. High: Allows an attacker to read or modify confidential data belonging to other web sites.
(that is taken from a PR5 hospital site, should be pretty indicative of the general market.)
http://arstechnica.com/information-technology/2014/02/window...
Well, no. No browser fully supports all HTML5 features. It's all a work in progress.
I guess your app happens to use features present in chrome, but other browsers lead in other areas. Off the top of my head, firefox had webrtc binary datachannels (important for multiplayer games) earlier. And a comment above mentions ES6 generators as well.
Screen sharing via get user media was added in this release Fx27, https://bugzilla.mozilla.org/show_bug.cgi?id=742832
Audio/Video support has been in Firefox since Firefox 3.5 https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Usin...
Tab sharing isn't screen sharing. Chrome lets you share your entire screen, not just a tab.
As I said in my original comment it is getUserMedia audio that is buggy on firefox (it cuts out after 5 seconds), not audio in general. Luckily there is a hack to get it working: https://support.mozilla.org/en-US/questions/984179. Looks like it might be a garbage collection bug - it's not seeing the reference to the input device from the script processor node.
Most users will never get around to finding them and trying them out.
http://mozilla.dorando.at/keyconfig.xpi http://forums.mozillazine.org/viewtopic.php?t=72994
if you get firefox directly from mozilla you'll have mozilla autoupdates.
in general, both are fine..
This link provides some details on how Firefox will deal with bad actors. https://developer.mozilla.org/en-US/docs/Social_API/Criteria
You may need to get your perception of time checked. ;)