I have kinda looked at it — it's not really what I wanted. For my personal website, I don't want an admin interface, password authentication and all that CMS-y stuff. Also, sweetroll was my "learning haskell" project, so of course I had to write a whole backend from scratch!
Setup wasn't the problem, Cabal sandboxes weren't much harder to use than stack… The actual benefit of stack is sharing compiled packages across all sandboxes instead of rebuilding everything every time.
Plugins in Haskell, or any compiled language, are kinda awkward to work with honestly. If you have to recompile the app, it's not very pluginy :D What are the other options? Dynamically loading shared libraries or using standalone RPC processes, neither of which feels good for a web app.
Embedded interpreters like duktape are pretty safe already. In terms of security model (you only expose what you want, there's nothing like file I/O available by default). Of course there might be bugs in them, especially memory bugs since they're written in C, but I'm not very concerned about actively hostile plugins tbh.
> Cabal sandboxes weren't much harder to use than stack… The actual benefit of stack is sharing compiled packages across all sandboxes instead of rebuilding everything every time.
I disagree. Stack saves tons of time by giving me package versions that just build together.
> Plugins in Haskell, or any compiled language, are kinda awkward to work with honestly. If you have to recompile the app, it's not very pluginy :D
Setup wasn't the problem, Cabal sandboxes weren't much harder to use than stack… The actual benefit of stack is sharing compiled packages across all sandboxes instead of rebuilding everything every time.
Plugins in Haskell, or any compiled language, are kinda awkward to work with honestly. If you have to recompile the app, it's not very pluginy :D What are the other options? Dynamically loading shared libraries or using standalone RPC processes, neither of which feels good for a web app.
Embedded interpreters like duktape are pretty safe already. In terms of security model (you only expose what you want, there's nothing like file I/O available by default). Of course there might be bugs in them, especially memory bugs since they're written in C, but I'm not very concerned about actively hostile plugins tbh.