When my wife and I bought ours it was only 1.5x a comparable (similar motor/blade spec) DeWalt/Bosch, maybe 2x a comparable Delta. The only saws available at 1/5 the price were on Craigslist.
Yeah, it's more, but as hobbyists we figured we were (1) more likely to make a painful (and costly) mistake than a professional who's working with the thing day in and day out and (2) less likely to be able to restore/maintain a used saw of unknown age, provenance, condition, etc. Worth it for us, and IMO probably for most serious amateurs.
My wife and I have been playing a bit of tongue-in-cheek "bingo" while driving around town, so I decided to draw up an actual bingo board with some of the things we look out for. We'd love ideas for more squares if y'all have any suggestions!
There's a trick to using box graters that most people don't know (I certainly didn't until recently)
The mechanics of pushing down/away are much better than holding the thing upright, dangling it over a bowl or whatever. Easy to just push with your palm too (and keep your fingers out of the way).
Obviously it's not for everyone, but I had this conversation with my parents after telling them I planned not to have children and it was... Fine? Kind of a bonding moment, even, we mostly just laughed about it.
Not every parent/child relationship trends this way, but for some of us there's a point in adulthood where you just become friends with your parents, and the parent/child roles sort of fall away. If everybody's mature and secure enough to handle it, talk about whatever the hell you want to.
scientifically proven ecological collapse
This is a pretty specific thing, but the general "we're all doomed" vibe is definitely not unique to today. Boomers and older had the threat of nuclear annihilation looming over them, and before that... well, disease and famine and death and destruction due to war have historically been the norm.
Imagine how you'd feel living in the Americas in the 16th or 17th centuries and either watching the destruction wrought by European settlers firsthand or, maybe worse, watching your peers die en masse of the diseases introduced by those settlers. Imagine living in Eurasia in the 13th century and watching the Mongol army sweep through.
None of this is to say that today's challenges aren't real and serious. Just that we're not the first to face such challenges.
Yowsa! That's cold.
That said, ground-source systems have been used to good effect in climates like that! But, of course, do what's right for you 🙂
You might not be totally out of luck:
It's not that weird, it's how TTLs work.
When your computer wants to know what server x.com is, it (oversimplifying a bit) asks its own internal DNS (Domain Name System) resolver, which asks your router's resolver, which asks your ISP's resolver, and so on, until an authoritative resolver is found.
Each of those resolvers, before asking the next one, has its own memory it can reference just in case it gets asked about the same address very often, because asking can be costly in terms of time (because you have to ask the next server for the answer OR because so many different request are coming in that it's difficult to answer all of them). This memory is called a cache, and everything stored in that cache is given a Time To Live (TTL).
When a resolver that knows the answer to "what server is x.com?" is found, it gives not only the answer, but also a guess at how long that answer is valid. That guess is the TTL for the next server's cache. This number is controlled by the owner of x.com.
What all this means is
x.com should always resolve to the same server, the TTL should be very long (because you want the resolution to be served from the cache, meaning it's faster)x.com will change in the near future you want the TTL to be very short (because you want resolutions to reach your authoritative server and get the new server address)And what THAT means, relative to this particular bit of current events, is that somebody fucked up. If this change was well-planned, then the TTLs would've been shortened in advance of the server switch, giving time for the downstream resolvers to clear their caches.
But that didn't happen, which means that when your device asks "what server is x.com?", it sometimes gets the answer from the authoritative server (updated correctly to point to Twitter) and sometimes it gets the answer from a cache (pointed at who knows what).
Basically, Elon once again rushed some shit through and sure enough it's a fiasco.
Rains when please?
Sooner than October would be great, but I'm not holding out much hope :(
The SSA has a great site showing projections into the future of various proposed modifications. That plan specifically does not on its own solve the problem completely (though it does help, extending the time frame for exhaustion of the trust fund out to 2060 or so). If we wish to avoid the exhaustion of the trust fund, we'll need other measures as well.