brianmario

I've noticed this with drums too. Trying out more complex things that required more coordination than I'd typically been able to use up to that point... I noticed that after taking a long break - like 6mo, between bands, etc - with me playing very little in between, I could then sit down and play the thing I couldn't before effortlessly.

I still don't understand it, but I'm here for it.

You can use the gear icon in the upper right to turn the sliders into text boxes.

Cool! I agree that using prepared statements is indeed the best way to handle this stuff.

There were plans to build out the binary protocol in Trilogy as well, it just hadn't been wrapped up by the time it was made open source. And if I recall, that branch fell pretty far behind. Maybe now that it is OSS, someone can contribute that :)

The `trilogy_escape` call (https://github.com/github/trilogy/blob/main/inc/trilogy/clie...) should do it.

Curious why this was marked as a dupe?

Unicorn, but the idea is the same. Forcing a GC between requests can have consequences on overall request throughput.

The Co-authored-by trailer isn't actually new. In fact it was already being used by over ~1M commits on GitHub before we launched the feature! :)

The git-core commit message conventions docs mention it (https://git.wiki.kernel.org/index.php/CommitMessageConventio...) as do the OpenStack commit message convention docs (https://wiki.openstack.org/wiki/GitCommitMessages#Including_...).

Using the Co-authored-by trailer is also really useful when pairing, where there is actually more than one author for the content.

This is especially useful when using https://teletype.atom.io :)

One common way to attribute multiple authors in a commit is to add a `Co-authored-by` commit message trailer. You can read more about git commit trailers at https://git-scm.com/docs/git-interpret-trailers.

As an example, if this was a commit message, the trailer adding my attribution would be like this:

`Co-authored-by: FirstName LastName <[email protected]>`

Wonder if they knew about GitHub Organizations?

https://github.com/blog/674-introducing-organizations

You can use this library in 1.8 or 1.9. It's especially nice in 1.9 because you can use it to tag strings with the correct encoding based on it's content, which has been a huge source of frustration in 1.9 up to this point.

Really though, the pain in the ass has little to do with 1.9 - encodings are just a pain because they aren't universally supported. So we'll often times get handed bytes with no encoding context so we have to assume or use detection libraries like this.

One argument is "well just use UTF-8 for everything" or "just pass everything around as binary then it'll be fine" - but unfortunately we don't live in a world where either of those solutions will work for everyone.

you should be able to hold shift to select multiple as well

I'd like to think I can consider it one of my "known" languages, but people like @ice799 (timetobleed.com) know C. There's a HUGE difference.

"It's just ruby."- My favorite quote from one of the best Ruby programmers I know, who at the time had very little to no experience with Rails.

I'd say any framework has a "steep" learning curve, after which things just become easier and easier.

A problem I often see is that a lot of people try to learn Ruby through Rails; And while that may work for some basics, a lot of things are still going to be "magic" until you understand Ruby itself a little better.

For the love of god please stop supporting IE6 people. It's not the Enterprise that's keeping it around it's US (developers that continue to support it).

If the entire internet didn't work on it, you bet your ass these slow-poke Enterprise folks would figure something out ;)

strange, I can't get to it either - hopefully it'll be working tomorrow after they all sober up ;)

Some people may not like it, but this is exactly why I chose to force UTF-8 for http://github.com/brianmario/mysql2 for all the strings you get back (in 1.9), and the connection itself. We've all dealt with improper use of encodings between applications, their persistence layer and their presentation. It's a nightmare unless you put your foot down and say "We're making everything Unicode, nothing comes in or leaves unless it is". This obviously doesn't work for everyone but it's my experience that it will work for 99% of all use cases.

@dnsworks - you should chat with @jf (twitter)/(jpf on github) and/or Jeff Lindsay. They've got some pretty awesome ideas for DNS beyond traditional use.

It introduces plug-able JSON back-ends, like the plug-able XML back-ends that exist today. It ships with JSON back-ends for the existing YAML implementation and the JSON gem. In addition to that all of the plug-able back-ends (XML and JSON) support parsing from an IO as well as a string now.

technoweenie has written a Rails plugin adding yajl-ruby as a back-end at: http://github.com/technoweenie/yajl-rails/tree/master

I also have a fork that I'll keep up today with the latest API changes in yajl-ruby at: http://github.com/brianmario/yajl-rails