I explored an adjacent topic - a UI component that seamlessly transitions from a nullable boolean to a multi select. I wrote a short blog post[1] and there is a page with this UI component in action[2].
It was a fun experiment and I liked the result. Still, I wouldn't do this outside of a hobby project (at least not without a very good reason and a lot of resources).
> But sand is quite expensive so my question is, why sand and not water?
The article says they will use a byproduct from a local industry, perhaps it's available for cheaper.
"The sand itself will also be sustainably sourced – it’ll consist of crushed soapstone, which is a manufacturing byproduct of another local industry. This material can apparently conduct heat even better than regular old sand.".
It's the not the cost of obtaining the water that makes water less viable, it's the cost of storing superheated water. Water has this pesky ability to expand 1600 times larger when it goes over 212 degrees Fahrenheit. That means that if not handled carefully you get deadly steam explosions.
Hot sand / crushed rock doesn't have the same problem. If you read in the linked article it says
> with the sand heated to somewhere around 500-600 degrees Celsius (932-1112 °F).
That would be extraordinarily hard to do with water as you'd need significant containment and safety measures.
If that water has to come from underground, yes, it would be cheaper and easier to just grab surface stone and crush it for material to make a heat battery.
Also, water tends to make for a horrible heat battery as it is much more thermal-emissivity than rock particles. You need all sorts of additional insulation to retain the heat, whereas the sand will insulate itself.
This is a power product manufacturer. I'm sure at some point they considered porting this to an actual chainsaw; the lack of screen must have been a blocker. I guess a lawnmower is the next best thing they could come up with.
With the advent of good battery chainsaws we’re only a few years away from one having a diagnostics screen, and which point doom on a chainsaw will be possible.
I've had mixed results. Some visits were fine, especially those where I wasn't logged in. During others I've seen errors, often when writing comment replies or voting.
You can set a hard budget on most cloud providers, including Azure etc. I actually did this thinking I was just setting a budget alert and that was a new and interesting way to interrupt production.
> You can set a hard budget on most cloud providers
Note that the submission references serverless providers, specifically netlify and vercel. I don’t think these support an easy to configure kill switch - in any case it wasn’t easy to configure in the scenarios listed on the page.
This is rookie-level shittifying. What it needs to do is insert `with` blocks at random, with various levels of nesting, so you completely lose track of the scope of any object property.
Too "bad" that `with` blocks are forbidden in strict mode and most JS is strict mode by default now. You could somewhat approximate it with lots of unadorned blocks and complex object destructuring.
{
const { prop1: a, prop2: A, prop3: xTy } = obj
// …
{
const { prop1: A, prop2: xTy, prop3: a } = obj
// …
}
}
And randomly add "-Decorator" suffix to class names.
Ages ago, I tried to diplomatically explain to our Senior Architect Grand Poobah (and my team lead) that one set of Decorators are actually Chain of Commands. And that they shouldn't be silently swallowing exceptions.
After a few minutes, he says "u/specialist, I'm surprised someone with your experience doesn't understand architecture." Then gets up and walks away.
Rather than putting identifiers into MOckiNG sPongeBob CasE, it should apply a standard case convention (including initialism, Systems Hungarian with incorrect types, etc) at random for each identifier.
function Make_List(firstString, second_string, chThirdString) {
var a = [firstString, second_string, chThirdString];
return a;
}
> No one wants to reformat the files because then it will mess up with git history.
GitHub will use a file `.git-blame-ignore-revs` to allow blame to ignore commits that make those kind of changes. (This is the format used for the `--ignore-revs-file` option to `git blame`.)
Git has something for every occasion I ever encountered with a need for something I knew was technically possible but didn't know if git would let me do it. It let me do it every time, truly the hacker's utility.
This is fun on mobile, tested on ios; I had to close the “works on desktop only” popup (via a popup blocker), but then I could tap to move in that direction and I enjoyed playing this way.
If you make something that lives on the web and doesn’t support all platforms, please consider showing the unsupported platforms a screenshot or video.
It was a fun experiment and I liked the result. Still, I wouldn't do this outside of a hobby project (at least not without a very good reason and a lot of resources).
[1]: https://merely.xyz/blog/2023/001-lets-design-a-new-form-elem...
[2]: https://merely.xyz/lenses