Sawamara
Joined 9 years ago
Joined 9 years ago
BTW, before someone screams whataboutism: adjusting your worldview according to facts and applying your moral standards to all countries is not whataboutism. Its a prerequisite to being able to morally condemn any action.
Some of these talking points fall apart upon typing them, let alone posting.
Are you even hearing yourself? Cities existed before billionares did. Society existed before pricks with god complexes started thinking that order and society organized the other way around.
Get off from Rand. Learn some actual history.
When you have the viewpoint of the maverick freegunning CEO/main architect, and you have a direct stake at what you do, of course you can switch the tasks up to make everything fresh. After all, no one is going to control you in any way whatsoever.
That does not go for anyone with a well-defined set of responsibilities,placed, say, in an "agile" environment. And besides, working above and beyond your means there just means you get more and more tasks in exchange, nothing else. Yaay?
So what this code demonstrates is that if you have to look up a billion keys, that is going to be slower than if you have to look up two keys for an object.
Additional reading for this: https://v8.dev/blog/fast-properties From this article:
const sparseArray = []; sparseArray[9999] = 'foo'; // Creates an array with dictionary elements. In this example, allocating a full array with 10k entries would be rather wasteful. What happens instead is that V8 creates a dictionary where we store a key-value-descriptor triplets. The key in this case would be '9999' and the value 'foo' and the default descriptor is used. Given that we don't have a way to store descriptor details on the HiddenClass, V8 resorts to slow elements whenever you define an indexed properties with a custom descriptor: