alelefant
> Did we really need all those features?
If you don't need them, don't use them. I've found the new features to be great. nameof, string interpolation, property initializers, exception filters, static imports, null propagator. And if you haven't used the language in awhile going back to 5.0 the async await features are fantastic. 7.1 introduced async Main which we've started using in console apps. I use all of these features every day.
> I would love it if I saw a new version of a language come out and it removes language features
Why, exactly?
Here's an excerpt that you might find interesting: http://www.eagleman.com/sum/excerpt
When you refer to the debug tools, are you referring to the Chrome extension or something else?
Jake: Well, maybe I don't use my exclamation points as haphazardly as you do.
Elaine: You don't think that someone having a baby warrants an exclamation point.
Jake: Hey, I just chalked down the message. I didn't know I was required to capture the mood of each caller.
Elaine: I just thought you would be a little more excited about a friend of mine having a baby.
Jake: Ok, I'm excited. I just don't happen to like exclamation points.
Given the revelations from the last few years, how many of you would agree that carrying out an illegal plan like this is safer online?
Anytime I visit the doctor, they always have Epic up on the computer. Granted, I know I'm living in the city where it's made, but it's used across the country. I even had a friend who moved out West and planned on just finding a random job, and it ended up being Epic to help install the software at health clinics in Washington.
I don't know their full stack of offerings, but I used some of their treatment billing software when I worked at a health care insurance company during my college summer vacation. It worked just fine, but certainly had an old software feel to it. I don't know if they offer any cloud offerings right now (their website sure doesn't make me think they do), but if they do I find it hard to imagine it's anywhere near as powerful as something that Salesforce could offer right out of the gate. I work with Salesforce every day where I work now and I have to admit it's very well done, although they certainly fall short in some areas.
I don't particularly care about Salesforce or Epic so long as my data is safe, but I'm interested to see how it plays out since it impacts my community.
Back on topic though, this was another good read. The debate about how to cook it was hilarious:
He insisted that there was an art to cooking octopus correctly. His includes a Neapolitan trick: a wine cork in the cooking liquid. Éric Ripert and Harold McGee dismiss this step as mere legend—to which Pasternack gleefully responds, “Éric Ripert is full of shit!”
I oddly think about this a lot without really recognizing it. It may sound silly, but to me what makes the difference is the event itself. Being a tourist at a museum, natural landmark and so can feel so much different than being a tourist at a local watering hole. Taking a natural landmark as an example, I view it as if the locals can't claim it as their own and it's meant to be shared and interpreted by the world. Museums are practically enablers for tourism so locals can't be upset about that.
But, when it comes to a local food or drink joint, tucked away in a neighborhood of sub-cultures, I can't help but feel as if I'm intruding. To focus on the experience at a place known as being "best authentic food X in city Y" or "great neighborhood bar, one of the best in city Y" is to focus on the brick and mortar, the customers, the employees. Given just the right media attention or online review a place can become a tourist petri dish and the atmosphere can be entirely thrown off. Although, there sits the problem as without at least some attention I wouldn't have known about it.
That probably comes across as selfish, but it's not about me. There's many cases where a place becomes successful, patronage changes, ownership ends up changing hands a year or two later, and the place isn't what it used to be. I think there is something to be said for protecting local sub-cultures which is what I viewed the authors point to be.
"To be a mass tourist, for me, is to become a pure late-date American: alien, ignorant, greedy for something you cannot ever have, disappointed in a way you can never admit. It is to spoil, by way of sheer ontology, the very unspoiledness you are there to experience. It is to impose yourself on places that in all noneconomic ways would be better, realer, without you. It is, in lines and gridlock and transaction after transaction, to confront a dimension of yourself that is as inescapable as it is painful: As a tourist, you become economically significant but existentially loathsome, an insect on a dead thing."