I've been working with the language for a few months.
I've been working with the language for a few months. Overall, I love pretty much every single aspect of the language. I am even starting to feel like the few things that I would like to have aren't necessary (such as HKTs and ML-style functors). In terms of platform support, F# has done almost everything right (I feel like Scala made boat loads of bad compromises to support Java interop, which I don't find at all with F#). There are entire classes of frameworks for web and mobile development in C# that are made obsolete even by the simplest language-level features like Agents, ADTs, Computation Expressions, Active Patterns, Type Providers, etc. My disappointments so far are super frustrating though. Like Jarcane, I've found quantity of documentation to be an issue. Most tutorials assume that you a) already know C# and b) are using VisualStudio, and the whole ecosystem is still very Windows-centric. It is nearly impossible to learn the language without an IDE, and all of the non-VS IDEs are pretty crappy in terms of F# support. The whole msbuild or whatever it is behind the scenes doing the building is completely opaque and incomprehensible. The compilation order issue (you basically have to tell the build system the order of compilation, with no cyclical dependencies) is pretty difficult to understand and sometimes very difficult to work with. It also makes code organization very unintuitive (you can't put code in directories?!). All in all, it is pretty frustrating, but at least they got the language right. The frustrations will likely go away in time, so I'm willing to put up with them for now. Maybe I'll get good enough at the language to actually fix them :)
Posted by saosebastiao on Apr 14, 2015, 5:32 PM
Tags
Related issues
- It’s such an annoying problem to solve.
- > My point is, the impression many people will unavoidably take away from "many recalls" is that the vehicle must me in the shop all the ...
- [Feature]: Ability to merge old runs with a new run
- Add `findManyAndCount()` to return count of queried items
- One of the best, and first, things we did when starting our machine learning platform was to design it using a plugin architecture.
- gh pr push
Raise real-world problems, find people facing the same issue, and discuss solutions.7,000 issues0 comments
ux (E-commerce)
It’s such an annoying problem to solve.
> My point is, the impression many people will unavoidably take away from "many recalls" is that the vehicle must me in the shop all the ...
[Feature]: Ability to merge old runs with a new run
Add `findManyAndCount()` to return count of queried items
One of the best, and first, things we did when starting our machine learning platform was to design it using a plugin architecture.
gh pr push
[feature]: Sync Collections with Git repo
Repeated SSH disconnects/reconnects that eventually stabilizes (large folder)
I've been working with the language for a few months.
I've been working with the language for a few months. Overall, I love pretty much every single aspect of the language. I am even starting to feel like the few things that I would like to have aren't necessary (such as HKTs and ML-style functors). In terms of platform support, F# has done almost everything right (I feel like Scala made boat loads of bad compromises to support Java interop, which I don't find at all with F#). There are entire classes of frameworks for web and mobile development in C# that are made obsolete even by the simplest language-level features like Agents, ADTs, Computation Expressions, Active Patterns, Type Providers, etc. My disappointments so far are super frustrating though. Like Jarcane, I've found quantity of documentation to be an issue. Most tutorials assume that you a) already know C# and b) are using VisualStudio, and the whole ecosystem is still very Windows-centric. It is nearly impossible to learn the language without an IDE, and all of the non-VS IDEs are pretty crappy in terms of F# support. The whole msbuild or whatever it is behind the scenes doing the building is completely opaque and incomprehensible. The compilation order issue (you basically have to tell the build system the order of compilation, with no cyclical dependencies) is pretty difficult to understand and sometimes very difficult to work with. It also makes code organization very unintuitive (you can't put code in directories?!). All in all, it is pretty frustrating, but at least they got the language right. The frustrations will likely go away in time, so I'm willing to put up with them for now. Maybe I'll get good enough at the language to actually fix them :)
Comments (0)
No comments yet. Start the discussion.