akra

11 ms·

121.
by akra 7y ago
As someone who has done some dev in F# professionally I think a lot of the comments above could come from trying to use F# like C#. WPF (and in general older .NET Microsoft frameworks) is probably one of the worst cases for F# however; the
122.
by akra 7y ago
The biggest difference in the past (i.e. industrial revolution) was that a human was still required when technology improved and the increased output only occurred from that tech when workers were skilled up to use it appropriately. Also tr
123.
by akra 7y ago
As you get used to the language some of the reasons make sense why it isn't C like. An example I've found is that (arg1, arg2) always defines a tuple wherever it is a function invocation or not. You can pass a tuple around to a tu
124.
by akra 7y ago
SQLProvider has been ported to .NET Core - I've used it no problem when scripting/prototyping across a variety of different data sources at once. Admittedly I tend to just use straight ADO.NET anyway - its simple enough to use and
125.
by akra 7y ago
I'm using F# tooling in Linux and both VS Code and Jetbrains Rider's IDE's outclass most functional language IDE's at present IMO. It's greatly improved within the last year or so. If you use code most of your app i
126.
by akra 8y ago
I think C# creates a state machine for every async/await method that is compiles which keeps track of where it is at after every await and invokes the next piece of code based on that. Also I thought async/await came in F# first?
127.
by akra 8y ago
The developers I've encountered that use F#'s Async get confused at first mainly because they are used to C#'s Tasks being started upon creation. I personally think the F#'s model conceptually is better and I've see
128.
by akra 8y ago
What aspect of performance though? Even that means a variety of different things to different people and it isn't just algorithms. I've met people who are bad at typical CS algorithms yet know their language of choice very well an
129.
by akra 8y ago
The way to combat that IMO is to continue to innovate the language improving both the language and the context it runs in (tooling, ecosystem, etc) making it easier to use, more robust, minimize the costs/benefits of changing, etc. Hav
130.
by akra 8y ago
When I use F# on Linux (my main machine) I use VS Code on Linux and it seems to work fine once setup properly and it has all the minimal features (e.g rename, find usages, etc). I've heard Rider as an IDE has F# support now as well. Yo
131.
by akra 8y ago
A link on the original announcement page states "Moving forward, you can simply think of ASP.NET Core as being part of .NET Core.". If this is right the high coupling between the CLR and what really is a framework/library on
132.
by akra 8y ago
It's not criminal per se. It's all in the law - they just aren't perks available to the typical employee. The cash jobs are but they're in a business where they can get this; a typical engineer can't ask to be paid
133.
by akra 8y ago
In Australia which this reply chain is about trades get paid exceptionally well if you have a successful business operation (not working for someone else). There's simply an oversupply of university graduates and a very liberal visa pr
134.
by akra 8y ago
I suspect there is a point of diminishing returns with this though; the extra complexity in the type system gets you less and less benefit but at a greater cost to code complexity/comprehension. It could explain why the mixed Scala&#x2
135.
by akra 8y ago
As a counter to this that may make it easier for a company to adopt and reduce the learning curve. Laziness can make it harder for some to reason about performance as an example.
136.
by akra 9y ago
> Why? Even writing micro service in C++ is dead simple these days Apologies to the commenter then. I misread that to be a "why bother?" to the original blog post and do this instead. All tech has its pros and cons and trying o
137.
by akra 9y ago
How come on every thread showing an example of how to do something in Rust there's a staunch C++ defender thinking the whole world should be using their language? C++ is a complex beast that due to its age has quite a number of disadva
138.
by akra 9y ago
Most of those innovations however seem to be playing "catch-up" though and there's a huge question mark as to whether most (not necessarily all) of the benefit goes to capital holders. Even the innovations that do benefit as
139.
by akra 9y ago
I agree with the first missing feature as you state; I just don't know how much value-add those features actually add in real world apps - often people use them in weird and unintitutive ways as well. F# has other features that other l
140.
by akra 9y ago
Disagree as someone who has programmed in both Scala and F#; I found F# pretty much could do the same things just in different ways. In F# I found more ways to squeeze performance than in Scala which by comparison is bloated. For the data a
141.
by akra 9y ago
Because IQueryable's don't always translate to working SQL. I've broken EF's IQueryable a few times in the past; NHibernate's one was really bad if I recall. The expression inside the IQueryable operator is checked
142.
by akra 9y ago
Having 10 lines of code for 10 different data sources and having a explorable Intellisense API for all of them is much nicer though than having 10 code generator + command line tools in my now required build pipeline, each one with a differ
143.
by akra 9y ago
Disagree with this; because it very much depends on the program being written. From what I've seen they've become more popular with ironically the exception of the SQL ones for the reason you describe. As long as you can get the s
144.
by akra 9y ago
You can via the F# Power Tools; at least in VS2015. In VSCode just create the folder as per normal and hit "F1->F#: Add File to Project" using the Ionide plugin. Admittedly the need for folders in my experience is a lot less th
145.
by akra 9y ago
Saw a presentation on this was done awhile back. Most features are exposable to C# pretty easily - it's pretty easy to design libraries where consumers wouldn't know it was a F# type at first glance if you know how things compile
146.
by akra 10y ago
I definitely agree with you for tuples especially smaller tuples. As tuples get larger however performance can swing the other way. As someone who codes some F# for my day job it seems that while tuples should be easier in a functional lang