Languages like Java are awful in that respect, as they make it super hard to declare new types.
People expect for a type to contain some logic, but it doesn't have to. e.g. a configuration is a type that contains other types that contains yet other types. But I have never seen it done like that in languages like Java.
This is the first version, here are some servers you can add, if you don't know any:
mathstodon.xyz - math
mastodon.art , sunny.garden - art
c.im - general
These kind of articles are sooo dumb. Those tech CEO's are acting like complete idiots.
1. You can measure productivity in a precise way only in some mindless repetitive jobs e.g. are Twitter employees more productive now that they are in the office. How do you measure that (if you measure it in profits, app quality etc. I'd say that they are much less productive)
2. Each person is different. I may be 10% more productive at home than in the office, and my coworker may be 20% less productive. Why do I have to be in the office because of some stupid statistic?
3. Fine, let's say people who work at home have lower productivity. But working from home enables you to hire people from all over the world as well as people who cannot go to the office for various other reasons. I'm not a big tech CEO, but somehow it seems to me that the best candidate in the world, working at 90% of their capacity will still perform better than the best candidate who happens to live in your city and is willing to travel.
4. Working from home is also linked to a better well-being, which means less turnover, better working environment etc.
5. Most importantly: the fucking planet is dying, because of carbon emissions and you want to just dismiss the obvious and already implemented solution for reducing those by letting people not travel to work, just because of some 10% profit increase.
Yes, you can use the same convention in React (or rather use React with the same convention), this is mentioned in the description actually.
As far as "prop drilling" goes, I never understood what is the problem that some people have with it.
If you just put your state in one object its just one more param that you have to pass to components. Do we really need a big-ass framework just because of one extra param.
Also, by passing state explicitly, you get a clear visibility over which component needs what. And it also allows you to restrict which component uses which parts of the state.
Will probably edit it, as many people complained. The focus here is useful predictions, in the sense of predictions that have utilitarian value, but string theory doesn't make any predictions at all, which is another issue altogether.