LoonyPandora

Likely as a result of the DMCA takedown request that has blocked access to their repo: https://github.com/github/dmca/blob/master/2014-07-11-MPAA.m...

I've installed the app, but have not created an account yet. Every few minutes I get a push notification that "Ed sent you a link". [0]

I think you have a bit of a problem with whatever system you are using to send notifications!

[0] http://i.imgur.com/3x7tcrc.png

Important to note that postfix dereferencing is experimental, and does not replace the existing method of dereferencing.

Also, I think the deprecation of core CGI.pm is pretty major. For now it just issues a deprecation warning, but will be removed totally from core in future versions, only being available via the CPAN.

https://metacpan.org/pod/release/RJBS/perl-5.20.0/pod/perlde...

I can see zero difference in the information density between the existing non-responsive design of that page [0], and the beta version of the responsive design [1].

While your point that mobile first design inevitably causes a lack of information density at desktop resolutions has some merit, it does not apply in this case.

[0] http://cl.ly/UFuw

[1] http://cl.ly/UFzs

Or even simpler, use the customizer [0] to download the bits you want. A few checkboxes and you're done.

[0] http://getbootstrap.com/customize/

Sounds like a very similar chain of events to the Goiânia_accident [0]

[0] http://en.wikipedia.org/wiki/Goiânia_accident

From the guidelines - and I think a much better way of adding commentary & changing headlines:

http://ycombinator.com/newsguidelines.html

  Don't abuse the text field in the submission form to add
  commentary to links. The text field is for starting
  discussions. If you're submitting a link, put it in the url
  field. If you want to add initial commentary on the link,
  write a blog post about it and submit that instead.

I totally agree about the private repo thing. In fact I emailed them and they added to their Feature Request List™

I suggest you email <support@github.com> to let them know more than one person would like the feature :)

Nothing of this has anything to do with cargo cults. There is an actual reason behind every rule.

There may be reasons, but I find there is often a lack of understanding about the context in which that rule was developed, and the compromises that were made. A developer not understanding why things must be done in a certain way, but doing it anyway sounds pretty cargo-culty to me.

To be able to see this information on the linked page, click on "Advanced: Enable" at the bottom of the screen. Then you'll see the "Output Scripts" section where this info is contained.

It's new in 0.5.0 [1] - Released ~10 days ago. Things in docker-land move super quick!

[1] https://github.com/dotcloud/docker/wiki/Docker-0.5.0:-extern...

Older thread with more comments: https://news.ycombinator.com/item?id=5663581

In case it's not clear, this is a development version along the road to the stable 5.18 release, expected in May 2013.

The Perl core team are getting very good at timeboxing their development and releasing on time.

This is really beautiful, and just what I need right now at my company. Well done, and thank you!

Incidentally 86% of Dutch people speak English, from my experience that is higher in coastal / docklands areas. Also an iPod shuffle is $49. I thought it was a nice gesture.

I don't know how long ago you paid for it, but I paid £35 for my license 3 years and 1 day ago (August 8th, 2009)

3 years of use from a product, plus we now have the almost-guaranteed support and speedier development because of it's Open Source nature. I think it was worth the money.

If you paid for it last week, I can understand frustration.

It doesn't appear to be a code-dump to GitHub, which would be indicative of fading interest on behalf of the original developer.

The ReadMe, build process, and licensing instructions all point towards this being a well planned Open Sourcing of a product.

I'm pleased with this, and hopefully it will spur development of TM2, allowing it to truly compete with the up-and-coming Sublime Text 2.

The payment not being clearly over HTTPS sets off alarm bells. We've trained people for years to not type CC details unless you see the padlock. Whenever I wanted a fancy in-page checkout form, I made the decision to serve the whole site over HTTPS, just for clarity.

The bundle itself looks very appealing.

Also, someone needs to practice spelling "recipes". There are two instances of the same typo on the page. Combined with the HTTPS issue mentioned earlier, this looks scarily like a scammers page.

"Tasty bonus recipies" "recipies with backbone"

http://training.perl.com/OSCON2011/index.html

