Tongue-in-cheek comment that I've read somewhere is that folks flee Democrat-run cities due to high taxes and mismanagement and move elsewhere, but then continue voting Democrat to bring back the same policies they wanted to escape from.
1,099 karma · joined May 8, 2018
Isn't this about government (IRS et al.) categorization of contractors vs. employees and not about GOOG specifically? IIRC there is a specific reason contractors cannot receive employee perks or even participate in team morale events.
(a) That's a messy, unappealing closet.
(b) The Alexa interaction felt awkward. Probably a touch interface would've worked better.
(c) Ugh, (used?) boots on the TV stand.
(d) Many of the clothing items we own are Asian items without barcodes. Wonder how the import would work on those.
(e) The website (chicisimo) could use a lot, and I mean a lot of copywriting love. So many walls of text. Some fashion photos should be front and center. It is hard to understand what is going on in the animated iOS screen.
It looks like they were asked by US regulators to sell it off due to privacy concerns: https://www.reuters.com/article/us-grindr-m-a-beijingkunlun/...
Greta visited the US and gave some compelling speeches. Will she visit China and India and do the same?
[1] https://www.forbes.com/sites/rrapier/2018/07/01/china-emits-...
[2] https://qz.com/india/1581665/indias-carbon-emissions-growing...
"Imagine paying rent for a home with rats, cockroaches, lead paint and mold. That’s what far too many of the estimated 600,000 residents of New York City public housing are doing, even after a lead paint scandal led to an investigation by federal prosecutors." [1]
[1] https://www.nytimes.com/2019/07/30/opinion/new-yorks-public-...
[1] https://www.economist.com/united-states/2019/09/05/donald-tr...
> Sponsored by some of the country's biggest companies: https://lesbianswhotech.org/newyork2019/#Sponsors
I don't know if this is representative of the current times, but sad if so.
Another friend had a persistent cough getting over a cold and was given oxycodone in liquid form "to help sleep." She never took it.
Both of these were at major facilities in the Bay Area. Thinking at least some of the blame falls on the docs.
Cooperative scheduling is used to schedule tasks on executors. A single executor is expected to manage many tasks across a small set of threads. There will be a far greater number of tasks than threads. There also is no pre-emption. This means that when a task is scheduled to execute, it blocks the current thread until the poll function returns.
Because of this, it is important for implementations of poll to only execute for very short periods of time. For I/O bound applications, this usually happens automatically. However, if a task must run a longer computation, it should defer work to a blocking pool [1] or break up the computation into smaller chunks and yield back to the executor after each chunk. [2]
"poll" here refers to the callback function in the future that actually does the work.
[1] https://docs.rs/tokio-threadpool/0.1.15/tokio_threadpool/fn....
All of the data needed by a task is contained within its future. That means we can neatly sidestep problems of dynamic stack growth and stack swapping, giving us truly lightweight tasks without any runtime system implications. ... Perhaps surprisingly, the future within a task compiles down to a state machine, so that every time the task wakes up to continue polling, it continues execution from the current state—working just like hand-rolled code. [1]
[1] https://aturon.github.io/blog/2016/09/07/futures-design/
Good reading list at the bottom of https://areweasyncyet.rs, starting with this post that uses generators as an example: https://boats.gitlab.io/blog/post/2018-01-25-async-i-self-re...