Live data from Hacker News

GameShell: A game to learn or teach the Unix shell

github.com

61–69 of 69 posts

Re: GameShell: A game to learn or teach the Unix shell

#63

I saw many games trying to teach programming, but never heard of any of them gaining significant popularity. I wonder why? I guess "play games instead of reading books" idea attracts audience with low motivation?

We all have different ways of getting motivated and learning. You shouldn't yuck other peoples' yum. I've definitely heard of some games that teach programming skills getting popular. For example, https://flexboxfroggy.com/ http://www.flexboxdefense.com/ for teaching css layout. https://www.freecodecamp.org/ isn't marketed as a game, but absolutely feels like one when you are going through the program. https://www.ha…

I learned about C with a book called "Head First C" about two years ago and it was amazing. It was kind of like a game, written in order to be fun. I learned so much in that book, about system calls, signals, file descriptors, processes, pipes etc.. it was amazing. I also used the AWK Programming Language about a year ago and it was amazing too. It was definitely a challenge to keep reading the book because i think I've become so used to instant gratification but books require multiple reading sessions... I have pretty strong ADHD so i actually feel really accomplished just by finishing and working through a (seemingly simple) book. :)

Re: GameShell: A game to learn or teach the Unix shell

#64
post #52

Earlier quoted context omitted.

Their first line is a quote from the README.

Ah, ok. In any case I was TA with Pierre teaching that class at Chambéry this semester, to run the gamesaves from the student without being too worried about my files i just ran the thing inside a bubblewrap bash session: bwrap --dev /dev --ro-bind /usr/bin /usr/bin --ro-bind /usr/lib /usr/lib --symlink usr/bin /bin --symlink usr/lib /lib64 --unshare-user --uid 256 --gid 512 --bind TP2 /TP2 /usr/bin/bash

Insert bwrap in lieu of docker and its the same thing. What the hell is bwrap?

Re: GameShell: A game to learn or teach the Unix shell

#65
post #28

If you dont like running foreign code on your machine, you can run docker and then run foreign code on your machine. Did anyone else catch this in the article? Doesn't it seem like this makes it even more likely to get infected? No one understands Docker in entirety let alone this random game. It seems like all this stuff should just be automatically done behind the scenes and yet it's not.

> It seems like all this stuff should just be automatically done behind the scenes and yet it's not. ...what stuff?

Whatever Docker is doing that your browser/OS/hardware isn't.

But that's the point. I have no idea what any of this stuff is actually doing. I'm just crossing my fingers that what I run isn't detrimental to my system. There's no actual understanding behind any of it anymore.

Re: GameShell: A game to learn or teach the Unix shell

#66
post #15

Earlier quoted context omitted.

Quoted post unavailable.

It may benefit you to read the HN Guidelines: https://news.ycombinator.com/newsguidelines.html , specifically the "In Comments" section. > Be kind. Don't be snarky. Have curious conversation; don't cross-examine. Please don't fulminate. Please don't sneer, including at the rest of the community.

It does not benefit me: you mistake niceness for kindness. There is little I can learn from you and your guideliness when you yourself cannot tell which is which.

Re: GameShell: A game to learn or teach the Unix shell

#67
post #52

Earlier quoted context omitted.

Ah, ok. In any case I was TA with Pierre teaching that class at Chambéry this semester, to run the gamesaves from the student without being too worried about my files i just ran the thing inside a bubblewrap bash session: bwrap --dev /dev --ro-bind /usr/bin /usr/bin --ro-bind /usr/lib /usr/lib --symlink usr/bin /bin --symlink usr/lib /lib64 --unshare-user --uid 256 --gid 512 --bind TP2 /TP2 /usr/bin/bash

Insert bwrap in lieu of docker and its the same thing. What the hell is bwrap?

Does no one think this is a problem? When even software engineers can't keep up with all these things, and your average citizen is completely clueless about how even the most basic of computer things work, do we not realize we are like the boiling frog in the pot?

Re: GameShell: A game to learn or teach the Unix shell

#68
post #16

Earlier quoted context omitted.

You are not supposed to "identify" anything on UNIX-like operating systems; that is what the file(1) command is for, specifically, especially so since the entire concept of UNIX is that everything is a stream of bytes . Attempting to manually manage files in this way defeats the purpose of the OS abstracting it away for the user; and the users of your executable should not have to care what your executable is written…

As someone who did grow up on Windows and still uses it regularly alongside Linux, I want to respond to this comment just to play the Devil's advocate (i.e. infuriate you). > especially so since the entire concept of UNIX is that everything is a stream of bytes. I consider this an archaic, anachronistic, ancient, outdated, primitive (they all mean the same thing; I just used a thesaurus to really drive home my point)…

This is a fantastic response, honestly. I'll add that your last point about how different users interact with their systems differently is especially relevant for the longevity of open operating systems. General users coming over to Linux who do not have extensive knowledge with computers beyond Windows will primarily be using graphical interfaces on their desktop, and making that process confusing for them by not accommodating that will quickly make them give up on the whole thing. If we wish to keep the software alive with a userbas then it's actually extremely important to allow and support things like this that are more intuitive.

Re: GameShell: A game to learn or teach the Unix shell

#69
post #68

Earlier quoted context omitted.

As someone who did grow up on Windows and still uses it regularly alongside Linux, I want to respond to this comment just to play the Devil's advocate (i.e. infuriate you). > especially so since the entire concept of UNIX is that everything is a stream of bytes. I consider this an archaic, anachronistic, ancient, outdated, primitive (they all mean the same thing; I just used a thesaurus to really drive home my point)…

This is a fantastic response, honestly. I'll add that your last point about how different users interact with their systems differently is especially relevant for the longevity of open operating systems. General users coming over to Linux who do not have extensive knowledge with computers beyond Windows will primarily be using graphical interfaces on their desktop, and making that process confusing for them by not ac…

No post body was provided.
Post reply on HN