Note to self: When making next joke about a phony plugin whose purpose is to eliminate rendering differences between IE and Firefox having rendering differences of it's own, google made-up plugin names first. Also, be less subtle.;)
We here at the Firexplorer project have been working on this. We're about ready to release a 0.1 pre-alpha. Unfortunately, a lot of the CSS support is kind of broken due to the way we implemented the wrapper. Firexplorer is actually a fork of Interzilla, which is up to 0.4 right now. They have better CSS support but some of the javascript functions don't always kick in like they're supposed to. But they plan on starting over with a new codebase in Interzilla 2.0, which should get javascript better supported, though it will mean reimplementing the CSS code which could introduce a few more bugs.
So you'll probably want to test your page against Firefox and then Interzilla, Interzilla 2.0 (when it's ready) and probably Firexplorer just to be on the safe side and make sure it works in all of them.
It was scary stuff, radically advanced. It was shattered... didn't work. But it gave us ideas. It took us in new directions... things we would never have thought of. All this work is based on it.
Also, if you read the post right after yours, you'll see that this wasn't even the problem... Except you should already know this because you replied to that post BEFORE you replied to this one.
And you replied:
I did read it. I even responded to it before I responded to you.
It's at this point I realize you are not really reading my posts. You must be reading them somewhat, but maybe "skim" is a better word. But this reply makes me understand why you're absolutely not getting what I'm saying about larger integers, cpu architecture and performance. I give up on you as a lost cause. If you're actually interested in understanding, go back and read my posts again and maybe you'll get it.
Sigh. I wasn't saying this WAS graphics code. I thought that was fairly clear. I was just making the point to you that choosing your variable size isn't just about size, it's about performance. CPU architecture handles certain variable sizes differently. This means different variables types will actually affect the performance of your app, even if it has nothing to do with the graphics.
Also, if you read the post right after yours, you'll see that this wasn't even the problem. The problem in the weird way they were prefixing things, which caused it to roll over way before the size of the variable did. It was a bug, plain and simple. Would have been a bug even if they had prefixed an Int64. Except you should already know this because you replied to that post BEFORE you replied to this one.
It's not just a waste of space, it's a waste of time. Using certain data types can be much faster, especially where graphics are concerned. While you don't want screw something up by skimping, picking the right data type for the situation is the way you get the highest performance from your code. Games would be a case where this matters a lot.
As AC pointed out, you're right about the yellow bar. I had unchecked it long enough ago that I forgot about it. But you have to admit, this bar will show up on almost every page, whether it breaks it or not (so many pages use at least a little scripting these days). So the user will quickly be used to it being a "normal" part of the browser working properly. Plus, the message displayed is fairly non-obvious: Scripts Partially Allowed [<script>:10][Java + Flash + Plugin: 0]
This is definitely a message for the advanced user. One for the regular user would be "Some features of this page have been automatically disabled. To allow them and reload the page, click on the Options button to the right."
If you're going to post a reply to a reply, please read the original message. This was in the context of having NoScript on, NOT in the context of disabling javascript. With NoScript, there is no big yellow bar, because javascript is on.
Sweet! Thanks for the update. I installed the RC and it seems to have cleared up. Very good news, indeed.
The frustrating thing was that I only just recently tracked down the cause of the problem. I had been dinking with a greasemonkey script and thought it was doing it.
The problem with non-geek users is that it's often not obvious at all that it's the lack of javascript that is breaking the site. Sometimes, the symptom of breakage is the LACK of something. If you aren't a bit techy, you won't notice that it isn't there.
This is a good opportunity to bring up a problem with NoScript. It seems to have a flaw with certain sites. With digg, it sometimes makes the thumbs and the show/hide comment links not work properly. It breaks the thumbs completely and instead of the show/hide working in a DHTMLish way, it instead follows the href version of the link. This bug doesn't show up all the time, but on a page where it does show up, you can reload over and over and still get the bug every time.
It does this even when all the sites it lists for the page are set to allowed. But if you set it to "Allow script Globally" (basically, letting EVERYTHING through) and reload the page, the bug goes away. So something there is being blocked that shouldn't be.
Bots were old news by the time AC came along. They had been used on MUDs for years before that. And it was much easier to create a bot for a MUD considering the limited input/output mechanism.
If/. were even more serious about keeping the crap out, they could disable the anonymous coward.
Actually, I would argue that it makes slashdot BETTER to have anonymous posting. A certain percentage of those people making junk comments anonymously would actually have signed up and commented as a registered user. Who knows what that percentage is, but even if its low this still keeps a lot of crap out of the normal comment view.
But as you have to admit, even non-mainstream obscure offbeat bands will frequently come out with one or two good songs and try to ride that success to sell an entire album of otherwise blah material. It doesn't just happen in RIAA manufactured-music land.
All of that is a moot point. The poster was pointing out that the effect of larger bookseller chains, cheaper online sales, and loss-leader places like CostCo are sufficient to run local bookstores out of business. All of these same influences are happening in the music store business, and all they can do is blame piracy.
Slashdot Mirror
Turns out it's "Don't be evil", not "Don't buy evil."
I think the appropriate phrase should be "Tests like chicken."
Note to self: When making next joke about a phony plugin whose purpose is to eliminate rendering differences between IE and Firefox having rendering differences of it's own, google made-up plugin names first. Also, be less subtle. ;)
We here at the Firexplorer project have been working on this. We're about ready to release a 0.1 pre-alpha. Unfortunately, a lot of the CSS support is kind of broken due to the way we implemented the wrapper. Firexplorer is actually a fork of Interzilla, which is up to 0.4 right now. They have better CSS support but some of the javascript functions don't always kick in like they're supposed to. But they plan on starting over with a new codebase in Interzilla 2.0, which should get javascript better supported, though it will mean reimplementing the CSS code which could introduce a few more bugs.
So you'll probably want to test your page against Firefox and then Interzilla, Interzilla 2.0 (when it's ready) and probably Firexplorer just to be on the safe side and make sure it works in all of them.
You used to live at BANK OF AMERICA? Now that's customer service.
It was scary stuff, radically advanced. It was shattered... didn't work. But it gave us ideas. It took us in new directions... things we would never have thought of. All this work is based on it.
Sigh. I wasn't saying this WAS graphics code. I thought that was fairly clear. I was just making the point to you that choosing your variable size isn't just about size, it's about performance. CPU architecture handles certain variable sizes differently. This means different variables types will actually affect the performance of your app, even if it has nothing to do with the graphics.
Also, if you read the post right after yours, you'll see that this wasn't even the problem. The problem in the weird way they were prefixing things, which caused it to roll over way before the size of the variable did. It was a bug, plain and simple. Would have been a bug even if they had prefixed an Int64. Except you should already know this because you replied to that post BEFORE you replied to this one.
I wonder how difficult it would be to make a DIY microwave "pain gun"...
BTW, Vader is Lukes father.
Also, it's a sled. His beloved childhood sled.
Sorry.
It's not just a waste of space, it's a waste of time. Using certain data types can be much faster, especially where graphics are concerned. While you don't want screw something up by skimping, picking the right data type for the situation is the way you get the highest performance from your code. Games would be a case where this matters a lot.
Have you tried the release candidate to see if it fixes that? I cleared up my problem with digg.
As AC pointed out, you're right about the yellow bar. I had unchecked it long enough ago that I forgot about it. But you have to admit, this bar will show up on almost every page, whether it breaks it or not (so many pages use at least a little scripting these days). So the user will quickly be used to it being a "normal" part of the browser working properly. Plus, the message displayed is fairly non-obvious:
Scripts Partially Allowed [<script>:10][Java + Flash + Plugin: 0]
This is definitely a message for the advanced user. One for the regular user would be "Some features of this page have been automatically disabled. To allow them and reload the page, click on the Options button to the right."
If you're going to post a reply to a reply, please read the original message. This was in the context of having NoScript on, NOT in the context of disabling javascript. With NoScript, there is no big yellow bar, because javascript is on.
Sweet! Thanks for the update. I installed the RC and it seems to have cleared up. Very good news, indeed.
The frustrating thing was that I only just recently tracked down the cause of the problem. I had been dinking with a greasemonkey script and thought it was doing it.
It seems to be breaking slashdot, too. I keep trying to give your comment a thumbs down and it's not taking effect...
DHTML includes things like CSS hovers. So breaking javascript doesn't break all DHTML. Just the javascript.
DHTML is an ill-defined umbrella term that just refers to anything other than static html.
The problem with non-geek users is that it's often not obvious at all that it's the lack of javascript that is breaking the site. Sometimes, the symptom of breakage is the LACK of something. If you aren't a bit techy, you won't notice that it isn't there.
This is a good opportunity to bring up a problem with NoScript. It seems to have a flaw with certain sites. With digg, it sometimes makes the thumbs and the show/hide comment links not work properly. It breaks the thumbs completely and instead of the show/hide working in a DHTMLish way, it instead follows the href version of the link. This bug doesn't show up all the time, but on a page where it does show up, you can reload over and over and still get the bug every time.
It does this even when all the sites it lists for the page are set to allowed. But if you set it to "Allow script Globally" (basically, letting EVERYTHING through) and reload the page, the bug goes away. So something there is being blocked that shouldn't be.
Bots were old news by the time AC came along. They had been used on MUDs for years before that. And it was much easier to create a bot for a MUD considering the limited input/output mechanism.
Well, that's it, then. Even orbital satellites are getting more action than I am.
But as you have to admit, even non-mainstream obscure offbeat bands will frequently come out with one or two good songs and try to ride that success to sell an entire album of otherwise blah material. It doesn't just happen in RIAA manufactured-music land.
All of that is a moot point. The poster was pointing out that the effect of larger bookseller chains, cheaper online sales, and loss-leader places like CostCo are sufficient to run local bookstores out of business. All of these same influences are happening in the music store business, and all they can do is blame piracy.
Are iPods running Linux really "iPods" anymore? Might as well say there's this cursor virus that infects Macs booted into Windows.
A more accurate title would be "virus that affects some versions of Linux."