-
Notifications
You must be signed in to change notification settings - Fork 284
Include a snippet on the power of .NET #1005
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
_snippets/dotnet_ecosystem.md
Outdated
@@ -0,0 +1,27 @@ | |||
--- | |||
order: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure this should be so high in the order
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the current order:
- Concise like Python (HelloWorld.fs)
- Concise syntax
- Simple lists
- String interpolation
- Pipeline operator
- Objects Made Simple (OOP.fs)
- Seamless .NET integration
- Rich interface system
- Object expressions
- Automatic property generation
- Type extensions
If .NET was to be expanded on to show all the possibilities of the ecosystem, logically it would be placed in between Concise like Python and Objects Made Simple. It's originally the first bullet point of Objects Made Simple, after all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do agree that perhaps everything related to interop should be placed next to the Fable sample though.
I like the idea, left a few comments That said on fsharp.org we very strongly emphasise F# as a Javascript language, followed by a .NET language. This is because Mucrosift site does plenty of focus on .NET and this site we decided to balance that by talking about JS first, then .NET So the interop sample and text should be written with that in mind. Either one sample each showing JS/TS interop, or one sample with text about both. Starting with JS first. |
(would be nice to get the markdown liner fixed or turned off, it's.all noise right now!) |
@dsyme My idea was that people would actually address the flagged problems when they edit some documents. Looking at the problems reported they seem real to me (e.g. super long lines that should be re-flown or bare links that Markdown doesn't render correctly) Perhaps someone should go and fix the current problems in a focused manner or we can add a note in the PR template for people to address those. We can, of course, relax the linter configuration as well, but this would reduce its usefulness IMO. |
@dsyme I changed the sample to show both JavaScript and .NET use. |
No description provided.