HNHacker News
TopNewBestAskShowJobs

KaeseEs

704 karma · joined August 8, 2010

A Cheez-It made self aware via MooseX::Declare
submissionscomments
KaeseEs··on This is engineering: Army Jeep torn apart and reassembled in 4 minutes
It did have a radiator, you can see it getting put back in at about 3:18
KaeseEs··on Slaying dragons with git, bash, and ruby
I noticed he uses the env trick for his shebang for ruby. I was first acquainted with this for Perl, and I've since more or less stopped using it since it caused about as many problems for me as it solved (funny thing, systems with the perl binary in a silly place sometimes have env in the 'wrong' place too :/). I'm kind of surprised that it made the jump to Ruby, since to my knowledge it came into use after the Ruby community had already finished borrowing from Perl that which it was going to borrow.
KaeseEs··on Ask HN: Is Perl dead?
He's referring to Moose, which is an insanely good object system, which wasn't prevalent at all 18 months ago but is nearly de rigueur in all but a handful of cases today. It's a mashup of CLOS, Perl 6, Smalltalk and a few other things that remains consistent, Perlish and intuitive. It's also crazy extensible - just look at the MooseX namespace on CPAN to see what I mean.
KaeseEs··on Forth versus C
My main beef was with the last bit - ""Infinite length" files allow sloppy, disorganized thinking and bad factoring. Definitions become longer without the discipline imposed by the 1K block boundaries. The tendency becomes to write a 20K file, or worse: a 20K definition." This reeks of Stackholm Syndrome, where having toiled under the limitations of a system for some time and developed workarounds and jerry-rigs* to get by them, one begins to view them as strengths for no other reason than their familiarity.

If nobody thinks like this any more though, congrats on escaping what is normally a sure route to smug weenie-ism.

*Eg. later in the same section, Brodie suggests defining constants associated with block numbers as a sort of ersatz filenames

KaeseEs··on Forth versus C
Regardless the merits of the language itself, the culture of Forth has some serious issues that cause me to doubt that a skilled Forth programmer truly has a development speed that is a multiple of that of a skilled C programmer. Cf. this advice from Thinking Forth:

"Some Forth practitioners advocate storing source code in variable-length, named text files, deliberately emulating the approach used in traditional compilers and text editors. This approach may become more and more common, but its usefulness is still controversial.

Sure it's nice not to have to worry about running out of room in a screen, but the hassle of writing in a restricted area is compensated for by retaining control of discrete chunks of code. In developing an application, you spend a lot more time loading and reloading screens than rearranging their contents.

"Infinite length" files allow sloppy, disorganized thinking and bad factoring. Definitions become longer without the discipline imposed by the 1K block boundaries. The tendency becomes to write a 20K file, or worse: a 20K definition."

(from page 144 of the 2004 edition)

KaeseEs··on Announcing the inaugural Code Quarterly Code Challenge
While I'm a bit dissatisfied with the XML bit, any excuse to write a parser is a good one for me! I haven't given the spec for their Markup language a close reading yet, but this seems like as good an opportunity as any to fool around with a precedence-climbing recdesc approach. I also like their approach to the [non-?]competition generally - commenting on interesting entries rather than just ranking them.
KaeseEs··on GCC - 'We make free software affordable'
Given your experience with both, what would you consider the pain points of getting a grasp of each when looking to contribute? I know when I looked at GCC, the mix of custom manual memory management (gcc_free and pals), semi-automatic management via obstacks, and automatic management via garbage collection seemed baroque and frightening.
KaeseEs··on GCC - 'We make free software affordable'
While LLVM isn't a fork and doesn't quite fit the model of the gnumacs/xemacs, gcc/egcs, glibc/linuxlibc &c. from years gone by, I do hope the new competition in the free compiler space will spur improvement and innovation in both projects. I would almost expect not only the state of free compilers, but the health of GCC itself, to be better with a viable competitor in LLVM and clang than without.
KaeseEs··on Leaving Oracle
Sun had a ton of chip designers, I'm skeptical quantity was the problem with respect to their SPARC development.
KaeseEs··on The Great Vim / Textmate Debate: Opinion #56 - How to make Vim more accessible
Does vimtutor not come with MacVim? It would have alleviated some of his issues.
← PreviousPage 6 of 6