Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Welcome to the M1 Windows project

amarioguy.github.io

Post reply on HN
Print view View original

131–140 of 276 posts

Re: Welcome to the M1 Windows project

#131

Post by matthewfcarlson »

amarioguy wrote: post #87

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…

I do love the Project Mu shout out at the bottom. Best of luck with your project!

Re: Welcome to the M1 Windows project

#132

Post by usrn »

singhrac wrote: post #88
usrn wrote: post #38

Earlier quoted context omitted.

I don't think Microsoft sees a future in Windows. Their current strategy seems to be one of extracting as much value from it as possible until it dies.

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?

Re: Welcome to the M1 Windows project

#133

Post by dataflow »

amarioguy wrote: post #87

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.

Re: Welcome to the M1 Windows project

#135

Post by maleldil »

nomel wrote: post #129
scoopertrooper wrote: post #113

Earlier quoted context omitted.

> I have already delegated this to after I get Windows working under the thin hypervisor Not to be 'that guy', but that's an odd use of of the word 'delegated'. 'Relegated' might have been the word for which you were looking. Edit: I know this will be down voted because I'm critiquing the word usage of OP instead of focusing on how cool their project is. I get that. I'm just pedantic and this sort of thing eats me al…

Personally, I've learned to talk more precisely from these sorts of comments than anywhere else. In real life, people will rarely correct you. I think the concept of a "meta comment" is interesting, where you could push this sort of thing into a separate parallel thread that would normally be hidden.

That's an interesting point. It's much easier to correct a stranger on the Internet, but it's also harder to be kind. Comments that manage to do both (like GP) are great, and I always like to see them.

Re: Welcome to the M1 Windows project

#136

Post by amarioguy »

dataflow wrote: post #133
amarioguy wrote: post #87

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.

I'll definitely take this into account thanks for bringing it up! Licensing is something I've thought about a bit before starting, right now since m1n1 (the hypervisor I'm iterating on) is MIT licensed for the most part, I'm inheriting that license too for my fork of m1n1 (i'll mainline the changes btw! need to work with marcan once they're done), but as the project goes further I'll definitely consider the question of licensing again.

Re: Welcome to the M1 Windows project

#137

Post by buffington »

Uptrenda wrote: post #134

So its a plan for a project and not an actual project? lmao, why is this on hacker news front page?

Because it perfectly satisfies the first guideline of "What To Submit":

> Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity.

Re: Welcome to the M1 Windows project

#139

Post by sassy_quat »

mschuster91 wrote: post #16
ComradePhil wrote: post #4

Why Windows? Why not ReactOS?

ReactOS is nowhere near enough the quality you'd need - you don't want to waste time figuring out if you are fighting a bug in ReactOS or in your own code.

If ReactOS crashes, it is quite clear where the problem lies, but I would'nt wait on them to fix it.

Re: Welcome to the M1 Windows project

#140

Post by j1elo »

dataflow wrote: post #133
amarioguy wrote: post #87

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.

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 between "hackers".

The original OSS licenses protected users (as in, final users) from predatory devs; nowadays, small devs and hackers talk in their forums about how to preemptively protect themselves against predatory users (as in, not final users, but other bigger devs that leech on other's work)

Post reply on HN