There's a great deal of labor involved in building+preparing casks, storing them, monitoring, maintaining the temp/humidity of a space. Additionally, a good chunk of the price of aged whisky is just due to the fact that the product is constantly evaporating and you're getting a lower yield on the same initial input. Price increase != value created
You're missing the point. The difference between three-year-old and fifteen-year-old whisky is mainly due to capital costs, not labour costs. According to the LVT, capital costs are not real.
> product is constantly evaporating and you're getting a lower yield on the same initial input
This so-called 'angel's share' accounts for ~2% per year, not 10%.
> According to the LVT, capital costs are not real.
Capital costs are not real in LTV?
A carpenter takes wood, nails and hammer and creates value making tables.
Hammers are a capital cost and are made the same way - workers are a factory xreate value by assembling steel and other components making a hammer.
Steel workers un a steel mill create value by turning iron into steel.
Iron miners create wealth by mining iron.
And so on.
Capital costs are accounted for. Not turtles all the way down, but labor - newly created value comes from labor. The value in a hammer comes from the labor to make it a year ago when you bought it.
Well, right, but that's different from "can reproduce the original work". I "can" start typing out song lyrics but it doesn't mean that I stole the songs I've listened to.
> When comparing password hashes, use constant time comparison instead of ==.
If you were comparing plaintext you'd get some info, but it seems overly cautious when comparing salted hashes. Maybe anticipating an unknown vulnerability in the hash function?
I'll get this occasionally when I've scrolled to the end of an article without realizing, attempt to scroll further a few seconds later, and then have my eyes/vision caught off guard by the absence of movement. Missing a stairstep was a good example--there's a similar moment of "frozen time" in both cases
There's some jank involved depending on which combo of x/wayland, window manager, and compositor you're using, but if you can manage to get virtual monitors working on an ultrawide it's great.
A lot of recent models also support "picture by picture" mode, allowing you to connect two separate inputs to the monitor and avoid doing anything in software.
I mostly agree, but there is one slight benefit: whenever I read one of these articles, each topic acts as a little quiz where I get to test whether I think it's a do or a don't before seeing the explanation
I think it actually adds some of the human part back in. "Hey, got a sec?" in person comes with quite a bit more context--body language, tone of voice--and a pretty quick transition into the content.
To me, the rhythm of an informative first message feels more natural than responding to someone's ping and waiting 2 minutes for the follow-up.
I've seen people claim that they show a variable amount of ads depending on the user, which I imagine would be based on your clickthrough rate or other metrics. The ratio between ads and content also seems to vary over time for me so I feel there's some form of optimization happening
Looks maybe like the opposite, there's way too much smoothing. I don't mind pixel perfect fonts or even aliased text but these just look like an aggressive blur was applied to everything
If you're seeing it blurry, the problem is likely your browser scaling it. Try downloading the photo and viewing it in a viewer with a 1:1 pixel ratio, like MS Paint. Alternatively, if you're on Chrome, running this in the dev console might scale it back for you:
It's shorthand for "I believe this is a problem that can be solved by the technology rather than requiring a manual workaround", not "I am entitled to a solution"
reply