Specifically the talk titled "Unicode Support Shootout: The Good, The Bad, & the (mostly) Ugly"

It's a year old now, but it's still relevant. It gives a very detailed look at unicode support across JavaScript, PHP, Go, Ruby, Python, Java, and Perl.

Apple haven't announced which machines will be compatible with the released version of Mountain Lion, so it's premature to say that Apple are "blocking" it. "Blocking" is also different to "Not Supporting"

Minimum specs have changed between beta and released version in the past. Apple has also released firmware updates to make machines boot in 64-bit mode as well. It is well within the realms of possibility that your machine could become "compatible" before 10.8 is released.

Secondly, as a point of reference the current MacBook Pro's do have upgradable hard drives and RAM. However the battery is not easily replaceable.

The problem is its overuse, not it's qualities as a typeface. Comic Sans is not a bad typeface, it was merely overused and became a cliche. Lobster is well down that same path.

Official support for WebSockets and SPDY in nginx is big news. WebSocket support especially, as previously it was impossible to do long-polling / WebSocket type work in nginx without resorting to unreliable 3rd party modules.

I live in the complex where these missiles are supposed to be deployed.

The part of this situation that upsets me the most is not the missiles, but what comes along with them - the heavily armed soldiers billeted for up to 2 months.

We have no choice in this, and were informed by a leaflet through the door.

This isn't war time and the Olympics only last for a few weeks. We shouldn't have to have soldiers and weapons in a residential complex!

By "original issue", I was referring to the actual GitHub issue / bug report.

On the wider issue of semicolons I am in agreement of you, and all my own code is written with that in mind - though I respect the bootstrap authors preference and would style my pull requests without semicolons.

If their insistence on not using semicolons causes conflict with other popular software, I would hope they see sense and fix those conflicts - even if that meant adding a semicolon or two.

    Now, this could be easily solved – by adding the friggin semicolon.

For reference, I sometimes use semicolons in my javascript, sometimes I don't. It depends on context and whether it makes the code more readable. It's not an issue I care enough about to get involved in a holy war, one only marginally more relevant than tabs vs spaces.

[1] https://github.com/twitter/bootstrap/issues/3057#issuecommen...

Perl has not been vulnerable to this kind of attack for 9 years (Perl 5.8.1)

[1] http://perldoc.perl.org/perlsec.html#Algorithmic-Complexity-...

A cursory glance at the visible portions of the code on http://skimling.com/ doesn't inspire me with confidence. Asking for credit card details on a non-secure page is unforgivable, and will land you in a lot of legal trouble (PCI compliance).

I think you would do better if you could show people the code.

My honest suggestion would be to just open-source what you have and build a bit of buzz within the community. From what I can see, you don't have anything that is worth buying right now. Perhaps that buzz you build will attract the right sort of hacker to help you build version 2.0

The issue I took was that in the HN submission you position them as best practices, but when questioned on them you said they are just guidelines that don't have to be followed all the time. This disagrees with your own views on what best practices are [1].

Perhaps it was just a badly phrased submission title, but it set the tone and direction of the discussion. The title effectively told people they are doing CSS wrong. People don't like to be wrong, and will go to great lengths to prove themselves right [2]. It's nothing personal and I bet if the title was less preachy, it would have gathered more productive comments and had a friendly tone.

In general your articles are high quality and the advice sound. I think this issue was caused solely by a bad title. Though I still don't understand why you hate IDs so much!

[1] http://csswizardry.com/2011/12/on-html-and-css-best-practice...

[2] http://xkcd.com/386/

Shove it on GitHub, it's edit in-browser functionality means it is accessible to non-techies. Problem solved.

All it needs is someone to pick a master format for the text and run with it. That should be someone with enough domain knowledge to choose wisely. I would say something like markdown with embedded metadata (like how you format a blog post with jekyll), but I admit I don't know anything about the requirements of the project.

That would be very useful. I struggled to find references to back up my statement, as the jQuery docs for .ajax() only has a vague "other methods may not be supported in all browsers" - with no further details.

A simple table showing browser support for different methods in .ajax() calls would help a lot!