Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rrradical
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
91.
▲
by
rrradical
10y ago
Just an observation-- every time the topic of alternate voting systems is brought up on HN, or anywhere really, the discussion devolves into an argument over which alternative system is the best. It's quite obvious to me that if we are
92.
▲
by
rrradical
10y ago
The quality of a type system isn't measured solely by what it allows you to do. After all, no type system at all would allow you to do anything and write as many bugs as you want-- not great, right? Instead, a better type system will l
93.
▲
Does Google execute JavaScript?
(stephanboyer.com)
339 points
by
rrradical
10y ago
|
106 comments
94.
▲
by
rrradical
10y ago
Yes. I wrote 5000 lines on this (and bringing that abstraction to Haskell). [1] 1: http://asivitz.com/posts/layers
95.
▲
by
rrradical
10y ago
These sorts of explanations are very neat and educational, I think, but to me they aren't that effective in actually bringing us closer to using a new voting system. All the discussion here is an example of what tends to happen, which
96.
▲
by
rrradical
10y ago
Hm, ok, that's interesting. I guess I stopped following Vim's progress once I switched to Neovim. It still seems to me that Neovim has the right overall approach (through cleanup, shedding ancient compatibility layers), but if tha
97.
▲
by
rrradical
10y ago
I'm not sure how it could be 'for worse'? Even Neovim benefits from the uptick in Vim patches, because they actually merge many of them into Neovim. So it seems like it can only be a good thing. Better editors for everyone.
98.
▲
by
rrradical
10y ago
That's fair. I got that they were joking, but I guess I didn't know to what extent.
99.
▲
by
rrradical
10y ago
The Haskeller was probably talking about the same 'deep freezing' feature that they mentioned above, right? Except it already has a name...immutability. But even as they were joking, the Ruby folks assumed it was some obscure theo
100.
▲
by
rrradical
10y ago
I could be reading the tone of the interview wrong, but it seems like there's a weird sort of anti-intellectualism bent to the Ruby community. In the middle, there's this exchange: Jonan: So you would just use pointers to poin
101.
▲
by
rrradical
10y ago
hey, thanks for posting! I'm the author - happy to answer any questions. The article is mostly about the theory side of things, but I've actually had a lot of practical success building UI with this technique. Now I'm most in
102.
▲
(De)constructing the Front End
(asivitz.com)
1 points
by
rrradical
10y ago
|
0 comments
103.
▲
by
rrradical
10y ago
I see things a bit differently. Some domains are well understood and it's relatively easy to write perfect code (e.g. mathematical functions, list manipulating functions, etc.), while in others it may be much harder (the file uploading
104.
▲
by
rrradical
10y ago
The author is just examining a common design mistake-- there's no sin there. Many times, it's a mistake to pass in a boolean switch when you could instead pass in the predicate function itself. That's a solid example that sup
105.
▲
by
rrradical
10y ago
So then stop using plastic bags? That's the whole point of the legislation.
106.
▲
by
rrradical
10y ago
It's true. Personally, I took that to be a bit tongue in cheek. I would compare it to "GOTO Considered Harmful"-- where the author wants you to imagine a world without such a technique in order to expand your abilities. (Even
107.
▲
by
rrradical
10y ago
Someone else addressed the details of your counter argument, but I'd like to respond to it generally. It seems like every time someone writes an article on how to write better code, there are responses about how it doesn't make se
108.
▲
by
rrradical
10y ago
Test cases...code review... How about type checking?? The idea of writing financial software without taking every available precaution to verify correctness is insane to me.
109.
▲
by
rrradical
10y ago
Generally you build the new list using the tail of the old list (which is unchanged), your inserted value, and each of the values in front inserted onto that. So, immutability is preserved. Any existing references will not see their values
110.
▲
by
rrradical
11y ago
That...is a great idea. Thanks!
111.
▲
by
rrradical
11y ago
I assume this is too green to work with cross-compilation (to arm built from x86, for example), but does anyone know if that support is planned? I did some haskell work with iphone in the past, and it was a pain to go from testing locally t
112.
▲
by
rrradical
12y ago
Oh jeez. I wish this were posted a few days ago. That's 5 hours of nodejs debugging I'll never get back. But really, I'm psyched this is available.
113.
▲
by
rrradical
12y ago
As someone who has made indie games with both traditional OOP and component systems-- I vastly prefer component systems. I disagree that they make things more complex. I found that they made things much simpler. Although, it does require le
114.
▲
by
rrradical
12y ago
I won't claim to be an expert on this stuff-- I've only recently been studying this. But, from my understanding, if you have a tree of GUI elements, each of those elements needs to have the same type, and that type needs to be kno
115.
▲
by
rrradical
12y ago
Ironically, Phoenix, as Firefox was originally named, was initially created as a slim alternative to the then bloated Mozilla browser. I'm sure we'll see history repeat itself in a few years.
116.
▲
by
rrradical
12y ago
Right. In OO, you can inherit, but in Haskell, you can't.
117.
▲
by
rrradical
12y ago
I'm talking about supplementing a toolkit. Like, in iOS or gtk or QT or whatever, there are stock widgets (buttons, sliders, text boxes), but you can also add your own widgets, like a date picker. A date picker would be modeled complet
118.
▲
by
rrradical
12y ago
I am a big proponent of functional programming, but there are situations where it would be veeerrryy convenient to have open types and inheritance, which is forbidden in a language like Haskell. Modelling something like a GUI toolkit is ver
119.
▲
by
rrradical
12y ago
Sure, but sometimes strong opinions are necessary to make progress. If Dijkstra hadn't written "Go To Statement Considered Harmful", would we still be using them today? Probably not, but it probably helped bring quicker progr
120.
▲
by
rrradical
12y ago
"I got this scar on my face during a mighty struggle!" "I'm glad to hear you attended your family reunion." No dice. :(
More ›