throw868788

8 ms·

1.
by throw868788 2y ago
Indeed. The company I work for uses F# for large revenue workloads across many services; mostly coming from non .NET dev's. It handles large scale customer traffic quite well without a hiccup and with the C# interop we never find we ar
2.
by throw868788 2y ago
Its funny because I've found the opposite; the fact that the smaller community (and lets face it - most FP langs have a much smaller community than needed to get the scale you are after) the more it needs to piggy back on the army of e
3.
by throw868788 2y ago
I do think this depends on region, as I've seen F# and Scala jobs typically outnumber Clojure for example depending on whether it is a .NET or Java shop. Mileage does vary. However to be honest anecdotally I do think even if they aren&
4.
by throw868788 3y ago
Would be interesting to see actual stats in F# usage which I doubt are relatively available. Given the reaction to this post from what is an old article there's still probably an underground interest in the language and some use in gen
5.
by throw868788 3y ago
Seems like a common theme that people prefer the F# language, but try to explain reasons why it hasn't succeeded from a technical view. I think the reasons IMO aren't technical but what the author has stated - C# is probably worse
6.
by throw868788 4y ago
There are differences between implicit/pre-emptive and co-operative multitasking though and there is probably tradeoffs for each. For Java however, much of the existing API exposes Threads, and locks. How do you introduce better scale
7.
by throw868788 4y ago
I see that in places I've worked. I've always resisted growing my team's headcount as I've seen it break efficiency first hand. However I'm well aware it makes our team less noticed, and less attractive when other c
8.
by throw868788 4y ago
I've used F# in a professional job and its fine - on very large scale apps for large corps. There's features in it that I feel make certain apps much easier to write that have no equivalent in C# or C# is just starting to get them
9.
by throw868788 4y ago
I think this is a problem with many languages - e.g. Scala, Kotlin, etc. The easier justification really is: Does it fit your problem space? Will you save dev time overall, is it more maintainable using this tool? Do your staff prefer worki
10.
by throw868788 4y ago
Just use a mixed solution then i.e. why not both? You're picking one thing that F# isn't great at - generated code tooling which IMO isn't in the spirit of many modern languages anyway. I don't get why some C# devs tend
11.
by throw868788 4y ago
My view: F#, or to be honest a cross-platform IDE like VS Code isn't probably appropriate for many of these apps or rather the dev workflow that Microsoft promote in those frameworks feels like old .NET to me. The frameworks themselves
12.
by throw868788 4y ago
These are nice but: - Templates are no substitute for intuitive and minimal code for a number of reasons. (e.g. how to extend, how to customize, confidence that it isn't brittle if I change one thing, etc etc). If a template doesn&#x27
13.
by throw868788 4y ago
I think that's the barrier with C# in general - the framework nature of it means there's a lot of "I don't know what I don't know" especially with ASP.NET which is quite large in scope. Don't get me wrong
14.
by throw868788 4y ago
Honestly I've found F# pretty OK to use compared to some other languages, especially when not using Visual Studio on a non-Windows machine where F# IMO is the better choice. Given a cross-development experience in some of the more rece
15.
by throw868788 4y ago
He's linked it here: https://devblogs.microsoft.com/oldnewthing/20190913-00/?p=10... . Its a good read. The LE format, especially with UUID 7 like UUID (seq UUID's), seems to be easier/faster to sort
16.
by throw868788 4y ago
This is what I think .NET's generics are like. Type information including all parameters are available, and JIT does as you say. The approach has some advantages (binary size, less memory instantiations when required) but a slight cost
17.
by throw868788 4y ago
> "hey, system, go through this btree, pull these items, merge with items from this other btree, etc” What I've always wanted in Postgres in one quote expect to also allow other index types (e.g. Hash/BRIN/etc) in its
18.
by throw868788 4y ago
I guess what I don't understand by this proposal is how the exchange rate is actually maintained. Will they print a lot more cash to keep the exchange rate depreciating as thus? The devil will be in the detail of this.
19.
by throw868788 4y ago
Realising this is what made money a lot easier to understand for me, and simplified the difference between different kinds of money. In the end its easier just to think of them as different currencies with stable pegs. It answers questions
20.
by throw868788 5y ago
I've defined it myself (when doing C# with functional heavy code but it feels clunky) but there's still edge cases where it isn't as nice especially with functions of multiple args, or functions passed in. Sure C# can do thes
21.
by throw868788 5y ago
I do think the pipe operator is very tied into the first-class currying support and HM type inference in F#. In C# I think it makes a lot less sense. To be honest I think each language should play to their strengths and only "steal&quo
22.
by throw868788 5y ago
Integrating the two apps hosted on different platforms is also quite difficult normally. Things you take for granted that need to be shared, reachable, etc between apps all now need to be done manually for that snowflake platform.
23.
by throw868788 5y ago
Sadly in my experience it is common for F# given its finance background at least historically, particularly in London/Europe. There is a culture of not showing your cards in these environments having worked in a few of them, and quietl
24.
by throw868788 5y ago
Different data structures have different tradeoffs that are used for different contexts. Usually arrays are faster than a linked list however I've seen arrays been used pretty badly as well with GC pressure and LOH pauses hence all the
25.
by throw868788 5y ago
Many of the points here don't necessarily have to do with the language, well at least to me and could easily have occured in other languages such as coding style. Sure - the language uses some sensible defaults and is somewhat pragmati
26.
by throw868788 5y ago
> If the patient is contagious before developing symptoms, the virus can spread very effectively even if many patients die. For better or worse all that means is that viruses may evolve to delay their symptoms rather than overall peak se
27.
by throw868788 5y ago
I'm wondering if there is some inherit flaw in coding some data structures in Node/JS. Maybe this is just another case of the "Node tax"? Things like boxing, floating point number arithmetic, manual pop counts, array cop
28.
by throw868788 5y ago
While I personally favour Postgres the biggest thing I think that MySQL has better is the "undo" log vs MVCC vacuum paradigm of Postgres. In a normal running system bad transactions should be significantly rarer than successful tr
29.
by throw868788 5y ago
The ironic thing is Australia really only got it when their zero COVID policies weren't taken seriously enough by its weakest actor who was more into "opening up". For people who don't know Australian politics it was the
30.
by throw868788 5y ago
> The only way you’ll stop this thing from mutating into a variant not covered by the vaccine is by eradicating it everywhere, simultaneously. When I hear words like everything, everyone, everywhere to describe any system I get dishearte

More ›