Welcome to the Lounge

The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.

Ah, there's so many frameworks to choose from in the javascript world. Angular does look good. I am totally unconvinced that NoSQL databases are actually necessary and even helpful, so I'll be interested to hear more about your thoughts on Mongo.

Christian Graus wrote:

where you can pass a code snippet as a method parameter,

Lambdas are the cat's meow, I use them all the time nowadays. Continuation functions are really cool too and absolutely necessary to understand when working in functional programming languages.

But it is really nice for one line conditionals and a great example of passing a code snippet as a method parameter and using extension methods.

staticbool Then(thisbool b, Action f)
{
if (b) { f(); }
return b;
}

Christian Graus wrote:

How does everyone else find time to keep up to date ?

Mostly I wait until someone pays me to do something that requires a particular technology. Otherwise, my time is one of the few things I "own" and therefore spend a lot of it investigating my own interesting ideas and technologies.

Yeah, that looks really cool. The truth is, I am doing some work in Angular and Kinetic, and so that's where my time goes. Like you, I am aware, but I need a reason to dig in to really learn it. I do enough C# that I feel like I should learn it, either way, but I've not managed to do so, yet.

I agree on NoSQL, I suspect it's the new thing that people feel they 'need' when they don't. I've heard of people start with NoSQL and realise they need SQL to do what they want. But, I want to know enough about it that if someone wants to pay us to use it, I can put my hand up and say I know it.

The coolest thing I've done with Action and Func is to put the call that processes a message into an Action lambda expression and then, depending on whether I'm animating the "mailing" of the message or not, the code either calls the Action or packages it up as part of what the animation code needs to know (sender/receiver and message.)

Then, when the animation code is complete (the message is received), the animator simply calls the Action and it executes at that point. The crazy and cool thing is, the animation code doesn't know and doesn't care what the action is, it just gets done when the message. And it's neat because it all works across assembly boundaries, there's no need for the animator to know about the executing code's namespaces, etc.

Anyways, I ramble, because it was a really good example of getting code to be more flexible in its behavior. If you have watched any of the HOPE[^] videos, you'll see what I mean.

Here's[^] a great article on computation expressions and continuations in C# and F#. It's well worth sinking one's teeth into.

Al Gore invented the Internet, but Pete invented Al Gore.Pete doesn't debug code, if there is an error the computer is wrong and it knows it!Pete does not use a scrollwheel. The scrollbar knows it better damn well move when Pete wants it to.Pete has counted backwards from infinity, negative one times!Google uses Pete for information.

Pete always knows where he is and how fast he is going.Pete knows if the cat is dead.Pete doesn't have to await for an async call to complete.Pete writes C# code using XAML.Pete renders a WPF Window on the Console Window.