3 ms·
F# to me would be a nice upgrade from powershell for ops/infrastructure code, due to terseness, a strong type system, and some similar syntactic concepts betwe
by juststeve 9y ago
F# to me would be a nice upgrade from powershell for ops/infrastructure code, due to terseness, a strong type system, and some similar syntactic concepts between both languages. many times i want to go 100% F# but due to the issues integrating f# i end up either having to write a lot of powershell, or shoe-horning C# classes and end up with two languages.. dont know what the fix is..
- phillipcarter 9y agoWhat are some of the issues you encounter in integrating F# with your ops/infra processes?
- juststeve 9y agoThanks Phillip for responding, I actually don't see any issues with F#, it's more: - The ubiquity of powershell and the ISE. powershell is installed on every server, and to step outside that means deploying a new compiler/runtime and its dependencies to production servers. - Doing operational tasks is easier with powershell (in the short term) because the existing cmdlets for managing servers are provided with the language. An example would be bulk updating 500k users in AD (with complicated logic that compares data between 4 or 5 other systems) - Using the Add-Type cmdlet to include F# libraries into Powershell requires a few manual steps that might break over time: https://tahirhassan.blogspot.com.au/2014/06/embedding-f-in-powershell.html https://tahirhassan.blogspot.com.au/2014/06/embedding-f-in-p... - Awareness/ecosystem - powershell feels like its being used to solve all 'server related' operational problems at the moment, and that F# is used for apps. i dont think my team mates would appreciate me solving a problem in F# unless everyone was happy about the choice of language beforehand.. Same goes for them if they wanted use python, rust, prolog. etc.