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

[jamcat]

What doesn’t work

There are newer progress updates than the one you posted. They now have Bluetooth, USB3, and GPU drivers working.

It’s strange they mention the Touch Bar not working, since Apple ditched the Touch Bar and there are exactly zero Apple Silicon computers that have one.

The other stuff currently not supported in the Asahi alpha are not crucial.

And it is worth noting that they have been getting tacit assists from Apple.

[2DaT]

There are newer progress updates than the one you posted. They now have Bluetooth, USB3, and GPU drivers working.

I'd rather not use an operating system with reverse engineered drivers.

[audiojunkie]

Linux can now run natively on Apple Silicon, thanks to the Asahi Linux project.

You can, but should you ? Running a system, that vendor doesn't officially support, with reverse engineered drivers.

What doesn’t work
DisplayPort
Thunderbolt
HDMI on the MacBooks
Bluetooth
GPU acceleration
Video codec acceleration
Neural Engine
CPU deep idle
Sleep mode
Camera
Touch Bar

Yeah, I guess you can "run" a Linux on apple silicon, but realistically you don't want to.

Spoken like someone who doesn’t know Linux. Why should there be “vendor” support when the world-wide community has continuously proved itself over and over? Or is it that you are used to having your hand held through everything?

All of the things you mentioned are coming. The Asasi project in new. It only started after the silicon was released. Have some patience and give the project a fair amount of time to mature.

[audiojunkie]

There are newer progress updates than the one you posted. They now have Bluetooth, USB3, and GPU drivers working.

I'd rather not use an operating system with reverse engineered drivers.

Reverse engineered drivers?!?!

Linux is a completely different operating system!

Yes, Linux drivers have to be written, but Windows drivers are certainly NOT reverse engineered. The very thought is a ludicrous!

[audiojunkie]

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.

[zerocrossing]

The only problem is it only fixes it cosmetically. Underneath it’s still Windows, which means randomly shitting itself when you open a new folder, not actually writing files to an external drive despite pretending that it did, the Windows registry…

I’ve been using Windows since Vista, and have not once experienced any of those problems. I do have many memories of having to zap the p-RAM on many a Mac.

[jamcat]

I'd rather not use an operating system with reverse engineered drivers.

I’d just be happy with stable drivers on Windows.

[BONES]

I've been happy with exactly those things for 25 years or so now.

if you can work like that then, yeah, good for you.

If you can't, what's wrong with you? Like I said, none of us have access to an anechoic chamber, there are always all kinds of sounds happening around us. You have to be able to deal with it or you'd never get anything done. I'm usually sufficiently focused on what I'm doing that I only notice that the fan was on when I switch the computer off at the end of a session. I'm trying to think of a feature I care about less when I'm looking for a new laptop and I literally can't think of anything less important to me than fan noise.

Windows 11 (ARM version) runs very well in Parallels, as I’ve heard.

Windows on ARM won't run x86 applications, though, so it is mostly useless to anyone with work to do.

I don’t know. So far, Microsoft has dropped the ball on Windows ARM

How so? AFAIK, it works really well. It's just that nobody cares so nobody supports it. Why would they when x86 is better? If Apple Silicon has taught us anything, it's that ARM has no real advantage over x86. Do Apple silicon powered Macs outperform x86 Windows laptops? No, they don't. Do they impress with incredibly long battery life? No, they are no better than the best x86 machines. So why would anyone bother supporting Windows on ARM, beyond the low-end stuff we've been seeing for the past several years?

Microsoft should have begun full scale transitioning of Windows to ARM a long time ago

Why? What would be the point? It's not like ARM hasn't been around forever. DEC Alpha had its day in the 90s but was soon comprehensively crushed by x86. You might think of ARM as the future but to anyone who has been around a while, ARM definitely feels like the past.

Why should there be “vendor” support when the world-wide community has continuously proved itself over and over?

Has it? I've not noticed. Nobody knows the hardware like the people who made it so who so going to be in the best position to write the drivers to best exploit its potential? It's just common sense.

[jamcat]

Windows on ARM won't run x86 applications, though, so it is mostly useless to anyone with work to do.

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

I don’t know. So far, Microsoft has dropped the ball on Windows ARM

How so? AFAIK, it works really well. It's just that nobody cares so nobody supports it.

That's how.

[audiojunkie]

audiojunkie wrote: ↑14 Feb 2023 15:31
Why should there be “vendor” support when the world-wide community has continuously proved itself over and over?
Has it? I've not noticed. Nobody knows the hardware like the people who made it so who so going to be in the best position to write the drivers to best exploit its potential? It's just common sense.

There's been lots of things you haven't noticed since you played with Linux. Why should drivers be any different?

Yes, it's common sense that the hardware designers would be in the best position to write the drivers. However, many (most?) tech companies provide information required for driver creation openly. As a common example, 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. NVIDIA! We never thought that they'd open up, but they did!

ANY device that is class compliant will work perfectly with low latency without requiring some special driver. Windows can't do low latency with class compliant hardware without some sort of crutch--ASIO4ALL? Please! Class compliant equipment is meant to be standardized equipment that runs on all three operating systems. Standards-compliant hardware shouldn't have to require a hardware cludge to run properly on an OS--yet Windows requires it. The Windows world has taken to frowning on Class Compliant hardware as being second class and not low latency, when it is the operating systems fault to begin with. Things are getting better with WASAPI, but ASIO still reigns supreme in Windows land, and heaven help the poor piece of hardware that doesn't support ASIO or WASAPI, because if it's class compliant, it's almost unusable in Windows.

