News for hackers. Stuff that matters.

skilldrick

Re:Easy 6502 - Learn the 6502 Assembly Language on Sunday July 08, 2012 @07:44PM (#4216089)
Hey, thanks. Yeah, I haven't yet fully explained all of the simulator.

0xfe is a random number - a new random byte is generated on every instruction.

0xff contains the ASCII code of the last key pressed.

My simulator is adapted from the one at http://6502asm.com/beta/index.html - that has a help screen with some more info. I mostly cleaned up the (atrocious) JavaScript and added a memory monitor and disassembler (and implemented a few instructions they'd left out).

Re:Art vs. Engineering on Saturday March 03, 2012 @09:37PM (#3661758)
> A friend of mine used to refer to code that was more art than engineering as “clever.”

I see "clever" code as the opposite of good engineering and art. Beautiful code isn't "clever". An elegant engineering solution isn't "clever".

Re:Introducing a new data structure, streams, in Javascript on Sunday September 11, 2011 @12:30PM (#2984077)
> As someone who conjured this exact thing up in another language after reading SICP

Me too! http://jsfiddle.net/skilldrick/vT2mC/

I didn't get very far with it though - the combined issues of JavaScript's lack of tail-call optimisation and its verbose lambda syntax made building streams to painful.

This looks like an interesting approach, though you'll never get around JS's heavy lambdas (unless you use CoffeeScript or something).

Re:Making inheritable objects in JavaScript without objects on Monday August 15, 2011 @06:50AM (#2886247)
Cheers. I guess you could call it an internal DSL, but I wouldn't call it an interpreter - all it's manipulating is the arguments object, it doesn't manipulate any strings. I'm sure string manipulation isn't the only thing that identifies an interpreter, but it doesn't seem like that to me.
Re:Understanding the Ruby object model on Tuesday August 09, 2011 @11:06AM (#2864276)
I'd recommend coming back and reading it when you've learned a bit more Ruby then. If you've "just started" then you probably don't yet have the experience in Ruby to understand what it means.

I understand that at a first glance this looks like basic stuff that doesn't explain anything useful, but with a bit more experience you'll see that it's fundamental to understanding how Ruby will react in certain situations.

Re:Understanding the Ruby object model on Tuesday August 09, 2011 @10:41AM (#2864167)
Haha I love it :)
Re:Understanding the Ruby object model on Tuesday August 09, 2011 @09:07AM (#2863824)
It's a bit like saying "I see a lot of women have jobs these days - does that mean that feminism is more than just a fad?" You're not going to get any helpful responses if you ask something inflammatory (and I think it shows maturity that no-one's flamed you).

Anyway, what would you gain from asking a bunch of Ruby developers whether Ruby is "just a fad"? This is hardly the best venue for that question.

Incidentally, I didn't downvote you, just thought I'd try to explain why nobody responded to you.

Re:Understanding the Ruby object model on Tuesday August 09, 2011 @08:06AM (#2863695)
> Note that this is a basic explanation, and glosses over higher-level concepts like the eigenclass/metaclass (I’ll leave that for a later post).
Re:Understanding the Ruby object model on Tuesday August 09, 2011 @05:57AM (#2863478)
It's essential to know this stuff to really understand how Ruby works. If you want to know which method is going to get called then you need to grok the object model. Classes in Ruby are much more than "fancy structs with allocation", and thinking of them in that way means you'll be losing out on a lot of Ruby's power.
Re:You should learn to type (properly) on Monday June 20, 2011 @05:03AM (#2673449)
Completely OT, but when I saw your comment, I new I recognised your handle, but couldn't think why. I finally worked it out though - you answered my first ever Stack Overflow question in 2009! http://stackoverflow.com/questions/418465/is-a-preference-fo...
Re:You should learn to type (properly) on Saturday June 18, 2011 @04:04PM (#2669399)
What an arrogant comment. If you'd read the post, you would have seen that I said it's often not the bottleneck, but there are times when you need to get stuff out of your head as quickly as possible.

This "typing is not the bottleneck" is such a cliché - I nearly wrote about it in the article. It presupposes that programming is some kind of pipes-and-filters activity where we're thinking and then typing and then compiling. I don't know about you, but when I'm programming I work in different states. Sometimes it actually is about getting the code into the computer as fast as possible. Not all the time, but sometimes.

Re:You should learn to type (properly) on Saturday June 18, 2011 @03:53PM (#2669380)
Thanks. I'm on Ubuntu and did

    sudo apt-get install gtypist
Re:You should learn to type (properly) on Saturday June 18, 2011 @03:41PM (#2669356)
> any advice?

GNU Typist, and real discipline. Force yourself to do it their way.

Re:You should learn to type (properly) on Saturday June 18, 2011 @03:39PM (#2669350)
I don't think not being able to touch-type will get you fired (if you can type fast anyway), but I don't agree that "it doesn't matter".
Re:You should learn to type (properly) on Saturday June 18, 2011 @03:38PM (#2669345)
It's probably worth clarifying here that touch-typing is different to typing-without-looking-at-the-keyboard-(much). As knowtheory said, many presume that they're the former, when they're actually the latter.

Older »