Recommended Posts

that mini tile idea is crap!...

why do u need to show what the startscreen looks like?

also.

u have it in charms. why do u need it anywhere else? pointless.

it feels similar to the thumbnail you get in DP when cursor is near left edge (where it shows preview of prev/next app)

I don't expect many desktop side UI changes at this point tbh. I think the bigger molding of metro and the "desktop" will happen in Win9 after more people get use to the new UI/start screen.

I really believe that what we think of as the desktop is just going to turn into a part of the UI where you can manage/work with lots of apps together like now of course but even future WinRT apps not just older Win32 apps like we're getting in Win8. I don't expect a split between the two sections come Win9.

I also expect the next thing to go will be the systray in favor of a new notification area in the UI that will slide into view from the side or the bottom etc. Then the last part will be the taskbar itself.

brilliantly written post! :)

do read it. Very informative.

Im thinking that Steven talked alot about new devices coming from AMD and Intel. Im very excited. I want a x86 tablet and if the AMD low power PCs can give me the performance, battery life, slim and light design, they can have my money! :)

brilliantly written post! :)

do read it. Very informative.

Im thinking that Steven talked alot about new devices coming from AMD and Intel. Im very excited. I want a x86 tablet and if the AMD low power PCs can give me the performance, battery life, slim and light design, they can have my money! :)

And it also clears up some misperceptions (even mine) on why the multi-API support on Windows 8 outside of ARM exists.

I have called Immersive on x86/x64 a *superset* UI; apparently, I was severely underestimating the case.

Windows 8 on x86/64 is a *superset OS* - basically WOA-plus.

The blog post (and the video) point out that WinRT is, by design, CPU-neutral (which Win32 isn't). Writing to the WinRT API means that as long as the API support is there, the application will work. However, WinRT, with it being primarily designed for lightweight-power-miserly architectures (such as Ultrabooks and ARM) means that it isn't suitable for the heavier applications (such as Outlook or even Photoshop or Acrobat Professional). With WinRT, the CPU isn't relevant.

However, some heavier-duty productivity applications, existing games, existing applications, are simply unsuitable for WinRT. (Outlook. Acrobat Professional. The full version of Photoshop. MMORPGs - even the F2P sort. Etc.) Therefore, Win32 still has a place. That's where everything from higher-end tablets and slates (such as SAMSUNG's existing SERIES 7) to traditional desktops, notebooks, etc. and the Win32 API come in. There are times that a ball-peen hammer simply won't do.

However, here's where the big change from previous versions of niche-targeted Windows (WinMo and TPC Edition in particular) comes in - the learning curve goes away - completely. You still have the jackhammer - or even the sledgehammer - in your arsenal.

