AnyOldName3

When I’ve seen foundations for homes get poured and they haven’t been on a large construction site that’s already been flattened (where the ability to work around things like trees wouldn’t matter), it’s been done by having one or two builders fill up a wheelbarrow with concrete where the concrete mixer lorry could drive to, then wheel it to where the foundations were being poured and empty their wheelbarrows into the foundations.

This machine looks much bigger than a wheelbarrow, and you still need to dig the foundation, so I don’t see how it could possibly need less space to be cleared than just pouring concrete into a hole would.

A shame they’re not brave enough to print a building on a bedslinger.

The problem with this kind of innovation is that it’s improving what’s already one of the fastest and easiest parts of building a house. Digging foundations, plastering the walls, doing the plumbing, doing the electrics and laying the flooring can all individually take longer than the bricklaying, and are much harder to automate.

It’s not automatically resolved on Windows. Applications can export a symbol to hint to drivers that they want the big GPU, just like they can hint with their .desktop file on Linux, but other than that, it’s up to the driver vendor to notice a bunch of users complaining about poor performance in a particular game and manually adding it to a massive whitelist, or the user manually changing a setting.

There’s a parameter that can be set in a .desktop file, PrefersNonDefaultGPU=true, which should force an application to use the dedicated GPU on a laptop, but obviously that doesn’t work for command-line-only tools.