I'm guessing Shockwave. It supports rendering in D3D and OpenGL. There was an FPS made in it once that was pretty fun, you could only play with bots though. It was also time locked so it wouldn't work after a certain date but rewinding your clock to the date it specified worked.
Indexing of HTTPS pages is most certainly a bug. Did the poster of the article report it to make Google Chrome a better product or is he just going to complain? It's only in beta.
And the work around is simple: Use Incognito mode for all sensitive work. Which is what it's for.
Apple ties their OS to their approved hardware. If you want to run the Mac OS, you need an Apple-made computer to run it on. Those computers are also notorious for having few upgrade options.
Of course there are individuals who have hacked Mac's OS to run on any PC... but Apple doesn't like those people for some reason... >_>
You must still be using IE8b1. b2 gets a whopping 21!
Also my Chrome gets 79*, so there!
* - I'm serious, actually. Although test results tend to fluctuate if you have high CPU load elsewhere and/or a speed test just barely passes sometimes.
Re:But we can already crash EVERY tab at once
on
Chrome Vs. IE 8
·
· Score: 1
Fun, I just tried it. Thanks for not making it a link, by the way.
Re:Didn't measure memory correctly
on
Chrome Vs. IE 8
·
· Score: 1
You know I thought they might have done something like that when I read the summary. You can see clear metrics of memory on about:memory in Chrome.
Re:Non-Tech Percent of Web Traffic from Chrome
on
Google Chrome, Day 2
·
· Score: 1
You can block third-party cookies but yeah they need something like NoScript.
For adblocking I'm temporatily using a hosts-based solution until someone makes an Adblock port or something.
V8 is also open source. In fact in the webcast just an hour ago one of the V8 devs said they'd love for other browsers to use their engine, or to use their ideas to make a better Javascript engine.
Why does a new process necessarily mean it will use lots of RAM? I have three apps running right now are all using < 100kb of memory each. Two tray apps and some background caching app for TortoiseSVN folder overlay icons.
IMHO, when you do a public release you should take the time to make a proper build, even if it IS a beta. All it takes is clicking a different button (at least in VS Express).
I was just playing on a Team Fortress 2 map marked as an alpha with horrid framerates. The map creator had released it but had not taken the time to optimize VIS*, and my framerate suffered at some parts where it should not have. It was very annoying and as a result I don't like an otherwise good map.
* VIS is a compile process responsible for making sure the game engine does not render more of the map at any point than it needs to, to improve framerates. The VIS compiler, as I understand how it works for both the Q3 and Source/GoldSource engines, splits up a level into logical chunks. The logical separators to these chunks are called VIS portals. The compiler then computes which other chunks the player can see when they are in any specific chunk. In game, the engine uses this to only render the chunks the player can possibly see from the chunk they are in. A map creator can place hint brushes to suggest optimum placement of VIS portals... in this case, a few of those might have helped the compiler to make better choices about chunk placement. The VIS compile stage can be skipped completely (commonly if you want to quickly test a map change) but then the entire level is always rendered. I don't think this particular author made THAT bad of a mistake since I found some areas in the level with good VIS.
Most GUI apps today have to be multithreaded. If there is not a dedicated thread to handle GUI events (IE when the user clicks something) the UI will freeze up whenever the program does something. Occasionally there will be an app that only does small, quick tasks when required, so this isn't an issue cause you can't notice the freezing. But any app that does a large amount of processing or any action that takes longer than a second or so should be using a second thread to do that work, so the UI thread is free (preferably to show the progress of the background task, allow the user to cancel it, etc).
1.) IE 8 is still in Beta. I'm sure most folks remember what that means. As in not quite feature complete yet?
Actually the general definition of beta IS feature complete, just not 100% bug fixed.
It's only when you start talking about MS where that changes. If this was Firefox we were talking about, this build would be considered an Alpha build by the Mozilla team.
Here is, IMO, general definitions of common project states:
Alpha: Not feature complete, emphasis on adding new features rather than bug fixing or performance tweaks.
Beta: Feature complete, emphasis on bug fixing and performance tweaks.
Release Candidate: Builds desired to be released as final. Focus on testing. Minor bugs may be fixed in later releases unless they are deemed serious enough to require fixing for the final release, in which case a new RC is issued.
Final Release: The last RC was deemed acceptable for general release.
I'm not sure where "Gamma" fits in there, I think it's the same as an RC.
Here's how Microsoft seems to be doing it, from my own experience in testing Vista, IE8, etc:
Beta: Not feature complete, emphasis on adding new features rather than bug fixing or performance tweaks.
Release Candidate: Feature complete, emphasis on bug fixing and performance tweaks.
Final Release: Minor bugs are left for the next major release version in several years, unless they are security related. Those and all major bugs are pushed out in future hotfixes and service packs.
Service Pack: The last pack of hotfixes makes the total patches for the product difficult to keep track of, so they are consolidated into a service pack.
Disclaimers: I have used Vista. I got my copy for free through an MS promo and I am not using it. On my computer it is too slow to use without wanting to chuck my CPU out the window. XP is much better. I conclude XP will run better on any computer. Once I get a new CPU I will probably end up using Vista, since it will likely run at a usable speed. IE8 looks pretty nice and actually has some features I would like to see in Firefox (easy deletion of typoed urls from history, thumbnails in search dropdown... although Ubiquity does the latter too) although I think they might have gone overboard with the dropdown boxes for "normal" users (I can see it now: "IE doesn't show me my bookmarks in the address bar lists anymore!" "You must've collapsed that group by accident." "What?"). I am looking forward to the inevitable Firefox extensions to port that functionality.:)
They probably also reply to spam, sign into phishing websites, and unzip encrypted ZIP attachments from untrusted sources. And turn off their AV because it keeps popping up alerts.
I find that a bit weird, since the Windows version doesn't use any Windows-specific APIs that I can see. It looks like a custom-made sliding notification box... which I would expect would already be in the Linux Firefox build! I'm pretty sure the Linux version has those (they appear when downloads finish etc), although I can't remember for sure.
Firefox has a security framework in place which is designed to prevent web pages from being able to manipulate the browser chrome (aka javascript code, UI, etc). So on the firefox level, pages can't access any add-on code to begin with. Up until recently pages could reference scripts or other chrome documents as urls but I believe this has been fixed in Firefox 3. The only possible exploits now would be if ubiquity explicitly registered javascript commands for any web pages to use to interact with ubiquity, and I don't believe there are any (actually ubiquity works exactly the opposite way, the user calls up ubiquity to interact with web page contents, not the other way around).
My understanding of the behind the scenes stuff in Firefox is rudimentary at best, so don't take my word for it. Mozilla has tons of documentation on their site.
Slashdot Mirror
I know that Source engine games by Valve limit themselves to 10kb/s up and down. It's a console variable you can change.
I'm guessing Shockwave. It supports rendering in D3D and OpenGL. There was an FPS made in it once that was pretty fun, you could only play with bots though. It was also time locked so it wouldn't work after a certain date but rewinding your clock to the date it specified worked.
Indexing of HTTPS pages is most certainly a bug. Did the poster of the article report it to make Google Chrome a better product or is he just going to complain? It's only in beta.
And the work around is simple: Use Incognito mode for all sensitive work. Which is what it's for.
Apple ties their OS to their approved hardware. If you want to run the Mac OS, you need an Apple-made computer to run it on. Those computers are also notorious for having few upgrade options.
Of course there are individuals who have hacked Mac's OS to run on any PC... but Apple doesn't like those people for some reason... >_>
You must still be using IE8b1. b2 gets a whopping 21!
Also my Chrome gets 79*, so there!
* - I'm serious, actually. Although test results tend to fluctuate if you have high CPU load elsewhere and/or a speed test just barely passes sometimes.
Fun, I just tried it. Thanks for not making it a link, by the way.
You know I thought they might have done something like that when I read the summary. You can see clear metrics of memory on about:memory in Chrome.
You can block third-party cookies but yeah they need something like NoScript.
For adblocking I'm temporatily using a hosts-based solution until someone makes an Adblock port or something.
Yeah, it's called mplayer for windows. :)
Google Chrome doesn't use the service, you must have installed other Google products. Chrome puts Google Updater in a Scheduled Task.
Also anonymous stats doesn't affect whether the updater runs.
Am I missing something? Press CTRL+H in any browser and you get the exact same thing.
You can change the new tab page URL. Check Options.
Use CTRL+ENTER to never search for whatever you put in the omnibox, and have Chrome assume it's a .com URL.
V8 is also open source. In fact in the webcast just an hour ago one of the V8 devs said they'd love for other browsers to use their engine, or to use their ideas to make a better Javascript engine.
Why does a new process necessarily mean it will use lots of RAM? I have three apps running right now are all using < 100kb of memory each. Two tray apps and some background caching app for TortoiseSVN folder overlay icons.
IMHO, when you do a public release you should take the time to make a proper build, even if it IS a beta. All it takes is clicking a different button (at least in VS Express).
I was just playing on a Team Fortress 2 map marked as an alpha with horrid framerates. The map creator had released it but had not taken the time to optimize VIS*, and my framerate suffered at some parts where it should not have. It was very annoying and as a result I don't like an otherwise good map.
* VIS is a compile process responsible for making sure the game engine does not render more of the map at any point than it needs to, to improve framerates. The VIS compiler, as I understand how it works for both the Q3 and Source/GoldSource engines, splits up a level into logical chunks. The logical separators to these chunks are called VIS portals. The compiler then computes which other chunks the player can see when they are in any specific chunk. In game, the engine uses this to only render the chunks the player can possibly see from the chunk they are in. A map creator can place hint brushes to suggest optimum placement of VIS portals... in this case, a few of those might have helped the compiler to make better choices about chunk placement. The VIS compile stage can be skipped completely (commonly if you want to quickly test a map change) but then the entire level is always rendered. I don't think this particular author made THAT bad of a mistake since I found some areas in the level with good VIS.
Most GUI apps today have to be multithreaded. If there is not a dedicated thread to handle GUI events (IE when the user clicks something) the UI will freeze up whenever the program does something. Occasionally there will be an app that only does small, quick tasks when required, so this isn't an issue cause you can't notice the freezing. But any app that does a large amount of processing or any action that takes longer than a second or so should be using a second thread to do that work, so the UI thread is free (preferably to show the progress of the background task, allow the user to cancel it, etc).
Why the single P? I'm pretty sure it's XAMPP, WAMPP, and LAMPP.
Also I second LAMPP. Since you're already familiar with XAMPP, LAMPP will not take you long to get used to.
I just wanna say for some reason it's more fun than you'd think to run Microsoft/Windows Update inside of Firefox.
1.) IE 8 is still in Beta. I'm sure most folks remember what that means. As in not quite feature complete yet?
Actually the general definition of beta IS feature complete, just not 100% bug fixed.
It's only when you start talking about MS where that changes. If this was Firefox we were talking about, this build would be considered an Alpha build by the Mozilla team.
Here is, IMO, general definitions of common project states:
I'm not sure where "Gamma" fits in there, I think it's the same as an RC.
Here's how Microsoft seems to be doing it, from my own experience in testing Vista, IE8, etc:
Disclaimers: I have used Vista. I got my copy for free through an MS promo and I am not using it. On my computer it is too slow to use without wanting to chuck my CPU out the window. XP is much better. I conclude XP will run better on any computer. Once I get a new CPU I will probably end up using Vista, since it will likely run at a usable speed. IE8 looks pretty nice and actually has some features I would like to see in Firefox (easy deletion of typoed urls from history, thumbnails in search dropdown... although Ubiquity does the latter too) although I think they might have gone overboard with the dropdown boxes for "normal" users (I can see it now: "IE doesn't show me my bookmarks in the address bar lists anymore!" "You must've collapsed that group by accident." "What?"). I am looking forward to the inevitable Firefox extensions to port that functionality. :)
They probably also reply to spam, sign into phishing websites, and unzip encrypted ZIP attachments from untrusted sources. And turn off their AV because it keeps popping up alerts.
Are you sure it isn't? Read what you said carefully... ;)
I always sized the XP/Vista borders down to minimum size using the "Advanced" button, until I found better third-party themes.
I find that a bit weird, since the Windows version doesn't use any Windows-specific APIs that I can see. It looks like a custom-made sliding notification box... which I would expect would already be in the Linux Firefox build! I'm pretty sure the Linux version has those (they appear when downloads finish etc), although I can't remember for sure.
Firefox has a security framework in place which is designed to prevent web pages from being able to manipulate the browser chrome (aka javascript code, UI, etc). So on the firefox level, pages can't access any add-on code to begin with. Up until recently pages could reference scripts or other chrome documents as urls but I believe this has been fixed in Firefox 3. The only possible exploits now would be if ubiquity explicitly registered javascript commands for any web pages to use to interact with ubiquity, and I don't believe there are any (actually ubiquity works exactly the opposite way, the user calls up ubiquity to interact with web page contents, not the other way around).
My understanding of the behind the scenes stuff in Firefox is rudimentary at best, so don't take my word for it. Mozilla has tons of documentation on their site.
Doesn't cooking destroy DNA?