Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Peaker
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
by
Peaker
9y ago
Attoparsec is fast, but used to have bad error messages. How do the 2 parsers compare w.r.t error messaging? Haskell has Parsec/Megaparsec which have better error messages, but are extremely slow.
62.
▲
by
Peaker
9y ago
> In my experience conflicts are not "usually due to very wide, mechanical changes", they're due to two people modifying the same file at the same time. Then it is likely a reversal of cause & effect. People are more r
63.
▲
by
Peaker
9y ago
> Since git-mediate can't actually tell if you applied the change to the other version correctly, you're getting no real benefit compared to just deleting the conflict markers yourself This is patently and empirically false: 1)
64.
▲
by
Peaker
9y ago
Except you don't really know if you actually applied the full change to the other version. That's what applying it to the base is all about. You often take the apparent diff, apply it to the other version, and then git-mediate tel
65.
▲
by
Peaker
9y ago
True, but if you follow a simple mechanical guideline: Apply the change 2 other versions (preferably the base one last) - then your conflict resolutions are going to be correct. From experience with many developers using this method, confli
66.
▲
by
Peaker
9y ago
That's why I showed an example of a rename. You write "manually fixed the conflict", where do you see that in the rename example? You just re-apply either side of the changes in the conflict (Base->A, or Base->B) and t
67.
▲
by
Peaker
9y ago
When you have that many conflicts, it's often due to massive renames, or just code moves. If you use git-mediate[1], you can re-apply those massive changes on the conflicted state, run git-mediate - and the conflicts get resolved. For
68.
▲
by
Peaker
9y ago
Haskell is quite well adapted to the humans that like using it :-) Partially it's a matter of taste. I hated Haskell syntax in the first few weeks ("Why did they have to differ on this?!") but later I realized it's objec
69.
▲
by
Peaker
9y ago
Haskell is difficult to learn! For virtually everyone. Especially people who already learned more mainstream languages, because it is so different. When I learned Haskell I was frustrated by its difficult learning process until I stuck with
70.
▲
by
Peaker
9y ago
> And here's the arrogant, self-important attitude that turned me off of Haskell. Haskellers are usually out to convince that Haskell is for most programmers, and that "need PhD to use it" is a myth. It is people frustrate
71.
▲
by
Peaker
10y ago
Normally, if you use archive (.a) files, then any .o files within them that are not needed, are thrown away. But that is at .o file granularity. There's no per-symbol dead code elimination. And if you provide a list of .o files (no .a
72.
▲
by
Peaker
10y ago
You might not care to shrink it down for 500KB to 200KB. But shrinking 200MiB binary to 40MiB is nice. See also: https://en.wikipedia.org/wiki/Wirth's_law
73.
▲
by
Peaker
10y ago
We created the Lamdu language that is designed to work well with its IDE. It has some features we miss in other languages (extensible&structural product and sum types), but also makes different trade-offs (all names are GUIDs behind the
74.
▲
by
Peaker
10y ago
That they are always terminating is very useful for programs that generate proofs, or otherwise don't have to be evaluated. But if you can encode the Ackermann function, proof of termination is not very useful in practice - as it may c
75.
▲
by
Peaker
10y ago
This is the same set of design principles that was behind COBOL, as I understand them. It is probably fine for the purpose of simple gaming scripts.
76.
▲
by
Peaker
10y ago
Why did they write their own VM? Was it sort of a write-once, run everywhere thing? So they can reuse the game code on various platforms?
77.
▲
by
Peaker
10y ago
The people who need not spend energy to control their cursing have more energy left to lie. These kinds of after-thought rationalizations can always work both ways. If you find yourself never surprised by any finding, you are probably doing
78.
▲
by
Peaker
10y ago
GC could possibly expose a program to timing side-channel attacks.
79.
▲
by
Peaker
10y ago
It shouldn't copy anything - I'd expect it to be optimized to not allocate any memory at all.
80.
▲
by
Peaker
10y ago
And even array-oriented algorithms can be quite nice, syntactically, if nice operators are defined for them[1]. But the FP community does not care that much about that kind of code, so nice operators are just not defined for them. [1]: htt
81.
▲
by
Peaker
10y ago
Haskell has far fewer correctness gotchas than other languages. They stuck to consistent, predictable behavior - even when it made things tedious for years until new techniques were discovered. Haskell does have performance gotchas, though.
82.
▲
by
Peaker
10y ago
import Control.Lens.Cons case uncons v of Nothing -> .. empty vector .. Just (head, tail) -> ..
83.
▲
by
Peaker
10y ago
Haskell LANGUAGE pragmas are like "from __future__" in Python and various other equivalents in many languages.
84.
▲
by
Peaker
10y ago
The universe can be modeled at least as naturally as a composition of functions of type (Time -> a) as a mutation upon a global mutable state.
85.
▲
by
Peaker
10y ago
> Why do you think so many IDEs come with vim emulation I was referring to the claim that a popular choice amongst IDE makers meant it was a good idea.
86.
▲
by
Peaker
10y ago
Popularity isn't really a good argument. It could either be because it's a good way to edit text, or because of inertia and extreme conservative nature of developers.
87.
▲
by
Peaker
10y ago
Excellent summary. A decade ago I was very well versed in how the bits and bytes of the MBR, partition table and BIOS boot process worked. Since then, I was completely out of the loop, and this filled me in.
88.
▲
by
Peaker
10y ago
My XPS 13 9350 came with Windows 10. The trackpad was awful. I installed Ubuntu on it, and the trackpad is great now.
89.
▲
by
Peaker
10y ago
Population-size wise, everyone living forever is like adding two children on average to each family. Since people will still die from various causes and diseases, it'll be less.
90.
▲
by
Peaker
10y ago
Yes, it is unambiguous, even if it is context-sensitive. If you don't have the available type names then it becomes ambiguous.
More ›