4 ms·

Just pick something and stick with it, every technology has its problems.

by nso95 8y ago

noncoml 8y ago
You are right! I should stick with Scala. It will also give me the opportunity to learn a new language! Play looks good, but maybe I should go with Scalatra instead? Should I be using Slick? It's quite different than any ORM I used so far, maybe I should bake my own Scala ORM. OK then, here we go. One more decision, REST or GraphQL? GraphQL seems to be the future. Let's go with that. Man, types are nice and Scala's type system is powerful, but sometimes I wish I had the flexibility of a dynamic language. It would make prototyping much faster. Fuck it, "git checkout -b node_v2"
- nso95 8y ago
  (ノಠ益ಠ)ノ彡┻━┻
- nostrademons 8y ago
  May I recommend creating an AI to automatically rewrite your codebase into the flavor of the month, thus saving yourself significant amounts of labor which you could use to create an AI to improve the AI which is rewriting your codebase?
- abledon 8y ago
  This is an example of some of the best performance art on hacker news
  - smt88 8y ago
    Although I love it and upvoted both comments, it's also an example of why straightforward comments waste much less time/text than jokes/satire (on HN)
- anon15476372 8y ago
  > types are nice and Scala's type system is powerful, but sometimes I wish I had the flexibility of a dynamic language. It would make prototyping much faster. You can use both scala and clojure seamlessly. I'm writing my first gui app in clojure for prototyping swing, but if I choose to rewrite parts of it in scala the rest of the clojure code would continue to work. There are several ways. using clojure in a scala project: https://github.com/Geal/sbt-clojure https://github.com/Geal/sbt-clojure using scala in a clojure project: https://github.com/technomancy/lein-scalac https://github.com/technomancy/lein-scalac jvm polyglot with maven: https://stackoverflow.com/a/9676895 https://stackoverflow.com/a/9676895 example: https://blog.michielborkent.nl/blog/2016/07/26/clojure-from-scala/ https://blog.michielborkent.nl/blog/2016/07/26/clojure-from-...
jbg_ 8y ago
On a single project, I agree. But each time I start a new pet/side project I like to use a different stack. It's a good motivation to learn new technologies, and you learn more about them by using them "in anger" than you do in a purely theoretical environment.
shams93 8y ago
Looking at nuxt.js, express and mongodb and then deploying customer pages as static pages on s3 rather than running these dynamically from the app. Picked up 100 customers in a single day so now I have to move quick.

Just pick something and stick with it, every technology has its problems.

by nso95 8y ago

Just pick something and stick with it, every technology has its problems.

You are right! I should stick with Scala. It will also give me the opportunity to learn a new language! Play looks good, but maybe I should go with Scalatra instead? Should I be using Slick? It's quite different than any ORM I used so far, maybe I should bake my own Scala ORM. OK then, here we go. One more decision, REST or GraphQL? GraphQL seems to be the future. Let's go with that. Man, types are nice and Scala's type system is powerful, but sometimes I wish I had the flexibility of a dynamic language. It would make prototyping much faster. Fuck it, "git checkout -b node_v2"

nso95 8y ago
(ノಠ益ಠ)ノ彡┻━┻
nostrademons 8y ago
May I recommend creating an AI to automatically rewrite your codebase into the flavor of the month, thus saving yourself significant amounts of labor which you could use to create an AI to improve the AI which is rewriting your codebase?
abledon 8y ago
This is an example of some of the best performance art on hacker news
- smt88 8y ago
  Although I love it and upvoted both comments, it's also an example of why straightforward comments waste much less time/text than jokes/satire (on HN)
anon15476372 8y ago
> types are nice and Scala's type system is powerful, but sometimes I wish I had the flexibility of a dynamic language. It would make prototyping much faster. You can use both scala and clojure seamlessly. I'm writing my first gui app in clojure for prototyping swing, but if I choose to rewrite parts of it in scala the rest of the clojure code would continue to work. There are several ways. using clojure in a scala project: https://github.com/Geal/sbt-clojure https://github.com/Geal/sbt-clojure using scala in a clojure project: https://github.com/technomancy/lein-scalac https://github.com/technomancy/lein-scalac jvm polyglot with maven: https://stackoverflow.com/a/9676895 https://stackoverflow.com/a/9676895 example: https://blog.michielborkent.nl/blog/2016/07/26/clojure-from-scala/ https://blog.michielborkent.nl/blog/2016/07/26/clojure-from-...

jbg_ 8y ago

On a single project, I agree. But each time I start a new pet/side project I like to use a different stack. It's a good motivation to learn new technologies, and you learn more about them by using them "in anger" than you do in a purely theoretical environment.

shams93 8y ago

Looking at nuxt.js, express and mongodb and then deploying customer pages as static pages on s3 rather than running these dynamically from the app. Picked up 100 customers in a single day so now I have to move quick.