dom0

Yes, this was done on purpose :)

> Machine learning excels at classification, and trash sorting is at heart a classification problem.

Classifying by physical properties is even easier by simply classifying by physical properties. Want to pull all ferrous metals out of a pile of stuff? Just use a magnet. Want to sort tin from plastic? Blower and conveyor bins by flight distance.

Incidentally, those elements not easily covered by this kind of sorting (which has been used for many years) is also not easy to cover by magical do-all machine learning, which will have a hard time sorting plastic-coated paper from paper from plastics, just like the processes above.

Just hook an old Quantum Fireball or something similar up to the power, they spin up with no controller connected.

"Leaked"

No, perpetual motion means more energy from less. This moves mined rock downhill, so the work of moving it uphill was done by geological formation.

~infty / until the mechanical brakes are worn down after the battery is fully charged from driving.

1.3 m/s² is quite something, quite a bit more than a typical tram or S-Bahn (both ~1 m/s², which is still quite a pull...).

You don't really need a toolchain, it can all be done lazily be the web application server.

> without horrible hacks like sticking the asset checksum in the URL.

What's wrong with this approach?

> One operation from over 50 years ago is your example? Back then the spooks were doing far worse, conducting operations against domestic civil rights groups.

Or torturing Americans civilians for eh... testing whether interrogation techniques would work on the real enemy(tm) as well.

Some blamed the NASA hack (this day 30 years ago) on the Russians at first.

(And that actually wasn't off by much, see the KGB hacks).

Python if statements will branch on very few processor instructions in the VM; so I don't think branch prediction of the processor is able to predict different Python if's — they're all the same to it.

Well, that... and even simple Python VM instructions tend to take dozens of insns to execute.

Much plain reference data is missing from the docs (like return types). Its neat to describe a function, but if you don't hand out the API, then the docs are not all that useful.

Django has a very deep package tree, there are tons of stuff in there — a lot of things you wouldn't expect.

> I'm not sure that you've taken the time to understand python development practices.

I think this tone is misplaced here.

There are still widely used packages that don't work with pip, like PyQt.

Ruby is just used rarely outside RoR, realistically speaking.

Render. The specularity of the surfaces is not quite right yet... with some more tweaking this could sure pass as a photo, though. Some wear marks are odd, too, but that can happen in real-life, too.

The cycles render is a pseudo-random path tracer, so the less samples are taken the higher the random noise. Increasing the samples and some other tweaking reduces the noise significantly, but also takes much more time. Denoising the rendered image can produce better visual IQ for less render time.

See https://docs.blender.org/manual/de/dev/render/cycles/optimiz...

Title is inaccurate, Windows, Linux and macOS are all affected.

> Microsoft is issuing security patches to all supported Windows versions at 10 AM, Tuesday, September 12.

> Information on Linux updates will be provided as soon as they are live.

> All iPhone, iPad and iPod touch devices with iOS 9.3.5 and lower, and AppleTV devices with version 7.2.2 and lower are affected by the remote code execution vulnerability. This vulnerability was already mitigated by Apple in iOS 10, so no new patch is needed to mitigate it. We recommend you upgrade to the latest iOS or tvOS available.

By definition, if your site is down, you don't need your assets.

Does not seem to affect Europe.

In fact, right now YouTube loads far quicker than it has for the last seven to ten days, where it would take ages to load any YouTube page.

Durable has a very specific meaning for I/O and is just not correct here.

POSIX does intentionally not specify any durability at all (e.g. a no-op fsync is explicitly permitted).

The rate of computation is obviously very similar for threads and async, but the rate of multiplexing is not. Switching between processes or threads takes more time than switching between fibers/coroutines. So the general observation that for massively multiplexed workloads fibers/coroutines are lower overhead is generally correct, but the more interesting question is of course "what qualifies as a massively multiplexed workload?" ... I'd argue most kinds of web application servers don't.

Other systems (Windows and I think Solaris, but some more obscure systems likely do this as well) can do asynchronous disk IO, but it's not perfect, either.

I think the main reason Linux doesn't really do it is that asynchronous IO is an intrusive change and there would be just too much work to implement it in all the file systems etc.; i.e. "not worth it".

Many applications which are not OK with synchronous disk I/O seem to find thread pools good enough: reasonably easy to implement, reasonably portable, usually performs ok.

The "BOM" lists a 35 Ah / 12 V battery, which is reasonable. A 420 Ah battery is (a) a boutique item (b) should weight around 120-140 kg (c) does not fit into a toolbox (d) costs significantly more than 299 $.

—

From a professional standpoint I'd nag about

> the battery is laid into the tool tray. Plenty of extra space in this toolbox, which protects the system from dust and the sun.

A closed box is not a good place to keep actively cooled electronics; less so when it's a black box in the sun.

My data point would be Borg Backup, which, if you were to consider Bountysource to be payment for development, is under-financed by perhaps a factor of 40. 80+ % of funding came from three organizations.

And what I've heard from other maintainers is that Borg seems to do comparatively well.

So no, if you think in terms of payment, donations do not work in the open source ecosystem.

It's far easier to make a phone surviving regular toilet dives than teaching people appreciation of things, or mindfulness. Ain't nobody got time for that.

Going through eight phones in ten years is an interesting choice for someone being disgusted by Appleconomics...?

> Innocent until proven guilty is an American ethical precept.

B-7, miss!

This concept predates Americans by a number of years; it certainly wasn't invented there. The idea can be traced to ancient Greek and was already applied by the Romans.