11–20 of 52 posts
One immediate benefit would be better support for react. Yes it works but not always as seamlessly as Angular/TypeScript.
So then what's the benefit? Doesn't codepen support TS?
> It's similar to JSFiddle, JSBin, CodePen, and others So then what's the benefit? Doesn't codepen support TS?
I really like these code playgrounds but my main issue almost always comes down to flexibility regarding which code I can keep private, which I can make public, and so on.
Just something to keep in mind as you decide to take this ahead.
Now to play with some typescript.
This is not related to the typescript aspect which, I realize, is the point of this contribution. I really like these code playgrounds but my main issue almost always comes down to flexibility regarding which code I can keep private, which I can make public, and so on. Just something to keep in mind as you decide to take this ahead. Now to play with some typescript.
>>> Code snippets you write are automatically saved in a compressed form in the URL. This has a few benefits:
- Your code never leaves your machine unless you decide to share your URL. Since the snippet is stored in the URL fragment (the part after the #), the CodeWich web server doesn't even log your code snippets.
- You don't have to rely on CodeWich's availability. You can download your own copy and run it locally, or host it somewhere you control, and you'll always be able to decode your CodeWich URLs to get the original code.
This is not related to the typescript aspect which, I realize, is the point of this contribution. I really like these code playgrounds but my main issue almost always comes down to flexibility regarding which code I can keep private, which I can make public, and so on. Just something to keep in mind as you decide to take this ahead. Now to play with some typescript.
https://github.com/calebegg/codewich#features : >>> Code snippets you write are automatically saved in a compressed form in the URL. This has a few benefits: - Your code never leaves your machine unless you decide to share your URL. Since the snippet is stored in the URL fragment (the part after the #), the CodeWich web server doesn't even log your code snippets. - You don't have to rely on CodeWich's availability. Y…
Codewich reproduced it from the URL?
p.s.: the more I think about it, the more I like it but is there any fear that some programs can't be compressed into a url?
p.p.s maybe not: http://stackoverflow.com/questions/417142/what-is-the-maximu...
This is not related to the typescript aspect which, I realize, is the point of this contribution. I really like these code playgrounds but my main issue almost always comes down to flexibility regarding which code I can keep private, which I can make public, and so on. Just something to keep in mind as you decide to take this ahead. Now to play with some typescript.
I've also provided a standalone version on Github which you can download and run locally or install somewhere in your company's intranet for internal use. It has no analytics and no outside communication.
https://github.com/calebegg/codewich/releases
If there are other ways to support this use case, let me know. I'm open to suggestions.
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'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
With type definitions available from npm and @types, its pretty easy compared to the TSD and Typings I had to use earlier.
This is not related to the typescript aspect which, I realize, is the point of this contribution. I really like these code playgrounds but my main issue almost always comes down to flexibility regarding which code I can keep private, which I can make public, and so on. Just something to keep in mind as you decide to take this ahead. Now to play with some typescript.
I agree completely. One of my goals with this was to make it entirely client-side. Your code is never sent to my server. It's stored in the URL after the #. You can share it by sharing the URL, but otherwise it's yours. I've also provided a standalone version on Github which you can download and run locally or install somewhere in your company's intranet for internal use. It has no analytics and no outside communicat…
Really smart and (to me) original.
This looks interesting. I've been wanting to mess about with TypeScript, but had only gone so far as scanning through the tutorials/intros. Nice to have a sandbox setup from the start. Also, really enjoying your "Flocking" script. Well done.
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…