3 ms·

First off, nice work! I always thought it is better to mix client/server rendering; the 'everything client' or 'everything server' both do not work for a large

First off, nice work! I always thought it is better to mix client/server rendering; the 'everything client' or 'everything server' both do not work for a large number of applications. So why not mix them. Unfortunately not much out there battery-included that consistently supports that model. I did not dive into IHP (I heard about it as the RoR for Haskell) but, after reading the introduction, I'm probably going to get depressed when I hear how you do the inevitable client-side stuff here; there is a really good opportunity to mix them as there is HSX and you can compile Haskell to JS. So there should be an opportunity to appoint, where supported, some (parts of) a page as serverside/clientside.

_query 6y ago
Thanks for your feedback! :) We have been tinkering a bit with building something close to Phoenix LiveView with HSX. Hope we can show something in that direction later this year.
- tluyben2 6y ago
  That sounds good; thanks for the response. Most stuff I do is in the middle between static/dynamic; needs solid SEO and prerendered parts for various reasons but also contains, for browsers that support it, quite a lot of dynamic elements. Now we just use asp.net/static-with-some-react but that is driving me bonkers.
  - dgb23 6y ago
    Static with some react sounds like a nightmare. One of the primary reasons why many moved to JS frameworks was to have a better separation of concerns and a single place where GUI logic resides. May I suggest you have a look at Next.js. It lets you solve this in a very ergonomic way. Maybe even for your existing project.
    - tluyben2 6y ago
      Yeah it is a nightmare; it is not my choice. It is the same ‘everyone uses it so we need as well’ type of thing thrown in by partners. Thanks for Next.js: I did not know it.
- Vosporos 6y ago
  I would love a IHP LiveView equivalent!! Thank you so much!
- shirogane86x 6y ago
  How do you think IHP would interact with something like concur-replica(https://github.com/pkamenarsky/concur-replica https://github.com/pkamenarsky/concur-replica)?

_query 6y ago

Thanks for your feedback! :) We have been tinkering a bit with building something close to Phoenix LiveView with HSX. Hope we can show something in that direction later this year.

tluyben2 6y ago
That sounds good; thanks for the response. Most stuff I do is in the middle between static/dynamic; needs solid SEO and prerendered parts for various reasons but also contains, for browsers that support it, quite a lot of dynamic elements. Now we just use asp.net/static-with-some-react but that is driving me bonkers.
- dgb23 6y ago
  Static with some react sounds like a nightmare. One of the primary reasons why many moved to JS frameworks was to have a better separation of concerns and a single place where GUI logic resides. May I suggest you have a look at Next.js. It lets you solve this in a very ergonomic way. Maybe even for your existing project.
  - tluyben2 6y ago
    Yeah it is a nightmare; it is not my choice. It is the same ‘everyone uses it so we need as well’ type of thing thrown in by partners. Thanks for Next.js: I did not know it.
Vosporos 6y ago
I would love a IHP LiveView equivalent!! Thank you so much!
shirogane86x 6y ago
How do you think IHP would interact with something like concur-replica(https://github.com/pkamenarsky/concur-replica https://github.com/pkamenarsky/concur-replica)?