snapdaddy

I did not get that at all. To me it sounds like she is coming clean with what she sees as the issues surrounding the project, including poor communication. I read that as, 'another problem we've seen is that people are unclear what it means to become a member of our organisation so we are working towards improving that.'

I initially read her apology and thought it was likely a response to an overblown situation that occurs because it's on the Internet and it's much easier to assume the worst of people's intentions.

I can imagine merging a PR I made that I imagined to be obvious and fine. I probably would have just said, 'oh yeah, sorry. I'll try not to do it again. My bad.'

But then again, that's probably why I'm not the leader of the .Net foundation :-)

One product (not yet mentioned here?) that seems to be getting overlooked is the trackball version of the split keyboard that you can mount on your armrests:

https://www.youtube.com/watch?v=fd4TipIRVlc

I've often sort of fantasized about that exact product. Now that I see it, I'm not sure how great it would be to facilitate working while laying back, but . . . it's certainly intriguing.

As someone who has been doing web dev for a long time, I find it interesting that I can understand the author's points, but that I don't relate to them at all.

For example, I agree that the angularjs to 'angular' transition was a bit wonky, but I don't understand having resentment or anger build up because I have to be a little more careful about how I craft search queries.

It feels like he's frustrated with a lot of things, and once you get in that mindset, each irritant takes on huge significance.

You don't start doing web dev because you really want to work with Angular, and I think that's the problem. You choose Angular because you think it will help you achieve an end-goal.

I suspect that he started working on a codebase that had already chosen Angular and he had no buy-in. In that case, problems become frustrations, rather than just 'things to learn'. For example, the documentation on the module system is pretty good. It covers the reasoning, shows a basic example, and then delves in for when you need more information: https://angular.io/guide/ngmodules.

Anyway, I enjoy working with Angular, but if something else works better for him, more power to him.

Thank you for somafm - that's pretty awesome

My argument against Haskell is that you are likely to build the wrong thing righter. My experience watching those around me is that it takes longer to write, but 'if it compiles, it's correct.'

The problem is that you probably don't know what you're building, so you would want a more flexible language.

I would lean towards python for all things data science, and go for infrastructure.