orta

I did a bit of a writeup on the gaps in soundness for TypeScript in the docs, https://www.typescriptlang.org/play?strictFunctionTypes=fals...

Here's hoping https://tc39.es/proposal-type-annotations/ solves this

Yep, it's just a repo of inter-linked markdown docs which you can view or edit on GitHub (or clone if you want to do some more involved editing.) You can definitely think of it as a wiki though as all engineers in the company would have write access.

I was working at Artsy while the OP was CTO (:wave:) and tried to help out a bunch on fostering a good attitude towards OSS - there's quite a few notes in both artsy/README and the blog

- (the making of artsy/README) https://artsy.github.io/blog/2018/08/21/OSS-by-Default-Docs/

- (OSSing our apps) https://artsy.github.io/blog/2019/04/29/how-did-artsy-become...

- (OPs writeup on the philosophy) https://code.dblock.org/2015/02/09/becoming-open-source-by-d...

- (the RFC process) https://artsy.github.io/blog/2019/04/11/on-an-rfcs-process/

Shame to see it happen, but an understandable decision - it's been a few years since I was writing native iOS code and AppCode really felt like a power-user tool in ways that Xcode couldn't.

AppCode team, you did such a great job IMO

One of the protagonists in the book Version Control works in customer service in a role a lot like you're describing, it's a great read for anyone into sci-fi https://www.goodreads.com/book/show/25733442-version-control

I wouldn't use this as an indication of flow's usage, the extension switched to using an LSP so the majority of the work for dev experience happens inside the flow codebase nowadays.

Thanks for putting in the time to make this work from Meta's side! Us folks on the outside appreciate it a bunch

"Neoliberalism" is a specific term for the conceptual forms of capitalism the west has been under since the 70-80s: https://en.wikipedia.org/wiki/Neoliberalism

Yeah, AssemblyScript is a key WASM language variant - I made a list of some of the other TypeScript-like implementations last year. Static TypeScript and TypeScriptCompiler do something similar in order to run inside web pages. At a quick glance, this proposal might get some ideas from the thinking done on BorrowScript

https://github.com/orta/awesome-typescript-derived-languages...

This is a very cool incentive for folks wanting to try get that idea they've had in their heads for a while proof-of-concepted!

Gross

Yeah, for sure, I agree with all of this. I think the best way to write TypeScript is to really treat it like the tagline "JavaScript With Syntax For Types" - some of the extras TypeScript provided from before TC39 were active have much less relevance now.

I've also made a pretty complex thing with shiki (shiki-twoslash which you could say is similar to torchlight but just for TS/JS)

Torchlight definitely a good chunk of work on top of shiki, and as an external API it might be much easier to work with in many non-JS ecosystems.

You could probably codegen the .d.ts output of your types into different the body of API responses (or use it to generate a json schema), forking deno for it is probably overkill

Yep, that is exactly what it is, just a simple GH webhook to azure develops / GitHub Actions trigger. https://github.com/microsoft/TypeScript/issues/46177#issueco...

Big fan, as a very active GitHub user the conversion to GIF for screen grabs had been a constant paper-cut

This was kinda explored at the start of April this year: https://github.com/microsoft/TypeScript/pull/43480

FWIW, sucrase (written in TypeScript) has done a great job of being in the same ordinal of perf as esbuild: https://github.com/alangpierce/sucrase#sucrase

I think there's quite a lot of potential for writing native elementary apps with gjs, https://gjs.guide

Crev is a very cool idea, if I was building a new dependency manager - I'd look into integrating something like crev as early as possible.

elementary OS has an App Store: https://developer.elementary.io

I'm not sure if it'd be big enough to get you doing it full time though.

TLDR: New constraints on how we approach teaching in the handbook / Omits trying to teach JS concepts / New compiler-backed code samples give better tools for describing how things work / PDF and Epub files for offline

I've found Relay to be pretty solid with error handling, though I think the ability in how to handle GraphQL errors does hurt Relay here, but it does for all GraphQL clients.

Re: parent, I also was surprised to see Relay dismissed on the list, it solves every problem they bring up in the list, perhaps maybe not the real-time aspects

Very cool. I'd recommend reading the built-in vscode extension for TypeScript, because with 4.0 we added a feature very close to that for editors into TypeScript and you can rely on our work instead. Links in: https://www.typescriptlang.org/docs/handbook/release-notes/t...

There are research teams at Microsoft exploring a native form of TypeScript ( https://www.microsoft.com/en-us/research/publication/static-... ) but the TypeScript team will never probably look at native support given the goal is to explicitly be JavaScript + Types, and that domain helps balance well with all the other ecosystem players ( https://www.youtube.com/watch?v=8qm49TyMUPI )

There's definitely teams at MS exploring about this problem (e.g. IntelliCode is my favorite for TS https://docs.microsoft.com/en-us/visualstudio/intellicode/in... )

Big fan of the app, and I've met the founder of Letter Opener GmbH before and he's a great guy. Very cool.

Dark

Plausible Labs has always been one I've looked up to: https://plausible.coop/about