What's your take on the name?  

985 members have voted

  1. 1. What's your take on the name?

    • Awesome
      124
    • Alright
      371
    • Horrible
      397
    • Undecided
      93


Recommended Posts

Well I for one think the name is relatively good. Having seen the logo, and the marketing - I think it could work out quite well!

And InsaneKiwi - the GUI is **BETA** Microsoft has already said that we won't see anything near the final GUI until Beta 2, so who cares what it looks like now!

wow some people have a really hard time comprehending that Longhorn was the codename of Windows Vista. The second the name Longhorn was announced it was set that the name will be dropped eventually for the final name.

Same goes for Windows XP's codename Whistler and every other Windows codename for that matter.

To make a long story short: The name Longhorn was never ever meant to be used as the final public name of the next Windows successor.

Vista will grow on you.  Give it time.

For those saying "[H]asta la vista", it's not funny.  Why?  Because that's said "Vee sta", this is said "vi sta" (short i).  So it doesn't make sense.

586257523[/snapback]

Both vistas are the same, with short "i".

Hasta la vista, that's spanish, and that's short :p

so with beta 1, Microsoft will use Vista or going to stay with the name Longhorn until the final version??

586257894[/snapback]

I won't be surprised if the bootscreen and build tag will still say Windows Codename: Longhorn on Beta 1.

Wasn't Windows Codename: Whistler changed to Windows XP on a system level until Beta 2?

so with beta 1, Microsoft will use Vista or going to stay with the name Longhorn until the final version??

586257894[/snapback]

That's a good question that I've been wondering myself. I suspect that Microsoft will stick with Longhorn. I was on the MSDN site and everything over there still refers to Vista as "Longhorn" ... http://msdn.microsoft.com/longhorn. But you never know :ermm:

Vista will grow on you.? Give it time.

For those saying "[H]asta la vista", it's not funny.? Why?? Because that's said "Vee sta", this is said "vi sta" (short i).? So it doesn't make sense.

586257523[/snapback]

So it sounds more like Windows Fisting instead? Damn I just got my heart set to Windows "Veesta&quo:p. :p

That's a good question that I've been wondering myself. I suspect that Microsoft will stick with Longhorn. I was on the MSDN site and everything over there still refers to Vista as "Longhorn" ... http://msdn.microsoft.com/longhorn. But you never know :ermm:

586257999[/snapback]

They will most likely stay with Longhorn, since that is the development name.

Actually Longhorn is the name of a sportsbar at Whistler Blackcomb ski resort ;)

586258219[/snapback]

Though all the characterizations are of Longhorn the animal (which is more commonly known). If I do remember correctly, the MS guy was wearing a cowboy hat before taking it off and putting on a Windows Vista cap.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • TLDR. Here is a far better title (just a basic example): Windows 11 26H2 to allow disabling Web search results
    • Restore will get my vote, only if to see if things are any different, doubt it though but Labour and Conservatives too out of touch and same thing over and over and over…, Lib Dem who?
    • There is nothing wrong with this title. You have completely missed the plot when it comes to "clickbait." The issue was never that a title tries to entice you to click, that is how titles have worked for over 100 years. The issue is when the title subverts expectations, getting you to click expecting something that isn't there. The classic clickbait example is "Boyfriend caught cheating, what happens next will shock you," then what happened next is the girlfriend was upset...which is probably the least shocking outcome imaginable. If sounds like what you want is for the titles to be a collection of 10-word summaries that you can skim, get the just of the story, and only click if you want more details. That is not, never has been, and never will be what titles are. You can go all the way back to print newspapers during the great depression and see the same thing. The newspaper was locked in a vending machine, all you can see is the headline, you choose to put in 5¢ to buy the paper and read the rest if you want. Those headlines were written in a way to sell the paper, not just to provide a summery. Here are two actual headlines from that time, "Wall Street Lays an Egg," or "Stocks Hit Bottom?" Maybe you'd say something like "it was wrong then and it's still wrong now." Okay, fine opinion to have, but it isn't like Neowin is doing something unjurnalistic, they are just following the age-old standards for written media.
    • AMD 26.6.2 driver brings FSR 4.1 support to RDNA 3 RX 7000 series graphics cards by Pulasthi Ariyasinghe A new driver is rolling out to Radeon graphics hardware owners, and alongside support for new games, AMD has just made its FSR 4.1 upscaling tech available to an entire generation of its products. Last month, AMD announced it is answering community requests to bring FSR 4.1 to past generations of its Radeon graphics cards. This would be starting with RDNA 3 RX 7000 products. Right on schedule, this is what's rolling out now with the AMD Software: Adrenalin Edition 26.6.2 driver containing official support for over 300 games. Following this, AMD is planning to bring out RDNA 2 (RX 6000 series) support for FSR 4.1 sometime in early 2027. As for the games, this Adrenalin 26.6.2 driver is a recommended install for anyone jumping into Ubisoft's upcoming Assassin's Creed Black Flag Resynced remake or id Software's DOOM: The Dark Ages' Revelations expansion. The two fixed issues in this release are these: Intermittent application crash or driver timeout may be observed while playing RoadCraft on Radeon™ RX 7000 series products. Purple screen may be displayed when using an HP Reverb G2 headset with SteamVR on Radeon™ RX 6000 series graphics products. The known issues AMD is still working on are the following: Intermittent application crash or driver timeout may be observed while playing Battlefield 6 on AMD Ryzen AI 9 HX 370. AMD is actively working on a resolution with the developer to be released as soon as possible. Texture flickering or corruption may appear while playing Battlefield 6 with AMD Record and Stream on some AMD graphics products. AMD FSR Upscaling and AMD FSR Frame Generation may show as inactive in AMD Software: Adrenalin Edition while playing Battlefield 6 when enabled on Radeon™ RX 9000 series graphics products. Failure to install may be observed while installing AI Bundle components in some regions with limited access to HuggingFace and GitHub. Model flickering or rendering failure may be observed in Maxon Cinema 4D and Blender on Radeon RX 7000 series and above graphics products. Users experiencing this issue are recommended to install AMD Software: Adrenalin Edition 26.3.1. Intermittent application crash may be observed on some models while running Blender on Radeon RX 7000 and above graphics products. Users experiencing this issue are recommended to install AMD Software: Adrenalin Edition 26.3.1. The newly released AMD Software: Adrenalin Edition 26.6.2 driver is now available for download from the AMD Software app. Find the official changelog here.
  • Recent Achievements

    • Dedicated
      tuben earned a badge
      Dedicated
    • Week One Done
      mnsgroup earned a badge
      Week One Done
    • Conversation Starter
      sumytbe earned a badge
      Conversation Starter
    • One Year In
      B4dM1k3 earned a badge
      One Year In
    • One Year In
      DarkWun earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      525
    2. 2
      +Edouard
      199
    3. 3
      PsYcHoKiLLa
      94
    4. 4
      Michael Scrip
      82
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!