Thread by @markekraus

Hi #PowerShell community. You may wonder where I've been these past few years. My blog is dormant. My PS PRs nonexistent.
What follows are my thoughts/feelings on recent community discussions.

1/11

This is not new. Neither the problems nor the promises. I sought in earnest to become a member PS Committee. Met with almost all of them. In the end, it did not happen. I'm mad, but not at any personal slight.

2/11

I'm mad because no one else was added either. Nothing sells me on previous MSFT employees on the committee being "community members."

3/11

I'm mad because I'm not alone in hitting roadblocks trying to make changes beyond the surface level.

4/11

I'm mad that hiring for #PowerShell advanced skills is impossible.
I'm mad the language isn't taken seriously by software engineers.

5/11

I'm mad that the community is over-saturated with 101 content and frilly shell decorations instead of fully leveraging .NET to solve interesting and/or complex computer science problems.

6/11

But, those are my feelings, and I kept them to myself as I silently backed away from a language and community I love and one I still think is better than most.

You don't need to care about my feelings.

7/11

But, maybe you should care that those who invest tremendous time improving their PS craft, learning the internals, building relationships, advocating the language.. are fed up seeing that effort leading to dead ends.

8/11

Maybe you should care the governing body for the language that your career depends on seems incapable of prioritizing language needs over business needs.

Because you may be next reaching that dead end.

9/11

It's senseless. The language could stand against Java, Python, Go, C#. It could have a sizeable pool if hireable experts. It could be taken seriously by software engineers. But, ask yourself why that's not the case.

10/11

So what's my solution? Fork? Create something new? Abandon #PowerShell for career-building languages and encourage others to do the same? I still don't have the answer, but I'm no longer content to stay silent and do nothing.

11/11

In the meantime, several of us in the community are in the early stages of investigating what it would realistically take to liberate the language and give it back to the community. It's no simple task, but perhaps worth the effort. No promises, though. No "public" details yet.