August 2015 Archives
So there’s a Q and a Stack…
Well that would explain a lot about Javascript, aha. Today was characterized by trying to debug the same issue for an hour or so, and then learning about this fundamental structure. “But wait, why doesn’t it ever stop for input?! Javascript sucks!” Ok, in this case, PEBCAK.
So I guess I better get used to deeply nested function calls in these server-side scripts where user input is involved. But looking at tomorrow’s reading materials, client-side stuff has handlers and more natural asynchronous treatment, so I am looking forward to that. Although not so sure I’ll be as big a fan of JS’s “prototype inheritance.”
Also spent some time this weekend developing DiscoverIt more. Got it up at http://1.discoverit.arielity.net. Slowly chugging along on that.
Javascript…
the ellipses say it all.
I mean, it is just day 1. But it’s definitely hard getting used to its idiosyncrasies after Ruby. -0?! That must be the most creative number I’ve ever seen. And 3 equal signs is just too much. Typing out .equals is almost faster. At least it would be a little more english-y than a row of ===.
But. I do like the return of semicolons, explicit returns, and (kinda) explicit declarations. I know. I’m weird like that.
Reinventing the Wheel…
…using a wheel. Ha.
After the longest assessment we’ve ever had (2 hours!) this morning, we continued on to RailsLite, aka our introduction to handling server requests/responses. All I can say is that after just 1 day of it, I’m glad the Rails guys blazed that trail for me, haha. Even with several layers of abstraction built in already (Ruby, WEBrick, and some of the Rails functions), things that seemed simple before suddenly required serious thought. For example, parsing parameter hashes. Sure, the straightforward params[key] = value pairing was simple enough, but once you add in multiple layers of nesting ( params[key1][key2].[key_x] = value ), how to construct the proper nested hash?
More details…