,
6 tweets,
2 min read
Read on Twitter
<thread> My thoughts around #PowerShell's future... Being blindly optimistic about PowerShell's future or overly pessimistic about major team member's departure is actionless. There will always be a future. /1
And it is the choice you make from this point on determines how bright that future is. When you choose to use PowerShell; learn about its new use cases (e.g in the Cloud); talk about it; build new solutions with it; /2
show the solution to peers; participate and contribute on GitHub/StackOverFlow/Reddit/PowerShell.org, and always ask your vendor when they will actively offer PowerShell support, you brighten PowerShell's future. I am sure you can think of lots more. You might ask why? /3
While roadmap from Microsoft can provide peace of mind. It is only to a certain degree. We all know about the fine print about the unpredictable future. But your choices turn into realistic and actionable "data points" for both major participants: the community and Microsoft. /4
Now enters the time to allocate development resources based on real customer feedback and measurable data. Think about what happens when such data shows a growing user base, usage, and feature requests? /5
Making this trend a continual reality is especially critical now that the server software growth slowing down and modern cloud-native application on the rise. I hope this resonates with you. Keep on building... with PowerShell 😁. /6 </thread>
