jjdeveloper

12 ms·

61.
The Future of Full Stack(youtube.com)
3 points by jjdeveloper 5y ago|0 comments
62.
by jjdeveloper 5y ago
I feel that the simplicity of just building on the server and pushing the updates across the wire is where we are heading. So a lot less double up, with regards needing to write both for the server and client. Validation especially will jus
63.
by jjdeveloper 5y ago
So good to see the progress in the Elixir community. Liveview seems to have got lots of peoples attention.
64.
by jjdeveloper 5y ago
The round trip is very quick, websocket with a tiny payload in most cases. This video does a great job of discussing the advantages (skip forward to 6:50) https://youtu.be/8xJzHq8ru0M
65.
by jjdeveloper 5y ago
If you want to save state for the counter to the server you would do a round trip. Otherwise you’d use some light weight JS lib, most popular one for simple interactions is Alpine.js. So simple ui JavaScript use Alpine and something like fo
66.
by jjdeveloper 5y ago
Tailwind gives you inline media queries and the confidence that your css doesn’t impact other elements on your site. Also you don’t need to think up class names. CSS variables are great, I just don’t really understand the value, I guess it
67.
‘This is just no way to live’: What it’s like delivering parcels for Amazon(abc.net.au)
2 points by jjdeveloper 5y ago|0 comments
68.
Phoenix 1.6 released removes the need for Node and Webpack(elixirforum.com)
3 points by jjdeveloper 5y ago|1 comments
69.
Spotify Building with Elixir/Liveview(thinkingelixir.com)
6 points by jjdeveloper 5y ago|0 comments
70.
Elixir's Phoenix framework removing the need to install node(twitter.com)
6 points by jjdeveloper 5y ago|0 comments
71.
by jjdeveloper 5y ago
I really like the way that Phoenix Liveview is trying to solve for this, trying to find the sweet spot in the middle of building multipage apps and SPAs. Great talk about it from the developer here https://youtu.be/8xJzHq8ru