Weebs

5 ms·

1.
by Weebs 4mo ago
Not the person you replied to but I leave unused variables as future TODOs. It's a warning in F#. I also often use them for inspecting data in the debugger
2.
by Weebs 4mo ago
Shhh no class consciousness on HN allowed
3.
by Weebs 4mo ago
Waiting for async to finish and await are two different things. Async functions essentially have a different calling convention than standard functions. They're either converting your code into continuation passing style, state machine
4.
by Weebs 4mo ago
I keep asking LLMs if I can define an interface implementation as an expression or without creating a new type in C# Every single one I ask always happily says yes, and starts claiming C# has local classes (a feature of Java)
5.
by Weebs 4mo ago
A VM with good FFI and structs is pretty unique and all of the tooling around .NET is excellent F# is a sleeping giant of capability in the FP/ML space, being able to use a lot of the existing tooling People rightfully point out how it
6.
by Weebs 4mo ago
Any lesser known knobs one should know? I'm considering a .NET backend for my compiler
7.
by Weebs 4mo ago
I've been working on a C++ backend for F# and while I'm very familiar with F# and it's AST I barely know C++. The amount of time I save being able to ask things, check my understanding, get design patterns, and paste issues I
8.
by Weebs 4mo ago
Now do it with code
9.
by Weebs 4mo ago
I'm wrestling with this right now. I only use LLMs for design and exploration because I am not employed and can't pay for a subscription right now, and they make the design phase feel like less of a fever dream because checking my
10.
by Weebs 5mo ago
A lot of code ends up being easy to factor out into small pieces for tests. I can't speak for Haskell but coming from another ML with eager evaluation step debugging works as you would expect
11.
by Weebs 5mo ago
I like to think about it as a VM that all the major browsers agreed to implement, designed by a broad group of stake holders with lessons from past plugin and VM systems For that it's pretty cool. I still wish we had DOM access though
12.
by Weebs 5mo ago
Certain algorithms are a lot easier. It's not needed though
13.
by Weebs 5mo ago
Interesting language! I like the focus
14.
by Weebs 5mo ago
They're modeling reactivity, not classes. It's a well established pattern in functional programming The one time setup mixed with repeated render calls is odd, but it's a design decision they made. It reduces boiler plate, th
15.
by Weebs 6mo ago
"I thought this would be about Hegel... oh, wait"
16.
by Weebs 2y ago
This is a direction I've been pushing in partly because I'm using a significantly slower type inference algorithm in my language. I'm hoping with that and focusing on separate compilation I'll be able to keep the fancy i
17.
by Weebs 2y ago
Afaik that is true of traditional HM, but fortunately there was a big advancement in inferring subtypes w/ Dolan's Algebraic Subtyping a few years ago! It's not nearly as fast as HM (O(n^3) worst case) but generally fast enou
18.
by Weebs 3y ago
I've been left out of the loop by people before because of it. It's not a big deal but it's annoying to have it come up all the time
19.
by Weebs 3y ago
There's definitely tradeoffs to some things, and I think in particular Rust's static guarantees can cause additional friction, but in general I've found ML derived languages to be extremely practical because it's a good
20.
by Weebs 3y ago
Good to hear they're providing a good dev experience. My only gripe at the time was more of a worry on whether the split was going to be worthwhile because the ML ecosystem is already so small, but I'm glad to hear the project has
21.
by Weebs 3y ago
I have nothing to say other than thank you! I might not use OCaml often myself, but I appreciate the effort to improve the ML ecosystem in any way :) I was a bit disappointed with the ReScript fork abandoning the compatibility with OCaml so
22.
by Weebs 3y ago
> And we should all try to do something weird. YES It's a big world out there and there's so many cool techniques we know are helpful but aren't widespread and really should be, and so much more to be discovered still!
23.
by Weebs 3y ago
You got me thinking and I think part of what it comes down to for typed FP languages is that you can either generally 1) Go for a simple design, but having poor interop with existing ecosystems because the language lacks equivalent features
24.
by Weebs 3y ago
Yeah I'm not saying immutability solves the problem, I am saying that having good support for immutability is helpful for building those synchronization and rollback systems. If I thought immutability was all you needed I wouldn't
25.
by Weebs 3y ago
I'm not the person you replied to, but symbols are easier to distinguish visually, tho they need careful balance. Too many are worse than too few
26.
by Weebs 3y ago
For those wondering why they've created yet another language, keep this in mind: Fortnite content is running code on possibly 100 remote clients simultaneously, and code often has state that needs to be synchronized across clients, whi
27.
by Weebs 4y ago
Push to talk is another important one (for me)
28.
by Weebs 5y ago
This has been hitting me hard lately in my late 20s. I'm realizing all of the cool "new" concepts I'm learning have been around since the 60s It's made me rethink the supposed "skill reset" that happens in
29.
by Weebs 5y ago
I know this is anecdotal but tools like f.lux made a huge different for me. I grew up with difficulties falling asleep and blue light filters like f.lux made an immediate impact on my ability to fall asleep on time. I was no longer in my te
30.
by Weebs 5y ago
also, better latency

More ›