You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"New Stack" |> Elixir, Phoenix, Elm & Tachyons? #37
changed the title [-]Re-do tech stack diagram to include Phoenix, Tachyons & Elm?[/-][+]"New Stack" |> Elixir, Phoenix, Elm & Tachyons?[/+]on Feb 6, 2017
Not sure if you want to take advantage of it, but you can call this stack 'PETE'. (Phoenix, Elixir, Tachyons, Elm). It sounds pretty catchy.
Might even be worth it to dedicate a new repo describing the PETE stack and why/how to use it, maybe even with some installation scripts/guides to start with the barebones Pete stack.
Perhaps even something like http://mean.io/ for this stack. (pete.io)?
Ok, it's dawned on me that having our "Tech Stack" doc saying one thing and using "New Stack" in projects is sending mixed messages ... so I'm prioritising communicating this better for today! 👍
@jruts I really like the succinctness of "PETE" as a name ...
but I've been racking my brains to think of an evolution of "PETE"
because it sounds like a "boy's name"
and we want to be as inclusive as possible ...
How can we assemble the various letters of the components of our stack into a word.
What about "TEPPE" (which is sadly not a gender-neutral person's name which would be amaze!)
it means "carpet" in Norwegian: https://en.wiktionary.org/wiki/teppe
and means we could have a "Magic Carpet" in the Logo!! 😮 😜
with TEPPE we include PostgreSQL in the Name so the Database Layer is Covered ... 🤔
I kinda like it... Especially with the Magic Carpet reference.
It feels like... a whole new world.
A new fantastic point of view.
No one to tell us no or where to go.
Or say we're only dreaming...
Our reasoning for using Tachyons is that several of our apps are still Server-Side Rendered.
Style Elements appears to be Elm (Client-Side) Focussed.
That's not to say that we won't be experimenting with it and possibly adopting it. 😉
Activity
[-]Update tech stack diagram to include Elm![/-][+]Re-do tech stack diagram to include Phoenix, Tachyons & Elm?[/+][-]Re-do tech stack diagram to include Phoenix, Tachyons & Elm?[/-][+]"New Stack" |> Elixir, Phoenix, Elm & Tachyons?[/+]jruts commentedon Feb 8, 2017
Not sure if you want to take advantage of it, but you can call this stack 'PETE'. (Phoenix, Elixir, Tachyons, Elm). It sounds pretty catchy.
Might even be worth it to dedicate a new repo describing the PETE stack and why/how to use it, maybe even with some installation scripts/guides to start with the barebones Pete stack.
Perhaps even something like http://mean.io/ for this stack. (pete.io)?
Any thoughts @nelsonic @iteles ?
des-des commentedon Feb 8, 2017
@nelsonic do dwly have any projects that have tried out this (awesome) new stack
jackcarlisle commentedon Feb 8, 2017
@des-des https://github.com/healthlocker/healthlocker
adds Most Wanted Programming Languages sub-heading in Readme for Elix…
nelsonic commentedon Feb 14, 2017
Ok, it's dawned on me that having our "Tech Stack" doc saying one thing and using "New Stack" in projects is sending mixed messages ... so I'm prioritising communicating this better for today! 👍
nelsonic commentedon Feb 14, 2017
Can you guess where the analogy is going...? 😉
nelsonic commentedon Feb 14, 2017
😮
from: https://www.wired.com/2015/11/i-turned-off-javascript-for-a-whole-week-and-it-was-glorious/
adds intro to "PETE" stack (name courtesy of @jruts 😉) for #37
nelsonic commentedon Feb 15, 2017
https://github.com/search?q=oops&type=Commits

We all make "mistakes" ...
mine was listening to "haters" and not embracing Elixir sooner!! 😞
adds note on exclusion of OS in "PETE" acronym for #37
nelsonic commentedon Feb 15, 2017
@jruts I really like the succinctness of "PETE" as a name ...
but I've been racking my brains to think of an evolution of "PETE"
because it sounds like a "boy's name"
and we want to be as inclusive as possible ...
How can we assemble the various letters of the components of our stack into a word.
also we are using:
and optionally:
nelsonic commentedon Feb 16, 2017
What about "TEPPE" (which is sadly not a gender-neutral person's name which would be amaze!)

it means "carpet" in Norwegian: https://en.wiktionary.org/wiki/teppe
and means we could have a "Magic Carpet" in the Logo!! 😮 😜
with TEPPE we include PostgreSQL in the Name so the Database Layer is Covered ... 🤔
jruts commentedon Feb 16, 2017
I kinda like it... Especially with the Magic Carpet reference.
It feels like... a whole new world.
A new fantastic point of view.
No one to tell us no or where to go.
Or say we're only dreaming...
re-word Why "New Stack" section to include link to: https://www.goodr…
pdavidow commentedon Aug 30, 2017
Swap out Tachyons for https://github.com/mdgriffith/style-elements
nelsonic commentedon Oct 10, 2017
@pdavidow we've added Style Elements to our "to learn" list: dwyl/learn-elm#96
Thanks for sharing!
Our reasoning for using Tachyons is that several of our apps are still Server-Side Rendered.
Style Elements appears to be Elm (Client-Side) Focussed.
That's not to say that we won't be experimenting with it and possibly adopting it. 😉