Tendo City

Full Version: The new Windows 8 logo...
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
<img src="http://static.arstechnica.net/assets/2012/02/windows-8-logo-4f3ec47-intro-thumb-640xauto-30437.png">

Yay? So yeah, it's not a flag I guess, but why the angle? Actually here's a different contemporary design.

<img src="http://static.arstechnica.net/2012/02/17/windows-1-logo-4f3ec5c-intro.png">

That's snazzy with a flat look, soft curves, friendly monotone color and... oh wait that's not a recent mock up? That's the Windows logo from the 80's for Windows 1.0? Huh...

As to the top one, they paid a top firm to slap that together. Unbelievable... Hey let's see what happens if I take that logo and turn it.. recolor...

<img src="http://img600.imageshack.us/img600/4618/xboxr.jpg">

Bam! New XBox logo. It's an X, it's boxes (or even a gift box wrapped up with ribbon), it's "flat, monotone friendly", it's identifiable. So why doesn't someone get a million for that? Oh right, the main "brand" a brand designer sells is their OWN to justify their existence.
Dark Jaguar Wrote:[Image: windows-8-logo-4f3ec47-intro-thumb-640xauto-30437.png]

Yay?
I think it's a perfect homage to a crappy os.. It's only fitting it have a crappy logo.
Actually it's looking to have some pretty amazing features. I've heard a lot of complaints about "Metro", but honestly I'll just be using desktop anyway so it doesn't affect me. All I ever cared about was underlying tech, not the pretty paint on top. Windows Server 8 in particular is looking pretty amazing.
Dark Jaguar Wrote:Actually it's looking to have some pretty amazing features. I've heard a lot of complaints about "Metro", but honestly I'll just be using desktop anyway so it doesn't affect me. All I ever cared about was underlying tech, not the pretty paint on top. Windows Server 8 in particular is looking pretty amazing.
You want be saying that when you see how the new architecture affects developers.. They did away with .Net and COM and replaced it with 64 bit stupid sticks.
.Net was a great tool, but the biggest problem with it was that in the end it was a layer on top of the low level minicore. The new core of Windows 8 is intended to have the expanded capabilities of .Net built right in, which should be a lot more efficient in the long run. It's a learning curve, but fact is, that's the tech world in a nut shell, one eternal learning curve and then you die.

Also, COM had to go. That thing was even longer in the tooth than the NT minicore.

The plus side of this is that all .NET code will still run in Windows 8. They just will be ending support for it, so developers can still make stuff for it, but for newer features, they'll all need to be learning a new set of skills.
Ya know I take it back. The Windows 1.0 logo wouldn't be contemporary for one reason. The typeface is unacceptably professional. All type faces need to be bland and "friendly" these days. Heck the Windows 8 logo won't fly unless they make that W a w, because poor capitalization is nice!

People don't want professionals they can admire any more. They want unpretentious "equals" that are at their level with all the flaws that come with it. No one wants to look up to anyone any more. They don't want to strain their necks...
Dark Jaguar Wrote:.Net was a great tool, but the biggest problem with it was that in the end it was a layer on top of the low level minicore. The new core of Windows 8 is intended to have the expanded capabilities of .Net built right in, which should be a lot more efficient in the long run. It's a learning curve, but fact is, that's the tech world in a nut shell, one eternal learning curve and then you die.

Also, COM had to go. That thing was even longer in the tooth than the NT minicore.
It's not efficient at all it's built on the same architecture as silver light. So even the simplest tasks will be like shooting yourself in the head. For example did you know that to access the filesystem will require showing a file open or file save dialog first? And any storage space used by the program will be isolated from the rest of the OS. It's going to be a god damn nightmare!
<iframe width="560" height="315" src="http://www.youtube.com/embed/xoKeQeMfN0s" frameborder="0" allowfullscreen></iframe>

Dark Jaguar Wrote:<img src="http://static.arstechnica.net/assets/2012/02/windows-8-logo-4f3ec47-intro-thumb-640xauto-30437.png"> Yay? So yeah, it's not a flag I guess, but why the angle? Actually here's a different contemporary design.
etoven Wrote:It's not efficient at all it's built on the same architecture as silver light. So even the simplest tasks will be like shooting yourself in the head. For example did you know that to access the filesystem will require showing a file open or file save dialog first? And any storage space used by the program will be isolated from the rest of the OS. It's going to be a god damn nightmare!

Oh I see what you're talking about. No don't worry, that was just ONE tool they revealed early on to allow easy porting of web apps and the like. They've since revealed the new low level API that's intended for much more capable "native" code. MS's only mistake was only showing that silverlight styled API early on, confusing a lot of developers. The one you're wanting has been branded WinRT.

http://www.winsupersite.com/article/wind...ime-142196
Dark Jaguar Wrote:Oh I see what you're talking about. No don't worry, that was just ONE tool they revealed early on to allow easy porting of web apps and the like. They've since revealed the new low level API that's intended for much more capable "native" code. MS's only mistake was only showing that silverlight styled API early on, confusing a lot of developers. The one you're wanting has been branded WinRT.

http://www.winsupersite.com/article/wind...ime-142196
I sure hope your right..