TomasSedovic

Yep. It's really fascinating. MS is much more common (and well-known) so even though the diagnostic criteria can get quite complex (because you have to eliminate any other potential case), it's a well-trodden path.

So it's great that with anti-NMDA there is an actual singular test to determine this, but given it's so rare and little-known, getting to that point is very much not given :-(.

What BurntSushi said regarding these things being very nonspecific is absolutely true here.

E.g. Multiple Sclerosis can very well fit what you're describing, too. Commonly, there's a flare-up (we commonly use the term "attack" funilly enough)of some neurological symptoms (numb limbs, tingliness, diziness, vision issues are very common) that can last a few days/weeks and then mostly or completely subsides (until the next time).

Absolutely not suggesting that's what it was, just that it is what it could be too (or many other things — auto-immune diseases in particular can be really broad and nasty).

Sushi, I'm so glad you're doing better. Some of what you said (including just writing about it for awareness and sharing) resonates with my MS experience. I'm sorry you've experienced this and I hope things will keep looking up! <3

Thanks for this! I want to check the WEB-inspired approaches at some point, this is super useful.

The Markdown one seems interesting too.

I'll probably stick with this for stuff where there's some expectation of drive-by contributions (the tutorial has seen a bunch, it was one of the motivations behind this) because requiring additional tooling can often be a bar that's too high.

Agreed on the general literate programming note. I'm not sure I'll ever pick it up for something that doesn't have an obvious accompanying article/book to come with it, but if I ever write another tutorial or something, I'll definitely use it from the beginning.

But knowing what's out there is definitely important (and AsciiDoctor is extensible so these things could probably be added as plugins).

For what ever it's worth, anyone looking into starting a roguelike in Rust would probably do much better by folloving the The Bracket link above.

In addition to it being a pure Rust library (which does make a difference when you get started, but also when you try to distribute your game) it compiles to WebAssembly as well meaning you can use the same code to produce a game that runs on the desktop and the web. And the tutorial covers much more ground as well, including ECS for those interested.

And finally, both the tutorial and tcod-rs are barely maintained anymore. I try to address questions/fix serious issues from time to time, but the chances of this seeing any significant developments in the future are very slim. The RLTK stuff is actively maintained and developed.

(I'm not the OP, but I did write the linked post, the tutorial -- which is based on the classic Python+libtcod one as well as started tcod-rs)

I was about to say a similar thing. Yes, in a CS-sense anything you can do in one Turing-complete language you can do in any other Turing-complete lang. They almost certainly were not disputing that.

If you factor in the real world, the number shrinks as you get to things like performance, cross-platform support, ease of packaging and distribution.

But still, Nu could plausibly have been written in Assembly, C, C++, D, Go, Nim, Zig, Haskell and so on.

You would have lost some of Rust's strengths and weaknesses and imported another set (regarding the language, tooling, performance, ease of debugging and so on).

I took the comment to mean that as far as they (all people intimately familiar with the language, tooling and ecosystem) are concerned, this would be a trade-off that would be negative enough to not begin or finish the project in the first place.

I don't know what plans and requirements the Nu authors had. But for my own game (a roguelike written in Rust) the requirements on the performance, distribution, stability, ease of development and dependency management meant that Rust was (at the time) pretty much the only viable choice for me.

Could someone have written it in C? Sure. Could I have written it in C? Likely, yes. Would I have ever finish the game in C? Almost certainly no. For various reasons none of the other languages would have done in those circumstances, not really.

Human language is an imperfect method for transferring information and sometimes one trades off brevity for nuance.

I would consider stalking closer to "harassment" than "hitting on someone".

No worries! Pretty much everyone I talked to who was aware of the deal (online and off) thought the same.

These things are pretty complex.

(disclaimer: I work at Red Hat, not on any OS/distro)

This is a nitpick, but Red Hat did not get bought by IBM. What happened was IBM announcing the intention to buy Red Hat.

It's maybe a subtle, but possibly important distinction. Red Hat is still its own independent entity until the deal goes through (which means IIRC passing the board's approval, SEC and likely other stuff). This is expected to happen in late 2019 I believe, but it might still fall through.

This doesn't absolutely dispel any possibility of IBM's influence, but it should be very low/zero until the merger actually goes through. But I also don't know how all this works.

I haven't the faintest idea, which is why I asked aphextron. Indeed, until today I thought the Unreal Engine was FOSS, but seems to be just source-available. That said, didn't id Software / John Carmack release a bunch of engines under FLOSS licenses in the past?

There are many more or less serious potential explanations: not enough people care, it wasn't (or still isn't) financially feasible, the people able to develop AAA engines are actively against sharing source or ideas, there's an engine development cartel actively pushing against it to keep their revenue.

Or it might just be a social or historical accident -- we may just have been extremely lucky with Linux and projects on that scale will never come again.

Or maybe everyone thought it would be a great idea but they also thought it would never work and so no one seriously ever started an open source engine. Maybe Godot will be a true AAA engine that will surpass them all in a few years.

I don't know.

I was about to bring out Linux as a thing that according to your argument just isn't possible with open source.

But you've mentioned it yourself, so you presumably don't see that as a contradiction.

What do you think makes the complexity of Linux achievable with FOSS while the comparable complexity of a AAA engine not?