Great discussions. Exciting first steps. Valuable criticisms & suggestions for improvement.
It is interesting that F#'s greatest strength - that there are compelling reasons to use it both from an abstract, elegance point of view, but also from a business perspective - actually make it hard to sell to either group. That seems to be the biggest challenge for the design team.
I also note that no-one likes the carousel, or at least the proposal for how it is to be used.
So here is a wild suggestion, keep the carousel, but have the elements be:
- F# for developers
- F# for business
- F# for data scientists (?)
- F# for educators (?)
Each pane could pastiche the design style that is most likely to appeal to each group.
Alternatively, a similar idea is on the topic of F# for developers:
- F# for C# programmers
- F# for python programmers
In each case there could be two sections:
- What is familiar? (Stressing an easy transition. Two side-by-side code snippets chosen to look similar. )
- What’s new? (Stressing the power & advantages of making the switch.)