News for hackers. Stuff that matters.
[dead]
Re:Ask HN: What tech stack would you choose for building you... by dang on Tuesday December 17, 2019 @06:12PM (#21820013)
Please don't do this here.
Re:Ask HN: What tech stack would you choose for building you... by arkanciscan on Wednesday December 18, 2019 @11:08AM (#21826256)
Do what exactly? Participate in discussion? Voice my frustrations? Contradict the popular opinion?

You know, I think I agree. Commenting on this site is a huge waste of time.

Re:Ask HN: What tech stack would you choose for building you... by dang on Wednesday December 18, 2019 @01:31PM (#21827735)
I thought it was obvious, but in case not: please don't post flamebait like "$language can die in a fire". We're trying to avoid programming language flamewars (or any flamewars) here. They get repetitive very quickly, and nasty too.

Also, can you please not post unsubstantive comments like https://news.ycombinator.com/item?id=21822655? We're trying for more thoughtful conversation here. If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the spirit of this site to heart, we'd be grateful.

Btw, I tend to agree with you on https://news.ycombinator.com/item?id=21810266 and thought that was well put.

Re:Ask HN: What tech stack would you choose for building you... by rvz on Monday December 16, 2019 @06:06PM (#21808517)
> TypeScript can die in a fire, and if you disagree you should join it.

This is probably a poor attempt at satire, but I'll bite. Actually yes, I'd rather disagree and jump in the fire to use TypeScript than to plod along using JavaScript with its clumsy type-system, designed by a team of clapping seals and to watch all the hell it truly brings.

If you think TypeScript should die in a fire then perhaps I'll see all companies using JavaScript in Dante's Inferno.

Re:Ask HN: What tech stack would you choose for building you... by arkanciscan on Monday December 16, 2019 @07:08PM (#21809059)
I don't dislike TS because I love JS so insult it all you like. Besides TS is just a superset of JS so it's still got all of JS's warts. It's just a glorified linter.

I dislike TS because it provides no benefit to me. I already have a type checker, it's called a browser. I dislike TS because a bunch of people who wasted their time learning Java or C# are forcing me to deal with it because they can't do their job without a compiler to tell them how.

You need types, that's your problem, not mine.

Re:Ask HN: What tech stack would you choose for building you... by JamesBarney on Monday December 16, 2019 @07:19PM (#21809151)
It's great that you always write bug free code, but then typescript was not written for you, it was written for the rest of us who write the occasional bug, refactor an API that we didn't realize another developer was using, or can't quite remember the order or shape of args that a library call takes that we only use once every 6 months.
Re:Ask HN: What tech stack would you choose for building you... by arkanciscan on Monday December 16, 2019 @10:49PM (#21810340)
Why don't your tests catch your TypeErrors? You do have tests don't you?
Re:Ask HN: What tech stack would you choose for building you... by stevenwliao on Tuesday December 17, 2019 @02:38AM (#21811497)
Why would you write a test instead of a type declaration if you had the choice?
Re:Ask HN: What tech stack would you choose for building you... by arkanciscan on Wednesday December 18, 2019 @11:13AM (#21826309)
TS checks at buildtime. It can't guard against runtime TypeErrors because JavaScript is a dynamic language (despite all the effort to "fix" that). Tests can catch all TypeErrors, TS can't. Why use two tools to do the job that one can do alone?
Re:Ask HN: What tech stack would you choose for building you... by Can_Not on Tuesday December 17, 2019 @01:49AM (#21811275)
Tests aren't an alternative to types. They're better together.
Re:Ask HN: What tech stack would you choose for building you... by ng12 on Monday December 16, 2019 @07:24PM (#21809193)
I agree that the type checker isn't that useful but I still use TypeScript for two reasons:

1. Accurate autocomplete.

2. Typing my domain models so they play well with autocomplete.

Re:Ask HN: What tech stack would you choose for building you... by arkanciscan on Tuesday December 17, 2019 @12:30AM (#21810930)
The first thing I do when I install an editor is turn all auto-completion off. Especially the auto-closing brackets. Drives me NUTS!
Re:Ask HN: What tech stack would you choose for building you... by gubsz on Monday December 16, 2019 @05:40PM (#21808238)
I can't tell if you're being sarcastic or not, but I'm really curious about the TypeScript hate. Besides some odd type mapping here and there, I've really enjoyed using it over plain old JS.
Re:Ask HN: What tech stack would you choose for building you... by arkanciscan on Monday December 16, 2019 @06:54PM (#21808934)
TypeErrors are just not a problem that I need a compiler to solve for me.
Re:Ask HN: What tech stack would you choose for building you... by odyssey7 on Monday December 16, 2019 @07:55PM (#21809401)
I used to feel that way — and in some situations I still do, like for a short script that I think won’t change much over time. But for a lot of situations I realized that I had so many things to keep track of myself. If there was an easy way for me to be looking back over my shoulder less, like with static typing, I was all for it.

Static typing lets me front-load the effort of making sure many different buggy cases won’t happen. The alternative is for me to think really hard proving to myself that those cases won’t happen each time I come back to the code in the future to add a feature or make a change.

Re:Ask HN: What tech stack would you choose for building you... by arkanciscan on Monday December 16, 2019 @10:31PM (#21810266)
More like front load all the effort of every error that may or may not happen.