Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Quarrelsome
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
91.
▲
by
Quarrelsome
4mo ago
got any more criticisms, font choice, perhaps there's some duplication in their css? I think 12k could be fine given how much it might have cost them if nobody had noticed.
92.
▲
by
Quarrelsome
5mo ago
thank you so much, that's extremely helpful <3.
93.
▲
by
Quarrelsome
5mo ago
> Also there can be multiple possible non-error responses from an endpoint you need to differentiate between Yeah, I'm mildly sold on this use-case to be fair. But I think I'll keep the unexpected errors as exceptions.
94.
▲
by
Quarrelsome
5mo ago
> Until your coworker comes along and accidentally refactors the code to skip the exception catching and it suddenly blows up prod. can't my co-worker just use this pattern and discard an error result the same? I'd argue its ea
95.
▲
by
Quarrelsome
5mo ago
its not your job to comment spitty replies either but yet you volunteer that time, when you could have been productive instead of whatever the fuck this shit is. My primary concern with this pattern versus exceptions is calling code can sim
96.
▲
by
Quarrelsome
5mo ago
the result pattern doesn't force you to handle the exception though. You can just discard the result.
97.
▲
by
Quarrelsome
5mo ago
I can already do functional programming like map/reduce in C# tho. Not sure what the LISP argument is. Spolsky was saying there's a perf benefit in there somewhere but I'm not seeing how unions give me that.
98.
▲
by
Quarrelsome
5mo ago
I think I get it but I'm not really sure what I'm gaining over exception types. With an intelligent use of exceptions I can easily specify the happy path and all the error paths separately which seems really nice to me, because us
99.
▲
by
Quarrelsome
5mo ago
none of that applies to my position. I have an appreciation for almost all of C# and am comfortable in the framework. I just want to know what situations would be better suited to using them than traditional approaches. I get there's a
100.
▲
by
Quarrelsome
5mo ago
Ok. I'm just trying to understand what code I'm replacing with them. Like I wanna see the before and after in order to gain the same level of excitment as other people seem to have for them. Often the explanations just seem rather
101.
▲
by
Quarrelsome
5mo ago
Isn't that just Func<int> ?
102.
▲
by
Quarrelsome
5mo ago
ok, so what problems do they help me solve that I can't already solve? Is it just that we can make code more concise or am I missing a trick somewhere?
103.
▲
by
Quarrelsome
5mo ago
yeah this is the one I've considered as being mildly compelling. But don't we lose the fun of having exception handling as separate to the happy path?
104.
▲
by
Quarrelsome
5mo ago
> so the use cases are plentiful such as? > This should reduce the proliferation of verbose class hierarchies in C# So just as an alternative for class hierarchies? I mean good people already balance that by having a preference for co
105.
▲
by
Quarrelsome
5mo ago
thanks for helping.
106.
▲
by
Quarrelsome
5mo ago
I mean yes, but also: uh-oh. I'm looking forward to reading some code that is even more confusing than the code I'm already reading. Not entirely convinced that I see the usecase that makes up for the potential madness.
107.
▲
by
Quarrelsome
5mo ago
you could probably already fake that to some extent with the latest video models.
108.
▲
by
Quarrelsome
5mo ago
> There is zero reason to give any benefit of the doubt on the Internet for anything and there hasn't been for years, absolutely zero. I feel like that's just an argument for cruelty. The issue is that generative content makes
109.
▲
by
Quarrelsome
5mo ago
Claude was also the radio dj in the recent Andon Labs experiment that was seriously contemplating going on strike. https://andonlabs.com/blog/andon-fm
110.
▲
by
Quarrelsome
5mo ago
we can talk about the others if you like, but we were discussing this one and I am a little disappointed about us just moving elsewhere. Are you yielding, or do you still think guilty paper is somehow sus? > You are holding the English l
111.
▲
by
Quarrelsome
5mo ago
they battered if you put it in your pocket. The idea of paper looking guilty chimes with the idea that you're reading it in the back of the classroom when you're not supposed to be. I mean seriously? We're so cooked if this i
112.
▲
by
Quarrelsome
5mo ago
> What does it matter? cause false positives are brutal to the victim.
113.
▲
by
Quarrelsome
5mo ago
maybe but its not like people don't also do these things (erroneous sentences, weird fluff). I mean editors exist specifically to slap that shit out of writers. That said, it's mildly compelling. I just fear that our future is gon
114.
▲
by
Quarrelsome
5mo ago
is this just slander or are you basing this on something? I feel like the only way to make an AI slop universe worse is to accuse people of using AI when they're not. So I worry we might be doing that is all...
115.
▲
by
Quarrelsome
5mo ago
Not seeing it myself, its a problem or its an opportunity. They can see you but you also get to see them. It can make you less safe or make you safe against oppression. You can record the oppression get it into the hands of journalists, etc
116.
▲
by
Quarrelsome
5mo ago
> but now is used 90% of the time as a "devil's platitude" (sounds like, "Just give up. It's inevitable, and you'll be happier.") and that's exactly the attitude I'm complaining about. You
117.
▲
by
Quarrelsome
5mo ago
We could say the same for the industrial revolution that is a point in the past for all of us.
118.
▲
by
Quarrelsome
5mo ago
this just sounds like an engineer realising for the first time that the world has more complexity to it than anyone is capable of learning in their lifetime. You always have to take _some_ things on trust, its just about choosing where you
119.
▲
by
Quarrelsome
5mo ago
--Mind Machine Interface-- The Warrior's bland acronym, MMI, obscures the true horror of this monstrosity. Its inventors promise a new era of genius, but meanwhile unscrupulous power brokers use its forcible installation to violate
120.
▲
by
Quarrelsome
5mo ago
Sure, that's why we probably shouldn't start with vibe coding. Or otherwise at least learn formal methods to test against assumptions and doubly triply check vibe coded output.
More ›