Recommended Posts

Wasn't Vista close enough to one? I mean I know it wasn't entirely, but you still had a new audio engine, new network engine, new security features, new graphics engine...you get the idea.

I wouldn't mind a new non-compatible OS project as long as I could guarantee the old OS couldn't read the new filesystem and therefore mess with it, but for MS that would be a hard thing to convince people to get unless it was cheap and had some really convincing reasons to snag it.

And likewise really hard to spend the money and time developing, especially when it'd be competing even more directly with alternative OSes, which are getting fairly well fleshed out at the moment. On that note it'd be competing with Windows itself, which would be just as painful for MS.

Windows 7 is really just going to be Vista Second Edition......

QFT

"You've let us know you don't want to face the kinds of incompatibility challenges with the next version of Windows you might have experienced early with Windows Vista. As a result, our approach with Windows 7 is to build off the same core architecture as Windows Vista so the investments you and our partners have made in Windows Vista will continue to pay off with Windows 7. Our goal is to ensure the migration process from Windows Vista to Windows 7 is straightforward," Veghte stated.

Source

QFT

Source

That doesn't mean anything!

Just because a new car's engine is kinda similar to the old cars engine .. does that mean the new car is a copy-paste of the old one?

No... because cars arent just engines ... they also have body shells, suspension, brakes, handling, chasis, interior design .. even the leather trim may differ...

Just because the kernel won't be rewritten, that doesn't mean Windows 7 will be Vista SP1. Just because they will be more compatible and use same guidelines .. doesn't mean they will be the same.

Microsoft started with a lot of new guidelines and principles with Windows Vista (on many fronts .. UI, networking, security...). By doing this they broke their own development cycle and released the os "3 years too late". They got a lot of critic on this but now it will pay off as they now have a new foundation to build on with the new principles with Windows Vista.

Also .. we know nearly nothing about Windows 7... Windows 7 information isn't public yet and people who do know what they are talking about can't just yet.

So till PDC you can speculate all you want but talking about 7 before ANY public information is out is just plain stupid and speculation.

Conclusion ... saying Windows 7 is Vista SP2 is just stupid as you (or anyone else in the public) know NOTHING about Windows 7 itself...

That was a CPU architecture change -- Not an OS architecture change. OSX is still fundamentally the same, just compiled for a different OS.

What you seem to want is a switch like Apple did from OS9 to OSX....but that's just silly. Apple had to do it. OS9 was a mess compared to more modern operating systems like Linux/Windows NT. It had no protected memory, multitasking, security concepts, etc.

There's no reason for Microsoft to make that kind of switch. Microsoft upgraded or flat out replaced many of the systems with Vista (Networking, security, audio, video, media, and so on) and look at how much people complained about that.

This.

There isn't a reason for MS to re-write Windows from scratch, Vista had a few components overhauled (including proper security elevation for users) and people whined and bitched about it constantly.

Re-writing Windows from scratch would break backwards compatibility, and love it or hate it, it's the reason Windows is so popular.

I expect the virtualization stuff getting so popular will offer MS interesting ways to mess around with compatibility problems though.

Virtualization isn't anywhere near the point as to be accessible to the casual user.

Try building a softgrid package. It's neither easy nor straightforward.

Try explaining installing why she should or how to install a guest OS in a virual machine. She'll look at you like you're crazy and wonder why she needs another windows to run her programs.

It doesn't have to be accessible to the enduser at all if it's part of the OS. Vista already does some virtualization.

You certainly don't have to make a guest OS of Vista within Vista for it to use its virtualization.

So I'm guessing you didn't quite catch my drift.

That doesn't mean anything!

Just because a new car's engine is kinda similar to the old cars engine .. does that mean the new car is a copy-paste of the old one?

No... because cars arent just engines ... they also have body shells, suspension, brakes, handling, chasis, interior design .. even the leather trim may differ...

Just because the kernel won't be rewritten, that doesn't mean Windows 7 will be Vista SP1. Just because they will be more compatible and use same guidelines .. doesn't mean they will be the same.

Microsoft started with a lot of new guidelines and principles with Windows Vista (on many fronts .. UI, networking, security...). By doing this they broke their own development cycle and released the os "3 years too late". They got a lot of critic on this but now it will pay off as they now have a new foundation to build on with the new principles with Windows Vista.

Also .. we know nearly nothing about Windows 7... Windows 7 information isn't public yet and people who do know what they are talking about can't just yet.

