greener_grass

7 ms·

61.
by greener_grass 1y ago
Huh, Richard Feldman of Roc and Elm fame!
62.
by greener_grass 1y ago
A small community but some things going on: - https://github.com/dotnet/TorchSharp - https://github.com/DiffSharp/DiffSharp - https://github.com/fsprojects/Furnace - https:&
63.
Shoelaces, software, graphics & more(fieggen.com)
1 points by greener_grass 1y ago|0 comments
64.
by greener_grass 2y ago
I agree, yet Make, CMake or even Node package scripts are more popular than Bazel.
65.
by greener_grass 2y ago
Everyone says they want a "tiny" "minimal" "lean" build-system, but there is lots of real complexity in these areas: - Cross-compilation and target platform information - Fetching dependencies - Toolchains I&
66.
by greener_grass 2y ago
My experience is that the less done in GitHub actions the better. I tend to prefer either: - Using a build-system (e.g. Make) to encode logic and just invoke that from GitHub Actions; or - Writing a small CLI program and then invoke that fr
67.
by greener_grass 2y ago
Very few languages let you have multiple versions of the same package in one project; fewer let you use functions from both versions together; and even fewer make this easy! This is something that would be enabled with hash identifiers and
68.
by greener_grass 2y ago
Readers might enjoy Mozart Was a Red, a play by Murray Rothbard https://www.youtube.com/watch?v=KIk5C2qsRH8
69.
by greener_grass 2y ago
You would do something like: open universe.mega_corp.finance_dept.team_alpha Then when you use `foo`, the compiler would know you mean `universe.mega_corp.finance_dept.team_alpha.foo`. There will probably need to be some kind of lo
70.
by greener_grass 2y ago
I've definitely noticed more anti-gary astro-turfing recently. He seems to have rattled someone...
71.
by greener_grass 2y ago
This could be achieved with a hierarchical namespacing scheme for functions, no? universe.mega_corp.finance_dept.team_alpha.foo But to use `universe.mega_corp.finance_dept.team_alpha.foo` in your application, you don't import
72.
by greener_grass 2y ago
https://archive.ph/N2bA3
73.
by greener_grass 2y ago
I disagree - if the Vision Pro had some strong use-cases then developers would hold their nose and make apps for it. The platforms that get apps are the ones where businesses see value in delivering for them. Of course businesses prefer it
74.
by greener_grass 2y ago
The companies that might acquire Reddit are affected by tariffs.
75.
by greener_grass 2y ago
Efficient hiring practices?
76.
by greener_grass 2y ago
Without access to the .NET ecosystem it would be dead in the water
77.
by greener_grass 2y ago
F# allows you to use React pretty much directly, but it has still been only a modest success.
78.
by greener_grass 2y ago
The JS approach is worse than a do-notation approach because it is not extensible. Now we are stuck without cancellation token propagation (forever?)
79.
by greener_grass 2y ago
This already exists with F#, OCaml, Scala, Haskell... it doesn't seem to be a big draw.
80.
by greener_grass 2y ago
When developing something I tend to have lots of programs open: - The editor - Several terminal windows - Some docs - GitHub PRs - AWS console - Admin tools like PgAdmin - Teams, Slack, etc. When screen-sharing with Zed, do I only get to sh
81.
by greener_grass 2y ago
There's a small chance they will get a cult following with more exposure and lead to increase in value of the IP.
82.
by greener_grass 2y ago
We already have many great GC'd functional languages at that performance level. I first learned about Roc from this talk: https://www.youtube.com/watch?v=vzfy4EKwG_Y That's a niche that is not currently filled (we
83.
by greener_grass 2y ago
The author learns that Java is not a Functional Programming language; lambdas ain't enough!
84.
by greener_grass 2y ago
Yes, I read the post. I don't understand why the goal is not to (eventually) implement Roc in Roc, maybe with a dash of something else for the "platform". Roc is pitched as a general purpose functional programming language wi
85.
by greener_grass 2y ago
OCaml allows mutation via reference cells.
86.
by greener_grass 2y ago
So why is it a non-goal of Roc to be implemented with this approach?
87.
by greener_grass 2y ago
I can't help but feel like the Roc team has an attitude of "imperative programming for me, but not for thee". And now they are doubling down on that by moving from "OCaml meets C++" to "C, the good parts"!
88.
by greener_grass 2y ago
> While we're at it, we also want to convert it to use recursive descent; it was originally written using parser combinators because that was what I was comfortable with at the time Aren't parser combinators just one way to do
89.
by greener_grass 2y ago
There's no good reason FSI can't be improved to handle this though
90.
by greener_grass 2y ago
> other F# script files This is where it breaks down a bit. Importing the same script file twice leads to errors, so you must manually ensure exactly once imports across your dependency tree of scripts. This is where C/C++ code reac

More ›