319 karma · joined August 5, 2024
No, but immutable defaults are powerful.
E.g. in JavaScript / Python, the built-in lists and dictionarys (which are blessed with special syntax) are mutable.
> Is the ability to use data/values exclusive to functional programming?
No, but expression-orientation makes this less painful
> Are monads exclusive to functional programming?
You can hack them in by abusing co-routines or perhaps async/await in various languages, but it will never be as good as something built for this purpose.
Type-inferences, type-classes and do-notation make monads workable in practice.
Rust has special syntax (`?`) for this AFAICT.
How can you "Make illegal states unrepresentable" with mutable state and sequences of mutations that cannot be enforced with the type system?
How can you do "Errors as values" at a large scale without do-notation / monads?
How can you do "Functional core, imperative shell" without the ability to create mini DSLs and interpreters in your language?
How did the Netherlands manage to overcome this back in the 70s and the UK has not?
Sometimes it's actually better to take the road, or you end up on a windy route that's near impossible to follow, debris everywhere, no right of way, etc.
I would like to try this with a "prefer offroad" option.
Is it cost of production being passed on or did the marketing department decide to do some "prestige" pricing?
> Unity devs run into
So it's viable but not perfect
Zed collaboration sounds great, but what about all of the other apps I use?
Image based sharing supports everything (poorly) automatically.
On the server you can run ASP.Net using Giraffe, which is a Functional Programming layer with comparable performance to C#.
On the front-end, you can write React in an true Functional Programming language.
And of course you can share F# code between frontend and backend.
Imagine if you can be in "dynamic mode" where you can add rules, facts, etc. in an adhoc way.
Then, once your game is better defined, you can compile the Prolog to native code so that it is highly optimized, executed in parallel, etc. The compiler could apply all sorts of optimizations we see in commercial game engines automatically.
This compiled object could then be embedded into a game engine with native performance.
Done right, this could even outperform imperative game engines, but be very easy to debug and modify.
2. Garbage collection and lexical scopes - you clean up memory quickly and in batch
3. Compiler optimizations - you turn functional constructs into imperative ones that reuse and mutate memory at compile-time, where it is provably safe to do so
Roc Lang might interest you: https://www.youtube.com/watch?v=vzfy4EKwG_Y
The second you hit some kind of breakthrough, capital finds a way to remove any and all guardrails that might impede future profits.
It happened at DeepMind, Google, Microsoft and OpenAI. Why won't this happen the next time?
And ironically, many in this community say that corporations are AI.
Pretty cool
Glasses that let you record people without their awareness / consent?
Downright creepy
I think the best play here would be to release them without any camera functionality at all, or the connotations will be that weird, sweaty guy that no one wants to sit next to on the subway (see: Google Glass).
Bikes have very low maintenance costs and if you buy second hand you don't lose much on resale.
Quick question: if the build graph can be dynamic (I think they call it monadic in the paper), then does it become impossible to reason about the build statically? I think this is why Bazel has a static graph and why it scales so well.
Being unable to position it inline is the problem.
You might not see the benefit, but many do. It prevents Python from being a good functional programming, for one thing.