easong

Small hiccup in the grand scheme of things. I believe that they will get a product car out this year!

I love mobx (definitely not one of the 58), but I would use redux on large apps (maybe, more than 15 pages?), especially if you don't care too much about performance. Redux has better debugging, forces more structure to the code, has a immutable data story, and there are more resources on the net if you need to bring developers up to speed. There are some configuration options for MobX that force the user to be more organized, but redux still feels more structured.

That being said, MobX is absolutely my go-to state management library now - it's probably the easiest free FPS you'll find anywhere, it's ridiculously easy to write, and it results in fewer LOC.

It definitely has advantages. But I don't think using babel precludes shipping a binary with a standard pre-built config.

Totally. I tell new devs to use typescript. But I don't think using babel precludes shipping a binary with a standard pre-built config.

Microsoft has absolutely done an amazing job with typescript IDE integration. But are there any end-user IDE benefits to typescript over flow/eslint? (Not being snarky.)

I've been using both on separate projects (with MS IDEs) and haven't noticed anything major.

I really wish that MS would release typescript as a collection of plugins for babel that would handle only one thing at a time (eg, the type system). Having my production build, es6 transpiler, type system, JSX compiler and so on (including a bunch of features I would rather didn't exist at all) all in one package feels like a failure of separation of concerns.

I understand that people find Babel's plugin ecosystem confusing and intimidating (it is), but I don't think a separate monolithic typescript that reimplements popular babel functionality is the answer.

Honestly, this sounds like a big step backwards in UX if implemented widely.

I would really rather not have to manually install a million packages when pulling down dependencies - "npm install && npm start" and then going to grab a glass of water feels great.

The given use case of a master parsing library doesn't really resonate. A handful of extra kb on disk doesn't bother me at all for an all-in-one solution, and I've never really had the problem of not being able to find a parsing library on npm to begin with.

(Note: I support trigger warnings and think that they have a lot of use as a tool even outside of the typical context)

I'm in close contact with a lot of social justice groups, specifically ones based out of UC Berkeley. It's not super widespread, but there are absolutely individuals who abuse the concept of triggers as a way to give themselves pretext to be cruel to others, to control conversations, or just as something to get righteously indignified about.

This is an issue with the individuals involved and not triggers per se, but just as with other social technologies it's definitely possible to abuse triggers.

I mean, react (and associated frontend technologies) are just a way of making it easier to write code within the constraints of browsers, which are honestly a small miracle. Yes, they're a pile of hacks upon hacks (the web was designed to share physics papers, not deliver complicated multimedia applications), but they let you write the same code for every major operating system, device, and form factor that exists and deploy it seamlessly over an unreliable network. It's shocking that everything works as well as it does.

And as programmers, everything we use is just papering over the horror of writing network-connected cat-sharing apps on weird-shaped bits of metal - why worry about a light abstraction over the JS build step?

My experience with Atom has also been sub-par, but Visual Studio Code is pretty cool and built on the exact same platform (electron).

I think you're the exact target audience for typescript, for what it's worth. It will give you type checking, IDE integration, compiler errors, modules, etc basically for free and is (not exclusively, and IMHO) built for people who find javascript distasteful.

What stack are you using? The description you give doesn't match my experience with modern javascript (react, webpack, flow/typescript, etc).

If you have to build a desktop app with jquery soup (or even angular), I definitely feel for you.