Decide on tech stack

[therealklanni]

Objective: frictionless development and devops

• Firebase hosting / database / auth

Framework

• Vue
  • low barrier to entry (i.e. low learning curve)
  • very little boilerplate
  • allows for quickly iterating and improving
• React
  • most popular
  • all the good things that come with React
  • moderate boilerplate
  • quickly iterate, but arguably not as quick as Vue due to slightly more boilerplate
• Angular
  • more boilerplate is necessary (contributes to friction)
  • less quick for iterating
• Elixir

CSS library/framework

• Bootstrap
• Material
• CSS resets only (no library/framework)
• other

Native Mobile?

• Yes - Vue Native
• Yes - NativeScript Vue
• No
• Maybe later

[troym9731]

Elixir is out if we are using Firebase. I guess at this point, do we want to use any sort of framework? If we're going to use anything, I'd prefer to mess around with Elm, but perhaps vanilla is the way to go.

As far as native goes, what kind of native mobile app are you thinking?

[alexsasharegan]

+1 Vue

[alexsasharegan]

Wait a second, what are we building exactly?

[troym9731]

Basically a redesign of the current site. One day, we might expand the functionality to include more features like letting recruiters post to a specific channel that people can easily opt-out of or something. So yeah, it'll never be a big thing, but could be fun to mess around with something.

[therealklanni]

Elixir is out if we are using Firebase. I guess at this point, do we want to use any sort of framework? If we're going to use anything, I'd prefer to mess around with Elm, but perhaps vanilla is the way to go.

Well, I do think we want a framework of some sort. The plan with our Elixir attempt was to have an admin panel for accepting or resending invites, and a job board that can be posted to without needing to be a Slack member. So definitely enough functionality to warrant needing a framework of some sort.

I'm personally not too interested in Elm. Also, like we talked about privately, at this point I would prefer using something with minimal friction. That way we can just focus on Getting Shit Done™️.

As far as native goes, what kind of native mobile app are you thinking?

I wasn't really thinking of anything, just throwing the idea out for brainstorming. I think ideally (or at minimum) we just design it "mobile first".

[therealklanni]

One day, we might expand the functionality to include more features like letting recruiters post to a specific channel that people can easily opt-out of or something. So yeah, it'll never be a big thing, but could be fun to mess around with something.

Yeah, definitely want a MVP approach. We can iterate and add features. Definitely don't want to try tackling all the "new feature" stuff right up front.

Basically a redesign of the current site.

Redesign, but also rebuilding it from the ground up. The original (current) site was built from a weekend project I built as a way for low-technical-aptitude people to easily stand up a "request invite to a private Slack" website. So when we set it up for our Slack it was just quickly hacked together.

[therealklanni]

So just to weigh in my opinion, I think I lean towards Vue for its simplicity. We should be able to develop quickly, I think.

[troym9731]

Well, I do think we want a framework of some sort. The plan with our Elixir attempt was to have an admin panel for accepting or resending invites, and a job board that can be posted to without needing to be a Slack member. So definitely enough functionality to warrant needing a framework of some sort.

Ok, cool. I'm down.

So just to weigh in my opinion, I think I lean towards Vue for its simplicity. We should be able to develop quickly, I think.

Sounds good to me, I just have zero interest in Vue. I'll help where I can, but I can't guarantee my motivation will be too high.

[therealklanni]

I just have zero interest in Vue

Well, what would you be interested in?

[troym9731]

Nothing that I could guarantee wouldn't cause friction, so I think we should go with Vue. I can rewrite the UI on my own after v1 😁

[therealklanni]

Well by friction I just meant learning curve, etc. For example, with Elixir we had to learn a whole new language. It was definitely fun, and I love Elixir, but our inexperience also lead to hurdles we ultimately couldn't get over. So "less friction" in that sense.

[troym9731]

I think the only hurdle we couldn't overcome was the postgres integration with Phoenix. We just had that one weird issue. Elixir itself only seemed to be the issue because of its infancy, although most people using Phoenix at that time also used Postgres, so I have no idea what was happening haha. And neither did the Elixir Slack!

But I understand the benefits of using something like Vue, as it has a low barrier of entry for others not including this team. Elm has a much higher barrier of entry.