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

Re:Forgotten Language: Jorf could have been Python or Ruby (... by gecko on Tuesday October 13, 2015 @07:46AM (#10379749)

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 switching on uMsg and then casting lParam to the relevant struct. And this is considered one of the absolute best web frameworks available right now.

On the bright side, I suppose we can look forward to equivalents of message crackers, OWL, and MFC for React soon enough.

[ Parent | on HN ]

Re:Forgotten Language: Jorf could have been Python or Ruby (... by gecko on Tuesday October 13, 2015 @10:03AM (#10380508)

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/

[ Parent | on HN ]

Re:Forgotten Language: Jorf could have been Python or Ruby (... by nubianwarrior on Tuesday October 13, 2015 @12:07PM (#10381373)

Good article.

[ Parent | on HN ]

Re:Forgotten Language: Jorf could have been Python or Ruby (... by narrator on Tuesday October 13, 2015 @09:06AM (#10380105)

One thing that also reminds me of Windows culture in web development is the continuous reinvention of how to do the same old boring stuff.

[ Parent | on HN ]

Re:Forgotten Language: Jorf could have been Python or Ruby (... by mstade on Tuesday October 13, 2015 @07:55AM (#10379781)

Haha yes, this is so on point it makes me laugh and then want to cry a little bit. Also, they host conferences for these things, where the kool-aid is a-plenty.

[ Parent | on HN ]

Re:Forgotten Language: Jorf could have been Python or Ruby (... by neurohax on Tuesday October 13, 2015 @11:42AM (#10381184)

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

[ Parent | on HN ]

Re:Forgotten Language: Jorf could have been Python or Ruby (... by agumonkey on Tuesday October 13, 2015 @09:09AM (#10380128)

It kinda frightens me too. Partly because reinvention at that scale is a bit sad, partly because it took me far too long to unplug myself from the current trends thrill and realize it.

Somehow it also says something, whatever the underlying structure, local and native VS remote and abstracted (dom/js), some patterns keeps coming back over and over.

[ Parent | on HN ]

Re:Forgotten Language: Jorf could have been Python or Ruby (... by kaonashi on Tuesday October 13, 2015 @12:13PM (#10381415)

> 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.

[ Parent | on HN ]

Re:Forgotten Language: Jorf could have been Python or Ruby (... by mosburger on Tuesday October 13, 2015 @11:12AM (#10380988)

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

[ Parent | on HN ]