Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fleventynine
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
91.
▲
by
fleventynine
3y ago
My argument is that the grid has to be designed to handle the load from cloudy weather that lasts over a week. Nobody can afford a battery system that can last that long. So the rooftop-solar enthusiasts either need to install and maintain
92.
▲
by
fleventynine
3y ago
As it is provisioned for peak demand, the grid will cost roughly the same to maintain as it does today, even if people only use it 10 days a year. In this world, there aren't many options: 1. Charge a fixed fee to everyone hooked up to
93.
▲
by
fleventynine
3y ago
Imagine a world where everyone in the state has an overbuilt solar battery system installed, but still relies on the grid those few times a year with extended cloud cover. It would cost a ton of money to maintain all that (mostly unused) i
94.
▲
by
fleventynine
3y ago
NEM 2.0 pays solar homeowners a rate that is far above the market rate of instantaneous power (paid via an unsustainable, regressive "tax" on non-solar households paying astronomical rates). Roof solar panels are far less economic
95.
▲
by
fleventynine
3y ago
They need to be careful with how high these charges are. Replacing their grid connection with an oversized solar-battery system combined with a propane backup generator might be more attractive to rich folks.
96.
▲
by
fleventynine
3y ago
Once home batteries are available in the $200/kWh price range, the California home solar market will come back. NEM 2.0 was a ridiculous transfer of wealth to rich households who could afford panels, and I'm glad it's over.
97.
▲
by
fleventynine
3y ago
If you're generating machine code at runtime (JIT), you can have memory bugs no matter what language your JIT is written in.
98.
▲
by
fleventynine
3y ago
We need more housing, and we needed it yesterday. Ugly is better than nothing. Folks that care about aesthetic quality over quantity are part of the problem.
99.
▲
by
fleventynine
3y ago
A reddit thread with anecdotes from EV owners during this cold snap: https://www.reddit.com/r/Calgary/comments/194yg8x/how_are_yo... General consensus was that while some models lost ~40% of their range,
100.
▲
by
fleventynine
3y ago
Likewise. A friend was almost killed a few years back by a counterfeit SSR purchased on Amazon. I would love to see them take some legal responsibility for the lethal garbage they let onto their platform.
101.
▲
by
fleventynine
3y ago
When the news stops being consistent with my lived experience, I stop paying attention.
102.
▲
by
fleventynine
3y ago
> if I spin up a VM with networking disabled I feel pretty confident I can run anything safely, even malware is not going to escape. You are putting too much faith in your VM monitor to keep you safe. There's a lot of attack surface
103.
▲
by
fleventynine
3y ago
> Let's remove 20% due to 8b/10 encoding Thunderbolt 3 uses 64b/66b encoding (unlike display port 1.2 alt mode), so there's more bandwidth left over for non-display protocols.
104.
▲
by
fleventynine
3y ago
I use Rust for bare-metal development (no libc, no allocator, no panic, 32k size limit), and it is comparable to C and C++ for that use-case. The project is 99.5% Rust with a bit of assembly glue for startup/interrupt handlers.
105.
▲
by
fleventynine
3y ago
Modern GCC is also primarily written in C++, and has had C++ deps since 2013: https://github.com/gcc-mirror/gcc/blob/master/gcc/input.cc
106.
▲
by
fleventynine
3y ago
It can be safe if the language provides a mechanism to tell the compiler that borrow_field1() and borrow_field2() will never mutably borrow the same fields. This would be part of the public API of those functions, and compilation would fail
107.
▲
by
fleventynine
3y ago
This is the biggest pain-point of the language. We need a solution.
108.
▲
by
fleventynine
3y ago
Why would you want to run 2.5G or 5G over fiber? 10G fiber transceivers are dirt cheap and barely use any power. It's the 10G copper transceivers that have thermal/power issues...
109.
▲
by
fleventynine
3y ago
I don't think permanently wiring high-speed twisted-pair makes much economic sense: CAT8: $0.55 / foot Max speed; 40 Gbit Max length: 30m ( https://www.monoprice.com/product?p_id=42957 ): --- 2 strand OS2 single-mod
110.
▲
by
fleventynine
3y ago
There's a lot to like about Zig, especially related to metaprogramming. Unfortunately, bulletproof memory safety is table stakes for a modern language. Without a garbage collector or borrow checker, Zig is DOA for any use case that inv
111.
▲
by
fleventynine
3y ago
Among 32-bit microcontroller-class architectures, modern toolchain support for rv32imc is second only to armv7m IMHO. Nobody wants to maintain support for any other vendor-specific ISAs.
112.
▲
by
fleventynine
3y ago
Embedding binary data should be part of the language/toolchain, not the operating system. For example, include_bytes!() in Rust.
113.
▲
by
fleventynine
3y ago
Grumpy NIMBYs. The state's ADU laws override local zoning requirements such as minimum setbacks, allowing their neighbors to build "horrible monstrosities" that "violate the spirit of the community".
114.
▲
by
fleventynine
3y ago
I agree with this statement if my data structures map cleanly to Rust's preferred single-ownership, which most problems in my domain do. Sometimes I do run across problems that are difficult to express in Rust without resorting to inte
115.
▲
by
fleventynine
3y ago
Then choose from one of the countless garbage-collected languages with sum types and a runtime; Rust is successful because it's offering us systems programmers something unique.
116.
▲
by
fleventynine
3y ago
Many of the safety benefits of Rust disappear once you start JITing machine code and jumping to it...
117.
▲
by
fleventynine
3y ago
IMHO, using an vector index as a pointer should be a last resort (as an alternative to unsafe). Although it's memory safe, you still have many of the traditional issues like stale pointers / use-after-free, plus you also have the
118.
▲
by
fleventynine
3y ago
> Even without any soundness issues or bugs or security flaws, people can just plain write malicious code. Rust prevents a lot of common _mistakes_, but people can also use it to write completely "safe" worms that are guarantee
119.
▲
by
fleventynine
3y ago
It would be nice to see some sort of sandboxing for these. I would love it if cargo had a mechanism to run all build actions for a crate inside a firecracker vm. That said, most build systems can access everything the user has access to, so
120.
▲
by
fleventynine
3y ago
It will "work". It won't be as fast and precise as the JVM.
More ›