Live data from Hacker News

Welcome to the M1 Windows project

amarioguy.github.io

181–190 of 276 posts

Re: Welcome to the M1 Windows project

#181
post #157

Earlier quoted context omitted.

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.

Sure, hence the "like". They could create or use a license that is fully open but prevents commercial use without a license.

Re: Welcome to the M1 Windows project

#182
post #146

Earlier quoted context omitted.

You're confusing closed source blobs and proprietary licenses with restrictive but truly open licenses like AGPL which would also protect the authors.

It doesn't look like we can say " licenses like AGPL ". It's more that AGPL is basically the only one in that vein. Remove the A, if you please, but that's pretty much it in terms of variety. On the other hand, reading HN over time I also got the idea that *GPL has been tried with the intention of avoiding abuse, and it failed several of those intentions. I now regret not having taken note each time I saw comments in…

The problem is not with the GPL. The GPL is just as enforceable as any other proprietary license. The difference is that these amateur projects often don't have the resources to fight infringement.

Re: Welcome to the M1 Windows project

#183
post #157

Earlier quoted context omitted.

In this case I don't think AGPL does what you want; it's oriented towards SaaS but this project is a bootloader.

Sure, hence the "like". They could create or use a license that is fully open but prevents commercial use without a license.

Such a license is not possible.

Re: Welcome to the M1 Windows project

#184

Earlier quoted context omitted.

> Microsoft aren't going to write drivers for the M1 - it's not their job It's absolutely their job to make Excel less of a P.O.S. on Mac.

Excel on Mac is a P.O.S. because Microsoft wants it to be one, they don't want users switching to Macs.

Microsoft’s MacBU has always been a separate team who I don’t think have ever held back on trying to make good products and have put surprising amounts of effort into it. Even the PC Office team doesn’t care if the Windows team does well, after all.

They do however have nightmarish build processes and technical debt that when I mention here get replies from people claiming I must have made it up.

Re: Welcome to the M1 Windows project

#185

hey, 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.

Do this, but make allowances for small businesses under a certain MRR.

Re: Welcome to the M1 Windows project

#188
post #183

Earlier quoted context omitted.

Sure, hence the "like". They could create or use a license that is fully open but prevents commercial use without a license.

Such a license is not possible.

How exactly is that? There are plenty of licenses that don't allow commercial usage.

Re: Welcome to the M1 Windows project

#189

Earlier quoted context omitted.

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…

Imagine you license a word processor this way, would it then be a violation to use that word processor to edit your resume?

Re: Welcome to the M1 Windows project

#190

Earlier quoted context omitted.

It does. Officially there is an ARM build of Windows that Microsoft licenses to OEMs, and there is (or maybe was?) Windows IoT Core which has a build for ARM. If I recall (grain of salt then) a while after the first M1 Mac came out one of Apple’s VPs had said something on the record about Apple having tried to get Microsoft to sell retail licenses of a Windows 10 for ARM build, because they didn’t want to deprecate B…

>a while after the first M1 Mac came out one of Apple’s VPs had said something on the record about Apple having tried to get Microsoft to sell retail licenses of a Windows 10 for ARM build Not quite. The Craig Federighi quote is: >As for Windows running natively on the machine, “that’s really up to Microsoft,” he said. “We have the core technologies for them to do that, to run their ARM version of Windows, which in t…

Pretty surprising that MSFT would end up with a deal like that, I'd feel like they would be in a position of strength. Unless all the ARM vendors were pretty supicious of whether Microsoft would succeed/invest properly in the ecosystem?
Post reply on HN