This post is Jankom Pog erasure.
- Posts
- 1
- Comments
- 315
- Joined
- 3 yr. ago
- Posts
- 1
- Comments
- 315
- Joined
- 3 yr. ago
The optimal format for interchanging 256-colour palletised animated images of giraffes.
When governments print banknotes, they can sell them and get money to do things at face value, instead of having to get loans and issue bonds where they'd have to pay interest or charging taxes where their citizens would object. In fact, in countries like the EU, UK and USA, despite normal people and normal companies using cash less and less, for the past couple of decades, the amount of cash printed has increased rapidly because as long as people buy it, there's a big incentive for governments to print it. Bigger face value notes mean more money for less printing, so are the best thing to issue, as long as people are buying them.
That leaves a big question of who on earth is buying more banknotes each year than the last. The obvious thing that can be best done by banknotes is storing a large value in a small space with the ability to be moved around without traceability or counterfeiting, which really only matters to money launderers. Things like bank transfers and cryptocurrencies can be traced as long as someone knows who owned the money at some point, but if you buy your bitcoin with cash from someone who doesn't keep records of who gave them the cash, then your crypto wallet is totally opaque to the authorities.
The people involved range from minor things like spouses hiding money in a divorce to tax dodgers to drug dealers to people traffickers to sanctioned governments, and when that's all added up and funneled through opaquely-owned shell companies so it doesn't look like it's Russia or Iran's money buying the cash, there's enough demand for governments to justify building new money printing facilities and issuing higher denomination banknotes.
If you want to learn more, there's quite a lot more detail in Everybody Loves Our Dollars by Oliver Bullough.
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 explicitly stated in A New Hope that they were shooting to miss when the main characters were escaping the Death Star because a tracker had been planted on the Millennium Falcon and they planned to follow it and destroy whichever planet was hosting the rebel base. You can't do that if you don't let them escape. Every other time they're in battle, stormtroopers are shown to be devastatingly effective except when a small garrison is overwhelmed by a vasty larger number of ewoks.
Obviously it cannot be damaged.
No, don't use
CLAMP, useCLAMP_TO_EDGE.CLAMPis a dumb mode for niche applications that all switched to using shaders around the turn of the millennium. No GPUs have direct hardware support forCLAMPand so they have to emulate it instead. You are throwing performance away for no reason.(also, technically, the image is using
CLAMP_TO_EDGEasCLAMPis a 50% mix of the border colour and the edge pixel colour, so it would be greyer if the border colour is grey like the first image suggests.)I've not read the novel, but the quote I replied to is from the film, so that's what I'm going off.
Part of the point that the film is making is that humans will treat each other as non-human and non-people based on minor details - replicants are engineered to be stronger, sometimes cleverer, and shorter-lived than natural humans, and no one could reasonably claim that the thing that makes a human a person is their level of physical strength etc., so there's no need to get into what they do have in common with natural humans to see that they're obviously people.
Once it's accepted that they're obviously people, then the film can examine things like how the differences in how society treats them affects them, and how all the reasons given to hunt down replicants are based on them having normal human reactions to the situations they're put in.
Depends on whether you're in a country that washes eggs before sale too get rid of the cloaca residue or one that keeps it on so eggs can be kept safely at room temperature. Unwashed eggs will have faeces on their shells, and you might not want to cook noodles in faeces.
In the UK, it's because it's the defence's job to notice this kind of thing, but paying for a good lawyer is life-ruiningly expensive, and public defenders via legal aid are paid hourly, but have a cap on the number of hours that's never enough to deal with anything properly, so are either rushing everything and miss things, or are massively overworked and earning well below minimum wage when their unpaid work is included.
I don't know if the same problems extend to Canada, but it's fairly likely, as the adversarial approach just inherently means the defence has to do loads of things that would be someone else's job or not need doing at all under alternative systems, so you have to have a trained professional doing lots of work, and that's inherently expensive, but taxpayers don't like spending money on defending people who probably did crimes.
It's not really the intended use case of Lua to be used in things that will be upgraded after they're released. It's meant for things that need to work exactly the same way in a decade as they do now, and that's best served by sticking to a specific version and either only upgrading to bugfix releases, or sticking to one specific commit forever. Those use cases also are better served by sticking to old versions of any libraries they use that are written in Lua (otherwise they might be hit by regressions or turn out to have been reliant on old buggy behaviour that's been fixed), so probably aren't upgrading to newer versions. That's why the article is making the point that it's not worthwhile for the maintainers of those libraries to keep compatibility with old versions of Lua as the people still using old versions of Lua are probably going to be sticking to old versions of those libraries, too.
It's not that uncommon for games to stutter for 50 ms, e.g. when an async task on a worker thread takes too long and holds up the rest of the game, or when something needs loading. For a Unity-based game, garbage collection can block the main thread for that long if the developer wasn't careful, too. It's also only sampling every 10 ms rather than recording every power state change, so a game that takes less than 10 ms to actually do its processing has a decent chance of missing any sampling points for a while.
The exact quote from the mailing list is:
The 300 ms decay is sized so that a render thread which is only 50-80% busy from periodic vsync and GPU-fence waits holds the boost across its whole busy period at a couple of CPPC_REQ writes total, while an idle core sheds the boost well before it can matter. The energy exposure of a wide window is small because EPP only influences behavior in C0 and an idle core sits in CC6 regardless. If folks want me to make these tunable I am happy to expose them.
I've not seen it so much with Java, but for Lua, it's not an English word, and most things in software are either English words or acronyms/initialisms, so it's usually a safe heuristic to assume anything that isn't an English word should be capitalised.
It's Lua, not LUA. It's Portuguese for moon, not an initialism.
You can't migrate once you've got a plugin ecosystem because you're not the maintainer of all third-party plugins, and the maintainers might have lost interest or died and used a licence that doesn't let anyone else take over.
3DPrinting @lemmy.world What to do with a roll of unprintable filament
For a lot of open source projects, there is a significant audience viewing the code itself rather than just what it does. There's encouragement for the user to open the bonnet and look at it and also tinker with it themselves. Even if you don't do that, there're still ways that the craftsmanship can show through and leave the user thinking about how it was made and how it works, and there's plenty of conventional art where the point isn't to think about the final product but instead what went into creating it.
As for the minified JavaScript in a typical website, it's not that different to graphic design where achieving a purpose for a business can come ahead of any priorities related to being art. Even if we say for the sake of argument that graphic design for commercial purposes is never art, it doesn't automatically mean that anything else that uses the same techniques, like drawing, can never be art.
There are also kinds of art that people produce that are never intended to be experienced by anyone else, e.g. a doodle in a diary, so I'd say there could still be art in code that was only ever seen by its creator and which was totally obfuscated when given to users as an app or website.