Is the GeForce 8800 GTS 512MB used in the review any good? It could only muster 18 fps on Crysis at only 1280x1024, regardless of CPU. Isn't that game about a year old? Interesting that the most graphics-hungry game would be two years ahead of the hardware (because 18fps doesn't cut it).
I would say it is. I think the Crysis developers just didn't bother spending any time optimizing.
It's easy to understand "Core" vs "Core 2" (2nd version of Core), and "Solo", "Duo", "Quad" (number of cores).
Actually, it's not. The Core Duo is not based on the Core microarchitecture, the Core Duo is just 2 Pentium-Ms fused together and does not include 64-bit support. The Core 2 Duo is the first CPU to use the Core microarchitecture and includes 64-bit support.
Don't forget that the first Intel Quad didn't actually include Quad in the name, either. It was called the Core 2 Extreme QX6700.
Someone needs to do the same for nvidia graphics cards...
I went out and bought an 8600 card, only to find out later that a 7900 is actually faster (despite being lower model number and previous generation tech).
Yeah, the lower end 8 series cards are real dogs. I wouldn't bother with any 8 series card under an 8800 GS/GT/GTS/GTX, as you pointed out, the 7 series cards are faster.
Ever try reading in and storing an arbitrary length string? I'm fairly convinced it's not possible in Ada.
It's not possible anywhere, unless you have access to an arbitrary size memory. Ada simply makes you aware of that fact before you put the code into production.
I'm not saying it has to be in a single step, indeed to do it safely will often require multiple steps. However, Ada doesn't seem capable of either.
The icing on the case was that if you do a get(foo), where foo is a fixed length string, it will read exactly the length of the string, hanging if there's not enough input and stopping part of the way through the input if there's too much. It might be possible to work around that by reading a single character at a time into a character and then repeatedly appending the character to a string which you could theoretically resize. However, IIRC, resizing the string, casting a character to a string, and appending to a string are all extremely painful or impossible.
Well, that and Ada's I/O is pretty terrible. Ever try reading in and storing an arbitrary length string? I'm fairly convinced it's not possible in Ada.
Yeah, but at 6 bits per pixel, you may as well kill yourself.
Um, all laptops use 6-bit panels. As do 95% of Windows-based desktops. That was the most stupid non-story ever...
Almost, but not quite. ThinkPads advertised with "FlexView" screens have full 8-bit per channel IPS panels. They are difficult to find now, however, apparently there's no suppliers left.
As for desktop LCDs, pretty much any screen under $500 now is going to use a trashy TN panel (and many of the ones above $500 too now, apparently). Personally, I'll be sticking with my 2x 20" 1600x1200 PVA panels (desktop) and 1x 15" 1400x1050 IPS panel (laptop) for the forseeable future.
My point is that you can scroll anywhere on the trackpad, just by using two fingers.
You don't have to use a special area nor do you have to move the mouse cursor to the scroll bar.
You can scroll in any direction, not just vertically or horizontally.
I do that too, except with just one finger.
Any useful laptop comes with both a nipple and a touchpad. The touchpad is of course useless for mousing, so you turn the entire touchpad into a scrolling device. Thus, you can mouse with the nipple, and scroll with your thumb on the touchpad, all without taking your hands off the home row!
You jest, no? It's the worst pointing device in the world and achieves nothing but getting in the way of the surrounding keys. Thankfully they can be removed. Each to their own, I guess.
On the contrary, any laptop that doesn't have a nipple is worthless trash. Touchpads are terribly inefficient for mousing.
Yes, the Thinkpad T series had IPS displays as an option even just a year ago, they were advertised as "FlexView". I own a T60 with a 15" 1400x1050 IPS display, and it's quite nice. As of today, it seems you can't get useful screens with a T60/T61 anymore, they're all widescreen TN panels (gross!). I guess I'll be holding on to that T60 for quite awhile...
You're confusing different things, like the pixel clock and the refresh rate. From my Xorg.0.log:
(--) NVIDIA(0): LEN L201p (DFP-0): 330.0 MHz maximum pixel clock (--) NVIDIA(0): LEN L201p (DFP-0): Internal Dual Link TMDS
That monitor still runs at 60 Hz though (via dual link DVI). The pixel clock controls link bandwidth, a lower resolution will require a lower pixel clock, but will still run at the same refresh rate.
You can run monitors at an arbitrary refresh rate over any link, but there really aren't any LCDs capable of more than 60 Hz (or possibly 75 Hz). Many CRTs can do 640x480 at 200 Hz or so, but few (if any) can do 1600x1200 at more than 75 Hz.
So, the link isn't the bottleneck, the monitor is. Although you'll be restricted to smaller resolutions if you use higher refresh rates.
Keep in mind that the response time numbers posted for TN monitors almost never reflect what'll be seen in real world usage. Manufacturers spend an enormous amount of time getting their monitors to cheat on the response time tests, as that number is what most consumers look at, despite the fact anything below (a real response time of) 16 ms really doesn't matter for a 60 Hz signal.
FWIW, both of my Lenovo L201p LCDs have 16 ms PVA panels, and even when specifically looking for ghosting I don't notice any.
I think the GP is referring to the kind of regular expressions you'd cover in a finite automata course (which I tend to refer to as "fake regular expressions", since I learned regex first...), not anything you'd actually ever implement in a library or programming language.
I read Mastering Regular Expressions, cover to, cover. I find that it started off very easily and even having no Regex knowledge outside of using *.* on the command line...
Actually, that's globbing that the shell does for you, not regex.
Slashdot Mirror
No, it really is written in Eclipse (although not necessarily using Eclipse).
Well, that depends on how many bugs you count for Windows... http://dell.com/open/
Instead of checking if $CURRDIL exists (and possibly removing it) before linking it, why not just add the -f option to ln?
I grab the filename and extension with this regular expression: /\/comics\/dilbert\/archive(\/images\/dilbert.*?)\.(gif|jpg|jpeg)/i
You could make that more readable by using a different regex delimiter, like so:
You might try typing the address correctly next time... s/oops/oop/g;
I would say it is. I think the Crysis developers just didn't bother spending any time optimizing.
Actually, it's not. The Core Duo is not based on the Core microarchitecture, the Core Duo is just 2 Pentium-Ms fused together and does not include 64-bit support. The Core 2 Duo is the first CPU to use the Core microarchitecture and includes 64-bit support.
Don't forget that the first Intel Quad didn't actually include Quad in the name, either. It was called the Core 2 Extreme QX6700.
Yeah, the lower end 8 series cards are real dogs. I wouldn't bother with any 8 series card under an 8800 GS/GT/GTS/GTX, as you pointed out, the 7 series cards are faster.
In the same way that a turned off and unplugged computer is very secure from network attacks.
I'm not saying it has to be in a single step, indeed to do it safely will often require multiple steps. However, Ada doesn't seem capable of either.
The icing on the case was that if you do a get(foo), where foo is a fixed length string, it will read exactly the length of the string, hanging if there's not enough input and stopping part of the way through the input if there's too much. It might be possible to work around that by reading a single character at a time into a character and then repeatedly appending the character to a string which you could theoretically resize. However, IIRC, resizing the string, casting a character to a string, and appending to a string are all extremely painful or impossible.
Well, that and Ada's I/O is pretty terrible. Ever try reading in and storing an arbitrary length string? I'm fairly convinced it's not possible in Ada.
You say that as if it's a bad thing.
Linux = $0
OpenOffice.org = $0
Konqueror/Firefox = $0
etc
I could go on, but you get the point. The preloaded OS is completely irrelevant because both will just run Linux anyways.
My point being that it's basically the same either way, except that Macs don't come with useful pointing devices. Period.
There, fixed that for you.
Almost, but not quite. ThinkPads advertised with "FlexView" screens have full 8-bit per channel IPS panels. They are difficult to find now, however, apparently there's no suppliers left.
As for desktop LCDs, pretty much any screen under $500 now is going to use a trashy TN panel (and many of the ones above $500 too now, apparently). Personally, I'll be sticking with my 2x 20" 1600x1200 PVA panels (desktop) and 1x 15" 1400x1050 IPS panel (laptop) for the forseeable future.
You don't have to use a special area nor do you have to move the mouse cursor to the scroll bar.
You can scroll in any direction, not just vertically or horizontally.
I do that too, except with just one finger.
Any useful laptop comes with both a nipple and a touchpad. The touchpad is of course useless for mousing, so you turn the entire touchpad into a scrolling device. Thus, you can mouse with the nipple, and scroll with your thumb on the touchpad, all without taking your hands off the home row!
On the contrary, any laptop that doesn't have a nipple is worthless trash. Touchpads are terribly inefficient for mousing.
RAID 20? I don't think that exists. Perhaps you meant RAID 50 or RAID 60...
Yes, the Thinkpad T series had IPS displays as an option even just a year ago, they were advertised as "FlexView". I own a T60 with a 15" 1400x1050 IPS display, and it's quite nice. As of today, it seems you can't get useful screens with a T60/T61 anymore, they're all widescreen TN panels (gross!). I guess I'll be holding on to that T60 for quite awhile...
You're confusing different things, like the pixel clock and the refresh rate. From my Xorg.0.log:
That monitor still runs at 60 Hz though (via dual link DVI). The pixel clock controls link bandwidth, a lower resolution will require a lower pixel clock, but will still run at the same refresh rate.
You can run monitors at an arbitrary refresh rate over any link, but there really aren't any LCDs capable of more than 60 Hz (or possibly 75 Hz). Many CRTs can do 640x480 at 200 Hz or so, but few (if any) can do 1600x1200 at more than 75 Hz.
So, the link isn't the bottleneck, the monitor is. Although you'll be restricted to smaller resolutions if you use higher refresh rates.
Keep in mind that the response time numbers posted for TN monitors almost never reflect what'll be seen in real world usage. Manufacturers spend an enormous amount of time getting their monitors to cheat on the response time tests, as that number is what most consumers look at, despite the fact anything below (a real response time of) 16 ms really doesn't matter for a 60 Hz signal.
FWIW, both of my Lenovo L201p LCDs have 16 ms PVA panels, and even when specifically looking for ghosting I don't notice any.
I don't think the (small) boost in prettiness justifies the (enormous!) drop in performance. There's lots of pretty games out that are much faster.
Wouldn't surprise me if it's true. Insurance is the biggest scam of all time, that it's mandatory for driving doesn't help either.
I was with you up until here, but I think you're wrong on that point. More likely is that Crysis is just poorly optimized.
I think the GP is referring to the kind of regular expressions you'd cover in a finite automata course (which I tend to refer to as "fake regular expressions", since I learned regex first...), not anything you'd actually ever implement in a library or programming language.
Actually, that's globbing that the shell does for you, not regex.