F# is sooo great
If you think F# is great, check out the OCaml. F# is just a shadow of its glory with a couple notable exceptions.
A new F# compiler feature: graph-based type-checking
101–110 of 118 posts
Re: A new F# compiler feature: graph-based type-checking
#102Earlier quoted context omitted.
FWIW my comment was along the lines of allergic reaction. I'm not an Elm fanatic, I'm just sick of seeing people snipe on the dude. You're entitled to your opinion, of course, and you articulated it well. But again I see it as another example of someone not liking being told "no", no?
That's really reductive and biased against us, the potential user base of Elm that decided not to engage. Why is it that we don't like being told "no," as opposed to the Elm leadership and Elm community not liking being told "this isn't a 100% solution for me so I'd like to modify it"? Obviously Elm is his passion project, that's fine. But nobody who locks down their compiler on a supposedly "open source" project can…
> That's really reductive and biased against us, the potential user base of Elm that decided not to engage.
My complaint isn't that you or anyone doesn't engage with Elm, that's your prerogative, of course.
My problem is that a small segment of people do engage with it whenever it comes up to smear the project in general or Evan in particular for nothing worse than wanting to run his own project his own way.
He's not an ogre? I mean here he is, look, he semms nice enough to me? "The Economics of Programming Languages" by Evan Czaplicki (Strange Loop 2023) https://www.youtube.com/watch?v=XZ3w_jec1v8
Re: A new F# compiler feature: graph-based type-checking
#103Earlier quoted context omitted.
SQLX has entered the chat [1]. [1] https://github.com/launchbadge/sqlx
Nice. Java has what looks like SQLx on steroids with the manifold project coming down the pike. https://github.com/manifold-systems/manifold/blob/master/man...
This is the coolest thing I have seen over the previous week! Looks fantastic!
Re: A new F# compiler feature: graph-based type-checking
#104Great addition to a great language. We've been building a very technical product in F# + Rust for the last three years or so (think R lang + R Studio or Replit but for DSLs we built for finance and contracts). While most folks tend to see F# as a .NET-oriented/back-end kind of language, they'd be missing some incredibly unique web technologies such as the Fable compiler (F# -> JS, Python, Dart, etc) and Elmish (Elm,…
I'm familiar with Fable, it's a very conscious choice not to use it in any web applications. Debugging its JS output is not fun.
Re: A new F# compiler feature: graph-based type-checking
#105Great addition to a great language. We've been building a very technical product in F# + Rust for the last three years or so (think R lang + R Studio or Replit but for DSLs we built for finance and contracts). While most folks tend to see F# as a .NET-oriented/back-end kind of language, they'd be missing some incredibly unique web technologies such as the Fable compiler (F# -> JS, Python, Dart, etc) and Elmish (Elm,…
[deleted]
Re: A new F# compiler feature: graph-based type-checking
#106F# is sooo great
If you think F# is great, check out the OCaml. F# is just a shadow of its glory with a couple notable exceptions.
Can you elaborate? From what I have seen the performance of OCaml isn't up to par with F#. The std. library is small compared to all of dotnet, not to say the surrounding ecosystem and third party packages and tools.
Syntax is of course subjective but to my eyes it's cleaner in F#.
Idk. Don't want to start a war but rather hear specific arguments for why you like OCaml more.
Re: A new F# compiler feature: graph-based type-checking
#107Earlier quoted context omitted.
If you think F# is great, check out the OCaml. F# is just a shadow of its glory with a couple notable exceptions.
Can you elaborate? From what I have seen the performance of OCaml isn't up to par with F#. The std. library is small compared to all of dotnet, not to say the surrounding ecosystem and third party packages and tools. Syntax is of course subjective but to my eyes it's cleaner in F#. Idk. Don't want to start a war but rather hear specific arguments for why you like OCaml more.
Mostly modules and corresponding type system features, AST transformation via PPX, better portability to non-x86 platforms.
Re: A new F# compiler feature: graph-based type-checking
#108Earlier quoted context omitted.
That's really reductive and biased against us, the potential user base of Elm that decided not to engage. Why is it that we don't like being told "no," as opposed to the Elm leadership and Elm community not liking being told "this isn't a 100% solution for me so I'd like to modify it"? Obviously Elm is his passion project, that's fine. But nobody who locks down their compiler on a supposedly "open source" project can…
> That's really reductive and biased against us, the potential user base of Elm that decided not to engage. My complaint isn't that you or anyone doesn't engage with Elm, that's your prerogative, of course. My problem is that a small segment of people do engage with it whenever it comes up to smear the project in general or Evan in particular for nothing worse than wanting to run his own project his own way. He's not…
As far as I've seen, there was no attack on the person.
What I usually see are warnings about what happened to the project and how it is run, mostly targeted to the unaware. This is a sign of respect to people's time before they waste it on something that might disappoint them when they get to know the details.
Re: A new F# compiler feature: graph-based type-checking
#109Earlier quoted context omitted.
Because they are pretty annoying to implement and most are quite fragile
They are only as fragile as your type source.
Maybe not 'fragile' as in buggy, not buggy, but I found them to be 'quirky'. Sometimes stop working unless I close /re-open VScode. Stuff like that.
And other downfall. Do they still not work with DOTNET Core??
Re: A new F# compiler feature: graph-based type-checking
#110F# is so good, such a shame so few companies use it. I have to touch C# and it's always a little bit painful after a few weeks of F# work.
I concur. All the .NET devs seem to prefer C# and are afraid to go near F#. It seems to be out of their comfort zone.Once people learn to code one way, they
often don't want to try new things, since C# works and pays the bills, they don't even try F#.