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

RubyWarrior - Bloc

bloc.io

Post reply on HN
Print view View original

51–60 of 70 posts

Re: RubyWarrior - Bloc

#52

Post by rschmitty »

hayksaakian wrote: post #29
phoboslab wrote: post #27

Earlier quoted context omitted.

If you buy it and don't like it for whatever reason, I can give you a full refund within the first month. That's easier for me to handle than a separate trial license.

I never thought about it that way. Totally stealing that idea.

have you really never watched TV with commercials about full refunds/money back guarantee?

Re: RubyWarrior - Bloc

#54

Post by StavrosK »

Oh goddamn, this is amazing. As someone who hasn't even seen Ruby code before, you could include a bit more on the syntax of conditional/loop constructs (if/while/etc), but it's amazing. I'll send this to my non-programmer friends right now.

Re: RubyWarrior - Bloc

#55

Post by nathas »

hayksaakian wrote: post #29
phoboslab wrote: post #27

Earlier quoted context omitted.

If you buy it and don't like it for whatever reason, I can give you a full refund within the first month. That's easier for me to handle than a separate trial license.

I never thought about it that way. Totally stealing that idea.

Just anecdotal, but we tried that for a while. Our signups and conversions are much higher with a trial. I work on a SaaS product.

Re: RubyWarrior - Bloc

#56

Post by jtms »

mmanfrin wrote: post #19

This is really great, but it would be even better if it showed where the error it's finding is located. I am getting some weird errors that I can't spot-find.

just play the original: you can use a the text editor of your choice, run in terminal, run with or without animation (nearly instant), and you have full debugging capabilities via puts. Also you get the rogue-like ascii graphics which is the original inspiration for the game.

Re: RubyWarrior - Bloc

#58

Post by jtms »

twelvechairs wrote: post #32

Nicely made. Some frustrations: - while, until, retry (and others?) not allowed. - not being able to see the class of something. Its more ruby style to do 'space.is_a?(Enemy)' than 'space.enemy?'. This would also help to build case statements rather than lots of ifs. - no 'print' or 'puts'. How am I supposed to know what 'look' returns when it never really tells me? - I prefer a single set of rules rather than adding…

- Not sure why they chose to disallow them here, but realistically #while loops are not commonly used in Ruby. Iterators such as #each or #map are far more idiomatic for Ruby. I still agree this is strange that they are not included here. The original allows all of Ruby https://github.com/ryanb/ruby-warrior

- Obfuscating the class is intentional... you are being given a limited set of "sensors" with which to interact with the world. Those are intentional rules by which to play the game.

- The original game is plain old Ruby run in the terminal and has full access to #puts or #print

- I think the point is to increase the complexity of the api slowly for those new to ruby and or programming in general. Not to beat a dead horse, but in the original there is the notion of epic mode where you do have access to all the rules and can attempt to run the entire tower with the same code.

Post reply on HN