All that experiment proved is early 90s was not a right time for technology like Newton. Nothing more.

I'm sure someone very early in human civilization thought fire was unviable because you could only get it from lightning. Who's going to go out in a thunderstorm to secure a fire before the rain puts it out? It'll never catch on.

For people who want productivity software suits like Office from lighter computers, they have online versions of Office.

Like it. The only nuisance is the class attribute you have to repeat across all tags that you need to fill in.

On a side note, you can now change the class name to whatever you want (thanks Luke Holder via github).

this is fixed: https://github.com/rthprog/fixie/pull/18

What is the better alternative?

don't know. But the smart folk behind should be able to figure something out.

Just auto-filling all <p>'s and <h_>'s might be an interesting option. You could also have the API allow you to list tag names to be auto-filled. It can even be smart and first check whether the tag in question already contains text content, and if it doesn't, only then auto-fill it.

Nice suggestion. I made some modifications so this is the new behavior. Child elements are targeted, and content is never overwritten.

``` <div class="fixie"> <p></p> <p>Hello <a></a></p> </div> ``` The above will cause only the first `<p>` tag to be filled, and the `<a>` tag.

In addition, you can now use `fixie.init(["CSS-selector"]);` to target arbitrary tag names, class names, and ids. If the tag in question contains text content, it will not auto-fill it (though it will auto-fill children, if need be).

I considered doing that, but the problem is that I've noticed that some people use <p> tags as breaks between paragraphs. Requiring a class makes sure that the developer/designer knows where their filler content is going.

If you're going to require classnames anyway, it might be more flexible to use those to define the type of content to insert. Personally I'd prefer adding a simple bit of js to a page to define the fixie behaviour, something like :

  fixie.fill('.my_header_class','head');
  fixie.fill('#my_id','paragraphs');

etc, as otherwise I have to have a special layout with lots of 'fixie' everywhere and perhaps a special structure using certain tags in order to use the js, and can't define what sort of content goes where except by changing the type of html element which contains it.

I'd prefer to start with an html document which has already been made, and consider how to add fixie to it in the least obtrusive way - and how to remove it later when it was not required, without impacting the document structure or classes etc at all. So if I can add a bit of js which adds fixie in an unobtrusive way to any existing page, and then remove it by simply commenting out that js, that would be preferable to having to set up a special template just to use fixie, or having to consider fixie use from the start. Fixie should really IMHO adapt to the html it is used on, not force that html to be adapted to it.

As mentioned elsewhere, this is now implemented as `fixie.init(["CSS-selectors"]);`

yep, we added fixie.init(query); functionality. coming up soon.

Junk results, mostly, yes. That way they can complete more taks faster and still make money because most of the time their work is not manually approved.

Yes, sometimes it is a good thing that it is mentioned, though. I don't think it is a path that we want to go down again, slowly or quickly.

I think the Godwins law thing has worn itself out now. We can't develop a history blank hole because it becomes the party/war/leader who must not be mentioned. The law is a fight against argument ad hitlerum, not against talking about the nazis.

that's what screencasts are for - write code and annotate it with with a voiceover as you along. There is big enough niche between plain text code and screencasts.

when I am working on my own project I try to dig as deeper as as I feel like. If I am a working on a client project I try to dig only as deep as I need to (with limited success)

Was that surprising ?

Well the person who I replied to said he got no confirmation and the form just reloaded, so I told him that he should see a confirmation page and showed him what to expect. Did you not bother reading the comment I was replying to?

Had the AirBnB been able to hush the victim by offering her a juicy paycheck, it would have been a textbook example of crisis management. That the arrangement didn't work out and the lady chose to divulge the details of the deal gone sour, the co-founders are being labelled cold blooded for offering the deal in the first place. I think it's just plain bad luck that AirBnB could not come up with a compensation package good enough to muffle the victim.