A Cheat Sheet To All the Browser Betas
Harry writes "I can't remember another time when there were so many Web browsers in prerelease form — 2009 should be a really, really good year for final browser versions. I have posted a quick recap of the state of the upcoming versions of Chrome, Firefox, Internet Explorer, and Safari." It is nice to see a healthy market of competition driving innovation in a market that has been largely stagnant in recent history. What do other folks see on the scorecard?
I did not read TFA entirely, but which browser is the better browser?
Beer is proof that God loves us and wants us to be happy.
http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9122719&intsrc=news_ts_head
Opera 10 alpha aces Acid3 browser test
Newest preview boosts browsing performance by 30%, claims Norwegian company
[Fuck Beta]
o0t!
Yet still galeon is my favorite browser. I have like 200 tabs in it, while in opera I have just about 30 tabs and in firefox just one window with 8 tabs...
#
#\ @ ? Colonize Mars
#
I judge all my browsers on Acid; my scorecard is a a blur of dinosaurs dancing, blue e's laughing, and JZW laughing at me. And I'm eating a lot of delicious delicacies.
Reasons not to download it: ...you can't get the Google Toolbar for it.
Surely this should have been in the "Reasons to download it" it section!
I only look human.
My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
what about linux? We need pr0n too.
Firefox: The only real browser right now. Supports a bunch of anti-crapware plugins (like adblock plus, which gets rid of /. ads) and general power-user scripts for those who want them. Aside from that, its everywhere on every platform that supports any form of graphical manager.
IE: MS has had to work because they prior have sucked and dragged down most every website that does "IE only" websites. It's a good thing that Firefox and standards are taking a front seat.
Opera: They're still around on X86 platforms? I thought they died out and only did DS and Wii browsers and diddled with X86 adware. Havent looked at them since their software didnt fit on a floppy.
Chrome: eh? Its alpha buggyware with none of the plugins we're used to. Im not going to even look at it until it has more what I would consider basic features.
Safari: I dont own a mac. I dont care to own a mac. And I dont even want to pirate OSX for my very compatible Thinkpad-T61 to run it. And pretty much every software ported from OSX to Windows is bad, and I mean BAD.
Konqueror: Too bad I mainly run Gnome and dont usually run KDE, but where's this browser? It traditionally has ran rather well for me, but Im not sure of the recent features.
As I mentioned in another posting regarding Opera 10 alpha:
No border-radius? *sniff*
Is it specified in some stupid way like Mozilla & Webkit do it?
Still no replies, so I dunno...that's not promising. I wants me some border-radius, multiple background image, and border image support! (among other things) A small subset of the major CSS3 features would go a LONG way.
I've been using Lynx on my 19.2kbps modem ever since the Intarweb revolution kicked me off AOL.
Why haven't they mentioned the new kick-ass beta of Lynx? I hear it supports Unicode text!
Runs great on DOS 6.22
Arachne is another great DOS web browser...
I like Chrome for one primary reason and that is I'm looking at a web page within seconds of opening the browser. Both Firefox and IE take anywhere between 20-30 seconds on my computer to load first time out. That means the later two browsers either stay open my entire session just so I can switch to them when needed and I have to put up with the clutter they add to my desktop/task bar or I put up with a sluggish environment.
Chrome doesn't make me make that choice. Since I'm not a big fan of add-ons, I don't miss them.
With my crystal ball... I see... more CSS headaches.
I disagree with the summary. These days, having a ton of browsers in beta/prerelease probably means they're all buggy, but they'll be released as betas anyway, and if you'll pardon the pun, we may never see polish on the Chrome! But, perhaps I'm being overly pessimistic - we may not have to suffer through the betas if the rolling blackouts take down our computers.
Be careful of your thoughts; they could become words at any minute...
I can't remember another time when there were so many Web browsers in prerelease form â" 2009 should be a really, really good year for final browser versions.
There are no final version any more. There is only beta. The software lifecycle ends with beta!
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
I remember back in 2002 when I bought the Linux version of Opera 5 because at the time Mozilla was a bloated resource whore and I needed a fast graphical web browser on a poor old 233MHz Pentium 2 box. I'm not exactly sure how much I paid for it, some where around $20 bucks I believe. I think still got the email receipt when I purchased it in one of my ancient email archives. I'll have to find it and post it sometime.
This space is not for rent.
Overall, how promising is it? Iâ(TM)d never argue that improving support for Web standards or souping up performance is insignificant, but overall, it looks like this is Opera 10.0 not because itâ(TM)s a huge deal but because the last version was 9.6. In other words, itâ(TM)s only .4 of a great big upgrade. If that.
What the hell is "it's only .4 of a great big upgrade" supposed to mean?
What about Opera 10 using a totally different engine? And since when are we back on measuring software by its version number?
The rest of the article is just as pitiful, if not entirely wrong.
Opera's mail client could always delete old mail, the new thing here is that it can automatically delete after n days.
These article always seem to miss OWB for AmigaOS 4.1.
:-)
http://strohmayer.org/owb/
It gets 100/100 on ACID3, check the screen shots on the site.
Geez!!
This may be off-topic; if so....sorry.
I've liked Opera each time I tried it although the interface is different it's a damn good browser. The reason it never grabbed me was the lack of any useful (Chuck Norris trivia anyone???....I'm serious, they have one so I guess at least one person on the planet has a use for it) plugins, specially for blocking adverts. In the settings you can disable JavaScript etc but there's no way to block adverts. Well I found one....and it works.
http://my.opera.com/Tamil/blog/index.dml/tag/urlfilter.ini
The above link explains how to create a blank urlfilter.ini file in your Opera profile directory, copy and paste some urls to filter out and restart Opera. Every site I tried before and after, it was like surfing in Firefox with AdBlock.....bliss. I don't think it's perfect, it depends on the site and the type of advert but it's a damn good start. It's also easy to add a new line to the text file if you come across an adserver not on the list.
Having said all that, I'm still blown away by how fast Opera is, even WITH adverts. Being able to block them helps speed that up further. I've been a Firefox user for so long that I don't think I could switch but Opera is a damn good second browser for site testing.
I recently tried Epiphany with Webkit, it may be one to watch for the future but it's a bit early yet.
Yeah, lots and lots of versions as they fix lots and lots of bugs due to everyone trying to beat everyone else to market.
"It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
Bit's of my brain as I try to deal with cross browser Javascript incompatibilities. I think it will go something like this...
aaaaaaaaaaaaaahhhhhhhhhhhhhhhhhhh - BOOOOM
My ism, it's full of beliefs.
comprehensive may do, may( not over to y3t another OpenBSD, as the
...by removing all the crap from web pages.
All that flash+advertising isn't free to download.
No sig today...
onhashchange
http://www.pathf.com/blogs/2008/03/ie8-html5-and-a/
msie8 is the first to implement this event. don't know what that is? ajax is the most important technological development in browsers in recent history (invented with microsoft's xmlhttprequest object, btw). however, ajax breaks history and bookmarking (can't go forward/ back, can't bookmark deep into an ajax session)
a way around this has been to hijack the hash part of anchor links, since they stay on the same page, but create a history. initially, this hack didn't work for msie, because msie didn't consider hash changes to be part of the browser's history, invoking valid msie hatred (msie7 fixed that oversight). but now, from the back of the class, msie jumps to the front of the class with onhashchange, becoming the programmer's best friend
currently, there is no way to tell when a browser's anchor hash link changes other than with extremly ugly, resource wasting kludges like putting a "heartbeat" on the web page (every 200 milliseconds, see if the url's hash link has changed... vomit). however, here's a recent history emulator without the odious heartbeat kludge (but no bookmarking functionality):
http://www.zachleat.com/web/2008/08/21/onhashchange-without-setinterval/
but now, msie, with onhashchange, makes ajax programming for history/ bookmarking elegant... for the very first time. there's plenty of reasons to hate microsoft folks, but hate them for actual real technical reasons
want one? ok: there's msie8's bullshit compatibility button. since msie8 tries so hard to be compliant for once, it is faced with backwards compatibility issues for rendering sites that only really work on msie now
http://blogs.msdn.com/ie/archive/2008/08/27/introducing-compatibility-view.aspx
ugggh
so the lesson is: by all means, hate microsoft and msie. but make sure your hate is grounded in reality, not ignorant bias which i see in a lot of comments here
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
If you never use Flash (Youtube/most videos), use Chrome. For whatever reason, Flash sucks in Chrome. Hard. Chrome is super fast, though, and is not a memory pig.
If you want the ability to customize website behaviour, use Firefox. Someone, somewhere has created a Greasemonkey script or an extension to create the behaviour you want.
If you want sane defaults and the stuff Firefox will have in two years, choose Opera. It's fast, and it has stuff you have to jump through hoops to get in Firefox. Don't believe me? Tell me when Mozilla offers this:
http://www.opera.com/link/
Firefox will offer this, just in two years. Trust me, it's how it has gone down in the past.
If you're on Windows, you've got IE by default. I would never recommend using it unless you have to. It's a virus vector like no other, it's a bloated pig, and the only upside is the tight integration with the OS. If you aren't programming, it's really not worth looking at.
PS: If you are at all worried about viruses, there is one solution that will keep you free of viruses while you browse.
Grab Virtualbox and a Linux ISO. Both Puppy linux and DSL are good options. Boot a virtual machine off the ISO, and surf inside the virtual machine. There you go: no viruses, ever while you surf. The nice thing about Virtualbox is that you can suspend the virtual machine, so you don't have to wait for it to reboot.
My 2 cents.
Slade
It's still an alpha. Personally, I think there would be border-radius support, but who knows.
Quick way to get 30% Funny 70% Troll: defend Opera browser on
fucking support disable-output-escaping already
https://bugzilla.mozilla.org/show_bug.cgi?id=98168
your reason for not supporting it is arrogance:
https://developer.mozilla.org/en/XSL_Transformations_in_Mozilla_FAQ_(external)
really? a desperately needed piece of functionality is bad xml?
you had pretty much the same holier-than-thou attitude behind your resistance to supporting innerHTML, and you reversed yourself, for good reason: its what programmers need and want. programmers are your friends. keep us as your friends
we shouldn't have to spend time coding special scenarios to support your browser, for the most stubborn and shortsighted of reasons
leave that kind of hatred for msie, ok? thanks
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
Really. Have they even managed Acid Test 2 yet?
DMCA, Hollings, Palladium. What might have sounded like paranoia is now common sense.
And just read the artcile, which is OK, and certainly better than most of the user-submitted comments with their own insightful (ahem) judgements.
Ah yes, I know this is /. and no I'm not new here...
Mind you, nothing in the article that most people here will not already know... /end grumpy rant
. . .if the story was actually about what I read it as the first time:
.DROP!
A Cheat Sheet To All the Browser BEATS
You know you're all a bunch of fly-skimmers. Admit it!
Mmmm. .
If the article is to mention reasons in favor and against using each given browser, it should also review fringe browsers. Midori (an XFCE browser) is in beta stage and if you're going to compare Safari and Chrome (both webkit browsers), Midori ought to be thrown into the equation.
It would also be neat to compare extensions wealth (especially its relevance to the latest versions), seeing as top available extensions are almost as relevant as the browser itself.
Isn't CSS 3 not officially out yet? I think that's why mozilla and webkit have weird ways to do it.
Isn't CSS 3 not officially out yet? I think that's why mozilla and webkit have weird ways to do it.
I believe border-radius has been in the CSS3 spec since the working draft from 2002. Should be time to standardize on 'border-radius' instead of 'moz-border-radius' or at least alias it to -moz-border-radius or something. As it is, one has to use -moz-border-radius and repeat with -webkit-border-radius to get it working in both, plus they each do individual corner specifications differently. Very irritating, but not as irritating as browsers that don't support the functionality at all.
http://i86.photobucket.com/albums/k93/chrishorgen/Funnay/facepalm.jpg
For most of human history, all browsers were in prerelease. Until 1995, only a few weren't in prerelease, like www and w3.
In fact, almost all browsers are still in prerelease. As they always are, except momentarily when they are released.
And this isn't just pedantry. All these browsers have the low quality that prerelease versions of software used to have before browsers were released, in the mid 1990s. They've lowered the quality of released software of all types down to what rarely would have been released.
--
make install -not war
"...largely stagnant in recent history."
Whereinthefuck have you been for the last five years?
Sig this!
I know you're trolling, but: http://www.ieaddons.com/. (Mostly crap, but then, so is https://addons.mozilla.org/.)
Even better: http://www.bhelpuri.net/Trixie/. Trixie enables user scripts (ala Greasemonkey) in IE.
SIERRA TANGO FOXTROT UNIFORM
Firefox has stealther, but its an add-on and so obvious that you've installed it to look at porn. (Obviously you could always set and reset privacy settings everytime, but that could be a pain)
But Chrome has a stealth feature built in, so you're not a fiend just for having it. Although you're still a fiend. But a fiend with some shame at least!
You can download Webkit nightlies for Mac OS X and Windows here, and you do not have to be a developer to do so. They will come with the latest version availiable of the Safari shell, which is right now 3.2.1.
Thank you.
....after all, what would we do without the original and best unasked-for app?
I predict a massive speedup in javascript execution in most camps... except for the Microsoft camp. I also predict that the browsers will be more streamline than ever... except for IE.
No ascii art.
so i write a comment board. someone wants to put < > & " ' < > & " ' in their comments. rather than just disable-output-escaping, now i have to (new XMLSerializer()).serializeToString the content, and then tediously work through all of the markup, then turn it back into a node tree
in javascript. or on the server. everytime i want to display the fucking content. special, for firefox. not opera, not safari, not chrome, not msie. those browsers have seen the light, why haven't you?
but noooo.. every time i want to use disable-output-escaping, i'm just a bad programmer, right?
fucking bullshit you arrogant fuck: IT IS THE MAJORITY OF CASES where it is perfectly necessary and important and appropriate to use disable-output-escaping. remember innerHTML? every time you use that, you're just a hack, right?
because assholes like you lack the imagination to consider real world programming tasks, outside of your holier-than-thou ivory tower mental straightjacket of how the world should behave, rather than how it actually DOES behave. there is the universe of programming tasks before you as determined by your stunted ability to understand reality, then there is the actual and real universe of programming tasks real programmers face. ever hear of RSS? jesus christ you arrogant fuck
but don't mind me, i'm obviously just some sort of low level hack. the need for diable-output-escaping is purely imaginary if you are good programmer. right?
fucking ignorant, arrogant ivory tower prick
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
"M$" is making IE8 standards-compatible by default, and it's telling web site operators (especially high-volume ones) to add a tag to make the browser drop down to "compatibility mode" or "quirks mode" that allow the site to be viewed
It's funny how no other browsers need this tag and how much work this simple tag requires. I'm afraid the simple tag did not work. Most of these so called "optimized" sites already use browser identification and should have already implemented M$'s quirk tag in their IE8 specific code.
Who the hell gave you an "informative" modpoint for spouting the M$ party line like that? Two minutes of thought with the most rudimentary of knowledge proves your explanation implausible.
DMCA, Hollings, Palladium. What might have sounded like paranoia is now common sense.
for not understanding that messiness is an aspect of dealing with real life constraints, not simply bad code
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
what's wrong with client side transformations?
except for firefox, that is
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
when i request a web page, what i get is serialized content. firefox is processing that stream into a nodetree. nothing you can possibly say gets around the obvious fact that processing serialized content into a nodetree is not only a normal part of a browser's functions, it is THE function of a browser
and now you are telling me that a browser can't do this essential function under some sort of mitigating circumstance?
sorry, i'm not sold. it's like you are telling me you can program a stoplight to play chess, but you can't make it glow red
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
for values of "small minority" that are actually the "large majority"
d-o-e is the STATUS QUO
(smacks forehead)
you know, we could be having the exact same conversation right now about innerHTML
can you describe to me why firefox caved on innerHTML?
if you can articulte that reason, then you've just articulated the SAME EXACT FUCKING REASON firefox should cave on d-o-e
or not
and i will continue to hate firefox every time i have to browser sniff (as ugly as that is) and write extra javascript to serialize the content, and replace(/</gi,"").replace(/"/gi,"\"").replace(/'/gi,"\'").replace(/&/gi,"&"), and turn back into a nodetree
what was that you were saying about significantly slowing down the process by inserting extra steps?
seriously, do you know what people do with fucking browsers? what kind of content is transferred? opera, msie, safari, chrome... they all seem to know. ITS NOT THE VIRTUOUS MODEL YOU BELIEVE IT TO BE. you really want to stick with this ivory tower approach about how people should process content rather than how they actually HAVE to?
you really can't imagine that the majority of content that has to pass through xslt processing has escaped content? that really is an alien concept to you?
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
1. escaped content is rare
2. client side xslt support is marginal
1. ask anyone who has dabbled in xslt in the browser, and they find out very quickly that firefox's pledge to not support d-o-e is an instant stumbling block, because your essential error is not seeing that serving and transforming escaped content is regular and usual, not weird and strange. and then you find out firefox's reason for not supporting d-o-e is willfull, and you get very angry at firefox, because firefox doesn't understand what programmers want and need, and where the future is
the idea is to keep firefox on top of all other browsers, and the choice made on d-o-e puts firefox at the back of the pack on a crucial function. your point about an extra processing step costing time is 100% true, but it is not the esoteric odd support that you suppose it is. making people using xslt in the browser without any need for d-o-e grind more cycles is PREFERABLE, because their use cases are the MINORITY of use cases. right now you are actually penalizing the MAJORITY of xslt implementers because the need for d-o-e represents the MAJORITY of use cases. this is your essential misjudgment, that not supporting d-o-e speeds up browsing for the majority of users. no, it slows it down
2. "We could remove our XSLT support tomorrow, and fewer pages would break than broke when we stopped allowing them to read the full filepath from a file input...."
absolutely true. except, ironically, for exactly the same high minded appeal to elegant concise code that moves firefox to not support d-o-e, xslt client side support is the future
there once was a time when i could have said "We could remove our CSS support tomorrow, and fewer pages would break than broke when we stopped allowing them to read the full filepath from a file input...."
not true anymore, for all of the obvious observations about style and content you already understand, obvious observations that also apply 100% to XSLT support on the client, in some better future we are inexorably moving towards
so why does firefox support XSLT at all? because firefox wants to remain relevant and on top of the marketplace. someday, someone is going to support XSLT 2.0 in the browser too, and, just as you note "We could remove our XSLT 2.0 support tomorrow, and fewer pages would break than broke when we stopped allowing them to read the full filepath from a file input...."
but again, that's not the point, because the point is where are browsers going in terms of the next intelligent step in the browser model?
now make believe it is 1998
"what is this css thing i keep hearing about?"
{enter search term "CSS" in altavista, read a geocities page on the topic...}
"oh! i get it! let me try... hmmm, netscape supports this css whizzbang gadget just fine. but fucking msie 4.0... hmmm... it says here that msie is refusing to support :hover and other pseudoclasses because they say this adds an extra processing step in their css processing model, and very few people support css, and very few people need pseudoclasses, because if you write 'good' code you handle dynamic page tweaks with javascript, that's what javascript is for, and so you don't need css pseudoclasses (sniff, sniff... looks down nose)"
{face turns purple with rage}
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
its like shortly before wed 2.0, and you're saying xmlhttprequest doesn't need to support both get and post
show some imagination of where the future is going
a further abstraction, like css represented
thats xslt in the browser
mark my words here, you'll see ;-)
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it