Yes - it's not what we're used to. (It's also not what Apple - or even Google - wants.)

Whoever would have thought that "Think different." (the old Apple slogan) could ever apply to Microsoft?

Everyone of these screenshots over the last couple of pages give me orgasms.

So excited for Gmail and calendar integration.

The Google Calendar integration is nice. The Gmail support isn't surprising in the least (mainly because Outlook has supported Gmail since it began, and added IMAP4 auto-configuration of Gmail accounts across all of Outlook two years back). I'm hoping that I can actually use Google Calendar with Outlook in Windows 8 (either the Consumer Preview or the finished product) without requiring an upgraded version of Office.

Interesting trivia courtesy of Long...

Photo EXIF evidence points to Windows on ARM before iPad release

Turns out Microsoft has been working on Windows on ARM for a while, quite a while in fact.

In Steven Sinofsky?s thesis of Windows on ARM (generically dubbed WOA) published on the Building Windows 8 blog today, two photographs of an early development build of Windows running on prototype ARM hardware dates the effort to as far back as 22 January 2010, almost a week before iPad?s announcement on the 27th.

Although Microsoft waited almost a year later to reveal WOA for the first time in public at a CES 2011 press conference, it?s now clear Microsoft too had future bets on an ARM-based ecosystem even before the iPad began selling and ARM took the spotlight for tablet devices.

As one might gather from Steven?s insight into the ARM development process, it became a lot more complicated to optimize the Windows experience on ARM than just porting all the code from one architecture than another. I think the dated photographs also reaffirm just how big of an investment this has been already with two years of development already in the bag.

Although no one can deny the influence the iPad has had and continues to have on Windows, Windows 8 is looking to level the playing field on ARM hardware with a vengeance. It?s safe to say WOA is not a knee-jerk reaction to the iPad, but a strategic move planned much earlier. But of course like most things Microsoft, with a longer lead time to market.

The NT kernel has been portable since the times of NT 3.x in the early 1990s. NT 3.51 and NT 4.0 ran on four different CPU architectures: x86, MIPS, DEC Alpha, PowerPC.

I'm pretty sure MS had an ARM build of NT running in their labs for years, just like Apple had x86 builds of all versions of Mac OS X running in their labs before the switch.

Long Zheng's findings are nice, but not earth shattering.

The NT kernel has been portable since the times of NT 3.x in the early 1990s. NT 3.51 and NT 4.0 ran on four different CPU architectures: x86, MIPS, DEC Alpha, PowerPC.

I'm pretty sure MS had an ARM build of NT running in their labs for years, just like Apple had x86 builds of all versions of Mac OS X running in their labs before the switch.

Long Zheng's findings are nice, but not earth shattering.

Well, I did say it's just trivia :)

OK, I requested canouna to try to dl Classic Shell and see if it could install and run in the beta build he has on hand, and here's the report:

http://forums.mydigitallife.info/threads/31998-Windows-8-Consumer-Preview-Discussion/page4?p=544698&viewfull=1#post544698

image_186.jpg

:s

This topic is now closed to further replies.
  • Posts

    • VS Code 1.123 introduces massive upgrades for persistent AI developer workflows by Paul Hill Microsoft has just released Visual Studio Code 1.123 alongside its annual developer conference, Build 2026. This release, as always, has a heavy focus on advanced AI agent integration and making the built-in browser more robust. Notably, this update brings big sync changes that keep your AI agents persistent across sessions. With this update, VS Code now supports cross-machine syncing for chat histories, touched files, repository contexts, and related PRs via GitHub accounts, tying users even more into Microsoft’s developer ecosystem. This update also introduces the new /chronicle command that allows you to query past sessions using natural language, generate instant standup reports, and get personal productivity insights. Microsoft has also made some improvements to network-dependent operations, it explains: “When a terminal command that is run by a local agent requires access to domains that are not configured as allowed domains, the command is automatically retried inside the sandbox with unrestricted network access. After that, if it still fails, it falls back to unsandboxed execution. This allows network-dependent operations such as git fetch to finish, while keeping filesystem protections in place.” Microsoft has not stopped there; in this update, it also allows developers to drag, drop, and pin multiple agent sessions side-by-side for easy code comparisons in real-time. It also introduces the Research Agent, accessible via /research. This is a read-only, depth-optimized tool that gets data from the web, local codebase, and GitHub to give you a Markdown report on complex APIs or unfamiliar code. Now, let’s talk about the integrated browser and some security enhancements. VS Code 1.123 features enhanced screenshot capture tools that allow for targeted Area Screenshots and Full Page Screenshots to send layout context instantly to AI chat. The address bar has also been revamped, supporting favorite pages and tab management. Finally, on the security front, this update introduces a safety-first two-hour delay on third-party extension auto-updates to safeguard against compromised or buggy releases. This release is now available for Windows, Mac, and Linux. If you have VS Code, keep an eye out for the update availability notification. If you still don’t have VS Code, you can get it here.
    • I'm hoping with the Surface Pro 12, I can use either USB-C for my Xreal One Pro glasses. With my Surface Pro 11 OLED X Elite, I have to plug them into the top port. The bottom port will power it, but nothing shows on the screen. Maybe it's my setting. When I plug in the glasses, I have it output only to the glasses. So maybe I need to turn on both displays with it in the top port, then switch the glasses to the bottom port and set it to output only to the glasses. And then hopefully Windows remembers the settings for either the top port and bottom port (one of the awesome features of Windows where it remembers the exact configuration when plugging in external monitors.
    • Forgive my ignorance, but the only difference I see here is that a USB-A is now a USB-C, so there are two of them. For the modern age (and I'd argue since 2020), most products would now come with USB-C as an option, if not the default. Display, charging, devices, etc on TWO connectors, sometimes all combined! So having 2 of those powerful ports is great for something this size! Meanwhile my Surface Pro (5) has a single USB-A port which I cannot even get display out to, instead relying on some Surface Connect dock which I don't have. That is a poor experience, not to mention expensive and not compatible with other devices. Thank God USB-C is mainstream!
    • wow. that color finally comes to Surface Pro. was always a little jelly when a friend had the sandstone Surface Laptop. I wonder how different this dune is from the sandstone. I'll be getting the dune version. always thought black and platinum were a little boring. I'll still have access to my blue Surface Pro 11 as it'll be a hand-me-down.
    • Looks a very subjective aren't they!? I like its simple design. I love the way Apple designs their products with function over form, minimalization, and simplicity over cluttered complex designs. Many, not all, of their products follow this trend, and the device becomes a tool rather than dominating the space. I do not however like their OS. I have never bought a Apple product, and while I'd consider the Neo for my wife, I am hoping there are better alternatives out there when her failing MacBook Pro 2017 finally stops. Fischer-Price is famously plastic, garish, and poorly made. Basically you're describing the Window Laptops the Neo competes against! This is how product design should be, and what Apple have often followed in recent years: https://tenprinciples.design/
  • Recent Achievements

    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
    • Week One Done
      oliviaexpo earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      482
    2. 2
      PsYcHoKiLLa
      227
    3. 3
      Skyfrog
      70
    4. 4
      FloatingFatMan
      58
    5. 5
      Nick H.
      54
  • Tell a friend

    Love Neowin? Tell a friend!