Why Windows? Why not ReactOS?
Why ReactOS? Why not AmigaOS? Why not any other OS?
The OP wants to boot Windows on an M1. That's why.
Welcome to the M1 Windows project
151–160 of 276 posts
Re: Welcome to the M1 Windows project
#152Earlier quoted context omitted.
Really? I think Windows is in the best state it's ever been... WSL is incredibly nice to use as a development platform, and many well-designed apps have a Windows version ever since Electron started becoming the de facto standard.
So Linux/GNU is a great dev environment and Electron is the standard for building apps. Tell me how exactly you think this means Windows is a healthy platform?
Hmm, I guess you must mean that the native Windows development environment (i.e. .NET/Windows App SDK) isn't very developer friendly; I'm afraid I don't have any idea or how to compare it to Swift or Cocoa. As a user, though, I have better access to software and tools than ever before!
Re: Welcome to the M1 Windows project
#153Awesome work, I'd love to be able to dual boot Windows on my M1 machine
Hopefully Microsoft just hires you and gives you the resources you need to do this properly
Re: Welcome to the M1 Windows project
#154hey, OP here, figured i'd clarify some things about this project: 1) yes, I realize this is going to be way harder than it seems, but I'm actually going to do my best to hopefully get a good user experience out of this and I'm easily preparing for this to be a multi-year effort, but I'm not going to give up right at the gate 2) Custom HALs were actually an option, up until very recently, since as of Windows 10, versi…
May I suggest you don't license the work in a way that allows it to be commercialized without your explicit permission and handsome compensation to you and any other contributors. You'll need this to be sustainable and it'll be incredibly frustrating if a company de-facto hijacks the development and takes it in a direction you don't expect or want.
IANAL but I'd like a license that goes something like this:
Companies: If you are working for a company/corporation/profit-generating entity, or otherwise intend to sell or use such code derived from this repository for profit-generating purposes, you shall not be permitted to use any of the source code herein until you email me (author email here) and we can come up with the appropriate terms and conditions for your use case.
Everyone else: Have fun!
Obviously it's missing some necessary edge cases and disclaimers, but yeah.
Re: Welcome to the M1 Windows project
#155Earlier quoted context omitted.
This part is why I hope x86 has a long life ahead of it. Everybody and their dog have their own standard for things in ARM-land.
One can hope that RISC-V in the future will not follow ARM's past mistakes.
The mistakes are already happening. There are RISC-V processors being shipped with unfinished extensions and weird MMUs and now Linux has to decide whether to support those or only support finished standards
Re: Welcome to the M1 Windows project
#156ah dirty ice cream
Re: Welcome to the M1 Windows project
#157Earlier quoted context omitted.
Oh but then half of HN will complain about how that's not truly open according to a dictionary definition thus automatically becomes untrustworthy and they won't touch it with a ten foot pole. (/s) Jokes aside, technically I don't disagree on the "dictionary definition" thing there... but it's interesting how the current landscape has shifted and now more control for the developer starts to become a common interest b…
You're confusing closed source blobs and proprietary licenses with restrictive but truly open licenses like AGPL which would also protect the authors.
In this case I don't think AGPL does what you want; it's oriented towards SaaS but this project is a bootloader.
Re: Welcome to the M1 Windows project
#158Earlier quoted context omitted.
That's only true up to a certain point. ARM is a very weird target, because a lot of standardized stuff we take for granted in x86/PC land aren't standardized on ARM. In particular, take the Interrupt Controller: x86 has a standard for it (well, technically has two, the PIC and APIC). The "standard" in ARM-land is the GICv3 or GICv4, but many different CPU vendors have their own. Apple has the "Apple Interrupt Contro…
Actually you might be surprised. Windows NT is _older_ than many of the "standards we take for granted in x86/PC land", and for example it does support multiple types of pre-ACPI ways of bringing up multiprocessor systems and specifically multiple types of interrupt controllers. Heck, x86 Windows even supports non-PC servers from Compaq and others; ever tried to press F5 during (old) Windows NT setup ? As the OP said…
> x86 Windows even supports non-PC servers from Compaq
Were there x86 but non-IBM compatible models or did you mean the alternate instruction sets (Alpha, PPC, RISC)?
Re: Welcome to the M1 Windows project
#159hey, OP here, figured i'd clarify some things about this project: 1) yes, I realize this is going to be way harder than it seems, but I'm actually going to do my best to hopefully get a good user experience out of this and I'm easily preparing for this to be a multi-year effort, but I'm not going to give up right at the gate 2) Custom HALs were actually an option, up until very recently, since as of Windows 10, versi…
I like your crazy energy, goodluck
Re: Welcome to the M1 Windows project
#160Why?