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

Post by Arkeus » Sat, Mar 25, 2017, 6:23 AM UTC

ohitsdom wrote: post #5

calebegg wrote: post #2

I've found that there's almost no "first class" support for TypeScript in similar apps like JSFiddle, Codepen, Plunker, etc. If they do support it, it's only the syntax, not the autocomplete and error highlighting (the cool parts!). So I decided to try making my own. Here are a few quick things I've written with it so far: https://goo.gl/zZy697 ("Flocking" behavior in a simple particle system) https://goo.gl/1q2kmr (…

It was really fun to change some values in your Flocking script and see how the particles react.

Post by nojvek » Sat, Mar 25, 2017, 2:21 PM UTC

johnfn wrote: post #39

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.

This is completely untrue. If you follow the progress of TS, you'll see they are completely committed to only adding features that will end up in JS proper. Time and time again they have refused to add features because they aren't part of Ecmascript.

Post by Ciantic » Sat, Mar 25, 2017, 5:11 PM 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 WhitneyLand » Sat, Mar 25, 2017, 7:14 PM UTC

wiredearp wrote: post #40

WhitneyLand wrote: post #36

Earlier quoted context omitted.

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.

If you look up "embrace, extend and extinguish" in the textbook, you will see Microsoft mentioned in the first sentence [1]. If you are old enough to remember Internet Explorer, you've already seen how this works. Consider then that static types do in fact extend JS and perhaps you'll see why this is not so reassuring after all. [1] https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish

Post by bastawhiz » Sat, Mar 25, 2017, 9:18 PM UTC

Ciantic wrote: post #46

bastawhiz wrote: post #34

Earlier quoted context omitted.

Yeah, using Flow with React is painful. Which is weird, considering they're both from Facebook. Want to add a propType for 'children'? Sorry, nope. Want to use the equivalent of PropTypes.node? Good luck with that. The biggest thing that I see as a barrier to entry for TS (and someone please correct me if this is no longer a problem) is integration with build tools from the rest of the ecosystem. Webpack with fancy l…

TypeScript's strong part is the IDE support. It worked great with Eclipse years ago (using the same language server), it worked with Atom years ago. It has Sublime plugin that also uses the language server (not tried this myself). This is because the whole language is build with IDE tooling in mind. It's also approachable, as more language servers are being built the same way, like the PHP language server that is now…