Skip to content

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

Closed

Description

@nelsonic

Activity

  1. added
    discussShare your constructive thoughts on how to make progress with this issue
    enhancementNew feature or enhancement of existing functionality
    on Jan 22, 2017
  2. changed the title [-]Update tech stack diagram to include Elm![/-] [+]Re-do tech stack diagram to include Phoenix, Tachyons & Elm?[/+] on Feb 6, 2017
  3. changed the title [-]Re-do tech stack diagram to include Phoenix, Tachyons & Elm?[/-] [+]"New Stack" |> Elixir, Phoenix, Elm & Tachyons?[/+] on Feb 6, 2017
  4. jruts commented on Feb 8, 2017

    @jruts
    Contributor

    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 ?

  5. des-des commented on Feb 8, 2017

    @des-des
    Member

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

  6. jackcarlisle commented on Feb 8, 2017

    @jackcarlisle
    Member
  7. self-assigned this
    on Feb 14, 2017
  8. added
    priority-1Highest priority issue. This is costing us money every minute that passes.
    on Feb 14, 2017
  9. nelsonic commented on Feb 14, 2017

    @nelsonic
    MemberAuthor

    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! 👍

  10. nelsonic commented on Feb 14, 2017

    @nelsonic
    MemberAuthor

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

  11. nelsonic commented on Feb 15, 2017

    @nelsonic
    MemberAuthor

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

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

  12. nelsonic commented on Feb 15, 2017

    @nelsonic
    MemberAuthor

    @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
  13. nelsonic commented on Feb 16, 2017

    @nelsonic
    MemberAuthor

    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 ... 🤔

  14. jruts commented on Feb 16, 2017

    @jruts
    Contributor

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

  15. assigned and unassigned on Feb 16, 2017
  16. added
    help wantedIf you can help make progress with this issue, please comment!
    on Feb 16, 2017
  17. pdavidow commented on Aug 30, 2017

    @pdavidow
  18. nelsonic commented on Oct 10, 2017

    @nelsonic
    MemberAuthor

    @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

Metadata

Metadata

Assignees

Labels

discussShare your constructive thoughts on how to make progress with this issueenhancementNew feature or enhancement of existing functionalityhelp wantedIf you can help make progress with this issue, please comment!priority-1Highest priority issue. This is costing us money every minute that passes.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions