Do you hate the looks Windows 10/11 - WindowBlinds might be the solution, look like Mac or anything

[BONES]

Yes, and for just $139 per year, you can use it to do things you can do on a Proper Computer (PC) for free.

[sQeetz]

You can buy a perpetual license.
Even if you had the subscription, it's €49 for the renewal.

[audiojunkie]

From what I read, it's x64 applications it won't run, but it can run 32-bit x86 applications.

It's all x86, "x64" is just shorthand for x86, 64 bit.

The rest is down to "who cares?", not that it doesn't work. It works fine but there is no point to it because x86 works at least as well and has Intel and AMD both pushing it forward at a rate of knots. All the reasons Apple has given for moving to ARM have turned out to be bogus, so why would the Windows world bother going down the same path?

The reality is that Apple have moved to ARM because it makes their lives easier, not because it brings any benefits to their customers. It means they can do the work once and use it for iOS, iPadOS and macOS. I'm sure their shareholders love it, I'm not sure why their customers put up with it, though.

NVIDIA has long been the hold-out for Linux drivers, preferring instead of providing open information for communities to write the drivers, to write them themselves. Even with that, we can't complain, because they are at least providing the drivers. That said, they have very recently fallen in line and also started open sourcing their driver software.

And what has been the benefit of that to users? I'm thinking zero, which is my point.

Windows can't do low latency with class compliant hardware without some sort of crutch--ASIO4ALL?

Now whose running on old information? I have no trouble getting realtime performance from WASAPI in Windows. It just works.

ASIO4ALL? Please!

OK, so 3rd party software is great when it's on Linux but not when it's for Windows. Double standards, much? I'd suggest ASIO-4-All is a great example of why it's just one big crap-shoot.

Class compliant equipment is meant to be standardized equipment that runs on all three operating systems.

Who cares? Class compliant is for morons who can't set things up for themselves. I'd have thought it was anathema to all the reasons anyone would want to use Linux.

The Windows world has taken to frowning on Class Compliant hardware as being second class

Which makes perfect sense. Things made specifically for a single OS have obvious advantages to cross-platform software. No need to compromise on anything.

All of the Linux drivers are already built into the Linux Kernel.

Which makes it at least as bloated as Windows, which is what people are trying to get away from. So why bother?

A popular piece of hardware that was created with Windows 95 drivers has a smaller and smaller chance of working well with each new generation of Windows that is released.

Not in my experience. The very first USB device I ever bought still runs as well in Win11 as it did in Win98. Of course, that's because the vendor has updated the drivers once or twice but the chances that a 3rd party might do the same is about the same for Windows as it would be for Linux. GIMP on Windows would be a good example of that sort of thing - ported by someone who needed to use it on Windows for printing, IIRC.

You're talking as though open source was the exclusive domain of Linux but it is thriving on all platforms so most of the things you tout as advantages for Linux are irrelevant because we have the same on other platforms. Things like Blender or Rainmeter come to mind or even ASIO-4-all.

Lol! Your responses are so error-prone it’s hilarious! I’m not going to bother responding. I’ll leave this little gem alone for history, so someone in the future can get a little chuckle out of it.

This is my favorite line (of many):

“It's all x86, "x64" is just shorthand for x86, 64 bit.”

[fmr]

But, if I’m paying $2000 for a laptop anyways, why would I buy the one that only runs Windows, instead of the one that runs both, ceteris paribus.

Does the current M machines run Windows? Not that I'm aware.

Of course all things are not the same, since Windows laptops in that price range are all “gaming systems” as already pointed out, and are noisy as hell.

Bullshit. As I already wrote, I have a gaming laptop (which actually cost way less than 2.000, more like half of it) and I rarely hear the fans working.

Linux works fine on them, so if Windows works, all three OSes are working on ARM processors.

I presume you are talking about some kind of VM. That's not "running Windows" IMO. Older Macs were able to run Windows natively.

Sorry, I missed your message. No, this is running natively, not a VM.

Natively? On an M CPU? Do you mean you are using a ARM version of Windows? I don't know if the picture I saw was yours, but I could see clearly Windows "in a window" with macOS environment behind. That's not "run Windows natively".

[audiojunkie]

No, I’ve posted no picture.

When compiling source code, the source code doesn’t care which processor it is being run on. The hard part is building the original environment that lets the compiler run natively on the processor. A compiler running natively on a particular processor, produces code code that runs natively on that processor. Since Linux is open source, all of the source code for the OS is then able to be compiled natively to that processor. You end up with a Linux OS native to whatever CPU architecture it was created on. That is what the Asahi project is doing. Once an initial base Linux OS is there, the next big part of the project is writing drivers for the particular hardware provided in the computer. This is the part the Asahi is now working on. It is all very much a native OS.

There is a free book available that details the process called, “Linux from Scratch”. Other than the general idea of how it works, it is beyond my skill level, but it is very interesting.

[fmr]

