[Feature] - Add support for powershell compilation

[razorblade23]

Is your feature request related to a problem? Please describe.
Not really ,just think it would be good feature to add

Describe the solution you'd like
If you could support generating powershell scripts as well as bash scripts, this would greatly improve usecase of this tool. We would be able to generate installer scripts or similar things for both windows and linux and mac...

[Mte90]

The problem on this that no one of the contributor uses Windows so it is difficult to start thinking of that.

[razorblade23]

The problem on this that no one of the contributor uses Windows so it is difficult to start thinking of that.

I feel the pain in this, i do not use Windows as well...

But i still belive that it would be great feature to add...

There is an abandoned project that tried to do this (in .sh and .bat, but the idea is the same) (https://github.com/batsh-dev-team/Batsh)

[ShalokShalom]

The problem on this that no one of the contributor uses Windows so it is difficult to start thinking of that.

The new version of powershell is cross platform.

[ShalokShalom]

Is your feature request related to a problem? Please describe. Not really ,just think it would be good feature to add

Describe the solution you'd like If you could support generating powershell scripts as well as bash scripts, this would greatly improve usecase of this tool. We would be able to generate installer scripts or similar things for both windows and linux and mac...

Did you consider using https://github.com/yassinebenaid/bunster

[Mte90]

The problem on this that no one of the contributor uses Windows so it is difficult to start thinking of that.

The new version of powershell is cross platform.

That's not enough just add another complexity layer because as example path on windows use the other \ symbol and testing from linux/osx is not the best real case.

To implement Windows we need someone that has time to do everything, the language is still evolving and we are still in Alpha stage after various release, focusing now the only devs we have in Windows is not the best option right now.

[ShalokShalom]

That's not enough just add another complexity layer because as example path on windows use the other \ symbol and testing from linux/osx is not the best real case.

To implement Windows we need someone that has time to do everything, the language is still evolving and we are still in Alpha stage after various release, focusing now the only devs we have in Windows is not the best option right now.

I am pretty sure Windows supports / now, and as I said, I think going the Go route is the best option.

The issue is not Windows, but simply another language, that's very different from bash.

That's it 🤷🏻‍♂

[ShalokShalom]

And we are not in Alpha, but in Beta.

[Mte90]

No, we are on alpha release. As project, we have chosen to go on different kind of release when 1.0 it will be ready :-)
Check the package versions https://github.com/amber-lang/amber/releases/tag/0.5.1-alpha

[ShalokShalom]

Sorry I misread that on the homepage, thanks for clearing that up.