steenreem
I would think that the purpose of concepts is to capture information at a higher density than tokens, so you can remember a longer conversation or better produce long-form output.
Given that, I would have expected that during the training phase, the concept model is evaluated based on how few concepts it emits until it emits a stop.
It's not as if the small group of people at the top determine everything else about the company: they only hire the people directly below them, and their influence decreases the further down you go. I think the larger determinant of a company is the business it is in, since that determines at large what people the company is attractive to and which it tries to hire.
There might also be value in having your employees be able to easily physically meet, and then location-dependent salaries make sense.
I would phrase your argument as simple as: you estimate the world is much more likely to become uninhabitable if we don't use nuclear.
What's the worst case of not using nuclear? It's the same as the best case of using it. Best case, nuclear would enable us to entirely phase out fossil fuel energy production, reducing the world's CO2 production by 25%, reducing green house emissions to the point that large parts of the planet no longer become uninhabitable.
Disclaimer: I'm the author
Why isn't short trading done secretly?
Typeless: Great editor tooling for JavaScript without types or annotations
If the US wants more than two colours in their spectrum, they need proportional representation. https://en.wikipedia.org/wiki/Proportional_representation
If content publishers want to post Corona related information that YouTube thinks is false, they'll just have to find/create another platform for it.
However, this condition is not enough, it doesn't cover the case where someone is being watched while they are voting. The condition should be something like:
"we need votes to be so private that only the voter can know what he voted on"
I don't see many solutions to this, except the '19th century' way of voting at a voting station, or a voting machine that can read minds. Obviously it would be pretty strange inputting your vote through thoughts, especially since this system might never allow you to confirm what you voted on.
However, I guess even ballot voting could suffer from collusion since it's not fundamentally private. You could take a hidden camera into the voting box and record your vote, and afterwards get a payout.
I'm surprised it's not more generally accepted as _the_ definition. Note that Markus Hutter the main author is currently working at DeepMind.
A simpler solution might be an editor with an auto-completion feature where completion items can be selected using abbreviations or full names with small errors.
I personally feel flatMap is a much more used method than flat, so if you want to remove one, I would remove flat.
I imagine a system where you publish news using your device (a mobile phone), and encrypted in a way so that only a small group of other devices, which you have explicitly trusted in an earlier step, can decrypt it, allowing only them to trace that the news came from you.
Then those trusted devices will decrypt and re-encrypt the news in such that they can forward it with only their trusted devices. When a device receives news from another, then it won't know whether the sender published that news, or is merely forwarding it.
Because all communication between devices is encrypted, a device can not be confirmed to be using this system, except by a device who he trusts.
When a device is compromised, he will only be able to see if another device is part of the system, if that device has trusted him. Also the compromised device will be able to read news shared to him, but he won't be able to see what device that news originates from.
To make sure that readers can filter news based on what publishers they like, there is the concept of a publisher.
Apart from news, devices can also share publishers. An publisher is a name plus public key. The creator of the publisher has the private key with which he can encrypt news (even before it encrypted for sharing), allowing readers of that news, who have the publisher's public key, to verify that the news came from that publisher. If a publisher is shared with a device while the device already knows a publisher with the same public key, then the device must chose which publisher to keep and which to delete.
Another use-case for threads that I see is when you have work-queues that have different priorities, so you put each queue into its own thread with a matching priority. For example, 1 thread for responding to UI events, and 1 lower priority thread for all background work.
Anyways, none of these use-cases require many threads. What use-case am I missing that makes go-routines useful?
I guess doing something in a thread is a fail-safe way to make sure that 'some time' is spent processing it, so for example for the UI tasks, it would be easy to just dump all handling of UI events in virtual threads.
1) Renting: the protestors rent instead of own the homes they're living in, so their costs go up with the housing prices. The government could have reduced this problem by promoting home ownership in the past.
2) Income inequality: the protestors are not techies, so they won't be employed by Google, and will earn far less than Google's employees. The government can reduce this problem by increasing income leveling.
I think that, if the majority of the people in the area side with the author, there is an argument to be made to, through political means, block bringers of gentrifications such as Google from entering this area.
Some of Google's money will flow to locals not directly employed by Google, but will this offset the increased cost of their living expenses?
Miksilo: a modularity first language workbench
DebtRatchet – Systematically remove debt from legacy codebases
Incremental on the other hand does cool stuff like use the result of the first computation to make the second computation faster, which SmartReactives does not do at all.
So I'd say although the projects are related they don't overlap in scope.