Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
deagle50
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
91.
▲
by
deagle50
3y ago
Don't blame you on the battery life, we'll have to see if the tiny M3 Pro has brings efficiency benefits without a reduction in real-world performance. I'm fond of the E-cores and my main gripe with my M1 Max is the 2 E-cores
92.
▲
by
deagle50
3y ago
The surface area of the M3 Pro vs M2 Pro tells you everything you need to know.
93.
▲
by
deagle50
3y ago
Add a thermal pad to connect the heatsink to the back cover and the thermal throttling will go away. Tons of tutorials on Youtube and it takes 5 minutes. I did it on my M1 Air and it doesn't go above 85-90C now.
94.
▲
by
deagle50
3y ago
Apple is favoring yields and margin over everything else. They cut the M3 Pro as much as possible so it's half the area of the M2 Pro.
95.
▲
by
deagle50
3y ago
Maximizing margins for the M3 Pro which makes up a large majority of MBP sales. The transistor count reduction adds up over thousands of 3nm wafers. They are probably getting twice as many M3 Pro chips per wafer over M2 Pro. Nudging power u
96.
▲
by
deagle50
3y ago
> Then the 'happy path' is just the rest of the function. Right, and that's why it's bad.
97.
▲
by
deagle50
3y ago
I'm not asking for exceptions. I'm asking for sugar for an empty return, and most importantly, a way to capture the error value after the function call.
98.
▲
by
deagle50
3y ago
Was just showing how Rust and Zig do it. Go capture could omit the ||.
99.
▲
by
deagle50
3y ago
As am I. "try" as sugar for a simple return, and "catch" to capture the error value.
100.
▲
by
deagle50
3y ago
What do you mean? To me it's not even close. value, err := foo(); if err != nil { // handle err }; value := foo() catch err { // handle err }
101.
▲
by
deagle50
3y ago
"else" for the happy path is part of the problem.
102.
▲
by
deagle50
3y ago
I think there's an easy solution to this, would love to know if I'm off track: postfix `catch` optionally captures the last value in the return tuple. Instead of value, err := foo(); if err != nil { // handle e
103.
▲
by
deagle50
3y ago
foo().unwrap_or_else(|err| { // handle err }); or foo() catch |err| { // handle err }
104.
▲
by
deagle50
3y ago
And I understand the advantages over exceptions, but we've made some nice progress since the mid 2000s. Sum types and error unions aren't rocket science and even the assembly line programming model that Go seems to have built to e
105.
▲
by
deagle50
3y ago
It's not just the empty return. It's that every fallible function call starts with `err = foo()` or `value, err = foo()`. You're forced to read `err` at the beginning of every function call even if you don't care. How w
106.
▲
by
deagle50
3y ago
Assigning errors at the function call... Worst part of go. Just add try/catch already.
107.
▲
by
deagle50
3y ago
AI trained with python banned python ads?
108.
▲
by
deagle50
3y ago
Outrageous. Bans like this without clear proof of violation should be illegal.
109.
▲
by
deagle50
3y ago
And it gets more perceptible when moving the caret (more pixels to track and you're actively tracking).
110.
▲
by
deagle50
3y ago
Users can easily feel one frame of latency at 60hz given enough visual feedback (pixels in this case). It gets harder at 120hz and above. I have a toy editor with Ropey and WGPU, just added a 100ms wait on char insert and it's rubber b
111.
▲
by
deagle50
3y ago
Or a cheap Zen 3/4 with ECC compatible motherboard.
112.
▲
by
deagle50
3y ago
Yabai can eliminate it entirely (after it's updated for Sonoma), if you don't mind disabling SIP.
113.
▲
by
deagle50
3y ago
First thing I did was set up Discord. 5x reduction in memory usage.
114.
▲
by
deagle50
3y ago
The other renters.
115.
▲
by
deagle50
3y ago
> If you're going to veer into Economics 101 then you'd better reconcile with the fact that this "renting" only causes more surplus to be captured by the publisher, and not by the consumer. Why should the savvy renter
116.
▲
by
deagle50
3y ago
It seems 4c requires .1v more through most of the clock speed range. It's purely a cost and density play.
117.
▲
by
deagle50
3y ago
He's not wrong about avocado toast. And ironically, if you stop paying 1000% markup on something so simple and save your money, you can neutralize the tycoon's leverage over you.
118.
▲
by
deagle50
3y ago
It's just code for "do it anyway", which would be fine in exchange for payment if expressed honestly.
119.
▲
by
deagle50
3y ago
I disabled all the UI elements in IntelliJ so it looks like Emacs, and I learned Vim motions. IdeaVim takes a .vimrc and I have almost everything I'd want from Emacs/Vim. Works great for me, I can pretend it's an old school e
120.
▲
by
deagle50
3y ago
Thanks for looking this up. I'm not just referring to blocs that just return the error, though even then your 154 occurrences lead to 462 lines of noise. Noise that could could be avoided with sugar like `?`. I'm referring to all
More ›