Sv: [ANN] Nitrogen Web Framework 2.4 Released

Tue Nov 17 09:10:17 CET 2020

GREAT!!!!  What a good way to start a day reading about your new Nitrogen release!

I've been using Nitrogen on a website for 5 years now without any problems, so it might be time for an upgrade.

/Hans Nilsson
________________________________
Från: erlang-questions <erlang-questions-bounces@REDACTED> för Jesse Gumm <gumm@REDACTED>
Skickat: den 17 november 2020 00:07
Till: Erlang Questions <erlang-questions@REDACTED>
Ämne: [ANN] Nitrogen Web Framework 2.4 Released

Hello Fellow Erlangers and (maybe some of you Nitrogenes)!

I'm proud to announce the 2.4 release of the Nitrogen Web Framework!

What is Nitrogen?

Nitrogen (http://nitrogenproject.com<https://protect2.fireeye.com/v1/url?k=2596db5a-7a0de388-25969bc1-866132fe445e-b46cff6db11e77c8&q=1&e=5bd24435-c2bd-4b69-b01a-03a04484ff65&u=http%3A%2F%2Fnitrogenproject.com%2F>) is an event-driven Erlang web framework that uses Erlang records to generate HTML and Javascript. It is a server-side rendering framework with (usually) a live websocket connection active at all times.

*************************************
Highlights from version 2.4.0
*************************************

* Added built-in Caching. The cache handler is, of course, customizable so that you can plug in your own caching system if you like (Redis, memcached, Mnesia, etc), but the default cache handler uses a caching application called NitroCache (https://github.com/nitrogen/nitro_cache<https://protect2.fireeye.com/v1/url?k=1682befe-4919862c-1682fe65-866132fe445e-26e86d4ae7f0547d&q=1&e=5bd24435-c2bd-4b69-b01a-03a04484ff65&u=https%3A%2F%2Fgithub.com%2Fnitrogen%2Fnitro_cache>). NitroCache is a basic ETS-based cache with a mutex to prevent simultaneous requests to the same key from being calculated in parallel. (This is a heavily modified fork of https://github.com/marcelog/simple_cache<https://protect2.fireeye.com/v1/url?k=3b6ec08e-64f5f85c-3b6e8015-866132fe445e-d397e6ba128f2132&q=1&e=5bd24435-c2bd-4b69-b01a-03a04484ff65&u=https%3A%2F%2Fgithub.com%2Fmarcelog%2Fsimple_cache>)
* Created a new library/tool called `rekt` (https://github.com/nitrogen/rekt<https://protect2.fireeye.com/v1/url?k=5e121910-018921c2-5e12598b-866132fe445e-166f6ba217fc12a1&q=1&e=5bd24435-c2bd-4b69-b01a-03a04484ff65&u=https%3A%2F%2Fgithub.com%2Fnitrogen%2Frekt>) that is sort of a parse_transform that allows inheritance with records. Basically, you can define new records based on other records. This uses a new module attribute called `-extend`. See the readme on the github page for details.
* Nitrogen's templating system now supports Pandoc (https://pandoc.org<https://protect2.fireeye.com/v1/url?k=ce3c89f2-91a7b120-ce3cc969-866132fe445e-3322cff3008ace8e&q=1&e=5bd24435-c2bd-4b69-b01a-03a04484ff65&u=https%3A%2F%2Fpandoc.org%2F>) for converting from and to various formats (like HTML, PDF, RTF, Markdown, etc). For this functionality, you must have pandoc installed on your system.
* Added new tools to assist with creating Nitrogen plugins.
* All documentation has been converted to markdown (from org-mode) for easier editing.
* The usual: New elements, actions, API functions, documentation, etc
* The Full Nitrogen Changelog:
https://github.com/nitrogen/nitrogen/blob/master/CHANGELOG.markdown<https://protect2.fireeye.com/v1/url?k=585b3431-07c00ce3-585b74aa-866132fe445e-373edeaa858a931d&q=1&e=5bd24435-c2bd-4b69-b01a-03a04484ff65&u=https%3A%2F%2Fgithub.com%2Fnitrogen%2Fnitrogen%2Fblob%2Fmaster%2FCHANGELOG.markdown>

One key callout for the Erlang veterans: Nitrogen is one of the few projects still on Rebar2 and reltool. I have begun the work of converting Nitrogen to rebar3/relx. Nitrogen has always relied heavily on some rebar2 and reltool hackery and I haven't had the time to rework it to support rebar3 properly while maintaining backwards compatibility. Nitrogen 3 will use Rebar3, and *may* break some backwards compatibility.

*************************************
A few other things of note
*************************************

As usual, binaries for self-contained quick-start development environments with all supported web servers (Cowboy, Yaws, Mochiweb, Webmachine, Inets) for all supported platforms (Linux, OSX, Windows, FreeBSD, Raspbian) are up for download now on: nitrogenproject.com/downloads<https://protect2.fireeye.com/v1/url?k=6a468095-35ddb847-6a46c00e-866132fe445e-59965b88ae87f614&q=1&e=5bd24435-c2bd-4b69-b01a-03a04484ff65&u=http%3A%2F%2Fnitrogenproject.com%2Fdownloads>

Nitrogen now has a public roadmap and it's up at: trello.nitrogenproject.com<https://protect2.fireeye.com/v1/url?k=312d4d0d-6eb675df-312d0d96-866132fe445e-89f3e28aa46ba1cf&q=1&e=5bd24435-c2bd-4b69-b01a-03a04484ff65&u=http%3A%2F%2Ftrello.nitrogenproject.com%2F>.

One final change, the #nitrogen IRC channel (on freenode) has been retired in favor of a Discord channel. This is accessible via discord.nitrogenproject.com<https://protect2.fireeye.com/v1/url?k=d7898071-8812b8a3-d789c0ea-866132fe445e-2ac672f1b7029876&q=1&e=5bd24435-c2bd-4b69-b01a-03a04484ff65&u=http%3A%2F%2Fdiscord.nitrogenproject.com%2F>.

*************************************
Some Personal Stuff
*************************************

Overall, I'm excited to finally have this new version released. It has been an embarrassingly long time since the last release, and although it has been so long, development has continued slowly and steadily. Nitrogen remains my daily environment and developing with it and for it continues to give me great joy.

There is another major announcement for Nitrogen coming this week. I'll give you a hint: it involves a word that starts with "B" and rhymes with "cook."

***************************************
C'mon! Get this over with already!
***************************************

If anyone is interested in becoming an official part of the Nitrogen team, please let me know. I know nobody really ever has time for open source, but if you're running an application that depends on Nitrogen for revenue or are a young go-getter who wants to change the world by working on a niche framework for an esoteric programming language, hit me up.

Finally, thanks to everyone who contributed code, submitted bug reports and issues, and asked questions. Every little bit helps and you folks are great for it!

And of course, thanks to everyone in the Erlang and Elixir ecosystem. Since coming into Erlang in the late 2000s (with the help of Joe's legendary book), it has been so exciting watching the evolution of the community and ecosystem (especially things like Rebar and Elixir).

The overarching BEAM community remains second-to-none.

Thanks all again, and happy hacking!

-Jesse

--
Jesse Gumm
Owner, Sigma Star Systems
414.940.4866 || sigma-star.com<https://protect2.fireeye.com/v1/url?k=ed9b9077-b200a8a5-ed9bd0ec-866132fe445e-c1d85e31aaaf48f1&q=1&e=5bd24435-c2bd-4b69-b01a-03a04484ff65&u=http%3A%2F%2Fsigma-star.com%2F> || @jessegumm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20201117/d523969d/attachment.htm>