throwAGIway

The createElement function is called immediately, and it immediately calls your component function. I don't think this is a significant difference. Many libraries accept a callback and I'm really not ready to call all that a framework just based on that.

Latest version of every browser, not every browser version I was forced to support because it was still used by a big chunk of users...

So this package is not the actual react-dom package I get when I npm install react-dom? Thanks for the correction!

Casdoor is one such Docker image, or Authelia, FusionAuth, Authentik or the Ory stack

Yep, it can potentially download pretty big datasets and then you can explore them entirely client side using Wasm SQLite.

Yep, agreed, also excited about Wasm, it's taking so long though... I was so excited I gave a series of talks at local tech conferences about it... In 2017.

What do you think you're doing when you call render(<App />,...)?

The app I maintain is a complex analysis tool that lets you build queries, explore data and create aggregate visualizations. The state doesn't even fit into URL, and connecting it to a DB... No thanks, that's be much harder and slower.

Not implementing auth doesn't mean using platforms. Just use any of the many OIDC client/server libraries or completely pre-made open source dockerized services.

For example react-oidc-context on the client side and Passport.js on the server, or Casdoor.

Note that this is the full package, and that it's normal to use a bundler that will treeshake things you don't use away. For example react-dom includes server-side rendering functions that are not necessary on browser side.

I was a web developer before jQuery, during jQuery and still am after jQuery. You really want react/similar even for very small apps. I went and tried to implement a simple calculator app without any dependencies just to see if it got better with Web components, but not really, way too limited to be useful for anything other than purely design tokens if you don't want to reimplement React. jQuery is not really necessary any more, the problems it used to fix are solved - but there is still no support to make a reasonably organized and performant reactive application.

BTW not sure what you mean with the useMemo - I built very large applications in React (hundreds of complex dynamic financial analysis pages) and didn't have much problems with it - could you go into detail please?

That's a very un-European view that would mark you as crazy here. Nobody goes to the army to get a job, not even those who can't find a job, and the unemployment office won't try to suggest it - it's not considered a job here, it's a service duty.

In my country we don't have mandatory military service. The "employer of the last resort" is the unemployment office and welfare, not army. I have never heard of anybody going to the army for any other than duty/ideological reasons, desperation for a job might even disqualify you - they want people who are motivated to join the army, not poor desperate people looking for money.

Could you provide a link to these datasets? People always talk about data but never show it. I wanted to make an opinion but couldn't find the data at all - not counting obviously opportunistic inconclusive studies designed to support a predetermined political opinion.

Cisco never was anything comparable to Microsoft.

I hope he kept his stock, short term dips are to be expected.

Nothing with Linux or Windows approaches the battery life, thinness, weight and performance combined.

Go for Preact if bundle size is your concern.

A basic React app is 3 lines of code with an optional but recommended compilation step. You can get a very complex app with 20% of the code compared to Angular. Nothing else of the big ones (React, Vue, Angular, Svelte) comes close. Just don't use bloat like create-react-app, instead make an empty folder and install react and react-dom yourself.

Show me a better one... And please don't say Vue or svelte because these are just the same thing a little differently.

React doesn't have a templating language, React has syntax sugar for JS function calls - a very significant difference especially when you add TypeScript.

Why would we do that? I'd rather pay more than this.

Hooks are not magic, they just increment an index that's used to access the state, which is saved in an array. So you have to call the same hooks at the same time on each component function call. That's it, zero magic.

Async and await is not useful for React, Suspense is done out of necessity. It's have to be generators if anything - but Suspense is older than wide support of generators and async/await too.

You don't have to use hooks nor Suspense at all - just use your own state management and pass it as a prop at the root render call, or no state at all.

Could you expand on the comparison to Munich, please? I can't imagine what could make it so much better it's worth the significant cost increase - unless you take advantage of the business opportunities I guess

The question I always have... Do you really expect people to behave like it's 1980s? Nobody - not the teachers, not the kids, not the parents want that.

I went to school when mobile phones were just beginning to be a normal thing. It took just a year or two before the teachers were like "why the hell don't you just phone your mom yourself?" and "Miss, there is no need to involve us, just call your child and resolve it yourself".

I used to get pretty bad headaches, I just called my mom for permission to go home and went. It'd be much more painful if I had to chase a teacher and convince them they need to call my mom and tell her I need to go home.

With today's technology I can do myself in hours what used to take our team weeks or months. But indeed, nobody buys stuff like that anymore.

You're doing cloud and k8s very wrong if your midrange laptop can beat it. Don't blame tools for your lack of knowledge. It's a complex tool for complex situations, it's not its job to make everything super easy for you. Just don't use it or let someone who knows how handle it.

I was part of such team. We supported one target only - Windows NT 3.5 and better, full-screen resolution 4:3 between 800x600 and 1280x1024, and database was the client's problem - we told them what version of Oracle they have to buy. Is it slow? Probably because your network or server is slow, have fun troubleshooting. Yeah, we were a very performant team because we constrained the project a lot and pushed quite a big chunk of it to the client.

Today I work in a team that supports a wide array of operating systems, device form factors, resolutions and aspect ratios, input methods; we maintain the backend and it's up to us to make it secure, performant and fast for users from anywhere in the world; and of course API access. Customer data doesn't fit on one disk and their processing can't be done with one machine, and they have a globally distributed workforce. We are slower because we do much more.

Yeah, it's tiring.

Why should I care what a protectionist government agency thinks? As a customer, I am very satisfied with the deal Microsoft offered.

Basically, users got a good enough product at no additional charge, greatly reduced costs and operational overhead, and you want the government to force users to pay more?