[Update: Razer also announced a new version of their 17" Razer Pro series, detailed below.]
Razer have unveiled an ultra-slim, gaming laptop called the Razer Blade. The specs are seriously impressive; a 14" HD screen, a 4th generation Intel processor, and a NVIDIA GeForce 765 graphics processor. That's some serious horsepower for a gaming laptop.
Also included is 8GB of DDR3 - 1600Mhz RAM and 128GB SSD drive, which can be upgraded to either 256GB or 512GB. It's the form factor that's most impressive to me; I really like my Samsung despite it's bulky frame but I do wish I had a more svelte laptop. Considering it's tiny dimensions, it's impressive that Razer have fitted so much in there.
Our esteemed Dale North was really impressed with the 2012 model of the Razer Blade but he realized the price was out of the range of most gamers. Starting at $1,799, the Razer Blade 14" might be a bit more palatable but still out of the range of some gamers. However, it might be the perfect sweet spot between portability and performance.
Razer also announced a new 17" version of the laptop that Dale reviewed last year. Aimed at combining gaming with audio/visual work. The Pro features a touchpad that can be loaded with apps for software like Photoshop, Maya and GIMP. The specs are roughly similar to the 14" Razer Blade, but a much more powerful Intel Processor is installed and as expected the price is higher, starting at $2,299.
Razer Blade 14" features:
Future 4th gen Intel® Core™ processor (formerly codename ‘Haswell’)
Get more destructoid: We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out
Unsavory comments? Please report harassment, spam, and hate speech to our moderators, and flag the user (we will ban users dishing bad karma). Can't see comments? Apps like Avast or browser extensions can cause it. You can fix it by adding *.disqus.com to your whitelists.