Mars

I’m sorry but framework and library in this post are going to be used loosely, because even React, Vue, Angular, Svelte, etc devs use the terms loosely.

React is mostly a UI library like you would find in most native app development. Of them all them JS frameworks/libraries is one of the less opinionated and with less batteries included. By design it does not does everything. Most other frameworks do way more.

It lets you define custom components. The components can have properties that their parent component defines and internal state. If the state or the properties change the component gets redrawn (magically). There are some lifetime functionalities (things to do on first render for example) and performance improving stuff (memoization) but mostly that’s it.

All the other features you talk about are third party libraries or frameworks that can operate with react or are build on top of and cover the bases, like routing, fetching, caches, server side rendering, styling utility libraries, component libraries, animation libraries, global state management, etc.

The big difference with the vanilla way is that the approach is mostly declarative. The runtime takes charge of updating the DOM when your components state or properties change.

You take a big performance hit, and an even bigger bundle size one, but the speed of development and huge ecosystem of readymade solutions can be really important for some use cases.

Other frameworks take different approaches to solve the same problems:

• Component system for code reuse and organization.
• Some way to manage state
• Some way to decide what to re-render and when.
• Extra stuff. Some frameworks end here, some have tools for everything you would need for a web app.

I just came back to copilot after the preview ended.

Keeps being pretty good at writing boilerplate, and not that good at much else.

For example when I’m writing a struct like “User” it more or less fills the fields I’m going to need, guesses the types and tags.

In new projects is also pretty good at suggesting things I might want to do. Maybe it gets the implementation wrong, but many times affect what I start working on next.

For the legacy Java code bases I maintain at work is completely useless. Maybe Copilot X can do something to help with that, we’ll see.

As a professional bite-mean-for-other-guy taker (right now in Java) this hurts my feelings.

I know it’s a joke, but it’s an old one and it doesn’t make a lot of sense in this day and age.

Why are you comparing null to numbers? Shouldn’t you be assuring your values are valid first? Why are you using the “cast everything to the type you see fit and compare” operator?

Other languages would simply fail. Once more JavaScript greatest sin is not throwing an exception when you ask it to do things that don’t make sense.

It’s super funny, but if you don’t try to use things as what they are not, the type coercion can’t hurt you.

But if you make a tradition of trying to add empty objects and numbers…

The great sin of JavaScript is gracefully (silently) failing when coders do silly things.

Fellas! Why are games today so buggy! Why are they incomplete? I just don’t understand!!!!‽‽???

He is delusional or triying to scare the poor Snoos. If anyone is angry about this and looking for a face to punch they have a clear target and is not some dude with a reddit t-shirt.

They are looking for a suit, no tie, popped up collar wearing, venture capital dudebro looking, jailbait ex-moderating, failure of a CEO.

I think I get were the “server costs” come from. The twitter algorithm they pushed to GitHub FIRST gets a set of like a thousand tweets to show you, then filters them, getting rid of blocked accounts for example. If you use one of the large block lists, you know, to bypass the lack of moderation, there is the “risk” that they neeed to do another request to get enough content to fill your front page of irrelevant stuff you don’t want to see.

I have tried, but I’ve been playing shooters mouse + keyboard for at least 25 years. It’s super hard for me.

Did not even started hahahahaha.

Looked good.

I don’t have to imagine that world, VSCode exists.

I understand the sentiment, but in some way I think you are missing the point. Let me try to explain the appeal.

When you play, for example, Diablo you spend the time with the game making your build. You also play the story and see the bosses but your focus gameplay wise is your build.

Yo go for that skill. You farm that weapon. Yo optimize your buffs and load out.

And when you are done, after 20 or 30 hours… the game becomes extremely easy. Playing your fully builder character has no challenge. And building another is a 20 hour time investment.

So you get into PVP. Or into boss rushes where yo can get marginal improvements. You repeat a very small amount of end game content for months.

Enter the “rogue” mechanics.

The play unit is no longer “the character”, now it is “the run”

You build a full character each run. You make meaningful decisions to make the most of your build with what the game is offering.

If a run goes badly you are 30 min or less away from getting were you were. If you win you can play again for a completely different experience.

You have no complete control about your build, so you can’t really on the same strategy and gameplay for the whole game. You have to engage with every system.

And your reward for playing is choice (more options to better controls your play style) and knowledge (to better use what the game throws at you)

And it’s true you repeat the initial part of the game a lot. But in Diablo (keeping with my previous example) you repeat the endgame. The only diferente is that one is front loaded and the other is back loaded. And initial areas USUALLY have more work put into them in both cases.

Also remember that there are a spectrum between Isaac likes and Hades likes. There are games were chance has lots of importance and a good build in the hands of a bad player can steamroll the game, where in others a bad build in the hands of a great player is viable.