"Sohel Alam" <***@gmail.com> wrote
| Microsoft had done it earlier, such as 2003server, wsus, Good Old Start
menu, these were replaced and to replace Microsoft has done horrible things,
so that. What if to promote Powershell, Microsoft stops development of wsh.
| The first thing that comes to my mind that it will remove support for
client side scripts in internet explorer. And definitely it will take some
time, but if Microsoft decides it can stop wsh.
Yes. So what? MS have actually been playing
both sides for a long time now. They "deprecated"
VBScript in order to satisfy browser standards.
They've pushed PS, yet made VBS a standard
option for custom actions in MSIs. As far as I
know they're not actively developing WSH and
haven't for a long time. They want to cater
to corporate IT people, but they don't want
to encourage Windows programming or
customization any longer. WSH and HTAs
provide a way for businesses to write their own
software utilities on a limited budget, with limited
skills. PS doesn't really offer that. It only offers
admin. So it's hard for MS to stop supporting
WSH and HTAs.
I think the IE11/Edge situation is probably a
good example of where MS stands. IE is still
around because it's needed for HTAs and shell
integration. That supports the "legacy" (and
current) tools that businesses are using it for.
At the same time, they're pushing Edge as a
browser. Edge doesn't support most IE functionality,
including VBS. And in fact, IE11 doesn't support
IE functionality unlss an exception is set up for
specific domains. MS have broken IE already, for
It's a strange situation. They seem to be wanting
to sell Edge as standards-compliant and get Windows
10 people to use it. Yet it's not compliant. And it's
only supported on Win10. So it's not even a serious
contender as a browser.
Microsoft made a calculated decision to make Edge
Win10-only in order to sell Win10. Naturally that's
backfired on them, because Edge is not in any way
desirable. So it just ends up being yet another good
reason to avoid Win10.
In general, MS are moving toward the idea of
Windows being a kiosk-style service: You rent
software, buy services, and MS controls the
access. So in that sense, WSH is not something
they want to encourage. But like VB6, they can't
afford to break tools that businesses depend on.
I don't know what you mean by client-side script
in IE. Script in webpages is more common than
ever. But MS are phasing out support for VBS and
And as far as breaking things, they can only do that
at all on a future Win10 version. If you're dumb enough
to use Win10 as your OS of choice then you've
implicitly agreed to let Microsoft take you for a ride,
destination unknown. Losing WSH should be the least of
your worries. The rest of us have no such concerns.