Curiosum Blog

The goal of this tutorial is to lay out the basics about queries, mutations, subscriptions, and everything around.

Staying on top of our game as developers can mean stalking new libraries and updates to our favourite languages. Maybe reading some industry blogs. But I never wanted to be a narrow-minded specialist – and that is why I enjoy a weird podcast or two every day.

Everyone learning a new programming language has probably been there. There’s a missing piece in the new programming language, probably a library.

Almost every programming language has at least one web framework in its ecosystem. In such a crowded space, the Phoenix web framework consistently ranks as the most admired in the world. My ambition with this article is to explain why it became the top pick in web development. Interested?

When we start to materialize our app from an idea into code, in the first days, weeks, and months, we create, develop and test our app locally, on our machine.

In the programming language world so dominated by an object-oriented paradigm, there is a strong need to popularize languages such as Elixir - a productive, scalable, functional programming language that consistently ranks at the top of the most loved programming languages in the world.

Offering a unique approach to interactive and real-time web development, Phoenix LiveView emerges as an interesting technological choice. Learn more about what makes Phoenix Framework's younger sibling stand out and how it compares against other contemporary counterparts.

Elixir and its ecosystem is gradually becoming the go-to platform for many web application developers who want both performance and productivity without a tradeoff. With a thorough crash course of Phoenix Framework's hot deal, Phoenix LiveView, using which we'll build a Messenger-like live chat application, we'll try to demonstrate that with Elixir it's easy to write real-time messaging apps that leverage the lanugage's concurrency capabilities.

Have you ever thought about making and handling reusable pieces in Phoenix? Or splitting big HTML templates into smaller, easier-to-read parts?