So till PDC you can speculate all you want but talking about 7 before ANY public information is out is just plain stupid and speculation.

Conclusion ... saying Windows 7 is Vista SP2 is just stupid as you (or anyone else in the public) know NOTHING about Windows 7 itself...

My god you just do not read. Nobody said its going to be SP2. The reference made is that its basically going to be like Win98 was to Win95. No major fundamental differences, because it is built on the same core. Your not going to see a Win98 to XP style jump, is the point that is being made.

but hey.... didn't Apple do it? Isn't Mac OS X coded from scratch on FreeBSD as opposed to MacOS 9 or older being just RISC-type stuff? well I guess yea it is trouble; they had it standard to dual-boot between OS X and OS 9 until developers had time to make new Aqua-themed OS X-compatible apps..... imagine that happening on a Windows scale where it's the most used OS on Earth..... yea..... chaos...... meh......... i STILL think Windows from scratch would be a golden opportunity to make things right.... hmm... or maybe escape through the "window" into the "sky" and release a new OS called Microsoft Skies alongside Windows..... ok i'm rambling now so cya later lol but wait then you can't have application windows; you would have fluffy cloudy application skies; ok omg ok bye! lol

Do you actually realise how monolithic the windows platform is? Completely rewrite the OS from scratch? You're kidding me right?

Windows is compatible with thousands of devices, do you realise how long it would take to achieve the same level of compatibility with a rewrite? What about software? One of the reasons Microsoft took so long with Vista is because they need to maintain the greatest percentage of backwards compatibility. Could you really imaging them brining out a complete rewrite, and half the worlds devices just didn't work, and even more software failed too.

And you can't compare Apple's OSX. Apple have been working on basically the same finely tuned hardware platform for years. A handful of specifically chosen devices work with it, so development time for ensuring compatibility is drastically cut down.

As far as I can tell three pain areas are partitioning tools (Vista really hates some,) RAID drivers (likewise,) and older development tools (which can be expensive to replace.)

For the first six-nine months I could understand that XP was just all around easier to get along with, while the drivers and app compatibility stabilized. Now, though, I can't imagine ever using XP again.

It doesn't have to be accessible to the enduser at all if it's part of the OS. Vista already does some virtualization.

You certainly don't have to make a guest OS of Vista within Vista for it to use its virtualization.

So I'm guessing you didn't quite catch my drift.

Oh I caught it, you just have no idea what you're talking about. The only "virtualization" in Vista is a bit of write re-direction so applications don't **** the bed when they suddenly can't write to certain parts of the FS/registry, what you want is a whole different beast entirely

It's pretty obvious you've never really used a virtualization solution. We had several deployed in my last workplace. Virtual PC/Virtual Server is pretty much what you see, but try explaining why your grandma needs to boot up ANOTHER OS to write an email or do some trivial task ala the classic enviornment in OSX. Don't forget to mention that she needs to shell out for another OS license, btw. I'm sure she'll be thrilled aobut that.

SoftGrid... well, heck, softgrid needs a virtual machine itself (or at the very least a spare real machine) to do the capturing, then you have to repackage and deploy the software. Oh whats that? You needed to install something to the context menu or interact with just about any other component on your system? Tough ****, ain't happening.

I don't know anything about Kidaro but I'm sure it's not that much simpler. My point is this is all way too advanced for your average user. They simply won't do it just to write a document or balance their checkbook. Buying a mac or even installing Linux is much less hassle.

It would be a massive undertaking to overcome these problems. It's easy to say they should, its a whole nother thing to actually go and do it. And to what benefit? So you can toss Win32 out of the system? You can already do that; Win32 is just a subsystem that runs on top of the NT kernel, which has been proven by pretty much anyone who knows anything about OS kernels to be fast, reliable, and extremely well designed. And if the whole point of virtualization is to keep compatibility with Win32 apps, well, why the hell don't you just leave the subsystem in there until you don't need it anymore and not take the performance and complexity hit virtualization incurs?

And while you're throwing away compatibility for virtualization, don't forget that you'll need an entirely new set of drivers. Don't worry, its no big deal. It's not like anyone had any problems with drivers when Vista was released.

People are claiming the Vista is bloated and blaming all this "compatiblity code" for taking up all the resources in their systems. Guess what? There's about 4 MB of compat code on your hard disk, and none of it is loaded until its needed. And outside of one check call, it doesn't have anything to do with kernel. What's taking up all the resources in Vista (mainly sucking up your RAM) is the new features in Vista: desktop search, SuperFetch and even the DWM. Turn off those features and you wind up with something like... oh I don't know, Windows Server 2008 which has received pretty much nothing but praise.

