Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

codewich.com

Post reply on HN
Print view View original

21–30 of 52 posts

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

#21

Post by seattle_spring »

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.

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."

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

#23

Post by paradite »

Good idea to encode the code in the url.

Unfortunately I think Chrome has a limit on the length of url you can paste into it. I tried copying the url of a slightly longer code into text editor and a new Chrome tab, the latter failed with a audio signal.

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

#24

Post by jiaweihli »

seattle_spring wrote: post #21
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.

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 that'd be extremely time-consuming. But if you provide an opposing viewpoint, back it up with clear reasons (this helps filter out positions that are undefendable), and I'm interested in defending my position or continuing the discussion, then we can have a meaningful discussion from that.

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

#25

Post by Nadya »

This is the cleanest layout I've seen for one of these playgrounds. 95% of my screen estate is the editor and preview - you shot the UI off the side and kept it out of my way. Thank you for that! The only thing missing for me are transpilers for CSS/HTML. I'm a bit spoiled in being able to use SCSS and Pug over at Codepen. Between choosing between autocomplete/error highlighting for .ts or SCSS/Pug support I sadly will pick the former.

I'm totally understanding if the only goal is to support .ts and there are no future plans to add scss/pug support, but I'd switch to using this in an instant over using Codepen if it ever gets added!

I'll play around with it and let you know my thoughts after I use it a bit. :)

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

#26

Post by z3t4 »

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.

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

#27

Post by spion »

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 believe that one area where TS could stand some improvement are multi-package projects. https://github.com/Microsoft/TypeScript/issues/3469

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

#28

Post by jstarks »

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.

What's an example of a TypeScript program where erasing the type information won't produce valid ES6? I had thought Flow and TypeScript were the same in this regard, but I am not an expert.

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

#29

Post by evmar »

jstarks wrote: post #28
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.

What's an example of a TypeScript program where erasing the type information won't produce valid ES6? I had thought Flow and TypeScript were the same in this regard, but I am not an expert.

TypeScript supports ES7 features, for example. It also has a few language-local quirks (like parameter properties, described https://www.typescriptlang.org/docs/handbook/classes.html ).

I find the grandparent argument pretty unconvincing though. People writing Flow are generally using JSX or ES modules (the Flow docs recommend the latter, for example), both of which require a transpiler like Babel to be used in a browser anyway.

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

#30

Post by beaconstudios »

faceyspacey wrote: post #20
beaconstudios wrote: post #10

Earlier quoted context omitted.

I use TypeScript in my startup - it's great and provides a lot more code stability over raw JavaScript but as you build up your type definitions you will likely hit a "roof" where TS doesn't support the next feature you would logically want. There's also no reflection on interfaces (as they're a purely compile-time construct like C macros) which sucks if you want no-noise DI. But overall it's really awesome and getti…

What do you mean by "the next feature you would logically want"?

well in my experience, and this has happened a few times with different requirements which is why I was generic, what happens is you try to use more and more of TypeScript's features to get strict typing (keyof, mapped types, discriminated unions etc) and they work great for 80% of cases. Then you push the feature too far and it falls down. For example, I managed to get tsc to hit a "stack depth exceeded" error by adding a minor variation on an existing complex type that I'd created. I find with TS types, less is very often more unfortunately. I'm trying to use TS like Haskell and it just doesn't play ball.
Post reply on HN