Investigate tech stack options - Githubissues

jakaarl / fkat

Keeper's Audio Tool

0 stars 0 forks source link

Investigate tech stack options #9

Open jakaarl opened 8 years ago

jakaarl commented 8 years ago

For some POC stuff, Node.js/Express with Jade templates is fine. However, the choices aren't carved in stone. Options for the following should be explored and listed, with strengths and weaknesses:

programming language
web framework/library (MVC or such)
web sockets (or whatever push technology we choose) library
template engine and/or other UI tools and libraries
other utility libraries (eg. ID3 tag support, audio streaming)

The ideal programming language for fKAT would be:

high-level, fKAT is not an OS or a device driver!
readable - concise is good, but readable is better!
productive (this is highly subjective)

Stretch goals:

interesting to use/learn
something familiar enough, but not too much so
the above two would kind of rule out Java, but...
static typing!!!!1111 (yes, this is why I'm not happy with JS)

Framework/library targets:

sufficiently abstract, with nice API for web sockets and whatever stuff we need
not Spring, I get to use that plenty (no hard feelings, I love Spring)

jakaarl commented 8 years ago

Some ideas to consider:

Haskell or Erlang/Elixir or Dart, provided there are suitable frameworks/libraries available
Elm for front-end?
Akka or other actor library?
perhaps Python would be an option?
some bells and whistles to go with Java to make it seem fresh and interesting?