I did that too and also found a lot of weird effects stuff. A lot of the CG doesn't look like what it's supposed to be when you look at it real close. Maybe this was a pre-render. We can hope.
If you're on call 24x7, forget the "work line" - the company should be paying the full bill for a cell phone. You shouldn't have to run a "work line" connection to your bedroom so you can hear it at 3 AM.
The work line should have only one hard connection - in the home office.
If they're going to use browser/OS references to pick up different computer, install a proxy (or even the UA Toolbar in Mozilla) to mask/change what you report and screw with them just using your one PC.
How do you account for things like the various ways IE calculates widths? IIRC, some versions use "width" to mean the whole element, padding, margin, border and all, while the spec (and maybe a version of IE) says "width" is the width of the actual content.
I think IE was designed with the spec in mind more from the standpoint of "this is what the spec says, how can we screw with it enough to not be noticed but still mess things up?"
So you want bug-for-bug compatibility with IE? I doubt all the IE rendering bugs and oddities are even documented. Sounds like the same struggle WINE has to go through with the Windows APIs.
While I want to agree, I'm afraid I just can't. I'm a developer, I use Mozilla 99.99% of the time at home. Although I do everything I can to stick with the standards and make sure things look/work right across browsers, my clients care more about IE than anything else (because that's all they've ever known, same with their clients) so if IE mangles what I've written, I don't have much choice but to fix it (and probably get what I didn't want in Mozilla, standards be damned). If I'm maintaining an old, horribly broken site, my goal is to just not hose what's already there, and that normally means not coding anywhere near the standards.
Like I said, I love Mozilla, I use it almost exclusively at home, and I would really, really, really like to believe that as long as I code 100% standard code and things check out OK in Mozilla I'm fine, at the end of the day if it doesn't look "perfect" in IE, it doesn't matter how correct it is or how nice it looks in Mozilla.
I remember in years past, you had to really look closely at a/. story on April 1 because the fake stories were so well-woven. This year, they aren't even trying and even worse, they're posting dupes!
As I understand it, one of the reasons for the GRE is so that you can have multiple Gecko-based apps running, without the bloat of firing up multiple copies. So yes, if the GRE crashes, all your dependent apps would go with it.
But how will that play once Phoenix & Minotaur are both using the GRE (Gecko Runtime Environment). Sure, if the UI bombs in Minotaur Phooenix will probably be OK, but if the GRE takes a dump, you're no better off than you were with Mozilla.
The last large "activity" our company's IT department put together was a BBQ & game at the local AAA baseball stadium. I can't stand the game of baseball itself (and I'm sure there were more non-fans than fans there), but the act of going out to the park and hanging out there was fun. The last thing I want the company doing to "improve morale" is to ask me to stay in the office and stare at the screen for several more hours - regardless of what's on the screen.
Your job does not define who you are. Being "computer geeks" does not mean we should not do anything outside that realm.
Oh, and don't BS me that my job is secure. A lot of really good people got let go in the last round of layoffs. If more are coming, tell me. If they're over, tell me that too. But don't ever "assure" me that my job is "secure" - there is no such thing anymore.
I seem to recall hearing that battered women's programs/shelters give phones to their clients. In the US (or maybe it's just New York), all cell phones must be able to connect to 911 even if they're not set up with a subscription. So, if someone's in trouble, they have a free call to 911 no matter where they are.
I'm on a mailing list and our AOL-based members frequently post "did the list die? I haven't gotten any email in the last couple days". AOL doesn't even reject the messages, they just get blackholed. Someone in the bowels of AOL's mailservers is a cache of tens of thousands of messages about pickup trucks.
Our listmaster has been around and around in circles with AOL on it several times. It's almost not worth fighting anymore. Use AOL, accept the fact that email you want will not always get to you.
NASCAR is becoming more and more like the IROC series every year. For those not familiar with it, IROC is a set of 8 races for "champions" basically to show off driving against one another. Short races, no real point, but the main thing is the cars are all identical.
I'm sure the cars are all the same shape now because Ford & Chevy got upset about last year. Last year Dodge started to pull ahead of the pack (while staying within the rules) and the Chevy teams got NASCAR to change a few rules to make their cars, and only their cars, a little faster. Same thing happened in the early 70s - Dodge was kicking Ford & Chevy's ass, so Ford & Chevy got the rules rewritten to the point where Dodge would have to develop a whole new engine just to stay in the game. So they bailed instead.
The whole thing is rigged. Not as blatant as F1, but it is. The cars quit being "stock" years ago and at the same time innovation, creativity and technology has been stifled.
Maybe she should have stopped in for a drink. Obviously the bartender is in it with the BSA and is upset your wife didn't want to come in and get druuk.
Re:Forgive the obvious question...
on
Superbowl XXXVII
·
· Score: 1
No, F1 is less prominent because it's so obviously rigged.
Wouldn't all that water moving through the ballast system make a lot of noise? Thinking about research/military applications - you don't want to be making noise which will disturb the area your observing or give away your position.
Slashdot Mirror
I did that too and also found a lot of weird effects stuff. A lot of the CG doesn't look like what it's supposed to be when you look at it real close. Maybe this was a pre-render. We can hope.
As I read it, the "dupe" was an unofficial speculation. This sounds as though Sun has made an official statement that the speculation was correct.
If you're on call 24x7, forget the "work line" - the company should be paying the full bill for a cell phone. You shouldn't have to run a "work line" connection to your bedroom so you can hear it at 3 AM.
The work line should have only one hard connection - in the home office.
If they're going to use browser/OS references to pick up different computer, install a proxy (or even the UA Toolbar in Mozilla) to mask/change what you report and screw with them just using your one PC.
How do you account for things like the various ways IE calculates widths? IIRC, some versions use "width" to mean the whole element, padding, margin, border and all, while the spec (and maybe a version of IE) says "width" is the width of the actual content.
I think IE was designed with the spec in mind more from the standpoint of "this is what the spec says, how can we screw with it enough to not be noticed but still mess things up?"
When you click on a node in the tree view of DOM inspector, it flashes a border around the element in the rendered view.
So you want bug-for-bug compatibility with IE? I doubt all the IE rendering bugs and oddities are even documented. Sounds like the same struggle WINE has to go through with the Windows APIs.
While I want to agree, I'm afraid I just can't. I'm a developer, I use Mozilla 99.99% of the time at home. Although I do everything I can to stick with the standards and make sure things look/work right across browsers, my clients care more about IE than anything else (because that's all they've ever known, same with their clients) so if IE mangles what I've written, I don't have much choice but to fix it (and probably get what I didn't want in Mozilla, standards be damned). If I'm maintaining an old, horribly broken site, my goal is to just not hose what's already there, and that normally means not coding anywhere near the standards.
Like I said, I love Mozilla, I use it almost exclusively at home, and I would really, really, really like to believe that as long as I code 100% standard code and things check out OK in Mozilla I'm fine, at the end of the day if it doesn't look "perfect" in IE, it doesn't matter how correct it is or how nice it looks in Mozilla.
And a pantload of hot grits.
Depending on the circumstances, the doctor may advise waiting much longer - perhaps even a year.
And to save electricity, use smaller fonts.
I remember in years past, you had to really look closely at a /. story on April 1 because the fake stories were so well-woven. This year, they aren't even trying and even worse, they're posting dupes!
As I understand it, one of the reasons for the GRE is so that you can have multiple Gecko-based apps running, without the bloat of firing up multiple copies. So yes, if the GRE crashes, all your dependent apps would go with it.
But how will that play once Phoenix & Minotaur are both using the GRE (Gecko Runtime Environment). Sure, if the UI bombs in Minotaur Phooenix will probably be OK, but if the GRE takes a dump, you're no better off than you were with Mozilla.
Extended warranty, how can I lose!?
Your job does not define who you are. Being "computer geeks" does not mean we should not do anything outside that realm.
Oh, and don't BS me that my job is secure. A lot of really good people got let go in the last round of layoffs. If more are coming, tell me. If they're over, tell me that too. But don't ever "assure" me that my job is "secure" - there is no such thing anymore.
I seem to recall hearing that battered women's programs/shelters give phones to their clients. In the US (or maybe it's just New York), all cell phones must be able to connect to 911 even if they're not set up with a subscription. So, if someone's in trouble, they have a free call to 911 no matter where they are.
We're not talking about the 300+ degrees Farenheit used for cooking.
I guess my cubicle neighbors do read/post on Slashdot.
I'm on a mailing list and our AOL-based members frequently post "did the list die? I haven't gotten any email in the last couple days". AOL doesn't even reject the messages, they just get blackholed. Someone in the bowels of AOL's mailservers is a cache of tens of thousands of messages about pickup trucks.
Our listmaster has been around and around in circles with AOL on it several times. It's almost not worth fighting anymore. Use AOL, accept the fact that email you want will not always get to you.
At some point, the federal gov't could conceivably ban them across the board.
NASCAR is becoming more and more like the IROC series every year. For those not familiar with it, IROC is a set of 8 races for "champions" basically to show off driving against one another. Short races, no real point, but the main thing is the cars are all identical.
I'm sure the cars are all the same shape now because Ford & Chevy got upset about last year. Last year Dodge started to pull ahead of the pack (while staying within the rules) and the Chevy teams got NASCAR to change a few rules to make their cars, and only their cars, a little faster. Same thing happened in the early 70s - Dodge was kicking Ford & Chevy's ass, so Ford & Chevy got the rules rewritten to the point where Dodge would have to develop a whole new engine just to stay in the game. So they bailed instead.
The whole thing is rigged. Not as blatant as F1, but it is. The cars quit being "stock" years ago and at the same time innovation, creativity and technology has been stifled.
Maybe she should have stopped in for a drink. Obviously the bartender is in it with the BSA and is upset your wife didn't want to come in and get druuk.
No, F1 is less prominent because it's so obviously rigged.
Wouldn't all that water moving through the ballast system make a lot of noise? Thinking about research/military applications - you don't want to be making noise which will disturb the area your observing or give away your position.