[NTLK] Navigating the web with the newton

Abraham Limpo abraham at familialimpo.net
Thu Dec 21 20:22:04 EST 2017

My plan to get the newton read https pages consists on adapting this
project https://github.com/tghw/macproxy and strip any modern convenience
that newton browsers don't need.

The plan is make the zero do the grunt work while leaving the newton only
the task of rendering the final product.

Unfortunately this is a weekend-to-weekend project and with holydays
approaching I don't think I will be able to do anything soon (I still have
to solder about 10 atari punk synths that will be the stocking stuffers of
my nephews).

So probably there will be at least a month until I can post a significant
update. And I don't know if something like this will be useful only for me.
But I think having a pi as a sort of coprocessor to the newton may open new
avenues to keep our green machines useful in the connected world.

2017-12-16 23:59 GMT+01:00 Grant Hutchinson <grant at splorp.com>:

> On 2017-12-14, at 6:03 PM, B Dudney wrote:
> > I’m no expert, but I think our dear Newts have exceedingly too little RAM
> > to handle current web pages, not least full of endless scripts! Not to
> mention
> > all sorts of conventions adopted since its browsers were written.
> Any properly coded web page *should* be viewable with JavaScript, plugins,
> CSS, or other enhancements turned off or blocked. Of course, this isn't
> always the case, but Newton web browsers are actually pretty good at
> ignoring all the cruft that they can't understand. If the content of a site
> can't be viewed without JavaScript, that speaks to the laziness of the the
> company and its developers.
> As I mentioned previously, the real issue is not being able to access
> HTTPS pages at all.
> g.
> ----------------------------------------------------------------------
> http://newtontalk.net/
> http://twitter.com/newtontalk

More information about the NewtonTalk mailing list