11–20 of 71 posts
It's fine to ask for feedback on your prototype, but that's probably better off as a standalone Show HN. Better for both sides -- you're probably not going to get as much feedback on your project as you'd like since it isn't the actual topic at hand.
In the past I’ve worked extensively in Clojure/ClojureScript. I really like the FP aspects and I came to really appreciate lisp generally, but I much prefer FP style in a statically typed language. I may look at Rust for some performance-sensitive stuff, and possibly Typed Racket for some DSL ideas I’ve been wanting to explore.
which might evolve to
React / Django+DjangoREST / Postgres / Redis / ES / RabbitMQ
Frontend / Mobile: React, React Native, MobX, TypeScript
ML: Pytorch
Ops: GCP, K8s
frontend:html,bulma css, cash js
deployment:terraform
I also primarily use TypeScript/Postgres where I have the choice. For UI I do prefer JSX but not React, I prefer something lighter and ideally supporting or amenable to partial hydration. I’m eager to use Deno more, there’s a lot that appeals to me more than Node. In the past I’ve worked extensively in Clojure/ClojureScript. I really like the FP aspects and I came to really appreciate lisp generally, but I much prefe…
Like what? I’m genuinely curious.
I feel like this question is poorly formed in the age of resume-driven development. I prefer types of problems to tackle. But, I don't have preferred stacks so much as stacks I dislike less that are prescribed for my consistent employment. My least disliked stack is the one that doesn't make me obscure, keeps my future career progression options sub-/Pareto- optimally open, while still making my pay competitive. So i…
Sounds like we're on the same page. I think TypeScript will actually overtake JavaScript eventually. It's just so nice to work with. JavaScript will of course always be supported and a prerequisite, but in terms of professional web and Node.js development on a broader scale, it's hard to imagine going back to writing plain JavaScript when TypeScript provides so much value for relatively little effort. Also, I've upda…
But if you're not able to write things bug-free on the first try already, Typescript can bring a lot of value as well.
One of the reasons we're vanilla is to make it much easier to find people to hire.
Instead of limiting the applicant pool to those who know a particular combination of the frameworks-of-the-day, we can hire from a much larger pool of candidates who are familiar with all of the basics.