Can confirm, installed central air AC (and improved insulation) at my place this year in Potrero Hill. Costly given labor and permit BS in SF. It’s consistently hotter than 20 years ago to. I had 80F+ in my house during 1/3rd of the year at 4pm over the last 3 years. Barely get any fog these days in my hood.
Are you familiar with the first sale doctrine? My actions were perfectly legal at all times.
I did this professionally, had bought hundreds of tp-link routers from legitimate suppliers. It's not like I found them on the street or anything like the sellers described in OP. I had over 50k invested in a specific router model at one point.
"Not everything exists for RISC-V that exists for the other ones, but that is filling in at incredible pace."
The RISC-V project is now 7 years old. Remember that the 6502 and its supporting hardware went from proposal to final silicon in 2 years. And that was done using a hand drawn layout.
UC Berkeley has had functional RISC-V silicon for years now as research devices. RISC-V hasn't really been a thing outside of their architecture research group for more than a few years now. The UCB-BAR also has some fairly decent RISC-V cores (BOOM and Rocket) available as open source RTL.
That may be but RISC is supposed to be simple (or if you prefer, reduced) and back then the 6502 had no infrastructure to speak of. 7 years is unquestionably a long time and then if you go to the RISC-V spec and look at lucky chapter 13, "B" Standard Extension for Bit Manipulation it says:
This chapter is a placeholder for a future standard extension to provide bit manipulation instructions, including instructions to insert, extract, and test bit fields, and for rotations, funnel shifts, and bit and byte permutations.
It's fairly easy to beat the given examples but in the end heap management is heavily dependent on application, client code, platform, hardware and many other criteria. It's a very complex problem space and what matters here is how existing important code behaves and continues to behave given that existing code has most likely made assumptions how the heap is managed.
glibc is a good example of a perfectly fine compromise not optimized for any particular use case. Anyone who has had performance issues with it has most likely already implemented their own solution for their problem set.
It might much more worthwhile to develop a set of malloc like implementations a developer can chose from instead of going for a fits all approach.
Further, the complexity and need for flexibility is exactly the problems that I'm trying to deal with here. That's why the challenge encourages splitting the allocator up in Unix-like pieces and stacking them to get the desired features.
I could be wrong, but I think production lipos (and variants) are closer to .15Wh/g, and not much higher than 0.25 for anything that isn't entirely theoretical.
