yokohummer7

13 ms·

121.
by yokohummer7 11y ago
> I'm surprised they've not introduced fundamental features to solve or mitigate this problem. The problem is, to completely solve space leaks, Haskell should abandon pervasive laziness. But laziness is sold as one of the best
122.
by yokohummer7 11y ago
I think you're misinterpreting what pcwalton said. Sure, seeing "use Rust" in every possible place is quite annoying, but what pcwalton described is why "compiles to C++" and "has 2 decades of libraries" d
123.
by yokohummer7 11y ago
But wouldn't factoring out the obsolete features limit the libraries that are available to use? I thought that was the point of the newly developed systems languages. Even if you follow some "sane" parts of the language, th
124.
by yokohummer7 11y ago
> it's a smell when a language is so verbose that it effectively requires a machine to help you write it The funny thing is that this feature also explains what Go is. Go relies heavily on the various tooling just to overcome the de
125.
Performance regression in Go 1.5(yokohummer7.github.io)
1 points by yokohummer7 11y ago|0 comments
126.
by yokohummer7 11y ago
DISCLAIMER: I'm not well-versed in type theory at all, so take my words with a grain of salt. Unfortunately I haven't seen any comprehensive article that discusses affine types in terms of Rust. So I can't recommend a link to
127.
by yokohummer7 11y ago
> Can you provide a good example of affine types and how they help with expressiveness? For example, let's say there's an HTTP server handler that must send each header line first, and finally send a body. So you should: co
128.
by yokohummer7 11y ago
Sorry, I don't have specific numbers. I was saying generally for all GC'ed languages.
129.
by yokohummer7 11y ago
> D is more pragmatic Being pragmatic is a very questionable claim. Its exact meaning varies from time to time, and a property that a certain people consider to be pragmatic can be considered to be not pragmatic by another people. It&#x2
130.
by yokohummer7 11y ago
Actually, as I'm so used to the articles that place benchmarks at the end, I immediately scrolled down to the bottom after reading the preface. Then I realized the pretty graphs are at the beginning. Anyway, this is an excellent way to
131.
by yokohummer7 11y ago
That's not my experience. Most Haskellers are indeed good people, but quite a few "vocal" ones are extremely arrogant and intellectually dishonest. Let me give some examples that I've met recently: - A Haskeller once sai
132.
Another misfeature of D(forum.dlang.org)
7 points by yokohummer7 11y ago|3 comments
133.
by yokohummer7 11y ago
Yeah, actually I recently installed Visual Studio and wrote some elementary F# code. Seeing the IDE and the debugging facility work out of the box was quite pleasant. I'm also sure I could get advantages from the huge .NET ecosystem, a
134.
by yokohummer7 11y ago
That's interesting, it seems that I'm biased because I've primarily seen desktop-ish libraries. Regarding your usage of `bad_alloc`, I think relaxing the current behavior of aborting will help implement such a behavior. Long-
135.
by yokohummer7 11y ago
If you can write programs without garbage collection, why should you use it? Because using it makes your life easier? To me, Rust is easier to use than both Go and Haskell. Regarding Go, I don't like its inexpressiveness. Regarding H
136.
by yokohummer7 11y ago
You say like C/C++ applications are particularly more resilient to OOM situations. That hasn't been my experience. You can deal with OOM in C/C++, but that doesn't mean it is quite viable. Even popular C libraries just