Are even session cookies blocked? If they are, thats completely retarded. If session cookies are blocked then many, if not most websites that use any sort of logon functionality are broken, like webmail, internet banking... everything. Using a session ID on the querystring is less secure than using a session cookie, as if someone shares their URL with someone, and that person visits that url before the session expires, then they have (intentionally or not) hijacked the user's session.
Homeworld is pretty similar to what I imagined Ender's game (although its been a while since I read the series)
Re:Introducing a joke you will get sick of quickly
on
The Xbox 360 Unveiled
·
· Score: 1
Yes, the delay in seing textures sometimes is definitely the CD load time. I have an Xbox, and it was very noticeable on GTA3 (LC) if you were driving fast - sometimes whole buildings, and the road would be a plain colour until you were actually on top of them. Then I put a modchip in my xbox, and copied the game to the HD, and the loadtimes are GONE. Going overa bridge to another section of the city involves a load time of about half a second. It what the grandparent poster said about San Andres is true (it asks too much of the current hardware & slows down in places) then I CAN'T WAIT to get it. The xbox has a lot more graphics and CPU power than the ps2 (supercomputer?) so hopefully they use that extra power to take some of the rough edges off, like they did with Vice City.
Here in NZ games are rated by the office of film and literature classification in exactly the same way as movies. This seems perfectly sensible to me.
GTA: Vice City has an R18 rating here. Fair enough, its an adults game, not a kids game.
Why are the publishers against this law? I would have thought it would have given them some protection: When some idiot kid shoots someone, and hoards of drooling ambulance-chasing lawyers start scream "GTA trained them to be killers! Rockstar are responsible!! they must PAY!!!" Then the publisher can turn around and say what were they doing playing the game in the first place?
I played Vice City right though, and loved it, but I certainly wouldn't want my kids playing it, and I'm not too comfortable with someone elses kids playing it either.
Normally I hate trolls, but thats the best trollage I've ever seen. Nice one, had me going until I saw your posting history.
Re:One problem I've hit with skype is...
on
John Dvorak Hypes Skype
·
· Score: 2, Informative
Yeah, sound quality is definitely much better than telephone.
I tried it to call friends in London, and it is pretty good, but a local call has WORSE latency than a call to europe, as each packet goes to europe and back again, instead of just once.
How it chooses the proxy to use if you're behind a firewall and can't accept incoming connections.
I'm in New Zealand, and when me & a friend in another part of NZ tried out skype, the connection was routed via another skype user in germany.
Some background: NZ is pretty much at the arse-end of the world, and national network traffic is very fast and reliable, but if you go out to the rest of the world you add in about 150 ms latency, each way.
Connections to europe are even worse, as the connection typically goes from NZ to the US west coast, then to the east coast, and then to europe. And back. Although our network infrastructure here is very good, international bandwidth is expensive, so broadband connections have a monthly traffic limit, of 1-10gb per month, depending on your provider and plan. One bonus of the provider I use is only 1/10th of your national traffic counts towards your bandwidth allowance.
So here I was, thinking the voice quality is pretty good, but there were a few glitches (probably dropped packets etc), but there was a latency of close to one second, and this local call was using my precious international bandwidth. Other calls had similar results - the quality is basically hamstrung into the worst case scenario.
Skype is very good in that It Just Works, but its almost completely devoid of any configuration or logging that tells you what its doing behind the scenes. My router supports uPNP, but sykye didn't even seem to be making use of that to route calls directly to me.
Has anyone in NZ had similar results? Have these problems been improved since I last looked?
There is significant evidence that NT 3.1 (and later) Windows 32-bit APIs were influenced by OS/2 's design.
WinNT's design was infact heavily influenced by VMS. Dave Cuter, VMS's architect at Digital was hired by MS to work on the design of NT. This article has more details, its a good read
Also, a lot of that 25 mb is shared libraries (i.e. the.Net runtime, GDI+) that are loaded once, and shared by each process that needs them, but their memory is included in each process that is using them
This page has a fairly good overview of how windows measures memory usage
R.I.P. COM, and good riddance!.Net has it all over VB6 and COM. I must have spent months of time solving COM related problems..Net allows people to write apps with (nearly) the performance and (nearly) the power of C++, with (nearly) the ease of programming in VB6. Microsoft really have hit the sweet spot with this one. It just works... no more COM funkiness where you don't really know what is going wrong and have to reboot to make something work.
I hope large parts of windows are re-written in.Net. C++ definitely has its place, but lets be realistic, 95% of software that is written in C++ doesn't need the performance and power C++ gives you, and when you factor in the difficulty of writting bug-free software in C++, the switch to.Net is a no-brainer.
Its fairly well established now that developing in.Net is at least 50% more productive than writing in VB6 or VC++, and I'd wager that the bug counts would be at least 50% lower too.
Because windows uses a large disk cache, if a page is swapped out to disk it isn't actually flushed from memory straight away - its still in cache.
If the app that owns that page wants it back within a few seconds of it being taken out of its working set then the page is taken out of the disk cache - very efficent.
Obviously it depends on what the system is doing, but very often a large % of your disk cache (system cache in task manager) is going to be holding virtual memory pages that haven't been written to your swapfile.
Back in the days of 8086 and earlier, CISC designs like the 8086 had complex instructions that did a lot of work, and some took upwards of 30 clock cycles to execute.
When RISC archetectures came along with their "one instruction per clock cycle" approach and kicked x86 of the day over the park Intel started putting a RISC back-end on their CPUs that decoded the x86 instructions to multiple RISC-like microcode instructions, and executed more than one microcode instruction per clock cycle.
These days many most x86 instructions are executed in one clock cycle. In spite of all its problems, x86 now has the best of both worlds now (cisc and risc), which is why it has survived.
As the grandparent post said, MHZ != performance. A good analogy tell computer illiterate people is MHZ is kinda like the RPM an engine will do. Higher RPM doesn't necessarily mean higher speed.
Also, its a RISC design. it may well do LESS in each clock cycle than x86.
And aren't we close to the theoretical limit transistors can switch at? If the cell processor starts at such a high clock rate it won't have as much headroom for improvement.
Its a decompiler for.net, and it spits out very good code, complete with the original variable names as long as the code hasn't been run through an obsfcurator.
Its very cool, load up a dll and browse the classes and decompile into vb or c# on the fly...
Nope, wrong. Task manager reports working set, which is whatever memory windows THINKS the process is using at the moment.
Reporting the total memory allocated by an app is meaningless, because much of that memory includes things like memory-mapping DLLs that are only loaded once, and shared amongst all processes using them.
Windows constantly trims pages from the working set of each process that haven't been accessed in a while and pages these out to disk.
When you click the minimize button windows assumes that the app (or at least large parts of it) are going to be inactive for a while, so it tries to remove as many pages from the working set as possible - hugely reducing the "memory usage" reported in task manager. Sometimes it is a little too agressive in trimming pages from the working set, and the "memory usage" immediately climbs a little again, as the app accesses memory pages that windows thought it could page out.
Try it with an app like MS Word that has background threads that constantly check spelling and stuff, and you'll see the working set goes up for a few seconds after you minimize it.
Slashdot Mirror
Are even session cookies blocked? If they are, thats completely retarded.
If session cookies are blocked then many, if not most websites that use any sort of logon functionality are broken, like webmail, internet banking... everything.
Using a session ID on the querystring is less secure than using a session cookie, as if someone shares their URL with someone, and that person visits that url before the session expires, then they have (intentionally or not) hijacked the user's session.
Did you know that helecopters can't really fly?
They are just so ugly that the ground repels them.
Yeah, is /. fucking up, or are asshats posting random posts from other threads here?
/. screwing the pooch.
My money is on
Homeworld is pretty similar to what I imagined Ender's game (although its been a while since I read the series)
Yes, the delay in seing textures sometimes is definitely the CD load time. I have an Xbox, and it was very noticeable on GTA3 (LC) if you were driving fast - sometimes whole buildings, and the road would be a plain colour until you were actually on top of them.
Then I put a modchip in my xbox, and copied the game to the HD, and the loadtimes are GONE. Going overa bridge to another section of the city involves a load time of about half a second.
It what the grandparent poster said about San Andres is true (it asks too much of the current hardware & slows down in places) then I CAN'T WAIT to get it. The xbox has a lot more graphics and CPU power than the ps2 (supercomputer?) so hopefully they use that extra power to take some of the rough edges off, like they did with Vice City.
Ok, you got me there :)
windows is 64 bit now as well.
XP and 9x are about as similar as XP and linux. Actually, XP and linux are a lot more similar, as they are both 32bit pre-emptive multitasking OS's.
9x is a pile of dirty hacks running on top of ms-dos its quite surprising it runs as well as it does.
Here in NZ games are rated by the office of film and literature classification in exactly the same way as movies. This seems perfectly sensible to me.
GTA: Vice City has an R18 rating here. Fair enough, its an adults game, not a kids game.
Why are the publishers against this law? I would have thought it would have given them some protection: When some idiot kid shoots someone, and hoards of drooling ambulance-chasing lawyers start scream "GTA trained them to be killers! Rockstar are responsible!! they must PAY!!!" Then the publisher can turn around and say what were they doing playing the game in the first place?
I played Vice City right though, and loved it, but I certainly wouldn't want my kids playing it, and I'm not too comfortable with someone elses kids playing it either.
It seems perfectly straightfoward to me.
HAHAA!!
Normally I hate trolls, but thats the best trollage I've ever seen. Nice one, had me going until I saw your posting history.
Yeah, sound quality is definitely much better than telephone.
I tried it to call friends in London, and it is pretty good, but a local call has WORSE latency than a call to europe, as each packet goes to europe and back again, instead of just once.
How it chooses the proxy to use if you're behind a firewall and can't accept incoming connections.
I'm in New Zealand, and when me & a friend in another part of NZ tried out skype, the connection was routed via another skype user in germany.
Some background: NZ is pretty much at the arse-end of the world, and national network traffic is very fast and reliable, but if you go out to the rest of the world you add in about 150 ms latency, each way.
Connections to europe are even worse, as the connection typically goes from NZ to the US west coast, then to the east coast, and then to europe. And back.
Although our network infrastructure here is very good, international bandwidth is expensive, so broadband connections have a monthly traffic limit, of 1-10gb per month, depending on your provider and plan. One bonus of the provider I use is only 1/10th of your national traffic counts towards your bandwidth allowance.
So here I was, thinking the voice quality is pretty good, but there were a few glitches (probably dropped packets etc), but there was a latency of close to one second, and this local call was using my precious international bandwidth. Other calls had similar results - the quality is basically hamstrung into the worst case scenario.
Skype is very good in that It Just Works, but its almost completely devoid of any configuration or logging that tells you what its doing behind the scenes. My router supports uPNP, but sykye didn't even seem to be making use of that to route calls directly to me.
Has anyone in NZ had similar results? Have these problems been improved since I last looked?
WinNT's design was infact heavily influenced by VMS. Dave Cuter, VMS's architect at Digital was hired by MS to work on the design of NT.
This article has more details, its a good read
Hmm you're clearly not using enough XML
Yeah, a 16ms is borderline for hardcore gaming. 12ms is certainly fast enough for me. But an 8ms LCD has TWICE as many frames per second.
8ms LCDs are common now, and check this out: 4ms lcds are on the way.
.008 seconds
8 ms =
1/.008 = 125 refreshes a second.
There is no way you can see the refresh rate at 125hz, and even less of a chance at 250 hz (4ms)
Also, a lot of that 25 mb is shared libraries (i.e. the .Net runtime, GDI+) that are loaded once, and shared by each process that needs them, but their memory is included in each process that is using them
This page has a fairly good overview of how windows measures memory usage
R.I.P. COM, and good riddance! .Net has it all over VB6 and COM. I must have spent months of time solving COM related problems. .Net allows people to write apps with (nearly) the performance and (nearly) the power of C++, with (nearly) the ease of programming in VB6. Microsoft really have hit the sweet spot with this one. It just works... no more COM funkiness where you don't really know what is going wrong and have to reboot to make something work.
.Net. C++ definitely has its place, but lets be realistic, 95% of software that is written in C++ doesn't need the performance and power C++ gives you, and when you factor in the difficulty of writting bug-free software in C++, the switch to .Net is a no-brainer.
.Net is at least 50% more productive than writing in VB6 or VC++, and I'd wager that the bug counts would be at least 50% lower too.
I hope large parts of windows are re-written in
Its fairly well established now that developing in
Nice link... kinda blows the whole thing out of the water.
I'd mod you up but I don't have points. Hopefully a moderater will notice your post
Because windows uses a large disk cache, if a page is swapped out to disk it isn't actually flushed from memory straight away - its still in cache.
If the app that owns that page wants it back within a few seconds of it being taken out of its working set then the page is taken out of the disk cache - very efficent.
Obviously it depends on what the system is doing, but very often a large % of your disk cache (system cache in task manager) is going to be holding virtual memory pages that haven't been written to your swapfile.
glad I could help
Once that was true, not any more.
Back in the days of 8086 and earlier, CISC designs like the 8086 had complex instructions that did a lot of work, and some took upwards of 30 clock cycles to execute.
When RISC archetectures came along with their "one instruction per clock cycle" approach and kicked x86 of the day over the park Intel started putting a RISC back-end on their CPUs that decoded the x86 instructions to multiple RISC-like microcode instructions, and executed more than one microcode instruction per clock cycle.
These days many most x86 instructions are executed in one clock cycle. In spite of all its problems, x86 now has the best of both worlds now (cisc and risc), which is why it has survived.
As the grandparent post said, MHZ != performance.
A good analogy tell computer illiterate people is MHZ is kinda like the RPM an engine will do. Higher RPM doesn't necessarily mean higher speed.
Also, its a RISC design. it may well do LESS in each clock cycle than x86.
And aren't we close to the theoretical limit transistors can switch at? If the cell processor starts at such a high clock rate it won't have as much headroom for improvement.
Try out Lutz Roeder's Reflector.
.net, and it spits out very good code, complete with the original variable names as long as the code hasn't been run through an obsfcurator.
Its a decompiler for
Its very cool, load up a dll and browse the classes and decompile into vb or c# on the fly...
Nope, rotor (microsoft's open-source version of the .net framework, builds on windows, bsd and osx) doesn't include any windows forms.
.net - primarily the JIT and GC.
Also, there are substantial differences between rotor and the full ver of
Nope, wrong. Task manager reports working set, which is whatever memory windows THINKS the process is using at the moment.
Reporting the total memory allocated by an app is meaningless, because much of that memory includes things like memory-mapping DLLs that are only loaded once, and shared amongst all processes using them.
Windows constantly trims pages from the working set of each process that haven't been accessed in a while and pages these out to disk.
When you click the minimize button windows assumes that the app (or at least large parts of it) are going to be inactive for a while, so it tries to remove as many pages from the working set as possible - hugely reducing the "memory usage" reported in task manager. Sometimes it is a little too agressive in trimming pages from the working set, and the "memory usage" immediately climbs a little again, as the app accesses memory pages that windows thought it could page out.
Try it with an app like MS Word that has background threads that constantly check spelling and stuff, and you'll see the working set goes up for a few seconds after you minimize it.