3 ms·
Our ways to hide that logic has been building libraries that handle nearly all of it. But since Haskell's ecosystem is small by comparison a lot of that logic
by verttii 7y ago
Our ways to hide that logic has been building libraries that handle nearly all of it.
But since Haskell's ecosystem is small by comparison a lot of that logic leaks to your own application code. Especially when dealing with something like stateful websocket applications.
- twitchard 7y agoA general-purpose library able to hide the necessarily specific logic of how network events and a poker game should interact seems... unlikely?
- verttii 7y agoSure, but the original argument was: > raw connection state, timers, transient and long-term persistent state Much of this surely can be abstracted away to 3rd party libraries/frameworks. Haskell, even though a higher level language than most out there, lacks the ecosystem support for a lot of things that are handled by some library in lower level languages.
- dllthomas 7y agoThe point was that these things need to be handled unusually in the case of a poker server in particular. If that's true, then a general purpose library that's handling them invisibly is probably handling them wrong for this use case.