Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
matryer
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
121.
▲
by
matryer
13y ago
I use it to keep track of the current BitCoin values on Coinbase.
122.
▲
BitBar - put the output from any script/program in your Mac OS X Menu Bar
(github.com)
1 points
by
matryer
13y ago
|
1 comments
123.
▲
Very interesting facts from MatFacts.co.uk
(matfacts.co.uk)
1 points
by
matryer
13y ago
|
0 comments
124.
▲
Disclaimr - website to protect you against offending people
(disclaimr.appspot.com)
1 points
by
matryer
13y ago
|
0 comments
125.
▲
by
matryer
13y ago
var obj = { /** * Says something in the console. * * say(msg) - Says something once. * say(msg, times) - Says something many times. */ say: Over( function(msg$string){ console.info(msg$string); }
126.
▲
Over.js - Elegant function overloading in JavaScript
(github.com)
1 points
by
matryer
13y ago
|
2 comments
127.
▲
by
matryer
13y ago
... and vice-versa
128.
▲
by
matryer
13y ago
We just thought it did too much for what we needed. It's a great library, and if I were parsing URLs in my apps I'd use it. But we just wanted a single get() interface and support for complex objects in the URL. Arg.js turns an
129.
▲
by
matryer
13y ago
for nested data - I 100% agree. I'd do that and use params for things like ordering or filtering on other fields: http://mystore.com/electronics/computers/manufacturer/apple/type/laptop#?o
130.
▲
by
matryer
13y ago
Ohh that sounds good... I've never done it before - fancy giving me a pull request? :)
131.
▲
by
matryer
13y ago
URL parameters ARE RESTful and I agree that your use case is exactly where parameters are useful.
132.
▲
by
matryer
13y ago
... I do like the 'routing all paths to one page' idea though.
133.
▲
by
matryer
13y ago
I love that style too actually - and always prefer it when I can. Sometimes, you just need parameters. But more and more I'm writing apps with no backend (Stretchr makes it easy to do so) in just HTML5 and JavaScript... and serving pa
134.
▲
by
matryer
13y ago
I agree actually - I prefer to keep them separate, which is why we included the hash() and query() methods too. I'd say pick one and stick with it. Arg.js has to care about both, because people use both.
135.
▲
Arg.js – Lightweight URL argument and parameter parser
(github.com)
32 points
by
matryer
13y ago
|
19 comments
136.
▲
by
matryer
13y ago
We wanted to support OAuth2 in Go and it was tricky to do in a TDD way, so we built Gomniauth. Today it supports Google and Github, but it's VERY easy to add providers. It's also general enough to support beyond OAuth2, so it'
137.
▲
Gomniauth: OAuth2 package for Go web apps #golang
(github.com)
3 points
by
matryer
13y ago
|
1 comments
138.
▲
Why Chicago is 'Stink Onions' in the Atlas of True Names
(bbc.co.uk)
2 points
by
matryer
13y ago
|
0 comments
139.
▲
by
matryer
13y ago
I need this
140.
▲
Love song inspired by HTTP Status Codes?
(soundcloud.com)
2 points
by
matryer
13y ago
|
0 comments
141.
▲
Fanjs: Circling the square with Math.PI - jQuery plugin
(matryer.com)
2 points
by
matryer
13y ago
|
0 comments
142.
▲
Coolest Offices in Tech – London vs. The Valley
(adzuna.co.uk)
2 points
by
matryer
13y ago
|
0 comments
143.
▲
Testify: Testing package for the Go language - Thou Shalt Write Tests
(github.com)
1 points
by
matryer
14y ago
|
0 comments
144.
▲
Disclaimr: Tongue-in-cheek disclaimer for posting offensive URLs
(disclaimr.appspot.com)
1 points
by
matryer
14y ago
|
0 comments