All of the Linux drivers are already built into the Linux Kernel. 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. Yet, with Linux, if it was popular, it will likely work right out of the box without faffing about with trying to find compatibility modes that will allow the Windows 95 driver to work. In fact, unlike Windows, you can take a free live distro and run it on a flash drive on your computer and be able to tell immediately if it works or not--no need to install anything to test things out--you try it and it works? It's supported.

So, to summarize and make it easy (Yes! Even for you!) to notice:

1. Many (most?) hardware manufacturers work hand-in-hand with the community in the creation of drivers for hardware.
2. Because of closely following standards, many drivers that won't work well on Windows without cludges and hacks work just fine in Linux.
3. The Linux driver model is very different from the Windows driver model--most popular hardware is supported right out of the box and works very well, even without "official" drivers. And why is that? Because the hardware manufacturers had a hand in the Linux driver development.

As always, I know you'll reply, so I will eagerly await your taunts...............

[audiojunkie]

Windows on ARM won't run x86 applications, though, so it is mostly useless to anyone with work to do.

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

I don’t know. So far, Microsoft has dropped the ball on Windows ARM

How so? AFAIK, it works really well. It's just that nobody cares so nobody supports it.

That's how.

Interesting subject! I can't speak for Windows' capabilities, but tools are currently in development to run x86-64 native apps on ARM 64 processors in the Linux world:

"With open-source software efforts like Wine+Hangover as well as other emulator efforts like FEX-Emu and Box64, the outlook is quite positive for being able to run Windows x86/x64 games and applications on the growing number of 64-bit Arm laptops and other non-x86 Linux devices."

As a reminder, WINE is a compatibility layer, not an emulator, so while the chip emulation may require a little extra CPU, WINE won't. WINE is also available for Macs.

What a lot of people don't realize, is that the tables have turned, and in todays world of mobility, ARM's technology sips electricity where Intel and AMD drink from the firehose. Almost all modern technologies are looking for ways to better do what ARM is currently doing. Intel and AMD won't go away at all, but as this world becomes increasingly more mobile, technologies that are very power efficient are the new gold standard. Arm on Windows is not going away, and will only become more prevalent. Apple has seen the light with its "M" series ARM chips. Linux has been supporting almost all processor types since the beginning. Intel started with pushing for this with its EVO line, but ARM is the true future (unless something drastic changes).

Here are some interesting articles I just quickly grabbed to emphasize my point:

https://techmonitor.ai/technology/silic ... indows-pc

Arm processors will become mainstream for Windows in 2024 – Qualcomm CEO. Interest in Arm chips is growing from PC vendors, though they have a long way to go to challenge x86's dominance.Nov 3, 2022

https://medium.datadriveninvestor.com/w ... %20happen.

Will ARM eventually replace x86?
As more compatibility is added, more users will switch to ARM because of speed, reliability, security and price. More people will leave x86 CPUs with their glaring vulnerabilities, and replace them with ARM powered devices. Of course this won't happen in a year or even two, but it will eventually happen.

https://www.kovair.com/blog/future-of-a ... er%20ones.

Why is ARM the future of computing?
Why Go for ARM? ARM processors are suitable for light and battery-powered devices like smartphones, tablet computers, and embedded systems. ARM processors consume less power, making them ideal for battery-powered devices. They provide better performance per watt and split complex operations into simpler ones

I could go on and on.... There are pages of articles like this. Will Intel or AMD go away? Nah, but ARM is now sufficient to run a full blown DAW on a laptop, while lasting for hours on batteries. Technology keeps getting better and better!

[BONES]

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.

[rj0]

This is another common occurrence on Windows.

Not on my machine for as long as I can remember.

Consider yourself lucky, then.

You are referring to the problem of files not being on an external drive after copying them, correct?

This is related to disk write caching on Windows. Disk write caching is meant to improve system performance by holding data in cache memory before it's written to disk, thus reducing disk I/O.

The default for removable storage is "Quick removal" which is supposed to disable disk write caching. The problem, though, is Quick removal seems to be broken in Windows 10, as it appears disk write caching is still being employed even when Quick removal is the default.

It may not be noticeable when copying a small number of small files, but it definitely becomes an issue when writing large amounts of data at once.

The solution is to use the "Safely Remove Hardware and Eject Media" button (despite Microsoft claiming it is not necessary in "Quick removal" mode), but Microsoft has hidden this feature and buried it in the System Tray, and it's no longer available when right-clicking a removable drive.

Granted, on a Mac you always have to eject media. But that is known, and Apple makes it easy to do, and complains when you don't. You're supposed to not have to do it on Windows, and it used to work that way correctly.

Never had those problems either (Windows 3.1 to present).

I am apparently very lucky.

[jamcat]

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

OK. The point is Windows 10 ARM64 can apparently run 32-bit x86_64 software, but not 64-bit x86_64 software.

Apparently Windows 11 ARM64 now supports emulation for 64-bit x86_64 software.

"Windows 10 on Arm provides emulation of 32-bit (x86) apps but can’t run non-native 64-bit applications. Windows 11 on Arm introduces 64-bit (x86-x64) emulation, greatly expanding the range of applications that run on the platform."

https://www.androidauthority.com/window ... d-3100713/

[sQeetz]

Everything runs on Windows 11 on Parallels, ARM, x86, 32bit, 64bit. The stuff that does not work are games that need DirectX 12. Tried installing Forza Horizon but it won't start due to that. It is being worked on, though...