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?
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.
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?
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.
I don't think the problem is the mailing list style of discussion. Looks like it works fine, even for big projects like the linux kernel. What I find frustrating with mailing list is the archive:
* sometimes there is no archives
* sometimes the archive is unsearchable, only browsable
* for archives with search capability, sometimes the search results are not accurate enough
If end users can find answers through mailing list archive, they needn't post nor subscribe.