Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
tome
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
31 ms
·
451.
▲
by
tome
2y ago
But the person I'm replying to didn't say "the price fixing mentioned in this article might also be applied to hotel prices". He/she said "Presumably because the CEO is mates with the competing CEO's and
452.
▲
by
tome
2y ago
Thanks, I take the point that housing is expensive and two people pooling their median wage can't afford an average price home, and in the meantime they're paying rent to landlords. I also take the point that whilst paying rent
453.
▲
by
tome
2y ago
> The person you are responding to didn't say that, I did. Ah, thanks, I got confused. > Haskell works really well if the problems you're solving don't have a ton of weird edge cases, but often reality doesn't work
454.
▲
by
tome
2y ago
So when you said > I think we agree Haskell is far too dogmatic about its abstractions when it's impractical to be used as a general-purpose language did you mean "sometimes some Haskellers use point-free style and it's im
455.
▲
by
tome
2y ago
I don't think I understand why not ... Presumably there has been a lot of immigration to the Netherlands in the same time. Naturally building needs to keep pace with immigration, so (300k + net migration) homes sounds like it should r
456.
▲
by
tome
2y ago
Yes indeed, regulatory capture is a problem.
457.
▲
by
tome
2y ago
What I don't understand is that you say "the Dutch are short somewhere between 300k and 400k homes" when you previously said "Simply adding supply doesn't really address the underlying problem if you don't look
458.
▲
by
tome
2y ago
Then they were sadly misinformed. The need to prevent cartels and monopolies has been known since the notion of capitalism was conceived.
459.
▲
by
tome
2y ago
> If any freshly built housing is bought up by landlords who can afford to outbid ordinary people, then adding supply doesn't alleviate the problem. Can you explain a little bit more about how this situation is supposed to arise? P
460.
▲
by
tome
2y ago
> Sometimes it feels like the easiest way to make money with a new business today is to build something that helps another person make money. Isn't this exactly what all B2B businesses do?
461.
▲
by
tome
2y ago
> Presumably because the CEO is mates with the competing CEO's and they all decide not to undercut each other. "Presumably" meaning what? Do you have some evidence or are you presuming it because it "feels right"
462.
▲
by
tome
2y ago
> Go is basically anti-Haskell. It forces you to be less clever and that's great. This is a bit of tangent, but I think it's worth pointing out the value in Haskell (at least as far as I see it) is not that it allows you to wri
463.
▲
by
tome
2y ago
> I think we agree Haskell is far too dogmatic about its abstractions when it's impractical to be used as a general-purpose language (because I don't think it's intended as a general-purpose language). Originally Haskell w
464.
▲
by
tome
2y ago
I'm reluctant to pick holes in what you describe because I know that I'm not getting a full picture and you have much more context than me, but with that disclaimer out of the way, I think I disagree fully with the details (despit
465.
▲
by
tome
2y ago
> And then there's the Haskell guys running around saying you can't do functional programming unless you've written a dissertation on category theory. I mean, I know you're trying to be funny and edgy, but because the
466.
▲
by
tome
2y ago
Thanks! Although I'd be interested in debating the topic at length (and I also have a longstanding offer to resolve anyone's space leak problems) I don't want to be That Haskell Guy^{TM} who won't let the topic go, so I
467.
▲
by
tome
2y ago
> Our team's big mistake was believing blog posts that swept laziness problems under the rug I linked a blog post[1]. I wouldn't say it sweeps anything under the rug. In fact it takes laziness out from under the rug and shows
468.
▲
by
tome
2y ago
It's great you found something that worked for you. For the spectators I think it's also worth reiterating that putting strictness annotations in data definitions that you didn't want to be lazy would also have solved it, jus
469.
▲
by
tome
2y ago
Sorry to be "that Haskell guy", but this kind of space leak is a solved problem. I call the technique that solves it "make invalid laziness unrepresentable"[1]. That doesn't mean it's a trivial effort to appl
470.
▲
by
tome
2y ago
You based your dislike of Haskell on a single book?
471.
▲
by
tome
2y ago
> So is it an interface or a function? Is it one and the same in Haskell? I am utterly confused. Functor is an interface. It has one member: a function called fmap. To specify how a type meets the Functor interface you have to define t
472.
▲
by
tome
2y ago
You're right, but my response would be that fst (5, error "second") and head [] = error "empty list" head (x:xs) = x are simply not things you should be writing. They're not good program
473.
▲
by
tome
2y ago
Sure, if your definition of exceptions includes "must include a stack trace", then sum types can't simulate exceptions. But by that definition Haskell hasn't had exceptions until the last year or two. You might agree
474.
▲
by
tome
2y ago
> By simulating exceptions, do you mean a `Result t e` type (which Haskell calls `Either l r`)? Yes, exactly. > The semantics of these are.. interesting, mostly thanks to lazy evaluation. For example, `fst (5, error "second"
475.
▲
by
tome
2y ago
> saying one is "an emulation" of the other is just stupid. I did say that indeed. Am I to conclude doing so was stupid? If so I would find that very rude. (For what it's worth I was trying to understand what astrange mea
476.
▲
by
tome
2y ago
I wouldn't say that's an accurate description of how Haskell handles side effects. In fact I wouldn't say that Haskell has side effects at all.
477.
▲
by
tome
2y ago
Can you elaborate?
478.
▲
by
tome
2y ago
> You're basically trading runtime efficiency for memory. What do you mean? Aren't GCs both less efficient at run time and use more memory?
479.
▲
by
tome
2y ago
I agree with Alexis. Bluefin approaches this by not actually having a nesting order. The effects that can be performed as specified as function arguments, so they can be freely reordered without changing behaviour. effectful, which was o
480.
▲
by
tome
2y ago
Yeah, that's basically the same problem as `StateT s (ExceptT e m)` but for `StateT s m` where `m` throws exceptions.
More ›