Wait, react is a framework now? People used to say that react is just a model binding library. FYI I haven't used react.

"React is actually a library, not a framework" is definitely a thing people have said here and there since its inception. It's a distinction that doesn't seem to buy anything in terms of explanatory power or clarity, so I tend to ignore it.

I think it's a shortcut for saying that react doesn't have an 'official' routing library (like vue-router) and state management library (like vue's pinia). So depending on what you choose to manage routing / state, one react app can be quite different from another.

Maybe nowadays there is a set of popular libraries for react so it becomes framework-y?

Vue-Router and Pinia have always been optional add-ons for Vue too, however, yet the Vue ecosystem seemed to to fine without those "aaakshually“ kinds of people that feel the need to micro-manage other people’s speech.

Generally the difference between a library and a framework is that you can use bits and pieces of a library to add functionality to your project.

A framework expects most of your project to be shoehorned into it.

Whether something is one or the other depends on which of the two most users are doing. It's not a very interesting argument, though, because debating semantics is the worst use of the limited time you have on this planet.

you can use React like a library, but I have never really seen it done.

Depends on the definition.

jQuery isn’t a “framework” either, at least not like Angular or Vue, though it can be extended with “plugins.”

Both jQuery and React are foundational technologies, so comparison is valid.

jQuery isn’t exactly a “framework” either, at least not like Angular or Vue, though it can be extended with “plugins.”

Both jQuery and React are foundational technologies, and comparison is valid.

Yep, react is indeed a library. Part of the confusion comes from a fact that react community was keen to hijack "react" name and slap it onto their own projects, for example there were react router, react query, react table, etc., so one could have get a feeling that react was like full-fledged framework, while most of these "react" projects were not affiliated with react the library in any way.

Housing price goes down, but there's no maintenance. No shops open nearby, no hospitals, no firemen, no police, no gas stations.

People will flock to cities that still have services. Then the cities will have the same population density as before.

But I guess my line of thinking is the need for these things will be lesser. The hypothesis is society will decrease proportionally There will still be firemen, there will just be less firemen than if measured against "now."

Cixin Liu's Dark Forest theory is security through obscurity. If you don't have any other defense mechanism, at least try to hide.

Hey me too! Japanese trap is great.

Examples examples examples. From the most common use cases to the less common. With annotations and links to the endpoint reference.

Seven Habits of Highly Effective People by Stephen Covey. I read this book during college, but I wish I had read it earlier in my life, like when I was in junior high. This book set my priorities straight.

I completly agree with you. It's a great book and i wish i had read it earlier and i would have done things better.

Marvin the paranoid android

Have you ever experienced your list becomes bloated with items? Then you spend your time prioritizing and reprioritizing the items?

When that happens to me, I just pick one item and forget the rest of the list.

Yes, that also happens from time to time. But I don't spend a lot of time on prioritising stuff at all, I just take the top item on the list and get it over with :)

In case the borrower fails to deliver, the broker lose license, ok understood, but what about the stock itself? Does the transaction gets rolled back? Or will the total number of shares be permanently increased at the cost of the broker's license?

Edit: The lender must write off the stock?

ASP.NET MVC skips the whole ORM part and let programmers deal with the issue however they like. I find this refreshing compared to Rails 2 which enforces ActiveRecord. I hear Rails 3 decouples ActiveRecord but I haven't seen it in action.

This is important if you have a plan to build front end to legacy database.