stephenhandley

cool idea but the design is frustrating.

there's a lot of noise on the page considering all I want to see are the names and they only occupy about 1/16th of the screen currently. would be more easily consumable if you grouped by bigrams and had each row devoted to a given leading bigram.

al

  hi        fi        ...

    alhico    alfiof

    alhiea    alfiou

    ...

be

...

if i click on a name, then show the affiliate links.. otherwise they're just wasting space.

given that all the domains you're displaying are the same length, you have a nice constraint to work with in the design and could really use space well.

I've got a demo video and more info here http://duhcam.hello10.com/

G+ is more about building an interest graph than FB, don't use it as a vanity/foodiate platform and it won't be a ghosttown. I'm mostly on it for link following and I'm getting super high quality science and tech links in my feed. the ghost-town characterization is way off base.

Exactly.

Those reviews look fake.

In my experience, the onboarding experience sucked and it crashed every time I used it until I installed it.

"Very cool!! Tons of features. Very fluid. Definitely a step in the right direction by Yahoo!"

Sounds like someone from PR wrote that.

psssst.... there's already "a guitar that anybody can play". it's called the guitar.

also, http://www.youtube.com/watch?v=23i8BzhxCy8

this should have launched in the UK.

word. yeah there's some bugs tho. after making something recurse with some circles, adding squares really turned it on its head for me. i dug the glitches tho. fun to watch it render too..the dynamics are pretty nice. got some screenshots here http://look.person.sh/tagged/recursivedrawing

this is awesome. support for deltas on transparency and colors would be really cool. also snapshot to save and share a picture

would it be possible to display the resulting chef recipes from the chosen configuration on /server/:id ?

awesome. maybe an alternative api would be to allow for something like

  fixie.init([".array", "#of .selectors", ".that", ".should", "#be .populated .with .lorem"])

or just a string like

  fixie.init(".string, #of .comma .separated .selectors, .that, .should, #be .populated .with .lorem")

I think that would address the class proliferation issue and still be explicit about which dom nodes should be populated. easier to maintain / comment out.

Many of the new approaches to science publishing I’ve seen haven’t done enough to directly address the silo problem or provide significantly improved alternatives. I suspect this is primarily because they’re trying to create viable scientific publishing businesses of their own. I believe taking a different approach around free, distributed, open source publishing and aggregation software would be better suited to transforming scientific communication into a more open, continuous, efficient, and data-driven process.

more here: http://tldr.person.sh/on-the-future-of-science

i don't understand the appeal of this when there's tons of client side js templating options (handlebars, jade, haml-js,...) that result in far more readable code than a $.el. prefixathon

oh awesome will check that thanks @jdd

awesome. anyone who has had the time to dig into the source want to elaborate on this?:

" Lo-Dash's performance is gained by avoiding native methods, instead opting for simplified non-ES5 compliant methods optimized for common usage, and by leveraging function compilation to reduce the number of overall function calls. "

also, any chance of contributing the improvements back to underscore or is this different enough that that's not a possibility?

rad... there's a bunch of bands on their i wish they had streaming live .. you have any idea why some bands aren't on the live stream?

yeah its their player. i was originally hoping to have better access to the individual channels/stages over the gdata api.. but there aren't individual streams so ended up being restricted in what i could do with the app.. pretty bummed about that, but there was no way to know until streaming started yesterday. just wanted to see what meteor was like and this seemed like a good candidate

i fucking hate posts like this.

"<power user> has gripes" => "<site> is dead".

you're either following the wrong topics, people, or just don't have a sense of humor (that bread question was funny as fuck)

there's still tons of high quality content on quora

i.e.

- http://www.quora.com/What-are-some-best-architecture-practic...

- http://www.quora.com/Jeremy-Lin-1/Whats-it-like-to-play-on-t...

- http://www.quora.com/Design/Is-there-a-science-to-picking-th...

ETC. ETC. ETC.

LAKES

seems like this is definitely something that's most useful as an app prototyping tool rather than a deployment environment. and if its a prototyping tool, i'd want it to run locally so i wouldn't have to deal with remote admin / debug

so it should probably just be open on github.

just throw express or restify in front of mongodb with some minimal scaffolding and generators. if i get a minute i'll try to get something like that up

yep seeing similar issues with younoodle, really buggy implementation ... content going unsaved, js alerts after pasting into fields. doesn't seem like having their own application form similar to ycombinator would be that big of a deal...

_ for enforcing encapsulation is great, probably the one thing I've seen in dart that's exciting. simple way of giving an existing naming convention significance and cutting down on character overhead. i could see a whole line of languages expand on this idea.

Pretty disappointed with the lack of risk with this. Conceptually seemed like something with a ton of potential, but the minute I saw the tutorial shoehorning the worst of Java and JavaScript into something new, it was a non starter for me...better being insulated writing CoffeeScript a layer up and waiting for a compiler.

Things I've noticed so far that I don't like: get/set proliferation, semicolons, braces, positional args, var for instance vars, int/num dinostyle pseudo-primitives.

It seems like they tried to do some cool things, but failed in execution. Like "Greeter.withPrefix(this.prefix);" one-line constructor definition .. where this.prefix is a "shortcut that assigns the parameter's value to the instance variable prefix". Eliminate needless code.. but instead of using a dedicated symbol to call attention to the sugar, they used "this." WTF.. did they specifically want to kill scanability.

Things I've noticed so far that I like: using "_" as a prefix to enforce encapsulation.

Enforcing naming conventions as syntax seems at least somewhat python inspired in the sense of bringing the whitespace is significant design to naming is significant.. wish there had been more of that.

If someone other than Google were doing this it would be dead in the water already.

I'm surprised to see no one has mentioned Quora on there. Their approach to making anonymity variable based on topic and context, while at the same time requiring real-identity backing it, works well. Users are able to hide their identity as needed while the site can still maintain accountability.

Really great point. Maybe load the low res version initially and then predictively load higher resolutions as the gesture proceeds and fade between them to compensate for the latency.

I prefer designing desktop and mobile in parallel rather than one before the other. Cycling between the two seems to bring up the constraints on the ui and compromises that need to be made more quickly than proceeding one to the other. Wrote more here: http://tldr.person.sh/resource-limited-responsive-design

F) http://domai.nr

your name being 4 letters makes that less useful than it would be otherwise.

So D) is probably your best bet for the reason pavpanchekha and Joakal already suggested: if you're successful you can buy the original domain name you wanted like dropbox, mint, facebook, twitter, etc.

Maybe try getting the same 4 letters twice in a row if that works...

lol this is just some pay your dues nonsense. "You will love rails if you begin at the start like we all did"

http://pine.fm/LearnToProgram/ (probably not relevant for HN) http://ruby.railstutorial.org/ruby-on-rails-tutorial-book http://devcenter.heroku.com/articles/quickstart