Profile

Cover photo
Gregory Collins
695 followers|101,259 views
AboutPostsPhotosVideos

Stream

Gregory Collins

Shared publicly  - 
 
Hey +YubiKey: we've been using your products for years at work, but I recently picked up a couple of Neos for my personal use and I am really impressed. Super easy to set up, great open source tooling, GPG support is basically unique in this form factor, and U2F just works and is a big usability improvement over 2-factor using a TOTP app like Google Authenticator or an SMS message. My SSH and GPG keys live on the smartcard now. Kudos!
7
1
Iustin Pop's profile photoGregory Collins's profile photoSimon Meier's profile photo
10 comments
 
Right after I got a couple of neos :-). Oh well -- for my purposes 2048 bit subkeys are enough for now.
Add a comment...

Gregory Collins
moderator

Discussion  - 
 
Just for fun; what's YOUR #ifdef  count?

    ~/personal/src/snap $  find . -name '*.hs' | xargs egrep '#if.*(MIN_VERSION)|(GLASGOW)' | wc -l
    64
2
1
Neil Mitchell's profile photoIvan Miljenovic's profile photoNoam Lewis's profile photoYuji Yamamoto's profile photo
5 comments
 
I have NoImplicitPrelude + import Prelude.Compat almost everywhere
Add a comment...

Gregory Collins

Shared publicly  - 
 
 
It is with immense sadness that I read about the passing of Paul Hudak today. A wonderfully kind and brilliant man who was a huge inspiration on me and many other people.
There's an update to this CaringBridge website. Read more and leave your message of love, hope and compassion.
1
Add a comment...

Gregory Collins

Shared publicly  - 
2
Amy Emel's profile photo
 
Yes! Cool guy with good ideas.
Add a comment...

Gregory Collins

Shared publicly  - 
 
+Icelandair is totally adorable :)
17
Add a comment...

Gregory Collins

Shared publicly  - 
 
Major milestone on the road to Snap 1.0: we now have 100% test coverage for io-streams, snap-core, and snap-server.

In the process of getting to 100%, I found quite a few small bugs in dusty corners of what was already a very well-tested codebase, and many opportunities to simplify or remove branches when I found that a certain function was difficult to cover completely. The old adage is still true: if it isn't covered, it isn't tested!

My intention is to throw down the gauntlet to people running other projects: yes, you should be building a test coverage report as part of your continuous integration runs (and you are running a buildbot, right? Now that https://travis-ci.org/ is around you have no excuse), and yes, the number on this report should be 100% or as close to it as possible.

#haskell   #snapframework  
32
1
Neil Mitchell's profile photoGregory Collins's profile photoAndy Gill's profile photoMartin Geisler's profile photo
9 comments
 
The problem is that sometimes you might want a tick box for the () in return (). Not often, but turning off ticks for () would be a special case. Perhaps a student can pick this up, and try things, and document what they can find?
Add a comment...

Gregory Collins

Shared publicly  - 
 
+Steve Kado will love this.
 
h/t to my brother +Jeremy Altheide for pointing me at this

Megachurch are a heavy rock band from Ohio who employ two bass players and eschew vocals in favor of televangelist samples.
1
Add a comment...
Have him in circles
695 people
Jason Knight's profile photo
Dylan McNamee's profile photo
Martin J-Gonzalez's profile photo
Michel Alexandre Salim (Arcane Hexed Mill)'s profile photo
Maciej Piechotka's profile photo
Sysomos's profile photo
Ingo Wechsung's profile photo
Aaron Turon's profile photo
Luke Palmer's profile photo

Gregory Collins

Shared publicly  - 
 
+Dell has been seemingly making better laptops lately (the ones I owned in the mid 2000s usually fell apart within six months), but if anything customer service is even worse than I remember.

I tried to order a laptop and have it shipped to the office, and forgot to set the billing address on my credit card to my home. Not only did Dell not catch this the night I actually made the order, I've been trying to respond to their customer service about this issue for three days now. I can't get them on the phone, I can't get them on chat, I can't get them over email, I can't update my billing address via automated form. The email the customer service guy wrote me was kind of rude, too -- "*Please note that failure to contact us within 1 business day may result in cancellation of your order.*"

I guess it's time to hold you to your own standard: your failure to be contactable by me within two business days will be resulting in the cancellation of my order. :-)
4
Erik de Castro Lopo's profile photoGregory Collins's profile photo
4 comments
 
Hilariously, today they shipped me the laptop. Now I have to get a return label from them and go to the UPS to return it. +Dell loves wasting my time!
Add a comment...

Gregory Collins

Shared publicly  - 
 
How could you not feel a little homesick after a weekend like this :-)

(Photo by Amy, Vancouver island)
6
Jerdon Collins's profile photo
 
Cool and beautiful place eh?
Add a comment...

Gregory Collins

Shared publicly  - 
 
I live in San Francisco now!
20
Gregory Collins's profile photoOzgun Ataman's profile photoChris Smith's profile photoAlex Lang's profile photo
6 comments
 
Let me know if you ever come north to Vancouver or Portland
Add a comment...

Gregory Collins

Shared publicly  - 
 
Tuesday afternoon nostalgia break! +Steve Kado 
1
Steve Kado's profile photoGregory Collins's profile photo
2 comments
 
+Steve Kado the kids get me every time
Add a comment...

Gregory Collins
moderator

Discussion  - 
 
People,

There has been a lot of debate over the Hackage package versioning policy lately. My plea to you: please follow the policy and put upper bounds on your version dependencies.

Some (typically those who maintain a lot of packages) advocate removing the upper bound from package version dependencies since it means you don't have to upgrade your package's dependencies if a new version of package foo comes out.

My contention has always been that this is a recipe for "code rot" -- old code that ought to still build without problems breaks because you depend on package "foo", which depends on "bar >= 0.2",  and the "bar" api changes between 0.3 and 0.4.  The linked github issue is an example of this.

I appreciate that package authors have a lot of work to do and that bumping package bounds on 100 packages gets tedious when a new version of bytestring comes out, but this is shifting the maintenance burden from you to all of your users in perpetuity. In order to keep this program building, I either have to commit to running on the Hackage treadmill and making sure all code I've ever written continues to build with the latest versions of all of the crap on hackage, or lock down upper bounds on all of the packages in the transitive closure of the bad package's dependency graph.

For libraries on Hackage this is probably OK because it's expected of a package author to keep current. This program, however, is application code and there is no excuse for it not to be buildable in this particular case. If upstream had followed the PVP then I wouldn't have to spend the 30 minutes or whatever it's going to take to fix this.
19
1
brad clawsie's profile photoDarren Grant's profile photoEdward Kmett's profile photoLuke Hoersten's profile photo
6 comments
 
I'm back from traveling, so I should be able to update all of my packages to support the latest version of text, which I presume is the issue.
Add a comment...
People
Have him in circles
695 people
Jason Knight's profile photo
Dylan McNamee's profile photo
Martin J-Gonzalez's profile photo
Michel Alexandre Salim (Arcane Hexed Mill)'s profile photo
Maciej Piechotka's profile photo
Sysomos's profile photo
Ingo Wechsung's profile photo
Aaron Turon's profile photo
Luke Palmer's profile photo
Basic Information
Gender
Male