Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"New Stack" |> Elixir, Phoenix, Elm & Tachyons? #37

Closed
nelsonic opened this issue Jan 22, 2017 · 12 comments · Fixed by #45
Closed

"New Stack" |> Elixir, Phoenix, Elm & Tachyons? #37

nelsonic opened this issue Jan 22, 2017 · 12 comments · Fixed by #45
Assignees
Labels
discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! priority-1 Highest priority issue. This is costing us money every minute that passes.

Comments

@nelsonic
Copy link
Member

nelsonic commented Jan 22, 2017

image

The New Stack for 2017 is:

see: #27

@nelsonic nelsonic added discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality labels Jan 22, 2017
@nelsonic nelsonic changed the title Update tech stack diagram to include Elm! Re-do tech stack diagram to include Phoenix, Tachyons & Elm? Feb 6, 2017
@nelsonic nelsonic changed the title Re-do tech stack diagram to include Phoenix, Tachyons & Elm? "New Stack" |> Elixir, Phoenix, Elm & Tachyons? Feb 6, 2017
@jruts
Copy link
Member

jruts commented 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
Copy link
Member

des-des commented Feb 8, 2017

@nelsonic do dwly have any projects that have tried out this (awesome) new stack

@jackcarlisle
Copy link
Member

@des-des https://github.com/healthlocker/healthlocker

nelsonic added a commit to dwyl/book that referenced this issue Feb 14, 2017
@nelsonic nelsonic self-assigned this Feb 14, 2017
@nelsonic nelsonic added the priority-1 Highest priority issue. This is costing us money every minute that passes. label Feb 14, 2017
@nelsonic
Copy link
Member Author

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
Copy link
Member Author

Steve Jobs introduces iphone
Can you guess where the analogy is going...? 😉

@nelsonic
Copy link
Member Author

@nelsonic
Copy link
Member Author

nelsonic commented Feb 15, 2017

https://github.com/search?q=oops&type=Commits
oops

We all make "mistakes" ...
mine was listening to "haters" and not embracing Elixir sooner!! 😞

@nelsonic
Copy link
Member Author

nelsonic commented 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.

  • Phoenix
  • Elixir
  • Tachyons
  • Elm

also we are using:

  • Postgres
  • Linux
  • Erlang

and optionally:

  • Blockchain
  • ProgressiveWebApps
  • Redis
  • MobileFirst
  • OfflineFirst
  • WebRTC

@nelsonic
Copy link
Member Author

nelsonic commented 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!! 😮 😜
image
with TEPPE we include PostgreSQL in the Name so the Database Layer is Covered ... 🤔

@jruts
Copy link
Member

jruts commented 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...

@nelsonic nelsonic mentioned this issue Feb 16, 2017
@nelsonic nelsonic assigned iteles and unassigned nelsonic Feb 16, 2017
@nelsonic nelsonic added the help wanted If you can help make progress with this issue, please comment! label Feb 16, 2017
@pdavidow
Copy link

Swap out Tachyons for https://github.com/mdgriffith/style-elements

@nelsonic
Copy link
Member Author

nelsonic commented 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. 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! priority-1 Highest priority issue. This is costing us money every minute that passes.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants