Thanks for the feedback! The script will download the latest version of Pulumi, extract it to ~/.pulumi/bin and then try to add that folder to your .bashrc or .bash_profile.
You should be able to read the source of the script directly at https://get.pulumi.com/ or even download it yourself, inspect it and then decide if you want to run it or not. You can also follow the manual install instructions which are listed a little further down on our install page at https://pulumi.io/install/, if you want total control over where it is installed.
I also just opened a pull request to our docs website: https://github.com/pulumi/docs/pull/430 to explain in a little more detail what we're doing with the scripts.
You'all spoke and we've listened. I've dusted off my old very barebones prototype, pushed it to a branch at https://github.com/pulumi/pulumi/tree/ellismg/add-dotnet, and will be hacking on this over the course of the next week. Collaborators are welcome (please do join the #contribute channel in our slack at https://slack.pulumi.io). And watch the branch, I expect we'll have something usable in a few days and it might help folks who are interested in supporting other languages with Pulumi.
In the meantime, as someone who had to learn TypeScript to start using Pulumi when I started here, I do encourage you to look at some of the examples we have and play around with them. It's actually a pretty nice language and with VSCode it's pretty easy to get started.
> I wonder what were the reasons, besides popularity contest.
(Disclosure: I'm a member of the Pulumi team).
Strictly a timing issue. We brought TypeScript/JavaScript online first and most of our focus was there while building up the supporting tooling. Fortunately, the design of the system makes it pretty easy to add new languages (we've since then done Python and Go). Most of the team is ex-.NET folks and I've been itching to build out the .NET support. Now that we've launched, it will at least become /my/ spare time project.
I'll be really excited when we have it well. Do keep your eye out!
FWIW (I work on the .NET Team and I wrote the mirror we use to keep TFS and GitHub in sync). When we started the project we maintained a mirror which kept our GitHub repository and internal TFS branch in sync. After a while, we decided that trying to maintain this was more harm that it was worth (the internal TFS branch used a completely different build system and there were other interactions between code which had been open source and code that hadn't that meant our internal branch was on the floor every few days), in addition it meant that we were carrying around a bunch of effectively dead code in the source tree.
We still do mirror some code (mainly the JIT) into TFS to make it easier to share code with the Desktop in an automated fashion. However, for the rest of the code (e.g. the VM and BCL), if there are improvements we want to bring back, an engineer will just port them manually.
For what it's worth, I'm the one of the folks that designed the original tuple class (the reference type, System.Tuple, that shipped before hand).
At the time, we picked one based indexing because we felt it sounded more natural when spoken allowed (mirroring saying something like: This is the first Item in the tuple).
I would expect that the design bled over into ValueTuple, which looks very similar to the reference version, except, of course, it is a value type.
In addition to backend compilation for managed code, Phoenix could continue to be used to compile C/C++ code. One of the things the team did was continue to compile the Windows codebase to compare Phoenix and UTC (for both functional and performance reasons, IIRC).
Disclaimer: I was on the Midori team for a few years but did not work on Phoenix itself.
At the end of every Bing TV add (at least on US Television), the spoken tag line is "Bing, the decision engine from Microsoft" (combined with the Microsoft logo in the corner), so I don't think the advertisers are shying away from the affiliation.
The intro computer architecture course used _Computer Organization and Design_ by Patterson and Hennessy. The practical component described here was driven by handouts, I'm not sure the text follows building something like this.
You should be able to read the source of the script directly at https://get.pulumi.com/ or even download it yourself, inspect it and then decide if you want to run it or not. You can also follow the manual install instructions which are listed a little further down on our install page at https://pulumi.io/install/, if you want total control over where it is installed.
I also just opened a pull request to our docs website: https://github.com/pulumi/docs/pull/430 to explain in a little more detail what we're doing with the scripts.