It depends where you live, really. Now that I'm here in LA, I very rarely have any trouble with older drivers. They can be annoying, but I've never had a close call with one. Back when I was living in a rural town, however, I had a lot of trouble with older drivers. They'd weave onto my side of the road, pull out with too little room and not accelerate... In general, they were a real hazard.
Chrome is doing more than browsers originally did. It's got a master process that's watching over everything else. The processes are also running at multiple different privilege levels. This may not be something that's absolutely new, but it does show innovation. There's nothing wrong with evolutionary progress. So-called "revolutionary" ideas often end up being less useful.
I find that browsers will crash or hang fairly often if a page is poorly coded or a plugin reacts badly. Unfortunately, people will always make mistakes and there will always be things that are capable of crashing a rendering engine, but if separate processes are used, the effects can be limited to the tab / plugin that cause the problem. This opens up a lot of other potential separations. It would be great if they could separate text-boxes from the tab somehow so that if a tab went to hell, one's Slashdot post needn't go with it. Obviously you're not going to see a separate process for each input, but relegating all user-generated state to a process separate from the rendering engine might be a good idea.
I'm having trouble understanding your argument about sandboxing, but it seems that you're for it. Separate processes greatly increase the degree of security in this case. Malicious coders would have to find a vulnerability in both the browser and the operating system to get around what Google is doing. If sandboxing is implemented in the browser alone, there's no operating system security to step in if there is a vulnerability in the browser.
As for the javascript engine... Yes, Firefox's is faster, but it's also more mature. The architecture for V8 has a lot of potential and who knows what kind of speed increases we'll see after further development. Also, There may be reasons other than speed that make a full javascript virtual machine a good way to go. It's good to have competing solutions which drive innovation.
A.htaccess password would not work well here. In this case, we're talking about authenticating a server, not a user.
Imagine the following:
1. User creates a secure connection to a malicious web site. 2. The compromized web site prompts the user for their credentials, which the user enters. 3. The malicious website now has the users credentials. 4. Depending upon the complexity of the transactions, the malicious site's server could forward the user with credentials to the site and they would be none the wiser. Later, the credentials are downloaded and the attacker can get whatever they want.
Actually, I do a lot of Windows scripting in JScript. WSH may not be the nicest environment in the world, but once you dump VBScript it gets a bit better.
I found Opera Mini to be a complete pain in the butt on my blackberry. You can't type in input fields, for example, it brings up a secondary input dialog, which you have to OK before you go to the next field or hit submit.
It could be argued that due to changes to layers above the physical storage medium, no physical storage solution can currently be considered archival. At this point in time, data needs to be constantly migrated.
Arrogant? I'd say realistic. If an employee is not interested in the job they're doing, they're probably not going to do it very well. There's nothing arrogant about realizing that you're going to hate a certain job and not taking it.
I would have marked it insightful again if I still had mod points. He may be going a little far, but it's absolutely true that the general public in the US doesn't care enough to do anything about it. How do you think we got into this situation in the first place?
You're not entirely on target there. You're required to provide notice when terms of a contract change. They're just allowed to change it if and when they please. Whether the customer reads the notice is a completely different story, however.
Re:Remember when the Internet was like that.
on
Internet2 and You
·
· Score: 1
The difference is that Internet2 has competition in place where the original Internet didn't.
You're drastically overstating the difficulty that is presented. Don't forget, that while all of those parts may come from completely different places and vendors, they're all manufactured according to standardized specifications. I'm not saying that there aren't some inherent problems when you get a large number of manufacturers involved, but don't go overboard with it.
Those sites targeted towards IE probably aren't going to bother with a doctype. Leave those without a doctype rendered in the old way as they have done. What they need to do is update the strict mode to todays standards.
Software comes about when there's a need for it. I don't know about you, but I haven't seen many situations where someone needed to connect Unix / Linux workstations to a Windows server.
I don't think this could really be compared to an ear ring, though. Something being implanted under the skin like that is dealing with different tissue. Percings eventually grow epidermal tissue around the wound. You're right, though, that they don't hurt. I can tug on my lobes and my eyebrow ring pretty hard without any pain at all.
I seen nothing wrong with how Slashdot is handling it. Quoting text response by response is going to fit in one of those two tags depending upon how much text you're quoting.
A) A 3d card is only required for Aero-Glass. You can still use Vista without one. B) Who doesn't have a 3d card in their computer now? C) Having 3d accelerated desktop makes things much nicer. Moving windows without tearing, drop shadows* without slowing things down, new ways of task management (e.g. Expose) etc.
* Drop shadows aren't just for looks. They make it much quicker to figure out the z ordering of windows.
It depends where you live, really. Now that I'm here in LA, I very rarely have any trouble with older drivers. They can be annoying, but I've never had a close call with one. Back when I was living in a rural town, however, I had a lot of trouble with older drivers. They'd weave onto my side of the road, pull out with too little room and not accelerate... In general, they were a real hazard.
Chrome is doing more than browsers originally did. It's got a master process that's watching over everything else. The processes are also running at multiple different privilege levels. This may not be something that's absolutely new, but it does show innovation. There's nothing wrong with evolutionary progress. So-called "revolutionary" ideas often end up being less useful.
I find that browsers will crash or hang fairly often if a page is poorly coded or a plugin reacts badly. Unfortunately, people will always make mistakes and there will always be things that are capable of crashing a rendering engine, but if separate processes are used, the effects can be limited to the tab / plugin that cause the problem. This opens up a lot of other potential separations. It would be great if they could separate text-boxes from the tab somehow so that if a tab went to hell, one's Slashdot post needn't go with it. Obviously you're not going to see a separate process for each input, but relegating all user-generated state to a process separate from the rendering engine might be a good idea.
I'm having trouble understanding your argument about sandboxing, but it seems that you're for it. Separate processes greatly increase the degree of security in this case. Malicious coders would have to find a vulnerability in both the browser and the operating system to get around what Google is doing. If sandboxing is implemented in the browser alone, there's no operating system security to step in if there is a vulnerability in the browser.
As for the javascript engine... Yes, Firefox's is faster, but it's also more mature. The architecture for V8 has a lot of potential and who knows what kind of speed increases we'll see after further development. Also, There may be reasons other than speed that make a full javascript virtual machine a good way to go. It's good to have competing solutions which drive innovation.
OK. We can compare it to FF3 beta, then. That was fast as hell.
A .htaccess password would not work well here. In this case, we're talking about authenticating a server, not a user.
Imagine the following:
1. User creates a secure connection to a malicious web site.
2. The compromized web site prompts the user for their credentials, which the user enters.
3. The malicious website now has the users credentials.
4. Depending upon the complexity of the transactions, the malicious site's server could forward the user with credentials to the site and they would be none the wiser. Later, the credentials are downloaded and the attacker can get whatever they want.
Actually, I do a lot of Windows scripting in JScript. WSH may not be the nicest environment in the world, but once you dump VBScript it gets a bit better.
I found Opera Mini to be a complete pain in the butt on my blackberry. You can't type in input fields, for example, it brings up a secondary input dialog, which you have to OK before you go to the next field or hit submit.
It could be argued that due to changes to layers above the physical storage medium, no physical storage solution can currently be considered archival. At this point in time, data needs to be constantly migrated.
You might want to get that looked at. It could be malignant.
I'm curious... It sounds like you're using MAC filtering. That's not very secure, but it is a pain in the ass. Why not use WPA(2)?
Even when it was, it was very easy to go in and see how everything ticked.
Arrogant? I'd say realistic. If an employee is not interested in the job they're doing, they're probably not going to do it very well. There's nothing arrogant about realizing that you're going to hate a certain job and not taking it.
I would have marked it insightful again if I still had mod points. He may be going a little far, but it's absolutely true that the general public in the US doesn't care enough to do anything about it. How do you think we got into this situation in the first place?
You're not entirely on target there. You're required to provide notice when terms of a contract change. They're just allowed to change it if and when they please. Whether the customer reads the notice is a completely different story, however.
The difference is that Internet2 has competition in place where the original Internet didn't.
We could go back to the good old days of having a console port on everything. Hooray!
You're drastically overstating the difficulty that is presented. Don't forget, that while all of those parts may come from completely different places and vendors, they're all manufactured according to standardized specifications. I'm not saying that there aren't some inherent problems when you get a large number of manufacturers involved, but don't go overboard with it.
Those sites targeted towards IE probably aren't going to bother with a doctype. Leave those without a doctype rendered in the old way as they have done. What they need to do is update the strict mode to todays standards.
I don't want the government any more involved in my internet access than they already are. A non-profit group would be an interesting idea, though.
By that logic wouldn't "Alunium" make more sense?
Software comes about when there's a need for it. I don't know about you, but I haven't seen many situations where someone needed to connect Unix / Linux workstations to a Windows server.
I don't think this could really be compared to an ear ring, though. Something being implanted under the skin like that is dealing with different tissue. Percings eventually grow epidermal tissue around the wound. You're right, though, that they don't hurt. I can tug on my lobes and my eyebrow ring pretty hard without any pain at all.
I seen nothing wrong with how Slashdot is handling it. Quoting text response by response is going to fit in one of those two tags depending upon how much text you're quoting.
Could anyone here give a rough translation of that? I'm curious to know what the law /actually/ reads rather than what the stories say.
A) A 3d card is only required for Aero-Glass. You can still use Vista without one.
B) Who doesn't have a 3d card in their computer now?
C) Having 3d accelerated desktop makes things much nicer. Moving windows without tearing, drop shadows* without slowing things down, new ways of task management (e.g. Expose) etc.
* Drop shadows aren't just for looks. They make it much quicker to figure out the z ordering of windows.
That analogy doesn't really work because copyright isn't a criminal offense in most cases.