kitten_mittens_

Aren’t PWAs only supported on Google’s very own browser?

> It’s really hard to find good C# talent that isn’t stuck in an enterprise development mindset.

I’ve found that C# devs manage quite well in F#, and the ergonomic way of doing things is sufficiently different to break people out of the 3+ levels of inheritance I’ve seen some small C# projects devolve into.

That said, the community is smaller.

Recently I was looking at my 200Kb app minfied for what was the largest portion of it, and, Lo and behold, react-dom comprised a little under half that size.

Part of this is because React and ReactDOM haven’t switched over to ESM (and still use CJS), but calling react small is probably not entirely honest, at least if you use it like most folks do.

If you’re using a bundler, it’s not that hard to remove extra locales. Functionality on the other hand...

If you’re using Docker on Windows, bind mount propagation isn’t a thing. Adding a new file (or maybe a folder) on the host machine means you have to restart docker.

This is especially bad in node development when you are trying to work on your npm dependencies.

Overall, I think the post is a little too dismissive about the performance implications of bind, and says a new function trigger rerenders.

In IE 11 and Safari for example with Babel transpilation, arrow functions are going to eat your frame rate alive, especially if you have a text input handler with some sort of validation around it. Even in latest Chrome and Firefox, you end up with inputs that feel slow.

I agree PureComponent and object equality cancel the benefits of each other out a good deal of the time.

The pure without handelers approach has the notable exception of a sortable table with inline editing, or even checkboxes, where row index of the handler matters.

Ultimately, it is better to make new devs to react aware of avoiding bind in render, than it is to retroactively add constructor placed binds in the app when frame rates are below 25-30 by default. Something I’ve seen quite a bit in redux apps.

Air quality is still a big issue too.

You sound like you’ve never flown Lufthansa (economy). Plane food, I think, is illustrative of how far most airlines in the US have fallen.

Maybe just not react-router.

Eslint and a Webpack dev server would have you covered in that regard.

It's pretty hard to argue that Amazon's relationship with the city is not toxic.

There are plenty of nimbys around Lake Washington. Even if one was to improve transit more on the east side of the lake, population density is low enough because of the lack of multifamily housing that it's a losing game.

People with long commutes that don't want the corresponding increase in traffic are probably justified. I personally wanted light rail to go out to Redmond, but that seems hung up on three counties (not just King).

I left Seattle just before Capital Hill and the U-District were served by light rail though. Maybe things have changed.

The post you're responding to is probably referring to languages that are further afield from JavaScript than Typescript (or coffeescript).

After wrestling to get get purescript code within a factor of four difference between IE 11 and modern Chrome, I think the suspicion a lot of folks with a background in JS have for "compiled" v. "transpiled" is well deserved.

Just because you target a runtime doesn't mean the nuts and bolts of ergonomics like existing library usage, profiling, and debugging are covered well.