In the context of the discussion, "compilation to native code" means "running against the natice API" rather than in the VM.
eh?
"native code" is an x86 instruction stream. There's no such thing as "the native API", unless you're talking about writing to hardware. Calling kernel32.dll!GlobalAlloc is no more native than new Object. Sure, they do different things, but they're just addresses of code you jump to.
But not quite adequate enough that you could resist one more time, eh?
I don't see that you've said much of anything, especially concerning the original point - CPU instruction pipeline lengths. In fact, most of what you've said has been a reflection of your character. Maybe that's why you've chosen to remain anonymous? Surely your karma rating isn't that important to you?
And this explains the SPEC marks kicking the P4's ass how?
well, it doesn't explain it mainly because i wasn't trying to. i was trying to explain why the clock-for-clock argument is invalid, but there are plenty of other reasons why the two processors are different, the pipeline length is just one of the most significant.
I'm just going to ignore the rest of your rant - I didn't even read it.
You know, I find it pretty interesting how vastly AMD's chips outpace the P4 clock-per-clock.
Not that interesting. The Opteron's pipeline is 40% shorter than the P4's. That's why the P4 can and must run at a higher clock speed to get equivalent performance. The same amount of work is being done, it's just split into different sized chunks of time.
Indeed. For-Pay software vendors will just pass any legislated liability costs on to the customer. I read somewhere that, on average, about 15% of the cost of goods bought in america goes to cover liability insurance. It doesn't make the products any more reliable, it just makes them more expensive, and protects the manufacturer's asses. Oh yeah, and it makes a whole bunch of lawyers filthy rich. Besides, have you read a EULA recently? They usually have a section that says you can't sue the developers for any reason.
I'd say that the FOTR extended edition DVD is one of the best featured DVDs available. Besides the deleted scenes and the four commentary tracks there's the excellent 4-hour making of documentary that I'd say is worth the $30 on its own. And then there's hoards of artwork and an interactive editing thing that's pretty cool.
Yup, that's a good tip. My company bought a new T1 recently and we had to move a whole bunch of new machines over to the new class C. Changing the static addresses and the dynamic ranges in the server's DHCP config meant that all the machines including stubbornly DHCP/BOOTP-only network print adapters could be moved nets by renewing the client leases.
I can't speak to DHCP, BOOTP and DNS servers on linux, but I found the NT DHCP extremely simple to install/configure.
Here's a comparison of Vera Serif/Sans with Times/Verdana on Windows XP with ClearType at 8 & 12 points (96 dpi): vera.gif.
A few things stand out:
vera serif is much bigger than times. it's a bit taller, but it's a whole lot wider.
the kerning (spacing between letters) is bad on the vera fonts. for example, check serif's 'az', 'he', 'um', and sans' 'ox', 'og', 'RO'.
the kerning is inconsistent between font sizes, too. check sans' 'WN'. in the small size they're crammed up against each other and in the larger size they're miles apart.
in the large serif, what happened to the space between 'FOX' and 'JUMPS'?
clipboard handling. RDP supports copy/paste between applications running on different sides of the connection. it's not limited to text, you can copy formatted text, cells from an excel spreadsheet, images, etc... unfortunately you can't drag/drop, and you can't copy files like this.
RDP (mstsc, mira, etc...) has many advantages over VNC (I use both regularly). Here's a few off the top of my head:
it's much more responsive. screen updates are faster. the mouse movement and cursor changes are handled better.
it uses much less bandwidth.
better handling of different bit-depths. whereas VNC just munges the graphics down to a lower bit depth, RDP actually changes the bit depth of the server so applications use the appropriate bitmaps/palettes.
likewise for different screen resolutions. RDP changes the resoution of the server's display to match the requested resolution. you can have a non-scrolling full-screen remote display regardless of the server's default settings.
better keyboard handling. the windows key and combos such as 'ctrl-shift-esc' are not supported on VNC.
RDP supports piping sound back to the remote client, playing sound on the server, or disabling it altogether.
redirection of local devices such as printers, drives and serial ports. these devices become available for use to the applications running on the server.
I'd agree with the 'business-class' HP [rinter choice. We have a couple of the older 4050's and they're reliable and quick. If you're prepared to spend $1,000 you'll never have to buy another printer again.
Slashdot Mirror
How about Control.PreProcessMessage , or Control.DefWndProc ?
System.Decimal ?
"native code" is an x86 instruction stream. There's no such thing as "the native API", unless you're talking about writing to hardware. Calling kernel32.dll!GlobalAlloc is no more native than new Object. Sure, they do different things, but they're just addresses of code you jump to.
I don't see that you've said much of anything, especially concerning the original point - CPU instruction pipeline lengths. In fact, most of what you've said has been a reflection of your character. Maybe that's why you've chosen to remain anonymous? Surely your karma rating isn't that important to you?
You're hillarious. Please, continue...
Oh yeah, and why the AC?
I'm just going to ignore the rest of your rant - I didn't even read it.
Who's going to insure the little guy?
why not use DNS LOC records to get better geographical locations of the browsers?
and both of those are based on bits and bytes.
I think they've just run out of places to look for Osama Bin Laden.
I'd say that the FOTR extended edition DVD is one of the best featured DVDs available. Besides the deleted scenes and the four commentary tracks there's the excellent 4-hour making of documentary that I'd say is worth the $30 on its own. And then there's hoards of artwork and an interactive editing thing that's pretty cool.
what are you saying, that the book predates the nightclub? either that or "I completely ignored the words of the parent article before replying."
I can't speak to DHCP, BOOTP and DNS servers on linux, but I found the NT DHCP extremely simple to install/configure.
Here's a comparison of Vera Serif/Sans with Times/Verdana on Windows XP with ClearType at 8 & 12 points (96 dpi): vera.gif.
A few things stand out:
Windows.Forms is not part of the CLR. It's part of .NET, a superset.
I believe they had a SPARC port at one point, but it never made it into circulation due to opposition from Sun. Surprise, surprise.
I'd agree with the 'business-class' HP [rinter choice. We have a couple of the older 4050's and they're reliable and quick. If you're prepared to spend $1,000 you'll never have to buy another printer again.
that's not what using does. in C# 'using' is used to explicitly call an object's Dispose() method.