Re:Build It with Nitrogen: The Fast-Off-the-Block Erlang Web...
by c22 on Wednesday November 25, 2020 @03:14PM
(#25213761)
I've looked at Nitrogen a couple times, but I haven't had a project to try it out on yet.
It looks really neat but also very websockety... I like to build websites/webapps that are enhanced but have sane (if sometimes clunky) fallbacks for users who aren't running JavaScript. How hard is it to shoehorn such fallbacks into a Nitrogen project?
Re:Build It with Nitrogen: The Fast-Off-the-Block Erlang Web...
by chops on Wednesday November 25, 2020 @04:09PM
(#25214325)
It is indeed very websockety. While it is a server-side rendering framework, it relies heavily on javascript and websockets (or fallback to ajax, if websockets aren't available).
However, there isn't a built-in mechanism to handle a client who simply doesn't have javascript enabled at all. Interfaces could be built with traditional HTML forms, but I understand that's not the same thing.
Re:Build It with Nitrogen: The Fast-Off-the-Block Erlang Web...
by kiliancs on Wednesday November 25, 2020 @12:05PM
(#25211428)
A link to the project itself was surprisingly difficult to find. I ended up going to the project's website, and even there I had to find the URL in a git clone command snippet. https://github.com/nitrogen/nitrogen
Re:Build It with Nitrogen: The Fast-Off-the-Block Erlang Web...
by chops on Wednesday November 25, 2020 @01:37PM
(#25212599)
Thank you! You're right, the leanpub listing should have a link to the project's homepage, and a link to the Github.
And I had removed the "Fork me on Github" banner thing from the nitrogenproject.com homepage, and forgot to re-add a proper link to the github. I've rectified both of these.
Re:Build It with Nitrogen: The Fast-Off-the-Block Erlang Web...
by chops on Wednesday November 25, 2020 @02:49PM
(#25213461)
Honestly, only tangentially (at best). Nitrogen is fundamentally an Erlang web framework, however the OTP skills learned should be universal. but we don't dive too deeply into OTP. We introduce gen_servers and supervisors and leave it at that. Most of the book is spent with the specifics of Nitrogen.
That said, the demos[1] on the Nitrogen homepage can give you a pretty good sampling of how the framework works.
It looks really neat but also very websockety... I like to build websites/webapps that are enhanced but have sane (if sometimes clunky) fallbacks for users who aren't running JavaScript. How hard is it to shoehorn such fallbacks into a Nitrogen project?
However, there isn't a built-in mechanism to handle a client who simply doesn't have javascript enabled at all. Interfaces could be built with traditional HTML forms, but I understand that's not the same thing.
And I had removed the "Fork me on Github" banner thing from the nitrogenproject.com homepage, and forgot to re-add a proper link to the github. I've rectified both of these.
Thanks again!
That said, the demos[1] on the Nitrogen homepage can give you a pretty good sampling of how the framework works.
[1] http://nitrogenproject.com/demos