bct

No mechanism, just a damaged bicycle.

I haven't watched the video yet either, but I'm guessing he's talking about Datomic's design, which would make this a good place to start: http://docs.datomic.com/architecture.html

Yup, having your bike slide off the road is no fun. A studded front tire helps a lot.

I think you had the wrong URL in your clipboard :)

From the docs:

"If the app does not respond with 2XX, then the server should try again later."

"Shirley has her client in maintenence mode; jerrold.me will attempt to deliver the notification later using an exponential backoff algorithm."

Having a good product is necessary, but far from sufficient.

I don't mean this in a cruel way (I'd really like this to succeed), but that's a list of features, not a plan for getting adoption.

Figuring out how to bootstrap network effects is critical.

How impotent it always was.

> Basically it's complicated in structure [...] but simple in interface, and that's pretty much the right place to be.

Thanks for posting this, this is a great analysis. It gets right to the heart of many of the disagreements I have with system design orthodoxy.

I think it's exactly the wrong place to be.

It's too bad that opposition to changes like this is often expressed so trollishly. There's a real tradeoff here (of simplicity and of portability) that gets glossed over.

It is. And the server doesn't even feed PhantomJS the HTML that it can generate, PhantomJS has to make another request to the server. I wonder if it can be made to recurse? https://github.com/meteor/meteor/blob/master/packages/spider...

The article links the wikipedia page on stereotype threat http://en.wikipedia.org/wiki/Stereotype_threat , which has plenty of references to studies demonstrating how this differs from other types of anxiety.

The entire article is about personal experiences that have prevented people from doing the things that they're interested in. It doesn't say anything about what society wants, or ideal demographic ratios, or whatever.

This isn't about philosophy or ideology, and it's interesting that so many people here are framing it that way.

> no one is complaining about low presence of men in female-dominated industries.

Do you actually know that?

You're mixing different layers of worrying.

People underperform because they're worrying about problem X (confirming stereotypes). Let's refer to this as problem Y (stereotype threat).

Education about problem X would be counterproductive; the article is suggesting education about problem Y.

IMO modern web browser internals are more complex and less fun to work on than 1991-era Unix clones.

I'm not being defensive of this project, I'm being critical of the direction web architecture is going.

Uzbl isn't really written in one language. uzbl-core (the Webkit wrapper) is written in C, the event-processing framework and tabbed-browsing wrapper are written in Python, and much of the functionality is handled by external scripts written in sh and javascript.

The difference has nothing to do with the language; hbro is taking a very different approach to configuration and integration. (e.g. uzbl does IPC using FIFOs and sockets; hbro is using ZeroMQ. uzbl is extensible with external scripts; hbro seems to be extensible using Haskell.)

(I'm the maintainer of uzbl. k0ral used to be involved with uzbl, and I'm sure hbro has learned from uzbl's mistakes.)

> I mean, it's not like HTML layout engines or JS-interpreters are somehow impossible to write from scratch.

Today's web standards are large & complex enough that it is practically impossible without a full-time team.

I'm bothered that that blog doesn't distinguish between sites that (A) email generated passwords for new accounts and sites that (B) email plaintext passwords for existing accounts.

Without the villain the fragile egos here at HN might have actually read & responded to the post, instead of using it as another opportunity to argue about gender politics.

> Painting men as super villains in some grand 'Dan Brown'ian plot of conspiracy against women will NOT work.

Nobody believes this! There's no conspiracy at work. But there is is a long history of gender-based discrimination, and cultural practices that still reinforce suffocating gender roles today.

The ideas you complain about - "men are expected to be taking care of women, women should be trading up etc." - are part of that.

> the woman was acting like a bimbo

Classy.

> [...] play dumb, bat her eyelashes and flip her hair [...]

The fact that you frame it in such a stereotypical way speaks volumes about the attitudes at work here.

> That's not a call for single-sex education.

The author was not calling for single-sex education, he was calling for us to find & support ways of giving new people "a more comfortable entrance into our general community".

It's sad, but (relative) newness is a pretty big feature; it gets attention, and attention gets users.

The web has no attention span. You're either brand-new and hyped beyond realism, or ancient and boring.

Interesting. It looks similar to the vim plugin fugitive: http://www.vim.org/scripts/script.php?script_id=2975

> The other 10% can (assuming Wayland is successful) use Xorg...

That's not very convincing. Assuming Wayland is successful, Xorg may vanish; that certainly seems to be what a lot of people are hoping.

I get a scrollbar in that pane when it's too small to display all the labels. That makes it pretty obvious, it's strange that you don't have one.

That's why you hang out on IRC (or the mailing list or wherever) and ask if anyone's working on it before you start.

The difference between assembly and (for example) C is vast. The difference between JS and CS is much smaller.

Whether the difference in usability and maintainability is worth the extra layer of complexity is an important question.