-
The ["PETE" stack](https://github.com/dwyl/technology-stack) is using some languages/framework that evolve rapidly (ex: elm 0.18 to 0.19 recently, see also the list of the release versions for Phoenix…
-
Is there a standard naming convention defined across the board for tutorials. For example, `graphql-node`, seems like it should be named `graphql-node-express`. The way it is written today, almost all…
-
# Funcional |> Concurrente |> Divertido
**Propuesta:**
Introducción al lenguaje de programación _Elixir_ y al framework web _Phoenix_, desde la perspectiva de un programador _Ruby on Rails_.
-
-
Version 0.3 is about **Evolution**, we hope to improve DX and productivity by converting it from a micro-framework into `rails`/`phoenix` like framework. And this is the first step:
- [ ] A cargo t…
-
Phoenix allows us to create a project with or without Ecto support, the idea is that if you can better separate your project into multiple libraries. This is exactly what I do, I have a `BusinessDB` l…
-
Language server support is essential for the future of [phcode.dev](https://phcode.dev). Language servers brings in code auto completion and advanced code assistance features inside phoenix. Almost a…
abose updated
6 months ago
-
Where to begin and what to prioritize?
Some ideas:
* Phoenix Framework (Elixir)
* Ruby on Rails (Ruby)
* Django (Python)
* Laravel (PHP)
* JavaScript
* Shopify
* WooCommerce
* OpenCart
…
-
Are there any plans for a CRDT version of elixiak.
I think with the rise in popularity of the Phoenix web framework, it's a great opportunity for Riak to be promoted as the database of choice for Pho…
-
- The extension of the file: .eex
- Instead of:
![image](https://user-images.githubusercontent.com/52173525/114257726-57ad8380-9998-11eb-9e0d-73f4e7dab6fd.png)
- What about we use the logo:
![eex…