my compile-time interpolators for
IP, URL, and Path make this a lot cleaner too
want to hijack that idea from sttp
the strongest part is the fact it enables FP code
fully functional prototype: https://github.com/outr/youi/blob/master/server/src/test/scala/spec/ServerDSLSpec.scala#L50
another feature of youi though is that all of those standard types are cross-compiled to Scala.js as well as that you can take advantage of them in the browser
if it side effects it's not exactly pure
which is a lot of what http4s emphasizes on
?
it's cumbersome if you never do it
and often fighting the type system is nicer than fighting side effect-related bugs
(not saying you should,. just that what you might find f'ed up in FP others may see it making sense)
I try to examine my reasoning and give things a fair shake, but I am also much more concerned with readable code than most people.
Which is why all of my open-source projects are so pretty. ;)
like cats used to look like black magic before
or doobie
Though this is mostly true, there's something to be said for readability without special knowledge. Lift eventually becomes "readable", but to any outsider it looks like gibberish. There's a trade-off that comes with "black magic" and very often I think Scala devs don't take that into consideration or just don't care. If the trade-off is worthwhile then I'm willing to make it, but very often the trade-off happens for no valid reason for some obscure "better practice" that is easily arguable. Further, immutable code very often suffers from serious performance impact.
Having written Scribe, which is more than three times faster than log4j, written 3d engines, and a strong focus on big data, performance is important to me.
@jmcardon I do hope you'll challenge the ideas put forth in youi, but I hope you're ready to defend the reasoning better than, "this is FP best practice" :-p
0.8.0 is your best bet
if you don't need any of that then 0.9.0-M8 is your best bet
@rvangsgaard I read your email, but it's still a bit unclear. You have an existing HTML template you're working with?
most of the changes have to do with the
HttpClient though
hey, for a library that I haven't focused on optimizing performance, we're doing pretty well on TechEmpower: https://www.techempower.com/benchmarks/#section=data-r18&hw=ph&test=json&l=zijunz-f