xodeus

6 ms·

1.
by xodeus 4y ago
> TS catches me writing numerous bugs a day I see this sentiment a lot but I honestly can't think of any non-trivial bugs that TS has caught for me. 99% of the bugs it catches I would see 1 second later when my page hot reloads and
2.
by xodeus 4y ago
This comment has just triggered my PTSD from every Typescript project I've had to work on.
3.
by xodeus 4y ago
I hope you're right, I've been waiting for Typescript to die for years
4.
by xodeus 6y ago
But you're not getting the wrong answer, it's doing exactly what it should do. That one isn't really even a weird language quirk like the others. It's just assuming you're not aware that parseInt can take a 2nd argu
5.
by xodeus 7y ago
That plugin is the worst thing I've ever seen
6.
by xodeus 7y ago
I take the train as well, but only because it would take me just as long to drive + parking costs in the city are insane
7.
by xodeus 7y ago
I would 100% rather drive 25 minutes each way instead of sitting on a train for 40 minutes each way even if I could use my laptop/phone the whole time
8.
by xodeus 8y ago
found the answer in the full proposal. Variables will always be assigned to, never checked for equality. To me this is pretty average and seems like it will cause magic numbers/strings/etc if I can't use constants where it ma
9.
by xodeus 8y ago
If I do the following: let visFilter = 'foo'; const newState = match (action) { {type: 'set-visibility-filter', filter: visFilter} => console.log(visFilter) } What happens? Is it checking if action.type