Arelius

Generally, running in a MMU without static task config would require relocatable binaries. I'm not sure why it'd preclude execute-in-place. As a relocatable binary should be executable from generally any address space. However I suspect that hardware without an MMU is not super likely to be able to support XIP.

It is based on FreeRTOS, so it should be fairly well documented.

Obviously there is simplification going on, but clearly somewhere between founder of a 5 person startup. And CEO of a public multi-national there is a line where they really are not much alike.

It's a neat piece of hardware, but honestly I never wanted to play any of the games. I don't really know for to do discovery for it, and none of the ones I tried stuck for me, honestly, I prefer to emulate games from my childhood, or retro/indie games I already have on my back-log.

At some point we will have to stop treating universities as tests to pass, and actually what they claim to be: places to learn. Ultimately it needs to be on the student to want to learn.

Obviously this would be easier if our entire school system before university wasn't seemingly designed too destroy every last ounce of a child's curiosity.

> My Chrome binaries are about 700MB on Mac and 500MB on Windows

That's kind-of the point though right? An application that has been say <700 MB for decades, suddenly deciding it'll take a multiple of it's size without asking seems pretty unreasonable, I think it's pretty fair to say the expectations for Chrome were set already.

It'd be similarly unreasonable for a video game that once took 50 GB, to suddenly decide to take 400 GB.

And actually to add, I've been finding myself going to nixpkgs first for reference on how to build and/or configure packages even outside of nix.

> I work on projects with terrible documentation because somebody pays me to do so or there is a significant potential that I can unlock.

I mean, I'd argue there is significant potential, but really, for me it's just easy because I've been doing it for 20 years, and documentation is always fundamentally worse than code in some important ways.

> If Nix project really cares about being competitive and adopt users, they have to document their stuff.

This is one of the good/bad things about OSS.. most users don't provide positive value to the project. So do they really want to adopt users? Shrugs but the project is certainly competitive.

You know, I used to agree, but what I realized, is I am a software engineer, and I'm used to working in large projects with source-code as the only documentation.

And that's what's great about NixOS, you just clone nixpkgs and treat it like any other underdocumented software you might work on.

It's like most things in software, if you constrain the problem enough, focus on the problems you actually have and make some smart choices early on, it can be a very modest lift on the order of a week or two for a 90% solution, but on the other end of the spectrum, it's a lifetime of work for a team of hundreds...

Except not in the USA. To bad the rings looks nice.

Copyright isn't some axiom, but to quote wikipedia: "Copyright laws allow products of creative human activities, such as literary and artistic production, to be preferentially exploited and thus incentivized."

It's a tool to incentivse human creative expression.

Thus it's entirely sensible to consider and treat the output from computers and humans differently.

Especially when you consider large differences between computers and humans, such as how trivial it is to create perfect duplicates of computer training.

Been looking into this for a while myself, very cool. It seems .nl has a lot of resources and support for this sort of thing. Any similar resources like coloclue in the San Francisco Bay Area? It seems confusing to find just a couple of U of rack space in SF that you could peer in and out of?

Great, so now I need a special editor plugin, and a compatible editor just to be able to properly view code?

No wonder why spaces "won"

Yes, this. Which the counter point is either, Don't align things, or use tabs for indentation, and spaces for alignment.

And maybe you can enforce no alignment, but that's a hard fight to win.

And as far as tabs for indentation and spaces for alignment, I've found no practical way to enforce this via tooling/linting. And a rule without enforcement becomes inconsistent, which is how we get files full of mixtures of spaces and tabs, which is how people get frustrated with tabs, and we decide to throw it all out.

And inevitably, that's part of how spaces "won"