No, I’ve posted no picture.

When compiling source code, the source code doesn’t care which processor it is being run on. The hard part is building the original environment that lets the compiler run natively on the processor. A compiler running natively on a particular processor, produces code code that runs natively on that processor. Since Linux is open source, all of the source code for the OS is then able to be compiled natively to that processor. You end up with a Linux OS native to whatever CPU architecture it was created on. That is what the Asahi project is doing. Once an initial base Linux OS is there, the next big part of the project is writing drivers for the particular hardware provided in the computer. This is the part the Asahi is now working on. It is all very much a native OS.

This applies to Linux, but I was talking about Windows.

[audiojunkie]

No, I’ve posted no picture.

When compiling source code, the source code doesn’t care which processor it is being run on. The hard part is building the original environment that lets the compiler run natively on the processor. A compiler running natively on a particular processor, produces code code that runs natively on that processor. Since Linux is open source, all of the source code for the OS is then able to be compiled natively to that processor. You end up with a Linux OS native to whatever CPU architecture it was created on. That is what the Asahi project is doing. Once an initial base Linux OS is there, the next big part of the project is writing drivers for the particular hardware provided in the computer. This is the part the Asahi is now working on. It is all very much a native OS.

This applies to Linux, but I was talking about Windows.

Oh, sorry. I misunderstood. I thought you were referring to the nativeness of the Asahi project.

In theory, the process would be the same—it “could” be done. But I have serious doubts that Microsoft would ever produce a version for their competitor’s CPU. So, in that sense, a Windows product would likely remain a system that would have to be run on a VM.

[audiojunkie]

Interestingly, because of the change to a custom-made CPU, unless Apple’s chips are fully compatible with ARM, it will be increasingly unlikely that Hackintosh enthusiasts will be able to make the current versions of MacOS work on non-Mac hardware, which may have been a strategic move on Apple’s part in the first place. So MacOS will likely need to be run as a VM as well if used on non-Apple hardware.

[pekbro]

I refuse to buy window blinds, I bought like every version since it came out missing only one upgrade, from 9 to 10 and I can't qualify for the upgrade to version 11. Not to mention all the other games and whatnot I bought from them over the years.

It's not the money, its the principle... Wardell is also a shitty game designer, I really never liked his games.

[BONES]

Lol! Your responses are so error-prone it’s hilarious! I’m not going to bother responding.

Right, not even one, just to show you might have a point? Sounds to me like you have nothing, bud.

This is my favorite line (of many):
“It's all x86, "x64" is just shorthand for x86, 64 bit.”

You're right, I should have been using the term x86-64, my bad -https://techterms.com/definition/x64 - but I didn't want anything I said to be applied to the wider range of 64 bit processors, as x64 includes 64 bit ARM processors, so x86 seemed a better fit. From now on, though, I'll use x86-64 to avoid confusing your tiny brains.

[zerocrossing]

It might be worth it just so I know where windows overlap. The thing I hate about Windows is that you can often have two windows that have no drop shadow or boarder color and it can get confusing as to what you're looking at. It's really bad design.

[fmr]

It might be worth it just so I know where windows overlap. The thing I hate about Windows is that you can often have two windows that have no drop shadow or boarder color and it can get confusing as to what you're looking at. It's really bad design.

I agree on this. Once MS went fully on board of the "flat trend" wagon they got rid of a lot of details like this, that helped a lot in the work. Slowly, they have been reintroducing some graphic elements, but the drop shadows didn't, yet

[kperry]

It might be worth it just so I know where windows overlap. The thing I hate about Windows is that you can often have two windows that have no drop shadow or boarder color and it can get confusing as to what you're looking at. It's really bad design.

Pretty certain this is fixable via the registry (or tool like WinAero).

[lfm]

It might be worth it just so I know where windows overlap. The thing I hate about Windows is that you can often have two windows that have no drop shadow or boarder color and it can get confusing as to what you're looking at. It's really bad design.

That's true, it's really hard to grasp what is going on at Microsoft these days.
- it's like fashionable with certain looks as windows 95/98 came and 3d look everywhere.
- now opposite, flat, flat, flat and no nuanced colors or anything, just a huge washout
- and cursor does not change shape to pointing hand when on an area that can be clicked

I'm just again praising Window Blinds. Been fixing some transparency stuff I just hate that just blurs things, and still some inactive window that have some things I have not figured out fully that goes transparent. But found all active window stuff.

I am not online with this new computer so help does not work for Window Blinds, so might install on my windows 10 laptop too to find the last things with transparency.

[revvy]

https://arstechnica.com/gadgets/2023/02 ... -macs/amp/

“Microsoft officially blesses Parallels as a way to run Windows on M1, M2 Macs.”

Don’t care either way and am not claiming it’s native, just sharing a news story.

No, it’s not Boot Camp but again, don’t care. When I used to run Win on my Intel Mac back in the day, I chose to use Parellels over BC anyway.