pygorex

http://www.reddit.com/r/IAmA/comments/v99eg/iaman_exmember_o...

Right now the top-rated comment by Nate Phelps is not in direct response to a particular question.

This top-rated comment is not on topiama.com:

http://www.topiama.com/r/4/iaman-exmember-of-the-westboro-ba...

I don't know if this is a feature or a bug or if hasn't been crawled recently.

It would be great to see these top-level comments!

------------

Linking to an answer's context would be super-useful as well. A great deal of the fun and value reddit supplies is the community commentary and responses to an AMA's answers. This can range from the funny to the insightful to the scary - something topiama.com doesn't capture. Which is great - sometimes you don't want the peanut gallery.

  "Having control over your schedule is the only way that women who want to have a career and a family can make it work"

Actually for developers like myself there's several use cases where having access to the complete generated source would be awesome:

1. Separate the positioning/layout styles and the color/font/design styles into separate CSS files. That way I can include all the designs created with Easel easily instead of copy/paste one at a time for each element generated.

2. For showing a mockup to a client or knocking out quick interface for a side project using absolute positioning can be acceptable.

Can Easel output an entire web page? - meaning can I layout an entire page then get a zipped download of the page plus any CSS and JavaScript resources?

Here's a real-world example formatted nicely:

  #nav .group LI A {
    color: #fff;
    text-decoration: none;
    display: block;
    padding: 4px 0px 4px 4px;
    border-top: 1px dashed hsla(0, 0%, 100.0000%, 1.0000);
    -webkit-background-clip: padding-box; /* for Safari */
    background-clip: padding-box; /* for IE9+, Firefox 4+, Opera, Chrome */	
    -webkit-transition: all 0.25s ease-in-out;
    -moz-transition: all 0.25s ease-in-out;
    -ms-transition: all 0.25s ease-in-out;
    -o-transition: all 0.25s ease-in-out;
    transition: all 0.25s ease-in-out;
  }

  #nav .group LI A {
    color: #fff; text-decoration: none; display: block; padding: 4px 0px 4px 4px; border-top: 1px dashed hsla(0, 0%, 100.0000%, 1.0000); -webkit-background-clip: padding-box; /* for Safari */ background-clip: padding-box; /* for IE9+, Firefox 4+, Opera, Chrome */ -webkit-transition: all 0.25s ease-in-out; -moz-transition: all 0.25s ease-in-out; -ms-transition: all 0.25s ease-in-out; -o-transition: all 0.25s ease-in-out; transition: all 0.25s ease-in-out;
  }

Um, no. The pages won't "instantly" load - the browser still has to make a round trip to load the page content.

A loading or progress indicator should still be shown letting the user know that this round trip is taking place - especially important if you're on a slow US cell network. If a user is on a slow connection and no visual feedback is given they may end up mashing a link, making the load time worse - or, worse yet, assume the site is broken.

Use either if you have an irrational aversion to page reloads.

Snark aside - jQuery Mobile uses a similar technique to cache entire pages in the DOM and for page transitions.

Even so I don't really see the need for this site. When I launch a project I post it to my web site portfolio or blog then aggregate out to Twitter/Facebook/etc. What advantage are you offering over established publishing tools?

As others have noted this is not JSON and is not necessarily an improvement to JSON - so calling it JSON5 is presumptuous.

Embrace the criticism. Instead of JSON5 call it NotJSON - a standard that breaks the JSON rules for a few narrow use cases - namely when you want a hand-written, commented JSON-like syntax.

1. I am not arguing that our evolutionary past should dictate where we explore. Rather, I'm arguing it must inform how we explore. Space travel is so lethal for our species that we are better off engineering machines, robots or beings that are specialized to operate in space.

2. The energy expenditure, economic cost and sheer distance of space exploration is many orders of magnitude beyond the costs of land, sea or air travel. Comparing terrestrial forms of travel to space exploration is disingenuous.

3. No endpoint. When the great explorers were trailblazing across the oceans there was a reasonable expectation of finding a suitable endpoint with fresh water, edible plants & animals, other people (!) and exploitable resources. With space exploration none of these things are present. We have to carry a suitable endpoint with us during the journey and plant it where ever we happen to land.

Expanding on that last point - imagine a specialized mars robotic explorer that goes on a one-way mission, taps in a sub-surface source of water, erects a basic greenhouse structure, goes into sleep mode for a few months, wakes up, plants some seeds, sleeps a while longer, etc. - it bootstraps a suitable endpoint for human explorers to inhabit years, decades or centuries later.

And the ideal of manned spaceflight should remain in the 60's - at least for the foreseeable future. We are magnificently evolved to inhabit this planet. The remainder of the solar system is insanely hostile to our form of life. It's far more sensible to engineer machines that can act as our eyes & ears and extend our narrowly evolved senses to far-out and lethal environments.