Edited by y_notm

Just give Vista time and then it will be loved as much as XP.

In time drivers will catch up as companies revisit and rewrite them.

I mean anyone else remember when Win2k came out or NT3.5 came out. It took a while for drivers to really be written for them that worked and were stable 100% of the time.

And what happened to blackcomb --- As the vision changed so did the code name-- I mean don't we all wish we had a dime for all the code names that never was... Anyone else remember Neptune?

http://www.winsupersite.com/showcase/ac_preview.asp

also here is the wiki on it

http://en.wikipedia.org/wiki/Windows_Neptune

I fail to see what's wrong with just expanding the implementation of the compatibility shims that XP and Vista already use (The Application Compatibility tab).

It seems like a much more elegant and lightweight solution than virtualizing a whole OS.

Edited by MioTheGreat

Now this is a topic that could help make the push to 8,000,000. Posts .

I do agree Windows 7 is not the vision blackcomb was.

In fact I think isn't it this Ski resort...

http://en.wikipedia.org/wiki/Whistler-Blackcomb

Just a thought what if it was not a Windows version plan but instead a location for the next business meeting to discuss the next Windows. (The Whistler which became XP). And someone only heard what they wanted to hear.

That is just my thought.

My god you just do not read. Nobody said its going to be SP2. The reference made is that its basically going to be like Win98 was to Win95. No major fundamental differences, because it is built on the same core. Your not going to see a Win98 to XP style jump, is the point that is being made.

Windows 95 (without IE4) to Windows 98 was actually a pretty considerable leap. You might be surprised how much was missing if you go back to 95. No quick launch, no drag-and-drop in the start menu, and the entire Explorer was very basic with far less extensibility.

I remember installing the Desktop Update with IE4.0 for Win95 and NT4.0 which gave it some if not all of what Win98 had... It also had preview in the side.

But yes it was a big leap... Though the question is have you ever installed Windows 95 using the old Windows 3.1 desktop. Instead of the Start menu-?

What Windows 98 had that Windows 95 did not have was better support for higher memory and drive sizes as well as Fat32 support.

I remember installing the Desktop Update with IE4.0 for Win95 and NT4.0 which gave it some if not all of what Win98 had... It also had preview in the side.

But yes it was a big leap... Though the question is have you ever installed Windows 95 using the old Windows 3.1 desktop. Instead of the Start menu-?

What Windows 98 had that Windows 95 did not have was better support for higher memory and drive sizes as well as Fat32 support.

Yeah but all the stuff that came with IE4 was basically the Windows 98 shell.

so i just caught up on what was said on this thread i started

Singularity: it's not something like a desktop O/S; it's just a small lil thingy for hardware and software geeks to go "Neee!!!" over lol :blink:

Neptune: yes; it's based on the old age Microsoft Encarta UI and navigation and it was soooooo cool! Just like the Longhorn concept video is cool today, Neptune was just as cool back in those days.... But of course they didn't go through with it; maybe they didn't want the whole OS to look like one big website hehe.

many posts are regarding the question WHY recode it from scratch? i could think of MANY reasons.... like i'm tired of how some developers release software that sticks its stupid driver(s) right at the very native boot opportunity and risk preventing Windows from starting, or just slow down the boot! A re-coded Windows with an appropriate loading time for such drivers would have a boot time of like three seconds!!! When Windows starts, the ONLY drivers that should be loaded are functional (i.e. filesystem, CPU, power management), and user experience (i.e. peripherals, audio, video) -- NOTHING ELSE! Why the f**k does Alcohol 120% want its stupid SPI CD-ROM driver thing to load during the Windows boot logo screen at the very beginning?!? They're just too lazy to make their stuff work by loading it later on when Windows starts that's why, and it's Microsoft that allows developers access to shove drivers there. Have any of you ever noticed that booting up after a clean Vista or XP install is only like 2 or 3 runs of the loading meter? And then after you install let's say the nVidia ForceWare drivers and you reboot, it is eternally gonna take about 6 or 7 runs of the loading meter! How annoying!

that's just ONE reason.

