purephase

Wow, odd coincidence here. I was just taking a stroll through the ISO 3166-1 country lists to update our own database and noticed that they had changed it to "Palestine, State Of".

I'm not sure when it happened, but I dutifully changed ours to match (in the same way Google has) as following the standards orgs is generally good practice.

Any concern with running Ruby 2 in development and 1.9 (presumably) in production? I'm doing it now for the startup time boost in both console and thin but worried I'll inevitably introduce some code that will not play nice.

Which, sadly, we've had to do in development as something has been introduced into Rails or sprockets that makes our development environment so slow it's unbearable with asset debugging enabled.

It really hurts not having the ability to dive into the separate files.

My guess is Wiccan. Philosophers love their witches [1].

[1] http://www.uwo.ca/philosophy/undergraduate/Courses/2000.html...

Not knowing which faculties at which institutions this derives from (although, one could probably assume that they're not Theist institutions) that is a plausible explanation.

However, if you change the Population selection to the "No Affiliation" option the numbers are still pretty skewed in the atheist direction.

A lot to dive into there, but the God results immediately jump out at me.

Thanks Steve.

I like this. I'm using a lot of FancyBox at the moment, but the ability to resize via CSS sounds like a killer feature. And, let's just pretend that the Bootstrap modal doesn't exist.

Thanks for sharing!

Are we going to see another 3.2 release outside of security issues?

There have been enough performance and functionality related issues in 3.2.13 that I was hoping to see at 3.2.14.

That one sentence sums up about a decade of professional contention. And I mean specifically relating to IBM software and hardware.

I should have left that job sooner.

It's changed since then?

Realized major improvements is a bit of an over-statement. They've made some new APIs available to US developers while completing sabotaging their existing developer toolset and sandbox environments to the point that they're almost unusable.

I could forgive this if their support seemed even remotely cognizant of these changes, but every time I get in touch with them it's like they're hearing about it for the first time.

"it's just walking, after all"

I read that in the common dismissive tone that I hear regularly and cringed. I'm not sure it was your intent but when higher-ups try to ascertain the level of complexity/work with little to no knowledge of the problem, these sentences fly.

Having been one of those managers, I understand that they're largely trying to be optimistic and justify their own demands but as a project drags on, it depresses the hell out of me.

For Rails folks, you can accomplish a lot of this with the excellent Twitter gem "secureheaders".

https://github.com/twitter/secureheaders

Looks interesting. I've been meaning to cobble something similar together for awhile as I keep running into this problem. Thankfully, now I don't have too.

Thanks!

Since you called me lazy (thanks for that), I'll respond. Keep in mind, I'm not remotely an expert nor do I claim to be.

A few FAQs? I think you're being a bit disingenuous. While the protocol itself is relatively simple to understand, the complexity related to its implementation is immense which is why we're still talking about it and not fully doing it.

Why it's complex:

1. The recommended approach is dual-stack. This means that network admins/system administrators will essentially have to manage two separate networks. Of course, this is assuming you have core-to-edge IPv6 support. If not, then you're upgrading all of your hardware.

2. Cost. Predominantly why we're still here. Often easy for us to push aside in our cosy developed world, but ignores an enormous number of legacy hardware deployed all over the world that will simply not work and, quite frankly, the solutions like tunnelling read a lot like the supposed pitfalls of IPv4.

3. Training. It's not a matter of a few FAQ's to learn, for a lot of technicians it is a matter of re-certification as all hardware has to be replaced which likely means new operating systems and firmware, proxying/tunnelling servers/devices ala Teredo/ISATAP.

For anyone that says it's a "no-brainer", I say that you have little to no experience in managing large heterogenous networks in cost-strapped organizations which, up until now, have had little to no reason to upgrade as the IPv4 address exhaustion issue does not really affect them (yet).

I don't either. But, you have to admit a grudging admiration of our ability to procrastinate and not have the whole thing collapse around us in the meantime. We've been talking about IPv6 for years in alarming tones about address exhaustion and yet, we're still ok.

I guess I'm a glass half-full person on this one.

That is sort of what I meant. I stick by my caveat at the end though and recognize that it is likely far more complex than that which is why we're in the situation we're currently in.

While certainly concerning, I think the OP is proving the opposite pole. The fact that solutions are continually evolving globally to solve the IPv4 address space issue, and pretty seamlessly too, speaks volumes to how amazing the internet and it's associated technology stack truly is.

IMO, the main issue with IPv6 is it's overall complexity compared to IPv4. While it's end goal is laudable, I agree with another comment in that there may have been a better halfway solution (IPv4.1) which could have eased the transition.

I say this knowing full well that the problem is very complex and the people working on it brilliant which makes me believe that there may have been no other way.

Very cool. I'll have to check this out. That profile tool looks interesting too. I've been using the rack-mini-profiler gem but it might be a good idea to do a deeper dive.

As always GH, thanks for sharing.

You're not the target market for those types of PDF's then. In large corporate environments, PDF's are roughly the equivalent of small web-apps that handle a lot of the data entry and sharing across the organization.

I'm not a proponent of this approach, but it is what it is and it is the reason that Reader is such a bloated security-ridden nightmare.

If you've ever run a marathon, you'd know. 4 hours is still a pretty decent time for 26 miles and, for most runners, the last leg up to finish line is usually a pretty exhausting/euphoric time. Aside from your own heartbeat and breathing, you really don't notice much else.

To me, it looks like they respond physically to the shockwave but are not mentally registering anything other than the finish line.

You clearly remember a different Sourceforge than I do as it was always clunky and inaccessible.

User prefs: "show_tab_close_buttons": false

In flatland.sublime-theme:

Tab element: "content_margin": [18, 5, 20, 20]

Tab button size (show_tab_close_button): "content_margin": [8, 8]

Tab dirty state: "content_margin": [18, 5, 15, 20]

Not perfect or I'd submit a pull request, but I like these tabs a lot more than the default.

Voted you up because you basically just described the situation I'm in now.

While successfully in production, the web servers were crashing multiple times a day (still Apache-modphp). So, I started to work on the PHP upgrade from 4-5 to get onto php-fpm + Nginx to stabilize the site. Lo and behold, the legacy db abstraction code (poor man's ORM) was not playing well with later PHP releases so I started down the path to patch what I could.

I successfully upgraded PHP, fixed a few of their outstanding issues, but I was weeks into this project and had not completed any of the new feature sets on my plate yet. Looking into the horizon I imagined months of wrestling with legacy code and the deeper I went (there was a SOAP layer I hadn't even looked at yet, they wanted REST/JSON) the more worried I became.

We evaluated a bunch of options and opted for a re-write. We're still deep into it but there is light at the end of the tunnel and I'm pretty sure it will be worth it in the end.

TotalFinder and Divvy work for me. I get exactly what he's looking for.

Very specific, but surprisingly useful. Thanks for sharing!

Congrats! Happy Mailjet user here so I'm glad to see good things happening for them.

I had it done about 4-5 years ago and it was/is the single greatest personal decision I've ever made. My vision was terrible before (-8 in one eye, -10 in the other) and it has stayed at 20/20 since.

The day of, I had my wife come with me and take care of the trip home. You'll be out of it, so make sure you have assistance. I think most clinics won't even do it unless you have someone else to help you.

The surgery was relatively quick and painless. You can see better immediately, but it is still a bit blurry. You'll be out of commission for at least 2 days. No screens, reading etc. Your eyes itch like crazy but you can sleep through it. My recommendation is to grab some audiobooks to listen to as you'll get bored quickly.

My night vision was terrible for about 5-6 months after so driving at night was risky. I avoided it for about 3 months until it was at the point that I could see safely. Halos around lights will be distracting for awhile.

For pain I was prescribed Ativan. I'm not a pill-person, I typically avoid tylenol, but I thought it would be fun. It was.

As I suggested, I grabbed a bunch of audio-books, threw on the funky sunglasses they give you and sat in the park for hours laughing my ass of to John Hodgeman. I'm pretty sure passerby thought I was out of my mind.

Possibly one of the best days of my life. ;) Good luck!

What are the "number of things"? As much as people are complaining about Reader, I don't see that as bad PR. I assumed it was something other than the Reader fallout.