Apple didn't put their future into the GPL though. They could easily stop distributing GPL'd code if they wanted to, without having a significant impact on their product line.
Does it matter how much you sacrificed for your employer? Nope, not a damn bit. All those pep talks about being in it together.. they're complete bullshit.
It could be true, and your boss could be laid off at the same time you are.
If they give you a mug or a fancy pen or a cheap desk clock with the company logo on it, that's when you know it's BS.
Thankfully, the job market is gradually improving.
Remember, when you see the unemployment rate go down, it's not because people are finding jobs, it's because they've abandoned hope and are no longer trying to get a job, so they no longer get counted as "unemployed" - they're removed from the equation.
However, for those who are still looking, yeah, maybe it is starting to get better. I've got an interview tomorrow.
If you need the job, lie. Sure, lying on your application is grounds for termination. If they find out, you could suddenly wind up unemployed again. Oh no.
What has your experience with SpamCop's system been?
Nothing but good things to say about them, and I've been on the other end too - I've worked in the abuse department at an ISP, and the vast majority of our spam complaints came from SpamCop. They put all the most important info in the subject line and the reports are all formatted consistently, making it very easy to deal with them. We were understaffed for awhile, so the SpamCop reports were the ones I dealt with first, because I could get them out of the way faster.
I also use the service myself. There have been some occasional glitches, which have almost entirely been due to denial of service attacks. These glitches have not caused me to lose mail, but DDoS attacks have caused mail to be delayed on occasion - normally it's delivered in seconds, but I've seen it take a day or so.
The way I have it set up, mail to my domain is forwarded to my SpamCop account, and anything that doesn't get stopped by their filter is forwarded on to my server at home. If I have any problems with my server at home, I can disable the forwarding and use SpamCop's webmail temporarily.
Depending on how you have things set up, if SpamCop thinks something doesn't look right, it is possible to report yourself to your own ISP's abuse department. They don't like that much. When submitting a complaint, be sure to review the list of addresses the complaint will be sent to before sending it.
Actually, if you're considering donating, you should consider signing up for their paid service. For $3/month, you get just about all the e-mail features you could want, and on top of that, you can submit spam reports much more easily.
That's not really up to me, is it? It will die when people stop using it. In the mean time I can choose to either 1) make my site render correctly for the people still running it, or 2) make my site not render correctly for those people. You can bet if I choose 2, they won't blame their crappy browser.
Actually Yikes, Yosemite and Sawtooth were internal code-names, never intended to be used by the public. The official public names of Yikes and Sawtooth names are "PowerMac G4 (PCI Graphics)" and "PowerMac G4 (AGP Graphics)" respectively, and the systems are distinguished by the orientation of the headphone and microphone jacks on the back (horizontal or vertical, I forget which is which). And, the code-name "Yikes" actually did make sense - Sawtooth was supposed to be the motherboard they used when the G4 was introduced, but Sawtooth wasn't ready yet, and Steve Jobs wanted to ship, so they quickly figured out how to throw a G4 processor onto a motherboard designed for a G3. Within a few months, they were replaced by Sawtooth systems. If you know anything about Steve Jobs, you'll understand why they'd call it "Yikes!" He has a reputation for throwing things at people when he's not happy.
The decision to ship the G4 early was widely regarded as a mistake, since Motorola wasn't anywhere near ready to supply sufficient quantities. I don't recall the result of Apple's lawsuit against Motorola for that.
I would do everything you said, in reverse: Write the imported stylesheet first, to get the look you want in modern browsers. Netscape doesn't understand style, so it will ignore it; now make a copy of the css you just wrote, and link it. Fix the stuff that breaks in Netscape, but without overloading any elements - because styling those elements explicitly will take precedence over anything that is supposed to follow inheritance properly in your advanced, imported stylesheet.
I don't follow you. Of course I mean start by creating a stylesheet that works in modern browsers, don't start by developing for Netscape 4. You'll go insane.
In my example, say you want a div to be a total of 200px wide including 10px of padding on each side. Start with standard code in main.css:
Now, because Netscape's box model is broken, you need to set the width to 200px in Netscape 4. To do that, make this change in main.css:
#foo {
width: 200px;/* overridden to 180px in not-netscape4.css */
padding: 10px;
background-color: #660044; }
And add in not-netscape4.css:
#foo {
width: 180px; }
Modern browsers will load both stylesheets, and the second one will take precedence because it's loaded later. Netscape does understand style but does not understand @import, so it will not load the second stylesheet.
This is an awkward way to do it; it would be much easier to make a stylesheet specifically for Netscape, instead of a stylesheet specifically not for Netscape, but I'm not aware of a good way to do that.
Yep, that bit me too. Check out this hack - you can put that in an IE-specific stylesheet and use conditional comments to load it. Note that fixed positioning is supported in IE5/Mac but with a serious bug - mouseovers don't work at all (when you move the mouse over a link nothing happens, the cursor doesn't change to a hand, the URL doesn't display in the status bar, the hover style doesn't apply, etc.) - and this hack (and the conditional comments to load it) only work in IE for Windows. Mac users with OSX should switch to Safari, but IE is one of the best browsers available for OS9 (Mozilla/Netscape 6 is big, slow, and no longer being developed for that platform), so those users may be out of luck.
I did RTFA and I didn't call it a URL. I guess I just don't understand what this is useful for. Perhaps that means it's not something that will ever be useful to me, but will come in handy for somebody else. Fair enough.
Try the opposite approach: start by getting it to work in Mozilla, then check it in other browsers. Along the way, use the W3C Validator. If you can't make it work in IE/Win and still validate, there may be a better way to do what you want that is standards-compliant AND works in IE/Win in addition to what you're used to. When that's not the case, use conditional comments (google if you don't know what they are) to let you write code specifically for IE/Win (or specifically for everything else).
Make your main stylesheet, then figure out which things don't work correctly in Netscape 4 (e.g. the width of a box incorrectly includes the padding, so for NS4 you should add the left and right padding when specifying a width). Where they differ, put the Netscape 4 code in the main stylesheet and the standards-compliant code in a second stylesheet. Comment the main stylesheet so you remember which code is specific to Netscape 4. Then load your stylesheets like this:
Any browser except Netscape 4 will load both stylesheets, so the standards-compliant code in the second one will override the Netscape 4-specific code in the main one.
You mean it's not enough to make sure it works in IE6 on Windows XP?? I wish more web "developers" were concerned with standards. Not only does it make their job easier, it makes it easier to use their sites (assuming the browser developers are equally concerned with standards).
Keep in mind that it's just as easy to build a standards-compliant site that doesn't work in IE6 on Windows XP.;-)
A site I'm building has a lot of browser-specific CSS code - stylesheets that will only be loaded by certain browsers. Every bit of it validates at validator.w3.org (except for internet-explorer.css, which is only loaded by MSIE 5 and 6 on Windows, and is loaded using conditional comments which the W3C validator doesn't parse). The problem isn't creating code that the W3C says is valid, the problem is creating code that works as you intend across multiple browsers, which the W3C won't help you with.
Don't get me wrong, it's a wonderful tool, but it doesn't eliminate the need for practical books like this.
How exactly will browsers implement this new protocol?
I'm confused about the concept of a "public namespace". If these new URIs are intended to point to information, where will that information be stored and how will it be retrieved?
Control-Eject works great for rebooting, shutting down and going to sleep. It does not work for turning the system on, and rebooting after a kernel panic. The only way for me to reboot my eMac after a kernel panic is to reach around the side of the machine and hold the power button for 4 seconds, then press it again to turn it back on.
Heh, weird. I get kernel panics pretty often. Had three in one day once, although going a few months without one is just as common. One time I got a pre-10.2-style kernel panic in 10.2.6 - that freaked me out because I had assumed all kernel panics had been completely replaced in 10.2 and that wouldn't ever happen. I took a picture of it.
Pictures here if you don't know what they look like, and technical docs here.
(similar to Ctrl-Open Apple/Closed Apple-Reset on Macs)
You may be thinking of the Apple II, which had "open Apple" and "closed Apple" keys (the former was an outline of the Apple logo; the latter was solid). As I recall, Control-Reset would interrupt a program, and Control-Open Apple-Reset would reboot the machine.
Macs have a Command key, which also has an open Apple logo on it, as well as the clover-leaf design. Older Macs also have a power key, which has a triangle - sadly, the power key is no longer to be found on Apple's Pro keyboards. Under classic Mac OS, Command-Power invokes the system debugger (MacsBug if it's installed, or the little white box), equivalent to pressing the Interrupt button next to the Reset button in the back of the machine. Command-Control-Power resets the machine, and is done in hardware rather than software so it always works.
Slashdot Mirror
Apple didn't put their future into the GPL though. They could easily stop distributing GPL'd code if they wanted to, without having a significant impact on their product line.
can't get much more obvious...
A little quick Googling...
Although the unemployment rolls declined more than usual between July and August, the labor department said there were fewer employed residents.
But behind the area's rosy unemployment rate is the reality that fewer people are working than a year ago - 2,900 fewer in Escambia County, and 1,255 in Santa Rosa County.
"While the number of people unemployed was lower, employment levels actually dropped slightly from July."
The number of jobseekers declined by more than 17,000 over the month. Sharp reductions were also noted in the number of job losers, as well as the number of jobseekers entering the labor market for the first time.
Does it matter how much you sacrificed for your employer? Nope, not a damn bit. All those pep talks about being in it together.. they're complete bullshit.
It could be true, and your boss could be laid off at the same time you are.
If they give you a mug or a fancy pen or a cheap desk clock with the company logo on it, that's when you know it's BS.
Thankfully, the job market is gradually improving.
Remember, when you see the unemployment rate go down, it's not because people are finding jobs, it's because they've abandoned hope and are no longer trying to get a job, so they no longer get counted as "unemployed" - they're removed from the equation.
However, for those who are still looking, yeah, maybe it is starting to get better. I've got an interview tomorrow.
But what if you have a lot of technical skills?
If you need the job, lie. Sure, lying on your application is grounds for termination. If they find out, you could suddenly wind up unemployed again. Oh no.
But at least it's income.
It doen't pay nearly as well as unemployment.
I bet Gordon Brown would find that amusing...
What has your experience with SpamCop's system been?
Nothing but good things to say about them, and I've been on the other end too - I've worked in the abuse department at an ISP, and the vast majority of our spam complaints came from SpamCop. They put all the most important info in the subject line and the reports are all formatted consistently, making it very easy to deal with them. We were understaffed for awhile, so the SpamCop reports were the ones I dealt with first, because I could get them out of the way faster.
I also use the service myself. There have been some occasional glitches, which have almost entirely been due to denial of service attacks. These glitches have not caused me to lose mail, but DDoS attacks have caused mail to be delayed on occasion - normally it's delivered in seconds, but I've seen it take a day or so.
The way I have it set up, mail to my domain is forwarded to my SpamCop account, and anything that doesn't get stopped by their filter is forwarded on to my server at home. If I have any problems with my server at home, I can disable the forwarding and use SpamCop's webmail temporarily.
Depending on how you have things set up, if SpamCop thinks something doesn't look right, it is possible to report yourself to your own ISP's abuse department. They don't like that much. When submitting a complaint, be sure to review the list of addresses the complaint will be sent to before sending it.
Kill their ratings and it will stop. Simple. Besides, it has Paul Anka's guarantee.
Um, Nielsen doesn't happen to be using me in one of their surveys at the moment; nobody will know whether I watch or not. Got a better idea?
I completely agree.
Actually, if you're considering donating, you should consider signing up for their paid service. For $3/month, you get just about all the e-mail features you could want, and on top of that, you can submit spam reports much more easily.
Better yet, just let Netscape 4 die!!! :-)
That's not really up to me, is it? It will die when people stop using it. In the mean time I can choose to either 1) make my site render correctly for the people still running it, or 2) make my site not render correctly for those people. You can bet if I choose 2, they won't blame their crappy browser.
Doesn't IE/Mac fail to load that as well? I could be wrong...
Oh, great trick for IE/Mac: in the stylesheet, make a comment that includes a backslash. IE/Mac will ignore the next rule.
Actually Yikes, Yosemite and Sawtooth were internal code-names, never intended to be used by the public. The official public names of Yikes and Sawtooth names are "PowerMac G4 (PCI Graphics)" and "PowerMac G4 (AGP Graphics)" respectively, and the systems are distinguished by the orientation of the headphone and microphone jacks on the back (horizontal or vertical, I forget which is which). And, the code-name "Yikes" actually did make sense - Sawtooth was supposed to be the motherboard they used when the G4 was introduced, but Sawtooth wasn't ready yet, and Steve Jobs wanted to ship, so they quickly figured out how to throw a G4 processor onto a motherboard designed for a G3. Within a few months, they were replaced by Sawtooth systems. If you know anything about Steve Jobs, you'll understand why they'd call it "Yikes!" He has a reputation for throwing things at people when he's not happy.
The decision to ship the G4 early was widely regarded as a mistake, since Motorola wasn't anywhere near ready to supply sufficient quantities. I don't recall the result of Apple's lawsuit against Motorola for that.
I would do everything you said, in reverse: Write the imported stylesheet first, to get the look you want in modern browsers. Netscape doesn't understand style, so it will ignore it; now make a copy of the css you just wrote, and link it. Fix the stuff that breaks in Netscape, but without overloading any elements - because styling those elements explicitly will take precedence over anything that is supposed to follow inheritance properly in your advanced, imported stylesheet.
/* overridden to 180px in not-netscape4.css */
I don't follow you. Of course I mean start by creating a stylesheet that works in modern browsers, don't start by developing for Netscape 4. You'll go insane.
In my example, say you want a div to be a total of 200px wide including 10px of padding on each side. Start with standard code in main.css:
#foo {
width: 180px;
padding: 10px;
background-color: #660044;
}
Now, because Netscape's box model is broken, you need to set the width to 200px in Netscape 4. To do that, make this change in main.css:
#foo {
width: 200px;
padding: 10px;
background-color: #660044;
}
And add in not-netscape4.css:
#foo {
width: 180px;
}
Modern browsers will load both stylesheets, and the second one will take precedence because it's loaded later. Netscape does understand style but does not understand @import, so it will not load the second stylesheet.
This is an awkward way to do it; it would be much easier to make a stylesheet specifically for Netscape, instead of a stylesheet specifically not for Netscape, but I'm not aware of a good way to do that.
Yep, that bit me too. Check out this hack - you can put that in an IE-specific stylesheet and use conditional comments to load it. Note that fixed positioning is supported in IE5/Mac but with a serious bug - mouseovers don't work at all (when you move the mouse over a link nothing happens, the cursor doesn't change to a hand, the URL doesn't display in the status bar, the hover style doesn't apply, etc.) - and this hack (and the conditional comments to load it) only work in IE for Windows. Mac users with OSX should switch to Safari, but IE is one of the best browsers available for OS9 (Mozilla/Netscape 6 is big, slow, and no longer being developed for that platform), so those users may be out of luck.
I did RTFA and I didn't call it a URL. I guess I just don't understand what this is useful for. Perhaps that means it's not something that will ever be useful to me, but will come in handy for somebody else. Fair enough.
Try the opposite approach: start by getting it to work in Mozilla, then check it in other browsers. Along the way, use the W3C Validator. If you can't make it work in IE/Win and still validate, there may be a better way to do what you want that is standards-compliant AND works in IE/Win in addition to what you're used to. When that's not the case, use conditional comments (google if you don't know what they are) to let you write code specifically for IE/Win (or specifically for everything else).
Make your main stylesheet, then figure out which things don't work correctly in Netscape 4 (e.g. the width of a box incorrectly includes the padding, so for NS4 you should add the left and right padding when specifying a width). Where they differ, put the Netscape 4 code in the main stylesheet and the standards-compliant code in a second stylesheet. Comment the main stylesheet so you remember which code is specific to Netscape 4. Then load your stylesheets like this:
<link rel="stylesheet" href="/main.css" type="text/css">
<style type="text/css"><!--
@import url(/not-netscape4.css);
--></style>
Any browser except Netscape 4 will load both stylesheets, so the standards-compliant code in the second one will override the Netscape 4-specific code in the main one.
You mean it's not enough to make sure it works in IE6 on Windows XP?? I wish more web "developers" were concerned with standards. Not only does it make their job easier, it makes it easier to use their sites (assuming the browser developers are equally concerned with standards).
;-)
Keep in mind that it's just as easy to build a standards-compliant site that doesn't work in IE6 on Windows XP.
A site I'm building has a lot of browser-specific CSS code - stylesheets that will only be loaded by certain browsers. Every bit of it validates at validator.w3.org (except for internet-explorer.css, which is only loaded by MSIE 5 and 6 on Windows, and is loaded using conditional comments which the W3C validator doesn't parse). The problem isn't creating code that the W3C says is valid, the problem is creating code that works as you intend across multiple browsers, which the W3C won't help you with.
Don't get me wrong, it's a wonderful tool, but it doesn't eliminate the need for practical books like this.
Anyone else notice info-uri.niso.org doesn't exist?
How exactly will browsers implement this new protocol?
I'm confused about the concept of a "public namespace". If these new URIs are intended to point to information, where will that information be stored and how will it be retrieved?
Control-Eject works great for rebooting, shutting down and going to sleep. It does not work for turning the system on, and rebooting after a kernel panic. The only way for me to reboot my eMac after a kernel panic is to reach around the side of the machine and hold the power button for 4 seconds, then press it again to turn it back on.
Heh, weird. I get kernel panics pretty often. Had three in one day once, although going a few months without one is just as common. One time I got a pre-10.2-style kernel panic in 10.2.6 - that freaked me out because I had assumed all kernel panics had been completely replaced in 10.2 and that wouldn't ever happen. I took a picture of it.
Pictures here if you don't know what they look like, and technical docs here.
(similar to Ctrl-Open Apple/Closed Apple-Reset on Macs)
You may be thinking of the Apple II, which had "open Apple" and "closed Apple" keys (the former was an outline of the Apple logo; the latter was solid). As I recall, Control-Reset would interrupt a program, and Control-Open Apple-Reset would reboot the machine.
Macs have a Command key, which also has an open Apple logo on it, as well as the clover-leaf design. Older Macs also have a power key, which has a triangle - sadly, the power key is no longer to be found on Apple's Pro keyboards. Under classic Mac OS, Command-Power invokes the system debugger (MacsBug if it's installed, or the little white box), equivalent to pressing the Interrupt button next to the Reset button in the back of the machine. Command-Control-Power resets the machine, and is done in hardware rather than software so it always works.