Having the close button on the tab is easier for new users. Having it where it was is easier for experienced users. A decision had to be made one way or the other, and it was made to favor new users, who probably wouldn't be able to find how to change it (or even know to change it), instead of the experienced users who will know how to change it.
FWIW, I hate it, too. But the reasoning behind it is solid, so I understand I'll just have to deal until someone makes an extension.
That would be the case... if Firefox extensions needed to be compiled. Which they don't.
Extensions are programmed in Javascript and XUL, and for some advanced ones, XBL. They don't need to be recompiled, because they don't need to be compiled in the first place. The fraction of a percent that have more demanding interaction with the host system don't even necessarily need to be recompiled, depending on how they hook in to the mozilla code.
You'd be right for other programs, but that's not how Mozilla works.
Obviously you didn't actually try it. The entire bookmarks and history systems have been rewritten, backend and frontend. Tabs have changed slightly to improve UE for new users. Plenty of other things have changed as well. That's not "no significant changes".
In other, shorter, words: Judge art solely on its artistic merits, pay for art based on a whole view of what your money gets you and what will be done with it by the person you give it to.
And that, kids, is why when you're writing a shopping list, you don't break out GCC, #include <stdio.h>, print each line out, and then make &&./shoppinglist > shoppinglist.txt.
Instead, you write the shopping list into a file in the first place.
Actually, according to someone I'm talking to at the moment, this has been known for a long time and Yahoo is dumb for reporting it as "news". That, and 1/2 of humans is a very conservative estimate.
So it's more than likely you have already welcomed our parasitic overlords.
According to a recent Zogby poll, 52% of Americans approve of impeaching Bush if he wiretapped an American citizen without a judges approval.
From this [rasmussenreports.com] poll you see a very different result - 64% of Americans thinks it's Ok to tap communications between U.S. Citizens and known terrorists.
Hahahahaha...... wow you're stupid. Does it not occur to you that if someone is a known terrorist, you can get a judge's approval to wiretap them?? In fact, I suspect something's wrong with that poll's methodolgy, since the number should be higher than 64%.
Everyone supports spying on terrorists. But almost no one supports spying on innocent citizens, and 52% of people think spying on innocent citizens is bad enough to kick the president out of office.
Okay. I'm perfectly fine with that attitude. Of course, if it's a company site then your boss probably isn't...
Different situations call for different things. Personally most of my site is served with an XHTML mime type, because I like it that way. In any business situation, that would be slaughter (as IE's feeble mind can't handle it).
Of course, unlike using application/xhtml+xml, resolution dependency generally points to bad web design...
I disagree. When I was at MOP (Mathematical Olympiad Program, AKA Mathcamp, where the US participants in the IMO are chosen/trained) many of the teachers used exactly that method. Po-Shen I remember was the worst/best. We all got used to seeing him start to write out a formula, pause in the middle, scribble a few things off on the side, and then finish--numerous times per class.
Probably it works well for some people and not so well for others.
Holy cow I don't even know where to begin with this... Sentence by sentence it is, then.
Good news, friend. XHTML, CSS, and PHP are the three major languages of the web today, and you already know one.
No, HTML and CSS are the major languages of the web. Unless it's sent with an XML mime type, all browsers treat XHTML as HTML--and that's the case for over 99% of XHTML pages on the web.
XHTML is very, very similar to HTML.
Except in a few very important ways, which will make your pages die a horrible death if you don't do it correctly.
Lots of other stuff is mostly the same.
How very, very true. Unfortunately, "lots of stuff" being "mostly the same" leaves you wide open to hit all the stuff that's changed.
The one big change you'll need to make is that all style tags have been dropped from XHTML. No more <b>!
a) This applies equally to HTML and XHTML, i.e., only with the Strict doctypes. b) <b> and <i> still exist even in (X)HTML 1.0 Strict. (IMO they shouldn't, but that's another story...)
You use CSS now.
Aaah, finally a correct statement.
Grab a book on moving from HTML to XHTML. There are lots out there!
Better, grab a book on how to write good, clean, semantic HTML, and another on how to use CSS well. These will improve your knowledge and understanding of the languages much more, and be a much better help.
As for programming languages, you'll probably be more comfortable with PHP than Perl. Again, I'd grab a getting started with PHP book and work your way in.
This depends entirely on current skillset and languages already known. Frankly, though, I'd suggest building all your pages statically until you have a good grasp on the HTML parts, and once you're comfortable with HTML and understand it well, then think about what gets on your nerves as being tedious and repetitious, and learn how to automate that with the programming language of your choice. The obvious exception is if you're doing something that requires interaction with the server, in which case I'd still suggest keeping them as separate as possible. It's like every other discipline--don't attempt advanced stuff until you have a good grasp on the basics.
As for programs...I do everything by hand in Notepad. It makes for very sleek webpages, and there's no other way to get full control over your page's code.
This is good. A plain text editor is the only way to really understand what you're actually doing with your web pages. There are better ones out there, though, with such things like syntax highlighting.
--
This post was not previewed, because I'm rushing to dinner.
Slashdot Mirror
Having the close button on the tab is easier for new users. Having it where it was is easier for experienced users. A decision had to be made one way or the other, and it was made to favor new users, who probably wouldn't be able to find how to change it (or even know to change it), instead of the experienced users who will know how to change it.
FWIW, I hate it, too. But the reasoning behind it is solid, so I understand I'll just have to deal until someone makes an extension.
Some of your extensions will continue to work properly in new versions. Others will not. That gives you a choice:
Which do you choose?
That would be the case... if Firefox extensions needed to be compiled. Which they don't.
Extensions are programmed in Javascript and XUL, and for some advanced ones, XBL. They don't need to be recompiled, because they don't need to be compiled in the first place. The fraction of a percent that have more demanding interaction with the host system don't even necessarily need to be recompiled, depending on how they hook in to the mozilla code.
You'd be right for other programs, but that's not how Mozilla works.
The idea of people who actually write markup language specifications and know a heck of a lot more about the internet than you do.
See also A blog post by someone who actually makes browsers and also knows a heck of a lot more about the internet than you do.
Obviously you didn't actually try it. The entire bookmarks and history systems have been rewritten, backend and frontend. Tabs have changed slightly to improve UE for new users. Plenty of other things have changed as well. That's not "no significant changes".
There is no link because, as plenty of people have pointed out, it's NOT released yet.
However, if you do want to develop it, the entire sources (trunk and many branches) are available through CVS, see the DevMo page on the subject.
What's sad is the "article" links to tinderbox builds, not even the official nightly development builds!
People really should not submit articles if they have no clue what they're talking about.
No it is NOT released.
See Asa Dotzler's blog post
And for those who want to learn how to count, please use apt-get install kids_counting_program.
In other, shorter, words: Judge art solely on its artistic merits, pay for art based on a whole view of what your money gets you and what will be done with it by the person you give it to.
Why is the JPL working with solar sails? Aren't they the Jet Propulsion Laboratory? Isn't this a bit out of their department?
And that, kids, is why when you're writing a shopping list, you don't break out GCC, #include <stdio.h>, print each line out, and then make && ./shoppinglist > shoppinglist.txt.
Instead, you write the shopping list into a file in the first place.
Interesting that you should post here with that username, because at least according to a straight dope article, Toxoplasma produces LSD.
Actually, according to someone I'm talking to at the moment, this has been known for a long time and Yahoo is dumb for reporting it as "news". That, and 1/2 of humans is a very conservative estimate.
So it's more than likely you have already welcomed our parasitic overlords.
Hahahahaha...... wow you're stupid. Does it not occur to you that if someone is a known terrorist, you can get a judge's approval to wiretap them ?? In fact, I suspect something's wrong with that poll's methodolgy, since the number should be higher than 64%.
Everyone supports spying on terrorists. But almost no one supports spying on innocent citizens, and 52% of people think spying on innocent citizens is bad enough to kick the president out of office.
Seriously, learn how to read.
Clarifying, that "fifteen years" note is the commit log note for that checkin. It's not a part of the code.
Oh, I just love the fact that they're hotlinking the script of someone else's web server. I just wish so badly it were mine...
They might have my IP, but I have theirs too! MUWAHAHA!!
Server not found
Firefox can't find the server at www.grokster.com.
Looks like they're slashdotted all right... That or my DNS is messed again.
And even better: Buy a card from the Open Graphics Project when it's available (first half of this year, if all goes well).
It's certainly what I'm doing (just sent back an Nvidia 6600 something-or-other I got for ACGPD).
No, we shan't.
XHTML has nothing to do with it (unless you're contrasting it to, say, building the entire website in Flash).
Rest of the post is nice, though.
Okay. I'm perfectly fine with that attitude. Of course, if it's a company site then your boss probably isn't...
Different situations call for different things. Personally most of my site is served with an XHTML mime type, because I like it that way. In any business situation, that would be slaughter (as IE's feeble mind can't handle it).
Of course, unlike using application/xhtml+xml, resolution dependency generally points to bad web design...
I disagree. When I was at MOP (Mathematical Olympiad Program, AKA Mathcamp, where the US participants in the IMO are chosen/trained) many of the teachers used exactly that method. Po-Shen I remember was the worst/best. We all got used to seeing him start to write out a formula, pause in the middle, scribble a few things off on the side, and then finish--numerous times per class.
Probably it works well for some people and not so well for others.
Holy cow I don't even know where to begin with this... Sentence by sentence it is, then.
No, HTML and CSS are the major languages of the web. Unless it's sent with an XML mime type, all browsers treat XHTML as HTML--and that's the case for over 99% of XHTML pages on the web.
Except in a few very important ways, which will make your pages die a horrible death if you don't do it correctly.
How very, very true. Unfortunately, "lots of stuff" being "mostly the same" leaves you wide open to hit all the stuff that's changed.
a) This applies equally to HTML and XHTML, i.e., only with the Strict doctypes. b) <b> and <i> still exist even in (X)HTML 1.0 Strict. (IMO they shouldn't, but that's another story...)
Aaah, finally a correct statement.
Better, grab a book on how to write good, clean, semantic HTML, and another on how to use CSS well. These will improve your knowledge and understanding of the languages much more, and be a much better help.
This depends entirely on current skillset and languages already known. Frankly, though, I'd suggest building all your pages statically until you have a good grasp on the HTML parts, and once you're comfortable with HTML and understand it well, then think about what gets on your nerves as being tedious and repetitious, and learn how to automate that with the programming language of your choice. The obvious exception is if you're doing something that requires interaction with the server, in which case I'd still suggest keeping them as separate as possible. It's like every other discipline--don't attempt advanced stuff until you have a good grasp on the basics.
This is good. A plain text editor is the only way to really understand what you're actually doing with your web pages. There are better ones out there, though, with such things like syntax highlighting.
-- This post was not previewed, because I'm rushing to dinner.