Anyway; I'm saying that re-coding from scratch is an excellent opportunity to do things right with no BS. Knowledge of how to make software work with today's hardware technology is exponentially more advanced, and it's limited by the current platform. For example I don't know about everyone else but the new "low-latency" Vista audio stack is laggy/choppy! I've gone through like 5 motherboards and 3 sound cards and like 6 installations of Vista ever since it was released, and no matter what, the problem persists! It's totally gone if you have a really suped up computer though, but even now with my X-Fi Fatal1ty Pro sound card, 2 gigs DDR2 RAM, etc. etc. and Windows Experience Index of 5.9, in Windows Media Player when I enable the crossfader, it's choppy doing the fading between songs!!!! Like COME ON!!! That's what happens when you remove the functionality of the audio stack from the kernel itself like it always has been. The whole architecture is just totally messed up. They NEED a fresh start!

Some posts express worry about compatibility with hardware devices and stuff. I'm sure that the thousands of beta testers would squish most all of such bugs. There could be a separate dev. team for the coded-from-scratch Windows and have it developed for like eight (8) years while regular Windows is being released on the side.

Yeah but all the stuff that came with IE4 was basically the Windows 98 shell.

For all the customization forums we have at neowin, you would be surprised by the flexibility of the IE4 shell update. Awergh's NT4 Visual Update packages are good example of it. You can get an XP/Vista'ish desktop out of a 95/NT4 interface.

