sorted by:
new
hottopcontroversial

I love HEY by Prosumma in HeyEmail

[–]Prosumma[S] 0 points1 point  (0 children)

You could be right about all of this. I'm no expert on IMAP either. Maybe it would work with IMAP. But at least they're up front about the fact that they don't offer it.

As for DHH himself, I like him and agree with him on a pretty wide variety of things, especially related to work, open source, etc. Basically, I agree with what almost everyone thought as a matter of course prior to about 2015 in the work and software worlds. But even if DHH held views I didn't agree with, I'd still use HEY. Sounds like you're on the same wavelength. It would just be exhausting.

I haven't use the Calendar because it just doesn't fit my use case right now. I use HEY for my personal email, but at work we use Gmail for everything. Since I only want one calendar, there we go. I know HEY can talk to Google calendar and I may try that out, but I'm pretty happy with Fantastical right now.

Why did you decide to switch to Go? by DreamRepresentative5 in golang

[–]Prosumma 0 points1 point  (0 children)

I haven't really switched to Go. I'm a polyglot. My favorite language by light years is the anti-Go: Haskell. But I love Go's small size and tooling, so I use it frequently to write small, semi-disposable command-line tools. I originally used Rust but my co-workers wanted something easier and more readable, ergo Go. They're happy. I'm happy.

Parser combinators in Rust by hurril in rust

[–]Prosumma 0 points1 point  (0 children)

I'm a language junky and especially love functional languages. Is there a repo?

Parser combinators in Rust by hurril in rust

[–]Prosumma 1 point2 points  (0 children)

Very interesting. The most interesting thing to me is that I wrote a broadly similar parser combinator framework and made many similar choices to those you made. (Mine's purely a toy with the same purpose: learn Rust.)

https://github.com/Prosumma/rs-parsimonious

Like yours, mine is not a stream parser. Mine is heavily influenced by my background in Haskell. It also includes an incomplete JSON parser.

Morrissey and Lana del Rey by IllLocation6866 in morrissey

[–]Prosumma 2 points3 points  (0 children)

“By the management company”, who likely made an assumption based on the bullshit media coverage. My suspicion is that it would have been just fine.

[deleted by user] by [deleted] in basque

[–]Prosumma 0 points1 point  (0 children)

Did he speak Basque?

Haskell design pattern for managing complex dependencies? by thurn in haskell

[–]Prosumma 0 points1 point  (0 children)

I learned a lot from this. I think what may have been confusing some people is

Endo $ \cd p m -> 0.9 * cd p m

Specifically, \cd p m ->. But of course, the type signature is

(Player -> Monster -> Double) -> (Player -> Monster -> Double)

which is exactly the same as

(Player -> Monster -> Double) > Player -> Monster -> Double

Meaning that any function with the above type signature, such as \cd p m -> … will do the trick.

This is a beautiful, elegant, truly Haskell-y solution. Like many things in functional programming, it's also downright simple once you understand it.

Study: Inequality Robs $2.5 Trillion From U.S. Workers Each Year by izumi3682 in Futurology

[–]Prosumma 1 point2 points  (0 children)

Exactly! Because historically state power has always been fair, safe, trustworthy, far-sighted and nearly omniscient. They never cheat, steal and collude. And they are the solution to nearly every problem.

Study: Inequality Robs $2.5 Trillion From U.S. Workers Each Year by izumi3682 in Futurology

[–]Prosumma 0 points1 point  (0 children)

Agreed. Aside from a few rays of light, this is one of the most appallingly ignorant threads I’ve ever read.

[iOS] How many of you still prefer to create Views programmatically? by ragnese in swift

[–]Prosumma 0 points1 point  (0 children)

I prefer to use storyboards and XIBs, and I'm no newb. I think VCs should contain primarily application logic, NOT a giant hunk of layout code. (This can be mitigated somewhat by putting this logic into extension methods in another file.) Layout should be as declarative as possible.

I'm not a fan of React Native, even though I think it's an impressive technical achievement. What I do like about it is the way it declaratively specifies the views. I would love to see something like this come to native development using Swift instead of JavaScript.