where's js.io?

[desmaj]

Hi Folks,

I gave someone the js.io link to use in a blog post, but it seems that
http://js.io/ now points to the world demo. That's not very helpful, I
don't think.

Is the informational site available at a different url?

Thanks,
Matthew

[Martin Hunt]

I'll put up a site today.  Michael (or anyone else), if you have time to write something about js.io for the new site, that would be great.

Also coming today: webkit and ie support are currently broken.  I have a patch to fix them both =) (well, IE6 may still crash a bit, not sure why).

Thanks,

Martin

[desmaj]

Hi Martin,

On Oct 23, 2:18 pm, Martin Hunt <mgh...@gmail.com> wrote:
> I'll put up a site today. Michael (or anyone else), if you have time to
> write something about js.io for the new site, that would be great.

Awesome! Thanks very much. Can you give a holler in #js.io when this
is ready?

Regards,
Matthew

[GWBasic]

I wouldn't get too hung up on IE6. It's loosing market share:
http://www.w3schools.com/browsers/browsers_stats.asp

The belief is that IE6 will be an insignificant minority in about a
year or so, thus spending a lot of time on IE6 for an application that
will be "mature" in a year could be a fruitless effort.

Besides, with ChromeFrame, for people who use IE6, you can stick up a
"This site requires ChromeFrame" just people used to do with Flash.
I'm doing it for certain pages that are just too difficult to get
working in IE, or are fundamentally incompatible.

On Oct 23, 11:18 am, Martin Hunt <mgh...@gmail.com> wrote:
> I'll put up a site today.  Michael (or anyone else), if you have time to
> write something about js.io for the new site, that would be great.
>
> Also coming today: webkit and ie support are currently broken.  I have a
> patch to fix them both =) (well, IE6 may still crash a bit, not sure why).
>
> Thanks,
> Martin
>

> On Fri, Oct 23, 2009 at 10:34 AM, desmaj <monkeylo...@gmail.com> wrote:
>
> > Hi Folks,
>
> > I gave someone the js.io link to use in a blog post, but it seems that

> >http://js.io/now points to the world demo. That's not very helpful, I

[Marcus Westin]

I'm with you - we're close to the point where it's not worthwhile (Wohooo!)0

The complication with IE6 is that many people who still use it do so because they have to, at work for example. IT departments with no incentive to upgrade machines are unlikely to do so. And it wouldn't surprise me if chrome frame will require admin to install on those computers as well.

Close, but not quite there :)