Show HN: Codewich – A live-updating TypeScript/CSS/HTML playground

Post by seattle_spring » Sat, Mar 25, 2017, 12:16 AM UTC

jiaweihli wrote: post #24

seattle_spring wrote: post #21

Earlier quoted context omitted.

Couldn't the same be said about TypeScript? "I wish Microsoft would drop TypeScript at this point. It's been a nice contribution and spurred some competition. But there is no real vision for how it's going to add a lot of value above and beyond Flow."

This is a bit meta, but both of you stated a position without providing a concrete rationale. Something to consider is that people can gloss over an explanation for convenience. For example: in the previous sentence, I didn't provide any proof that it's accurate. You could make the argument that nobody glosses over explanations for convenience. I don't think it's necessarily worth proving every statement, because tha…

Post by bastawhiz » Sat, Mar 25, 2017, 12:58 AM UTC

WhitneyLand wrote: post #11

I wish Facebook would drop FlowTypw at this point. It's been a nice contribution and spurred some competition. But there is no real vision for how it's going to add a lot of value above and beyond TS. One immediate benefit would be better support for react. Yes it works but not always as seamlessly as Angular/TypeScript.

Post by WhitneyLand » Sat, Mar 25, 2017, 2:32 AM UTC

z3t4 wrote: post #26

WhitneyLand wrote: post #11

I wish Facebook would drop FlowTypw at this point. It's been a nice contribution and spurred some competition. But there is no real vision for how it's going to add a lot of value above and beyond TS. One immediate benefit would be better support for react. Yes it works but not always as seamlessly as Angular/TypeScript.

Flow is JavaScript (with type annotations) while Typescript is an entirely different language that needs to compile to JavaScript. You do not need any source maps for Flow as it just replace the type annotations with spaces. So you get to eat the cookie and keep it, while with Typescript you eat the cookie and lock yourself in.

Post by johnfn » Sat, Mar 25, 2017, 4:05 AM UTC

smdz wrote: post #18

WhitneyLand wrote: post #11

I wish Facebook would drop FlowTypw at this point. It's been a nice contribution and spurred some competition. But there is no real vision for how it's going to add a lot of value above and beyond TS. One immediate benefit would be better support for react. Yes it works but not always as seamlessly as Angular/TypeScript.

I wish the same. Unfortunately not many devs are trying out TypeScript. I've used React+TS for a year now. It works perfectly. The decorators in TS are great to use with the react-redux implementations - makes the code look less verbose The only problems I have faced is when type definitions are not available for certain libs. The workaround is simple - using "require(...)" instead of "import .. from ..." statements…

Post by wiredearp » Sat, Mar 25, 2017, 5:10 AM UTC

WhitneyLand wrote: post #36

z3t4 wrote: post #26

Earlier quoted context omitted.

Flow is JavaScript (with type annotations) while Typescript is an entirely different language that needs to compile to JavaScript. You do not need any source maps for Flow as it just replace the type annotations with spaces. So you get to eat the cookie and keep it, while with Typescript you eat the cookie and lock yourself in.

No, this is hyperbole and misleading. Follow their roadmap and stated direction. They have always been committed to aligning with standards and whenever ES adopts new functionality they gravitate to it's lead. They will never drift off to some mutation that isolates you from the JS ecosystem or its benefits.