Blogs quote other blogs all the time. But they make it look like a quote. Usually indented, offset, quoted, in italics, etc - with a prominent link to the source article. It's a small formatting detail but it has huge implications - it sends a clear signal that is immune to any plagiarism claims - "this is not our content but, dear reader, we still think it's worth your attention".

Also the twitter response is pitiful. Even if you're convinced that you've done nothing wrong that does nothing to change the fact that the original author feels slighted. Telling him that he's shouldn't feel aggrieved does nothing to fix the situation.

A simple apology along with an edit to the TNW article to clear up any attribution issues would have solved a small problem and prevented it from exploding into a mini-scandal.

Yes. Don't do it.

One of the biggest problems you're going to have at the get-go is finding people who actually give a shit about your product/service. Adopting an invite-only system attaches a huge negative filter to this problem: you are making it more difficult for prospective users to discover and use the product.

There's one very important caveat to this:

If you are relatively well-known and already have a large number of people following your blog, twitter or other web presence a invite-only system can make sense. Google can do invite-only because they can command millions of eyeballs through a simple press release. You are probably not Google.

When you are a somebody an invite-only system feels like an exclusive club that can create buzz & desire. When you are a nobody an invite-only system feels arbitrary and frustrating. You are probably a nobody.

Who do you want on your team? Someone who understands Opa? Or someone who knows what browsers know, in detail?

If I know only Opa I'm limited to what the Opa developers know about these technologies. I'm limited by what they know. By mastering these technologies I'm only limited by what I can imagine.

Opa is a barrier on my imagination.

For more complicated forms using a tool like jQuery Validation plugin makes more sense: https://github.com/jzaefferer/jquery-validation

What's happening here is liar's debt. Early in his career he must have made a decision to lie about his education, when no one was looking and when the chances of someone verifying the claim were low. He reused the lie on every subsequent job and it's stuck with him. It became encoded in the DNA of his professional reputation and he could not disabuse himself of it without making himself look the fool.

Now if the lie is recent and was used to get the head job at Yahoo - well then it's an even stupider lie. Why risk your professional reputation over something so trivial?

This is so true in programming as well. It's very easy to be consumed by the process and neglect the purpose and end-game.

Case in point: last year I took on a project for a personal fitness trainer looking to launch a web app where users could enter their weight, height, activity level and exercise goals (lose weight, build muscle, etc). With this input the app would return meal plans, exercise routines and supplements schedules.

Nothing I've mentioned so far is patentable - these features are obvious to anyone who has tried to lose weight and already exist online.

So what was the patentable bit? Well, the client had devised an algorithm that worked the inputs and emitted the diet recommendations & exercise plans. That he had created in an Excel spreadsheet. And I am more than happy to keep that confidential under the NDA.

A filter by age would be good. When a puppy is put up against an older dog I almost always upvoted the pup.

The title is misleading. A "pure HTML" site wouldn't contain CSS, JavaScript, PNG, JPG, videos - modern web design is really the binding together of a lot of different technologies to create compelling experiences.

Your title translates as "An interesting church site that doesn't use Flash or some other browser plugin".

Well since the quote essentially boils down to "damn look at dem titties" then yes it is very demeaning & disrespectful!

It's also sexist. Why? Because it's self-absorbed. Whoever spoke that quote wasn't thinking about how their words might make Katie feel in a room-full of people. "I'm a man I like titties and anyone else's thoughts and feelings don't matter." That's sexism in a nutshell: that the default and correct perspective is the male perspective. That anyone who doesn't hold this perspective just needs to "chill out".

Ouch. I hope that $500,000 is refundable in case of death or accident.

> Any human that makes the trip will be stuck inside the vehicle for the 214 days it would take to actually travel to the Red Planet.

I once made a road trip from Seattle to Tennessee in 3 days. In the middle of a frigid winter. During blizzard conditions. Of course we took breaks to get out of the car, stretch our legs, have a piss and get some fresh air. At the end of the trip I was ready to hang myself. The boredom and rigor of endless driving became unbearable. The prospect of taking a similar trip, over a much longer timespan, in much more hostile conditions and paying for the privilege is not appealing, at all.

Or code, test & deploy web apps from an iPad.

Or design & layout web pages on an iPad.

We live in a post-mainframe era even though mainframes are still alive an kicking. But a mainframe isn't required create, test and deploy PC software. Once PCs are no longer required to create, test and deploy code for mobile devices we'll be in a post-PC era - that is, once PCs are no longer a required part of the general purpose computing ecosystem.

However I can see the problem with such a culture if your boss happens to be a bcrypt-tard and is closed off to discussion/learning.

Context is everything. Re-reading the article I think I may have been hyper-parsing the question....