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

Forgotten Language: Jorf could have been Python or Ruby (2005)

ralsina.me

Post reply on HN
Print view View original

61–70 of 74 posts

Re: Forgotten Language: Jorf could have been Python or Ruby (2005)

#61

Post by mosburger »

gecko wrote: post #44
brusch64 wrote: post #23

Earlier quoted context omitted.

Regarding the "Windows culture": WinProc programming was indeed pretty horrible. Didn't really program a lot in WinProc - but I've cut my teeth with MFC which was supposed to make it better. They broke down the big switch in the program and created classes (the c in MFC) and macros. The VCL of Borland was more abstracted, but we've used MFC. I am pretty happy that I don't have to do this any more. When I started with…

You know what's ridiculous? I totally agree that WndProc was horrible. But the web community is now reinventing it so directly that all I can do is bang my head repeatedly on my desk. Have you seen Facebook's Flux/Dispatcher framework, for example? The Dispatcher is usually a massive switch statement that takes a single argument, which will be a record field that corresponds with the event type. It's exactly like swi…

Also, incidentally, how Java 1.0 handled events in its windowing toolkits IIRC.

Re: Forgotten Language: Jorf could have been Python or Ruby (2005)

#62

Post by neoeldex »

V-2 wrote: post #47
z3r0d4v3 wrote: post #26

Earlier quoted context omitted.

whoa - ty 4 the link man, i just tested it and got ethically blewn away! screener: http://mnml.is/hn/jorf_on_war.png

Anyway, it's interesting that he singled out nuclear weapons, but eg. landmines would be just fine

I always figured landmines, and ammo are considered chemical weapons

Re: Forgotten Language: Jorf could have been Python or Ruby (2005)

#65

Post by neurohax »

gecko wrote: post #44
brusch64 wrote: post #23

Earlier quoted context omitted.

Regarding the "Windows culture": WinProc programming was indeed pretty horrible. Didn't really program a lot in WinProc - but I've cut my teeth with MFC which was supposed to make it better. They broke down the big switch in the program and created classes (the c in MFC) and macros. The VCL of Borland was more abstracted, but we've used MFC. I am pretty happy that I don't have to do this any more. When I started with…

You know what's ridiculous? I totally agree that WndProc was horrible. But the web community is now reinventing it so directly that all I can do is bang my head repeatedly on my desk. Have you seen Facebook's Flux/Dispatcher framework, for example? The Dispatcher is usually a massive switch statement that takes a single argument, which will be a record field that corresponds with the event type. It's exactly like swi…

I am creating this small library that can be described as "jquery for streams of heterogeneous schemaless messages" which pretty much could be a lean replacement for the ugly switch at flex-like architectures. You can sneak a working barebones, very early preview at https://github.com/constructo/neurobus

Re: Forgotten Language: Jorf could have been Python or Ruby (2005)

#66

Post by V-2 »

hobs wrote: post #59
V-2 wrote: post #39

Earlier quoted context omitted.

Thanks for shedding some light on it. Personally I quite like the sound of English (my native tongue being Polish), and "jorf" doesn't sound to me any worse than Jeff or Ralph :) but obviously I don't have the same sensitivity as native speakers.

Interesting you say that, you may not know that Ralph is also slang for "to vomit". I don't think "to Jeff" is anything yet.

Haha no I didn't. I just tried to think up an example of something phonetically similar but innocent, but there you go. Bad for Ralphs I guess.

We've got an old idiom that subtitutes vomiting for "going to Riga" (the Latvian capital). Not really aimed against Latvians, it just plays on certain phonetic similarity of Ryga and "rzygać" (to puke). Different languages, same bag of tricks.

Re: Forgotten Language: Jorf could have been Python or Ruby (2005)

#67

Post by nubianwarrior »

gecko wrote: post #56
gecko wrote: post #44

Earlier quoted context omitted.

You know what's ridiculous? I totally agree that WndProc was horrible. But the web community is now reinventing it so directly that all I can do is bang my head repeatedly on my desk. Have you seen Facebook's Flux/Dispatcher framework, for example? The Dispatcher is usually a massive switch statement that takes a single argument, which will be a record field that corresponds with the event type. It's exactly like swi…

And the comment is now a blog post with more context for those who were lucky enough never to write raw Windows code: http://bitquabit.com/post/the-more-things-change/

Good article.

Re: Forgotten Language: Jorf could have been Python or Ruby (2005)

#68

Post by neurohax »

Johnny_Brahms wrote: post #37
z3r0d4v3 wrote: post #28

http://mnml.is/hn/jorf_on_war.png

Meh, that is a bit like the iTunes EULA. You are not allowed to use it to make weapons of mass destruction. Maybe it is removed by now, but I found it hillarious back in the day.

Well.. Reaggeton music qualifies as a psy-weapon of mass destruction.

Re: Forgotten Language: Jorf could have been Python or Ruby (2005)

#69

Post by kaonashi »

gecko wrote: post #44
brusch64 wrote: post #23

Earlier quoted context omitted.

Regarding the "Windows culture": WinProc programming was indeed pretty horrible. Didn't really program a lot in WinProc - but I've cut my teeth with MFC which was supposed to make it better. They broke down the big switch in the program and created classes (the c in MFC) and macros. The VCL of Borland was more abstracted, but we've used MFC. I am pretty happy that I don't have to do this any more. When I started with…

You know what's ridiculous? I totally agree that WndProc was horrible. But the web community is now reinventing it so directly that all I can do is bang my head repeatedly on my desk. Have you seen Facebook's Flux/Dispatcher framework, for example? The Dispatcher is usually a massive switch statement that takes a single argument, which will be a record field that corresponds with the event type. It's exactly like swi…

> The Dispatcher is usually a massive switch statement that takes a single argument, which will be a record field that corresponds with the event type.

Stores have the switch, and you're supposed to break those up along model lines. In most the apps I've written, they never get beyond 4 or 5 branches.

Post reply on HN