5 ms·

I specifically said that I didn't mean from a technical point of view. I know full well about typescript's features :) I generally try to avoid talking about th

by shados 10y ago

I specifically said that I didn't mean from a technical point of view. I know full well about typescript's features :) I generally try to avoid talking about things I haven't tried extensively. And for your second point, I love to learn something new! But that is specifically something I've had to deal with far too many times already (not just with TypeScript), so it wouldn't be new. And it is quite common these days for companies to show you their code when they get near offer time, or to discuss their architecture and coding philosophy, so I very rarely have surprises on that front anymore. Doesn't mean I don't learn new things. I don't avoid things that haven't burnt me yet. Heck, even if they did, it might be because I didn't do it right. But there's only so many times I can get burnt before I start avoiding certain things :)

KirinDave 10y ago
> I generally try to avoid talking about things I haven't tried extensively. I don't mean to press this point too hard, but you feel comfortable offering a dissuasive opinion on something but not "talking about it"? I don't know how to interpret that. > But that is specifically something I've had to deal with far too many times already (not just with TypeScript), so it wouldn't be new. I don't know what you mean by this either, I'm sorry. > And it is quite common these days for companies to show you their code when they get near offer time, or to discuss their architecture and coding philosophy, so I very rarely have surprises on that front anymore. I certainly think the second half of this is true. I think it's quite rare for companies to actually share real production code in any significant volume, unless of course it's already in the open. > But there's only so many times I can get burnt before I start avoiding certain things :) Again... what do you mean? Are you implying that Javascript has burnt you? Or Typescript? Or you won't use technology funded by Microsoft? I'm sorry, I read your post several times trying to understand your intent, but I ended up with more questions than I started with. That's probably on me.

by shados 10y ago

KirinDave 10y ago

> I generally try to avoid talking about things I haven't tried extensively. I don't mean to press this point too hard, but you feel comfortable offering a dissuasive opinion on something but not "talking about it"? I don't know how to interpret that. > But that is specifically something I've had to deal with far too many times already (not just with TypeScript), so it wouldn't be new. I don't know what you mean by this either, I'm sorry. > And it is quite common these days for companies to show you their code when they get near offer time, or to discuss their architecture and coding philosophy, so I very rarely have surprises on that front anymore. I certainly think the second half of this is true. I think it's quite rare for companies to actually share real production code in any significant volume, unless of course it's already in the open. > But there's only so many times I can get burnt before I start avoiding certain things :) Again... what do you mean? Are you implying that Javascript has burnt you? Or Typescript? Or you won't use technology funded by Microsoft? I'm sorry, I read your post several times trying to understand your intent, but I ended up with more questions than I started with. That's probably on me.