I agree that a zero-tolerance policy could go overboard. But how many non-technically inclined people were really writing the "this is my dog" pages before automated tools came out? HTML 3.2 is still a perfectly valid standard, and how many of those cheesy personal pages are currently written in notepad? Almost none. People use a variety of WYSIWYG editors to make their simple pages.
So isn't having a more powerful, flexible, and modular language like XHTML 1.1 a potential boon for those programs? Besides, I've written pages that conform to that standard by hand. Once I got used to the changes, I realized that it was indeed much easier - a lot more modularity and cleanliness to the code.
Does a silly little one-off page take more code and thought than before? Yes. But is the average person equally as likely to write an XHTML 1.1 page by hand as an HTML 2.0 page? Yes - because both chances are pretty much zero.
There are a lot of crappy pages out there. If a page doesn't make it through the HTML validator why should anyone expect a browser to render it? Are your pages at work valid? What's the point of standards-compliant rendering engines if they all allow exceptions to the standard to be rendered?
That's what makes me so crazy with all of the idiots who claim that browsers should accept fucked up code just like IE. Why???
Do you expect to write a program that won't compile and still have it run correctly? Or at all? If you write a letter in badly broken English, do you expect others to be able to read it and fully comprehend it? Then why in hell do you expect it out of a rendering engine???
All my friends and I wear the boxer-briefs (and that's what the exchange sells). I'm assuming the compression shorts would be similar (haven't worn them), but possibly tighter on the legs and the crotch. That would be bad, because you need *some* air circulation down there. Otherwise, you'll have a killer case of crotch-rot after being in the field.
I think arts is pretty darn good. However, where it falls short is working with thing like flash & certain games. It still has a ways to go.
I think the real major weakness is the diversity of the sound options in linux. Is arts the way to go? gstreamer? If someone would settle on one from on-high (and maybe they already have), I think a lot of our problems would clear up within six months.
That's all well & good. However, my point is that this guy is a fairly minor player in the OSS scene. I'm not bashing his abilities or his contributions. But, I'm also not impressed enough (nor are a lot of/.'ers, judging from the comments) to see the point of this story.
He did some stuff a while back & then dropped out of the scene, such as it is, for a while. Now he has sound problems & bought a Mac instead. Good for him. Why is this newsworthy?
People talk about his obvious skills. He wrote xscreensaver - big deal. It kinda sucks, quite frankly. Don't get me wrong, I could never write a replacement. Of course, I've always been able to get my sound to work properly.;-)
My point is that when ESR said "CUPS sucks," people were (for the most part) interested. It fostered a healthy discussion about where we were in printing & where we wanted to go. Sound is a no-brainer. No one here in their right mind is going to say the current state is fine - we know it's not. So what the point of the story? I'm really trying not to be an asshole, I just can't for the life of me see why this was newsworthy. Thanks.
So he worked on Netscape/Mozilla and then quit right before they started to really innovate again with Firefox because he didn't want the rewrite & bitched about how they weren't innovating.
He also did something with Emacs back in the day & does xscreensaver, which, let's all be honest here - isn't all that fucking spectacular.
So why do we care that he got his ass kicked by ALSA? Seriously, it's a pain in the ass, but "Man baffled by Linux sound; switches to Mac & says it's much easier!" doesn't exactly blow my skirt up as a story.
Well, why can't the stores make money off supporting it?
"We'll include this better browser, as well as Internet Explorer. If you want to learn more about it, you can buy this user guide (which we're reselling from the Mozilla store) or you can pay $25 to come to our open-source class held every other Tuesday night."
Your site falls flat when resized. I would view it like this. My near-sighted grandparents would try to increase the size and end up with this. In an effort to make sure people only view it the way you want it to be viewed, you have kill accessability.
So, are we supposed to have a good academic discussion about where we stand on the issue or are we supposed to flame anyone who is a proponent of Intelligent Design?
Because the summary seems predisposed towards the latter.
[~/bin]$ perl password.pl How many characters? 9 Case sensitive? y Alphanumeric? y Symbols? y Star t with vowel or consonant? y oerugezep [~/bin]$ perl password.pl How many characters? 9 Case sensitive? n Alphanumeric? n Symbols? n Star t with vowel or consonant? n unovoyoqi
Seems to ignore what I'm telling it. Haven't tried to debug yet, but it's probably easily fixed.
Works fairly quickly, but is happier with more than 256MB RAM. Only downside is sound is locked for every session except the first. I can't wait for the sound situation in Linux to get simplified and fixed. *sigh*
Excellent, I understand now. I think my confusion was that I assumed with only one instance of Gecko being loaded into memory, a crash in one would still bring down the others. If that is not the case, then I am all for it. Thanks.
You're forgetting one very important thing. As a matter of fact, everyone who is a big Moz suite fan says the same thing as you, but they forget one of the biggest reasons for FF/TB: seperating the memory of the various suite applications.
Does no one remember that there was (and may still be, I use FF/TB instead of the suite now) a major problem with one part of the suite crashing and taking the rest with it? Many times I was bitten by a buggy Moz Mail plugin crashing and pulling my 10+ tab web session off the cliff with it. I was very happy to hear that they were going to redo the various components as stand-alone apps and then later reintegrate them into a single cohesive suite, but one with more protection between its various pieces.
Now the latter part of the plan seems to have fallen by the wayside and only time will tell if it will eventually happen. I understand and agree that running both FF and TB takes an inordinate amount of resources when compared to the suite, but I'm hesitant to lose that safety separation. I'm hoping that there is a happy medium that can be reached (and please educate me if you know what that would be). But what you suggest sounds to me like an invitation to the disasters of old.
Why are you joining the Marines? If you think you're 'different' and 'very smart', then you're probably going to have a very difficult 4+ years....
Hrm... aside from the fact that he never said that, I consider myself "different" and "very smart." And the Marine Corps made an officer out of me. I've been in over eight years (combining NROTC and active duty) and I'm very happy. In fact, I've thrived and I've seen others like me thrive time and again.
So next time make sure you know what the hell you're talking about before you spout off. Thanks.
Look at the Windows XP Pro EULA (scroll down to Section 12, "DISCLAIMER OF WARRANTIES"):
...Microsoft and its suppliers provide the Product and support services (if any) AS IS AND WITH ALL FAULTS, and hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of reliability or availability, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of negligence...
Slashdot Mirror
I agree that a zero-tolerance policy could go overboard. But how many non-technically inclined people were really writing the "this is my dog" pages before automated tools came out? HTML 3.2 is still a perfectly valid standard, and how many of those cheesy personal pages are currently written in notepad? Almost none. People use a variety of WYSIWYG editors to make their simple pages.
So isn't having a more powerful, flexible, and modular language like XHTML 1.1 a potential boon for those programs? Besides, I've written pages that conform to that standard by hand. Once I got used to the changes, I realized that it was indeed much easier - a lot more modularity and cleanliness to the code.
Does a silly little one-off page take more code and thought than before? Yes. But is the average person equally as likely to write an XHTML 1.1 page by hand as an HTML 2.0 page? Yes - because both chances are pretty much zero.
That's what makes me so crazy with all of the idiots who claim that browsers should accept fucked up code just like IE. Why???
Do you expect to write a program that won't compile and still have it run correctly? Or at all? If you write a letter in badly broken English, do you expect others to be able to read it and fully comprehend it? Then why in hell do you expect it out of a rendering engine???
I know his pain -- I also suffer from this disorder.
(Can't parents just explain it away by saying that Superman is All Kinds of Super?)
"F n o r d
All my friends and I wear the boxer-briefs (and that's what the exchange sells). I'm assuming the compression shorts would be similar (haven't worn them), but possibly tighter on the legs and the crotch. That would be bad, because you need *some* air circulation down there. Otherwise, you'll have a killer case of crotch-rot after being in the field.
I think arts is pretty darn good. However, where it falls short is working with thing like flash & certain games. It still has a ways to go.
I think the real major weakness is the diversity of the sound options in linux. Is arts the way to go? gstreamer? If someone would settle on one from on-high (and maybe they already have), I think a lot of our problems would clear up within six months.
That's all well & good. However, my point is that this guy is a fairly minor player in the OSS scene. I'm not bashing his abilities or his contributions. But, I'm also not impressed enough (nor are a lot of /.'ers, judging from the comments) to see the point of this story.
;-)
He did some stuff a while back & then dropped out of the scene, such as it is, for a while. Now he has sound problems & bought a Mac instead. Good for him. Why is this newsworthy?
People talk about his obvious skills. He wrote xscreensaver - big deal. It kinda sucks, quite frankly. Don't get me wrong, I could never write a replacement. Of course, I've always been able to get my sound to work properly.
My point is that when ESR said "CUPS sucks," people were (for the most part) interested. It fostered a healthy discussion about where we were in printing & where we wanted to go. Sound is a no-brainer. No one here in their right mind is going to say the current state is fine - we know it's not. So what the point of the story? I'm really trying not to be an asshole, I just can't for the life of me see why this was newsworthy. Thanks.
So he worked on Netscape/Mozilla and then quit right before they started to really innovate again with Firefox because he didn't want the rewrite & bitched about how they weren't innovating.
He also did something with Emacs back in the day & does xscreensaver, which, let's all be honest here - isn't all that fucking spectacular.
So why do we care that he got his ass kicked by ALSA? Seriously, it's a pain in the ass, but "Man baffled by Linux sound; switches to Mac & says it's much easier!" doesn't exactly blow my skirt up as a story.
And all of them seem to be coming out of your mouth...
Even a broken clock is right twice a day...
Otherwise, it would be just plain silly, of course.
Well, why can't the stores make money off supporting it?
"We'll include this better browser, as well as Internet Explorer. If you want to learn more about it, you can buy this user guide (which we're reselling from the Mozilla store) or you can pay $25 to come to our open-source class held every other Tuesday night."
For those who haven't seen it, here's the Google cache.
Your site falls flat when resized. I would view it like this. My near-sighted grandparents would try to increase the size and end up with this. In an effort to make sure people only view it the way you want it to be viewed, you have kill accessability.
Oh well, if everyone knows it, then I must be an idiot. I didn't realize you knew so much about combat situations. Thanks for teaching us.
So, are we supposed to have a good academic discussion about where we stand on the issue or are we supposed to flame anyone who is a proponent of Intelligent Design?
Because the summary seems predisposed towards the latter.
Commonly known by whom?
In KDE, simply go the the K Menu->Switch User.
Works fairly quickly, but is happier with more than 256MB RAM. Only downside is sound is locked for every session except the first. I can't wait for the sound situation in Linux to get simplified and fixed. *sigh*
Excellent, I understand now. I think my confusion was that I assumed with only one instance of Gecko being loaded into memory, a crash in one would still bring down the others. If that is not the case, then I am all for it. Thanks.
Paragraphs are your friend. Use them.
You're forgetting one very important thing. As a matter of fact, everyone who is a big Moz suite fan says the same thing as you, but they forget one of the biggest reasons for FF/TB: seperating the memory of the various suite applications.
Does no one remember that there was (and may still be, I use FF/TB instead of the suite now) a major problem with one part of the suite crashing and taking the rest with it? Many times I was bitten by a buggy Moz Mail plugin crashing and pulling my 10+ tab web session off the cliff with it. I was very happy to hear that they were going to redo the various components as stand-alone apps and then later reintegrate them into a single cohesive suite, but one with more protection between its various pieces.
Now the latter part of the plan seems to have fallen by the wayside and only time will tell if it will eventually happen. I understand and agree that running both FF and TB takes an inordinate amount of resources when compared to the suite, but I'm hesitant to lose that safety separation. I'm hoping that there is a happy medium that can be reached (and please educate me if you know what that would be). But what you suggest sounds to me like an invitation to the disasters of old.
Hrm... aside from the fact that he never said that, I consider myself "different" and "very smart." And the Marine Corps made an officer out of me. I've been in over eight years (combining NROTC and active duty) and I'm very happy. In fact, I've thrived and I've seen others like me thrive time and again.
So next time make sure you know what the hell you're talking about before you spout off. Thanks.