It looks nice for very simple screen scraping. On the other hand, simple screen scraping doesn't require much coding anyway. LINQPad is a superb environment for playing with that.
Congrats on your new job, Charles!
Your regular C9 interviews will be missed.
It's a crappy headline but a fun video.
Regardless of what one may think of Gilad Bracha's computational theology (or pragmatic lack thereof), his performances are as close to stand-up as one can expect from anyone dealing with this subject matter. Simply put, he has a great sense of humor that makes his presentations worth the watch on that merrit alone.
This time he discusses ideas from functional programming.
I'm really looking forward to hearing more about the project. With so many man-years invested it it, hopefully it will go beyond research.
*snip*If all 512GB isn't usable then for all practical purposes, the drive isn't really 512GB. It makes no sense to count the part that isn't actually usable.
So make the actual size of the hard drive slightly more than 512GB so that the *USABLE* capacity is 512GB. That would be the fair and honest thing to do.
Quite right. All else is frankly an excuse - whether delivered apologetically or not.
*cough* topic *cough*
What do you guys think about the proposal to declare local variables as part of expressions?
int.TryParse("123", out int x);
I find this excruciatingly ugly - but understand the desire for compactness. But then why not solve this at the API-level with nullable primitive types?
var x = int.ParseNullable("123"); // x : int?
var x = int.ParseNullable("123") ?? 0; // x : int
I guess if you have to interact with lots of methods that use "multiple return values" through out parameters rather than tuples or other structures then this saves you pain.
Most of this stuff appears to be minor syntactic sugar - nothing major like async/await. I think Lucian once spoke about async methods returning multiple values. Perhaps something a la this: