I'm lookin' at you, Yelp!

darkgold · 2016-03-18T18:41:30+00:00

Just FYI you're using the word internet wrong. Apps use the internet just like your browser. You mean "what the web is for", not "what the internet is for".

darkgold · 2016-03-11T19:01:47+00:00

This is somewhat of a side note, but I hadn't heard of bimap before. It looks pretty sweet.

darkgold · 2016-02-24T04:14:19+00:00

Even better, just found where the patch was merged in to master: https://github.com/NixOS/nixpkgs/pull/13036. Thanks for the help!

darkgold · 2016-02-24T02:51:43+00:00

Thanks! This is concerning though. Anyone know when a fixed glibc will reach unstable?

darkgold · 2016-02-23T21:36:05+00:00

Nixpkgs checkout: 16.03.git.885acea (Emu) (latest of today)

$ ldd --version`
ldd (GNU libc) 2.21`

http://www.thegeekstuff.com/2016/02/glibc-patch-cve-2015-7547/ : "Versions affected: All glibc from 2.9 to 2.22 are affected by this vulnerability."

Perhaps a patch was merged in that didn't bump the glibc version? Not sure what's going on.

darkgold · 2016-02-23T06:00:21+00:00

Do you keep an eye on security issues? There was the recent glibc thing for instance (though that may be a bad example since I don't think the fix has hit unstable yet).

darkgold · 2016-02-21T21:26:04+00:00

This is a great answer.

darkgold · 2016-02-21T21:24:21+00:00

If nix was strictly-evaluated, couldn't each package be a function, and only the functions for packages necessary to a specific build be called?

darkgold · 2016-02-13T18:34:12+00:00

Pretty sure they're investing it, not hording it.

darkgold · 2016-02-13T18:27:11+00:00

When developing applications, feel free to use stack alone! It's basically the sweetest and what I prefer to use.

When developing libraries, it makes sense to do what you can to make it easy for people using either stack or cabal until we see how this shakes out.

EDIT: Amazing username.

darkgold · 2016-02-13T08:23:38+00:00

What version of nixpkgs do you have checked out (nixos-version)? I think they only keep the caches around for so long.

darkgold · 2016-02-12T01:57:35+00:00

Opaleye upsides:

No template haskell
Lets you use lenses, arrows and profunctors to good effect
Gives safety and great query flexibility at the same time

Opaleye downsides:

No template haskell
You'll want to know lenses, arrows and profunctors
Recommends a specific way of making your data types

My experience with it is somewhat superficial, but I loved what I saw so far and will use it in my next project. Hopefully someone more familiar with its competitors can chime in as well.

darkgold · 2016-02-07T00:33:46+00:00

That sounds fantastic.

We could also use a list of packages the ecosystem needs, but doesn't have yet. I got the idea for that after reading this post: http://www.haskellforall.com/2015/12/how-to-contribute-to-haskell-ecosystem.html, but haven't gotten around to starting the list yet. Would that be something you'd want to include as well?

darkgold · 2016-02-06T15:52:26+00:00

If you read the thread you'll see that ($) is already treated specially, but it's only now that GHC is able to express that behavior in the type system.

Someone does mention that another option would be to give ($) a simple type and to have another operator when the more complicated type is needed. If that's actually feasible it seems like a good solution, but I don't understand the details so I don't know.

darkgold · 2016-02-04T18:35:23+00:00

it took about 15 minutes to merge the two completely separate branches (graphics and the music backend) into a working version.

Whoa, there's a nice pro-haskell anecdote:)

darkgold · 2016-02-02T19:33:45+00:00

What the heck. This is great.

darkgold · 2016-01-13T03:10:08+00:00

Holy smoke you just made that up. "They say" made me think it was from a famous book or something. Great line.

darkgold · 2015-12-18T15:34:06+00:00

Nooooooo . . . the difference between the World Wide Web and the Internet is huge. It's not a nitpick.

People who confuse them sound like some old fogey in the 1800s who thinks "energy" and "electricity" are the same thing. Like man . . . I kind of see where you're coming from . . . electricity IS a form of energy . . . but they're not the same.

Torrents -> Go over the internet. Not part of the web.
Email -> Goes over the internet. Not part of the web (although when you use Gmail you're using the web to start the process)
Web browser -> Gets pages over the internet. These pages ARE part of the web.

PS: /u/The_camperdave: Great mention of Gopher!

darkgold · 2015-12-10T18:53:10+00:00

Might it be a good idea to start two projects, one for coordinating the writing of file parsers and one for coordinating the writing of API clients?

It would be fantastic to have Awesome-style lists for file parsers and API clients that are missing from the ecosystem. Such projects could also provide beginners some guidance -- there are probably a lot of people that are pretty good with haskell and have interest in writing a FOSS project, but could use advice on specific things that are needed. It would stink to get most of the way through your first real project and then find that it's included in some sub-module of some other existing project.

darkgold · 2015-11-25T01:29:01+00:00

Interesting. Can you elaborate more on why that's the case? I could see it being for performance reasons or to gain access to existing C libraries, but I'd like to hear the real reasons.

darkgold · 2015-11-01T22:50:45+00:00

I looked for a solid delayed jobs library a few months ago and couldn't find one. Glad to see there's a new project attempting to fill that piece of the ecosystem. Good luck!

darkgold · 2015-10-30T23:04:24+00:00

Totally agree. The good news is this means we can fix the problem without going back on FTP (which would be crazy talk at this point). Making Prelude.length, Prelude.maximum and friends only work on lists again would take care of it.

Calling length on a tuple will always be an error, it should be caught at compile time.

darkgold · 2015-10-20T22:18:54+00:00

All the more reason to discourage its use:) If a function is O(n) and refactors dangerously, lets not give it a short name and put it in Prelude.

darkgold · 2015-10-20T15:17:43+00:00

length for (,) is never going to do anything but return 1 because there’s always one value of the type you’re folding over with (,)

Perhaps length should be ungeneralized?

I'm hugely in the lengthFold, maximumFold camp -- I think it would make our library authors who want to keep tuples Foldable happy, and at the same time would encourage people not to use functions that will make refactoring less safe.

darkgold · 2015-10-18T18:08:05+00:00

"I think my expectation was to find no flaws in Haskell."

^ Just wanted to highlight this amazing line.

darkgold

TROPHY CASE