A Stroll Around C# 7

C# 7? There are 7 seven versions? Seriously? Who needs 7, because we’ve seen how well 7 of anything has worked out. Take those movies where the main character, who has serious daddy issues, runs around swinging a really large glow stick with his two pet robots trying to “save the galaxy”. They enthusiastically announce, “Hey come see part 7 in the series!” and then BAM they kill off one of the major characters, by his emo son no less, and we were all sitting in the theatre like, “What happened?” and who’s to say C# 7 isn’t going to do the same thing? It’s going to lure us in with a false sense of childhood security and then smack, “we broke your favorite feature!” and I don’t think I can handle that. I don’t need to suddenly find out that C# 7 suddenly axed Reflection or some other cute fluffy feature that’s my security blanket for keeping bad requirements away, so maybe I should stop with 6. It would be a nice conclusion for the language. Throw in a snappy ending credits song and maybe a space explosion, and people could be really happy ending C# there.

Let’s be serious though. You really want to see how the story continues, and maybe they didn’t remove your favorite go to code Swiss army knife after all. Stopping at 6 would be nice, but you don’t want to live in the past. You want to see how the story continues. It’s like eating that second to last piece of bacon and deciding that even though you really want the next one you’re “satisfied” with what you have. SAID. NO. ONE. EVER. You want to know if that next piece of bacon will make you even MORE satisfied than before. Is that gluttony? Maybe, but it is a gluttony of porky awesomeness, and if you don’t get it, someone else will, and then you’ll be strolling around secretly screaming at that person, “You will rue the day for taking MY BACON!” (Rue the day? Who talks like that?) Maybe it would be better if you did come, and claim that last piece of bacon for yourself.