3 ms·

Build It with Nitrogen: The Fast-Off-the-Block Erlang Web Framework

31 points by andrenth 6y ago

kiliancs 6y ago
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 https://github.com/nitrogen/nitrogen
- chops 6y ago
  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. Thanks again!
mkl95 6y ago
Would you say the skills learnt from this book carry over to Elixir app development? I've been really interested in Elixir, Phoenix and OTP lately.
- chops 6y ago
  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. [1] http://nitrogenproject.com/demos http://nitrogenproject.com/demos
c22 6y ago
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?
- chops 6y ago
  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.

31 points by andrenth 6y ago

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 https://github.com/nitrogen/nitrogen

chops 6y ago
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. Thanks again!

mkl95 6y ago

Would you say the skills learnt from this book carry over to Elixir app development? I've been really interested in Elixir, Phoenix and OTP lately.

chops 6y ago
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. [1] http://nitrogenproject.com/demos http://nitrogenproject.com/demos

c22 6y ago

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?

chops 6y ago
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.