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.
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 suppose the problem is that I see typescript as the fragmentation. If MS leverages babel (they can even keep shipping TS as their own thing if they want, I just want them to provide babel plugins), we can all use that and focus on making it as cross-compatible and streamlined as possible. (Well, really, we can focus on providing a single well-documented on-ramp to new javascript developers, which I think is the main problem and the one MS set out to own with typescript.)
Right now, we have the typescript ecosystem, the babel ecosystem, and the other wannabe ecosystems. If I like Typescript's type system but want to use babel for async-await (for instance, I'm aware it's in TS next), I'm basically SOL. Babel has more end-users (AFAIK), generally has the first/only implementation of <feature>, and my impression is that the surrounding development community is larger and more active (typescript stuff tends to come down from On High).
For instance, you can use https://github.com/gcanti/babel-plugin-tcomb to get run-time type checking with babel/flow for free. That's really cool! Unfortunately, the same is not possible with typescript (AFAIK), because MS decided that was out of scope. If Typescript was offered as a babel plugin, somebody else could implement it for typescript and we could all be happy.
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.
Of note is that of these, I think only the elixir and ruby (?) solutions are distributed. Additionally, Phoenix channels are doing a lot of work that the other solutions aren't.
(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.
While the cryptocurrency conversation online is dominated by right-libertarians, I think you'll find that a lot of hard/radical leftwing direct-action types are very much obsessed with cryptocurrency and structures like the DAO. I personally don't look at the cryptocurrency scene/DAO with anything more than bemusement, but I think that community is often presented in a very unpleasant light (look at the weird nerds!).
A more charitable stereotype might be that cryptocurrencies and automated contracts appeal to anyone who thinks that they can design (through their technical expertise) a better world than the current political elites. I'm not saying that they're right or that their line of thought hasn't been historically responsible for atrocities, but I don't think it's fair to paint them as sociopaths.
It's disappointing that this article doesn't address the various animals with a degree of biological immortality (eg jellyfish, lobsters). I'm not convinced that the laws of thermodynamics make (human-scale) aging inevitable and insurmountable if there are several unrelated critters who have managed it.
More likely is that immortal monkeys don't make evolutionary sense given the energy requirements.
We don't have anything remotely close to a free market in housing, though - I would be much, much more apt to lay the blame for the current housing crisis at the feet of misguided zoning and NIMBYism (often dressed up in pseudo-leftist rhetoric). We need to build more houses, for anyone, as quickly as possible and as much as possible if we want to shift the curve of rental pricing. Right now, the market wants to build - we should let it. If the state wants to step in and build more housing too, great, but first it should get out of the way.
I agree that tiny houses are a feel-good distraction.
That's how these things always go (15 years is the usual "sentence"). Assuming that the US is willing to play ball, they'll start negotiating now and eventually trade him for a visit from the director of the CIA or some rice or whatever. AFAIK no American since the Korean war has actually served a sentence from the DPRK.
I don't want to get into too much detail on this out of respect for Otto. I wasn't there when he took the poster down, but I definitely believe that he did.
Also, no invisible lines were crossed - we were told very specifically before arriving in NK by the tour company that under no circumstances should we go to the staff-only floor of the hotel and that people had gotten in trouble for going there previously (it's moderately infamous). My memory of that is hazy, but it may even have been in response to a question about that floor from Otto. As I said in another comment, I really don't think that the NK government is interested in oppressing tourists for no reason.