JohnyTex

6 ms·

1.
by JohnyTex 4mo ago
> In MySQL, if you acquire a lock on Alice, then attempt acquire on Bob... then another session acquire Bob, then acquires Alice: The engine notices. Nothing bad happens. One of the threads gets marked as a deadlock and is rolled back, t
2.
by JohnyTex 4mo ago
How would you ensure Alice doesn't overdraft her account?
3.
by JohnyTex 4mo ago
If the failure mode of the "correct" solution is to exit the program, I stand by my assertion that it is incorrect by construction.
4.
by JohnyTex 1y ago
The situation is a bit more complex in F# than C#, as there are multiple ways to do it. Scott Wlaschin has a good overview post about it here: https://fsharpforfunandprofit.com/posts/dependencies/ FWIW you can do
5.
by JohnyTex 1y ago
Personally I think F# is excellent for writing ye olde CRUD applications, especially as the business logic becomes more complex. F# is really good at domain modeling, as creating types comes with minimal overhead. C# has improved a lot in t
6.
by JohnyTex 1y ago
FWIW I think writing F# is a really cohesive experience in day-to-day work. While there are usually at least two ways to do things, due to .NET interoperability requirements, it’s usually pretty clear which way is the “right” way to do some
7.
Demystifying the Enigma Machine – A Functional Journey by Isaac Abraham [video](youtube.com)
1 points by JohnyTex 1y ago|1 comments
8.
by JohnyTex 1y ago
Isaac Abraham gave an interesting presentation at the last Func Prog Stockholm about modeling an Enigma machine in F#. Some interesting history in there, also a good introduction to F# if you haven't tried it before.
9.
Little languages are the future of programming(chreke.com)
179 points by JohnyTex 4y ago|208 comments