http://www.msfn.org/board/NT4-Visual-Updat...html&st=100

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

    • No registered users viewing this page.
  • Posts

    • Why it's almost impossible to produce a smartphone in the United States by Hamid Ganji If you look at the back of some Apple products, you can see the famous phrase “Designed by Apple in California, Assembled in China.” This phrase appears on products from one of the largest smartphone brands in the United States. These products are designed in the U.S., but their manufacturing takes place in China, India, Vietnam, or even Brazil. But why can’t Apple, as one of the largest American tech companies, produce its iPhones on U.S. soil? The idea for this topic came to me after the Trump Foundation launched a smartphone called the T1 and claimed that it was designed and built with American values in mind. However, this claim did not last long, as it was revealed that Trump’s phone was actually a rebranded HTC U24 Pro, with only a gold case and minor internal component changes. You see? Even a phone that is supposed to represent American values is manufactured in China. With a gross domestic product (GDP) exceeding $32 trillion, the United States is currently the world’s largest economy, while China ranks second with around $20 trillion. On the other hand, the United States is by a wide margin the global leader in various technological fields, and American companies spend hundreds of billions of dollars annually on research and development. From Apple and Google to Microsoft, Lockheed Martin, Boeing, and others, American tech and industrial giants lead their foreign competitors in many sectors. The United States also has no shortage of smartphone brands. Apple, Google, and Motorola are among the major brands in the smartphone market, collectively holding a significant share. However, the vast majority of their products are manufactured outside the United States. So why is it that the world’s largest economy, home to the most advanced technology companies and industrial powers, cannot produce a smartphone on its own soil? Let’s explore this question together. Even threats to impose tariffs won’t work After Trump entered the White House as the 47th President of the United States, his administration adopted strict tariff policies. One of these policies was the imposition of a 25% tariff on smartphones manufactured outside the United States. Trump said he “had a little problem” with Apple CEO Tim Cook over producing smartphones outside the U.S. So he thought that threatening a 25% tax on imported phones might force Apple to bring manufacturing back to the United States. “I have long ago informed Tim Cook of Apple that I expect their iPhones that will be sold in the United States of America will be manufactured and built in the United States, not India, or anyplace else,” Trump wrote on Truth Social. Image via The White House Although Apple currently manufactures some of the iPhone’s chips in the United States with TSMC's help, it still shows no willingness to shift full iPhone production to the country. At the time, renowned Apple supply chain analyst Ming-Chi Kuo wrote on X, “In terms of profitability, it’s way better for Apple to take the hit of a 25% tariff on iPhones sold in the US market than to move iPhone assembly lines back to the US.” However, manufacturing a smartphone in the United States is not as easy as it might seem, and many technical and economic barriers are involved. The lack of necessary manufacturing hubs There is a clear reason why many companies prefer to manufacture their products in China. China has established itself as the main global manufacturing hub for international companies, and over the past few decades, large contract manufacturers have emerged there, allowing companies like Apple to outsource production. One such example is Foxconn, which also manufactures some Apple products in India. Building the infrastructure required to produce smartphones in the United States would require tens of billions of dollars in new investment. Factories would need to be built, essential manufacturing equipment would have to be installed, and, most importantly, a skilled workforce capable of operating these systems would need to be recruited and trained. The United States currently lacks the core infrastructure needed to manufacture smartphones, and for this reason, many companies prefer to outsource production to Chinese contractors rather than spend tens of billions of dollars to build that infrastructure, which is significantly more economically efficient. Additionally, building such infrastructure in the United States could take up to a decade, ultimately leading to a significant increase in the product's final price for consumers. Shortage of trained labor in the U.S. compared to China Decades of serving as a global manufacturing hub have allowed China to build a massive talent pool in the production sector that is almost unmatched worldwide. Today, if a company chooses to manufacture its products in China, it can be confident that the workers involved in production have years of experience in their respective roles and are capable of producing high-quality goods with minimal errors. Even if we assume that tens of billions of dollars were invested in building smartphone manufacturing infrastructure in the United States, finding skilled workers would remain highly challenging. Apple CEO Tim Cook visiting the iPhone 6 assembly line in China in 2014. Image: Tim Cook on X In a 2015 interview on CBS’s 60 Minutes, Tim Cook said the main reason Apple isn’t producing in the US is a lack of skills. "China put an enormous focus on manufacturing, in what you and I would call vocational kind of skills. The US over time began to stop having as many vocational kinds of skills. I mean you could take every tool and die maker in the United States and probably put them in the room that we're currently sitting in. In China you would have to have multiple football fields,” Cook said. Also, in 2017, at the Fortune Global Forum in Guangzhou, Cook once again emphasized the importance of highly skilled Chinese workers. “China has moved into very advanced manufacturing, so you find in China the intersection of craftsman kind of skill, and sophisticated robotics and the computer science world. That intersection, which is very rare to find anywhere, that kind of skill, is very important to our business because of the precision and quality level that we like. The thing that most people focus on if they’re a foreigner coming to China is the size of the market, and obviously, it’s the biggest market in the world in so many areas. But for us, the number one attraction is the quality of the people,” Apple CEO said. Higher labor costs in the United States Producing almost any product in the United States is more expensive than in many other countries, and one of the main reasons is the higher cost of labor in the U.S. According to the Bureau of Labor Statistics, median weekly earnings of full-time workers in the United States were $1,235 in the first quarter of 2026. Meanwhile, the average annual salary in China's private sector in 2025 was RMB 71,590 (US$9,961). In many parts of the world, the weekly wage of an American worker is equivalent to several months of income. Another important factor to consider is that in the United States, the workforce capable of working on a smartphone assembly line is highly specialized and therefore commands higher-than-average wages. According to an estimate by Bank of America, producing an iPhone in the U.S. is technically possible, but “iPhone cost can increase 25% purely on higher labor cost in the U.S.” However, this 25% increase applies only if final assembly is performed in the United States while components are still sourced from China or elsewhere. In this case, the price of a base iPhone would rise from $799 to around $1,000. But in another scenario, if Apple were to produce the required components for the iPhone within the United States, production costs could increase by more than 90%. Trump’s dream for a “Made in the USA” iPhone might never come true In a free-market capitalist economy, one of the primary responsibilities of any CEO is to maximize profit. Using Apple as an example, Tim Cook’s role is to maximize the company’s profits so that it can fund research and development for new products and invest in areas such as artificial intelligence, while also keeping shareholders satisfied. Therefore, it is entirely understandable that Apple would choose not to bring its manufacturing back to the United States and instead keep production in countries where labor is cheaper, and products can be manufactured at a lower cost, thereby maximizing its profit margins. What is your opinion about manufacturing smartphones in the United States? If you are an American citizen, would you be willing to pay hundreds of dollars more for a smartphone made domestically in the USA? Let us know in the comments.
    • Cheers everyone for the replies. It's been very useful. 👍
    • Compared to the 7735HS it is around 25-30% slower in multi-threaded tasks (according to Google search) I did a review of the 7735HS Beelink SER6 Max in 2023, but thinking about it, it's not comparable to the 7730U. For the example you gave about how it will be used, the 7730U is actually an excellent choice for its power and battery efficiency.
  • Recent Achievements

    • Reacting Well
      JuvenileDelinquent earned a badge
      Reacting Well
    • One Month Later
      Excellence2025 earned a badge
      One Month Later
    • Week One Done
      Excellence2025 earned a badge
      Week One Done
    • Week One Done
      flexorcist earned a badge
      Week One Done
    • Week One Done
      Woland13 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      194
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      71
    5. 5
      FloatingFatMan
      67
  • Tell a friend

    Love Neowin? Tell a friend!