gotofritz

Why are you afraid of the truth

"Class act" is doing a lot of lifting there

You say "exemplar", as if the 10 year long 2 to 3 upgrade which almost killed the language didn't happen... if it wasn't for the massive userbase of data scientists and academics which kept using it no matter what, python would have gone the way of perl

Great tool and great choice of video, it keeps the reactionaries away from your project

The legacy app is absolutely NOT fast if you have a significant amount of notes. Still worth using because the current app simply lacks the functionality (they "solved" the costantly freezing problem by preventing people from selecting more than 50 notes at once, for example). But certainly not fast

Unnecessarily pedantic, yes.

"Smartphones" are only "smart" compared to what came before. Which to the youth is irrelevant, because before their day. To them a phone and a smartphone are the same thing. All your comment does is to let everyone know you are old enough to remember phones which weren't smart. Not sure what it adds to the conversation

There has ALWAYS gotta be a pedant, isn't there...

The article is obviously about smartphones and social media

This would have been a good discussion 10 years ago, but these days it's pydantic first, hardly ever use dataclass

> Things like ... are probably not decided on and implemented by the engineering team but are coming down as a requirement from the top

Yeah, welcome to the real world. We _all_ have to handle requirements like that, except maybe when we build our portfolio site

> It'll be interesting to see if whoever steps up to maintain React at that point will be able to grok its internal complexity, and to see how the community reacts to a rift when their favorite view library team pushes for one vision but the moved-on "rockstar facebook engineer" pushes for a different vision.

Kind of what is going on with Node / Deno... and like the chap who quit the Angular 2 team to start Aurelia hoped would happen to him (sorry buddy!). My guess is that he'll find out that there is more to a framework than rockstar developers. Like Facebook backing, or like UX designers being in love with your library because it reflects their approach to problem solving. Like CRA, hot module reloading and all that jazz. These are all things that put React where it is today

> hooks don't have an obvious context.

I mean, that's the whole point of hooks... they get the context of whatever host function scope they are in. That's why the 'reusable logic' spiel. So if you create a useLocalStorage hook, for example, you can then plug it into any function component and it will use. It's as if each function was an invisible class, with an invisible this.state

Organising apps by language seems weird...

Micro services are a different kettle of fish though

Firstly, the benefits they offer have often little to do with the architecture itself, but with the bigger picture (separating teams, CIs, allowing different stacks, managing costs, scaling, etc).

Secondly, unlike microkernels, not all microservices have to talk to every single other microservice. If you have a service to send emails, say, there'll be a few services that interact with it, but the majority won't. The same for an image resizing service.

So what you say doesn't necessarily hold

I am looking forward to Betty Boop remixes...

Yes, of course, we all have the time for endless fiddling with regular expressions... please