6 ms·
Very cool. Should be a part of Excel tbh. LINQ is much better suited for data munging than JavaScript.
by HeckFeck 4y ago
Very cool. Should be a part of Excel tbh. LINQ is much better suited for data munging than JavaScript.
- qwerty456127 4y agoF# is even better.
- eitland 4y agoMaybe, but I think C# has the advantage that "everyone" knows it or Java so it is trivial to get started. Last I checked, admittedly a couple of years ago, starting with F# wasn't absolutely trivial.
- eckza 4y agoIt is, if you know where to look. Therein lies the problem. The language doesn't have much marketshare, and few champions. I just finished reading Scott Wlaschin's Domain Driven Design for Functional Programmers and it's an incredible, batteries-included guide that goes from "hello world" to "and here's how you use it in an organization" in a few hundred pages. I wish I had been exposed to it about a decade ago. Incredibly easy to follow and well-explained.
- fsloth 4y agoThis! Other good books are ”Expert F#” by Granicz, Syme & Cisternino, ”Real world functional programming” by Petricek and ”F# for scientists” by Harrop. The last is old but still really great in succintly explaining what ’new&unfamiliar’ structures in F# are great for pragmatic software engineering. Why is there so little noise in F# land? I have no data, but I can guess that the language is so unproblematic that everybody is just happily coding instead of explaining how to fix something. It’s also not very good at guis so there is usually nothing visual to demonstrate.
- grugagag 4y agoWhat’s the markershare though? F# is great but Microsoft made it sortof a second class citizen
- fsloth 4y agoF# is installed by default with Visual Studio, and the tooling is pretty good. I think it hardly is second class citizen? Not promoted nearly as much as C# for sure. AFAIK F# is on quite solid foundation, as there is the F# foundation that would keep ball rolling, so to speak, were Microsoft to renounce the language. I have no idea what the marketshare is though. On Tiobe (https://www.tiobe.com/tiobe-index https://www.tiobe.com/tiobe-index) it seems to be nearly on par wit Scala and much more popular than Haskell or Ocaml.
- pjmlp 4y agoPretty good if only what one cares about is CLI and class libraries. According to JetBrains developer survey, an amazing 3%. https://www.jetbrains.com/lp/devecosystem-2022/csharp/ https://www.jetbrains.com/lp/devecosystem-2022/csharp/
- fsloth 4y agoTooling: Not only CLI and classlibs. The debugger in Visual Studio follows calls to c/c++ dll:s over pinvoke withhout a cinch. (Same as C#). If you wrap complex entities in e.g. Protobuf then writing hybrid applications is pretty straighforward and on solid ground. All of the GUI stuff is missing of course. I would not advice to implement a GUI on top of F#. The main feature of F# imo is it's succint type system where one can wrap everything in a type without much bureaucratic cost, but in a way that makes program structure so much more obvious. "If it compiles it's correct" is prety much how it goes.
- pjmlp 4y agoNot enough to justify many .NET shops to go multi-lingual projects. They already have to use C# no matter what, given the GUI and database frameworks. Adding C++ or PowerShell into the mix might happen, due to the frameworks and workloads that require reaching out to them. While adding F#, even if more expressive, it barely makes sense from business point of view. It isn't as if a mixed C#/F# codebase brings the same value as doing Python/C++. Also to note that while F# team has pivoted into trying to make F# attractive to data science, their employer is one of the reasons why CPython is now taking performance more seriously.
- pjmlp 4y agoFor that you already have PowerQuery on Excel. As for being better, F# is better on the language level, but sadly sucks on the tooling effort for .NET frameworks, that Microsoft is willing to spend on it.