Most UK housing stock is poor quality, old and draughty. Pre-req of switching is fixing that. Then, when you've got a nice hermetically sealed house, you need to solve fresh air, which is another cost. Labour is extremely expensive in the UK and tradespeople are poor quality and swindlers (sorry, it's true 95% of the time).
And most people don't have £10k+ to drop on upgrades
We're not used to needing aircon, so the whole concept is a bit foreign
Electricity is expensive (0.31 EUR/kWh)
Plus, we've been burned by governments pushing "green" things:
- They scammed us with cavity wall insulation, which has caused some serious structural and expensive issues. It was inappropriate for many houses and a ton of conmen popped-up to take government money with no fucks given
- Diesel was sold as 'green'
- They had a scheme pushing loft insulation but the installers often just threw rolls of insulation into the loft and ran way (not even kidding)
Basically, multiple governments have created just about the /worst/ possible history and conditions to get people on board with heat pumps
I have a very small, draughty house and spend ~800 EUR a year on gas (heating + hot water + hob). Not ideal but I'm still running on the gas boiler that came with the house 10 years ago that's only had ~300 EUR of maintenance spent on it. The house gets hot, I can have boiling hot showers whenever I want. If anything goes, wrong, I can all any of 30 people to come fix it
They're not skeptical, it's just that no one wants to pay $10k to have a $2k unit installed, and new entrants who want to offer anything other than what the entrenched services have to offer have to be abused and hazed for 4 years near minimum wage changing out $5 capacitors for $1000 (to their company, not them) before they can get a trade license, and after that they have to go through an onerous contracting paperwork to open up a business. So we don't get new businesses popping up offering mini split installation.
End result is most of the units that get installed in the US are probably DIYing off-paper and then shutting the fuck up. I live in a place with no inspections for owner-builder and that was the only way I was able to get away with it, and even then I had to pass an EPA 608 license to handle the refrigerants since I did not want to get fined a bazillion dollars if someone found out.
It’s the largest residential model that Ecoer makes. The home is a 3-bedroom, large but nothing crazy. The installers said they erred on the side of too big, rather than too small, and that’s corroborated by my back-of-the-napkin math and Google searches indicating that “too big” is standard practice in the HVAC industry. So in theory, it shouldn’t be a lack of power. I think it’s poorly optimized. From what I’ve been reading, the pressure in the lines is very important. I have no idea if they are pressurized properly. The unit apparently has sophisticated monitoring of the line pressure, but the IoT gateway has no end-user access which is a huge red flag for me that I wasn’t aware of before it was installed.
Do you have a source for “with very little observer effect”? I don’t know better, it just seems like a big assumption the CPU can emit all this extra stuff without behaving differently.
Trace data are sent through a large/fast port (PCIe or 60-pin connector) and captured using fast dedicated hardware at something like 10 GB per second. The trace data are usually compressed and often only need to indicate whether a branch is taken or not taken (TNT packets from x86, Arm has ETM but similar enough trace path) with a little bit of timing, exception/interrupt, and address overhead. The bottleneck is streaming and storing trace data from a hardware debugger (since its internal buffer is usually under half a second at max throughput) although you can further filter by application on Intel processors via CR3 matching. (Regarding the last five years of Apple: I'm not sure you'll find any info on Apple's debuggers and modifications to the Arm architecture. Ever.)
If you encounter a slowdown using RTIT or IPT (the old and new names for hardware trace) it's usually a single-digit percentage. (The sources here are Intel's vague documentation claims plus anecdotes; Magic Trace, Hagen Paul Pfeifer, Andi Kleen, Prelude Research.)
Decoding happens later and is significantly slower, and this is where the article's focus, JIT compilation, might be problematic using hardware trace (as instruction data might change/disappear, plus mapping machine code output to each Java instruction can be tricky).
It's not an assumption, this is based on claims made by CPU manufactures. It's possible to get it down to within 1-2% overhead.
Intuitively this works because the hardware can just spend some extra area to stream the info off on the side of the datapath -- it doesn't need to be in the critical path.
I am obliged to use a public GitHub org for work. Is it “blessed path” to try do the CR part in tangled and sync back to GitHub? I would love to profit from my nice jj habits at the review stage!
The showering thing is an urban legend; you can have landlords try and enforce it, but it infringes on your basic right to enjoy your property iirc and is unenforceable.
When I used to live there, about 20 years ago, getting notes under the door from some neighbour complaining about whatever noises during the evening used to be common.
As a jujutsu fan, I like to prepare a nice clean commit history for my reviewers to probably ignore. But I kind of assume - there’s _some tool_ we could use - perhaps on top of GitHub - to make stacked reviews not suck, either actually stacked PRs or just incrementally reviewing a nicely divided branch PR. I thought it might be graphite but it seems that needs some whole other tooling _stuff_ on top? Any recommendations ?
yeah, for sure -- avoid stacking changes in the first place! the purpose of PRs and code review is to establish a single unified shared context between multiple stakeholders. it's the author's responsibility to propose changes that are independent and coherent and easy to understand.
