Live data from Hacker News

A new F# compiler feature: graph-based type-checking

devblogs.microsoft.com

111–118 of 118 posts

Re: A new F# compiler feature: graph-based type-checking

#111

Earlier quoted context omitted.

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??

They've worked for several years now on dotnet, but the type provider author has to do some work to allow their type provider to compile and target that runtime.

Re: A new F# compiler feature: graph-based type-checking

#112
post #16

Great 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,…

Do you integrate Rust and F# in any way or do they just talk via an HTTP or similar API?

Re: A new F# compiler feature: graph-based type-checking

#113
post #108

Earlier quoted context omitted.

> 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.

Every time Elm comes up people climb out of the woodwork to cast aspersions on it for no better reason than that Evan wants to run his project his way. Some people evidently just can't accept that and have sustained a grudge that drives them to comment on it whenever it comes up.

Look, I get it, I'm still sore about Google Feed Reader, 'member that?

But enough is enough. It's old news. Get over it. Etc.

It's like if every time someone mentioned Caddy server there was someone bringing up that time Matt Holt put that header in and pissed off a bunch of people. Life goes on. We forgive and let things go.

It's high time for folks to forgive Evan for his mistakes. I mean, he's very young still, eh? Cut the guy some slack already?

Re: A new F# compiler feature: graph-based type-checking

#114

Earlier quoted context omitted.

Please PLEASE enough with the character assassination of the Elm guy. He wants to run his own project his own way. There's a small but dedicated residue of people who just can't stand being told "no" and go around crapping on the kid whenever they get a chance. I get it. You don't like Evan's project management style. Move on already. - - - - The fact of the matter is that he's a person who took his thesis, made it i…

It's not "character assassination" to criticize someone.

No, it's not. But making the same criticism over and over again every time the subject comes up even tangentially is.

Re: A new F# compiler feature: graph-based type-checking

#115
post #108

Earlier quoted context omitted.

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.

Every time Elm comes up people climb out of the woodwork to cast aspersions on it for no better reason than that Evan wants to run his project his way. Some people evidently just can't accept that and have sustained a grudge that drives them to comment on it whenever it comes up. Look, I get it, I'm still sore about Google Feed Reader, 'member that? But enough is enough. It's old news. Get over it. Etc. It's like if…

Again, the things I read are not personal, grudges or inability to accept someone's personal choices. For starters, you write his name more than anyone else here. You're not doing him any favor specially when it comes to Streisand Effect.

When I propose a tool to my CTO I couldn't care less about the project's leadership personal choices.

Mature engineers think in terms of ROI, dependability, bus factor, predictability, funding, mind-share, hiring ease, license, etc.

But it would be naive and unprofessional of me to handwave technical issues with the tools. And ALL tools have hard edges and undesirable characteristics.

And putting a header in a HTTP server is not proportional as restricting who can change the source code of a compiler.

Matt Holt is awesome btw. And so is Elm author.

Re: A new F# compiler feature: graph-based type-checking

#116
post #108

Earlier quoted context omitted.

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.

Every time Elm comes up people climb out of the woodwork to cast aspersions on it for no better reason than that Evan wants to run his project his way. Some people evidently just can't accept that and have sustained a grudge that drives them to comment on it whenever it comes up. Look, I get it, I'm still sore about Google Feed Reader, 'member that? But enough is enough. It's old news. Get over it. Etc. It's like if…

Evan wants to control the technology. That's a management decision that makes it unfit for purpose. This is a legitimate criticism that had long ranging impacts. I have seen no reason, no commitment from the management side, to believe this won't happen again. It is worth bringing up when there are similar alternatives without such a spotted history of lockdown and control issues from management. I know nothing about the fellow. This is not personal.

Re: A new F# compiler feature: graph-based type-checking

#117

Earlier quoted context omitted.

F# is my go-to language for new backend projects and console apps. You can be as functional as you like, with imperative/mutable/OOP escape hatches available for those rare but unavoidable times you need them

Have to agree. Recently decided to try out Python instead. Everyone at work wanted Python, it's popular, so why not give it a shot. In constant regret, missing the type checking in F#.

I haven't done so yet but I keep meaning to check out Fable's support for F#-to-Python: https://fable.io/docs/getting-started/python.html

Re: A new F# compiler feature: graph-based type-checking

#118

Earlier quoted context omitted.

F# is my go-to language for new backend projects and console apps. You can be as functional as you like, with imperative/mutable/OOP escape hatches available for those rare but unavoidable times you need them

Have to agree. Recently decided to try out Python instead. Everyone at work wanted Python, it's popular, so why not give it a shot. In constant regret, missing the type checking in F#.

[deleted]
Post reply on HN