zebracanevra

Hopefully some collaboration can be made between swfchan and the IA. swfchan claims to have 217753 flashes: http://swfchan.com/ (Edit: NSFW. Would recommend an adblocker before opening, at least.)

It archives flashes (and their threads!) from /f/ and others. A great historical resource.

The presentation of swfchan may not be for everyone, but it does hold an immense amount of data.

Noticed that on my 5T (using Nova Launcher). If I disable the OnePlus Launcher package the navigation gestures cease to work.

Some small towns like Bundanoon [1] have banned water bottles, but in no way have water bottles been banned across NSW.

There has been a push from leading supermarkets Coles and Woolworths to ban single use plastic bags, with great success. But that's a private matter, not from the government. Other states have banned them, but not NSW. [2]

[1] https://www.theaustralian.com.au/news/nation/bundanoon-in-wo...

[2] https://www.abc.net.au/news/2018-12-03/supermarket-ban-sees-...

In Sydney, the public transport trains refer to all of their passengers as "customers" as well.

Every single time I am referred to by that name over the PA it weirds me out. Maybe if this was a private system, but for public transport? Customer is just the wrong word.

When I purchase a product, Google can track that package if it detects tracking info.

When I book a flight, Google notifies me when the flight is leaving, providing suggestions about when to leave my house in order to make it.

All of these things can be done from reading your email. For someone invested in the Google ecosystem, this is a nice and seamless integration that helps me in my life. That is why they are extracing data from your mail.

fetch's Response.text also returns a Promise, so you'd have to await twice:

  const lines = (await (await fetch(myUrl)).text()).split('\n');

> If this were 70.5GB instead of 705MB and the data exhibited identical performance, the final archive would be 4.1GB smaller

I don't think the savings for a file 10x as large can be extrapolated. This likely wouldn't work as the (default) window size for XZ would be too small; the similarities would be too sparse. To get the same benefits you'd need to use at least 10x as much memory by increasing the window size.

I believe write cost is ms/write

0.006 write cost = 410ms

0.03 write cost = 1966ms

In node, require()'ing a dependency is stateless - it searches ./node_modules/ for the module, then ../n_m/ then ../../n_m/, etc, until it finds an appropriately named module.

In JSPM/SystemJS, require()'ing/importing a module is still by name (as it supports NPM modules), but the package.json file has to be parsed in order to map module names to an installed module version. Note, this mapping is only done in the developer environment - once you build a bundle all the mapping is statically compiled into one file.

Previously, worker dynos never slept. On the new free dynos, you now get a free worker dyno, but the tradeoff is that the app must sleep for 6 hours/day.

Does that sleeping time include the worker dynos? If it does, when do they sleep? Workers can't "timeout" like web dynos can.

This also removes the 750 free hours, so now you cannot spin up a 2X/PX dyno to test out something needing more resources than the 1X.

The solution to deadlocking is using async all the way down - i.e. don't use .Result. you can also tell C# not to resume on the same context after an async call by using .ConfigureAwait(false) on the tasks, thus preventing two locks on a context, and the deadlock.

The author states two threads accessing a single resource is a race-condition, but that's only true when the threads are competing for that resource - in the case outlined in the article, it would be sequential, and only one thread would be accessing the resource at one time. No race condition.

I think it's not too wise to think of async/await as a special coroutine which never uses multiple threads, but as an easy way to write synchronous code and have it execute asyncronously. If you need fine control over what threads are used, maybe you're better off controlling it manually.

Correct me if I'm wrong, but I'm pretty sure this has been in Chrome Beta for at least 2 or 3 months - it was hidden in chrome://flags