16 Dec
2011
16 Dec
'11
10:54 p.m.
On 16 December 2011 17:48, Timothy Pearson <kb9vqf(a)pearsoncomputing.net>wrote;wrote:
<snip>
Just a reminder to keep it civil here folks. Personally I try to provide
both a JS and non-JS version of any given feature--while people may no
longer have K6 CPUs not everyone has an Android/iPhone either. Providing
a non-JS version allows people with midgrade phones to still use all the
features of the website.
Again, I am not suggesting implementing a giant javascript hell. I am
suggesting a small and simple piece of JavaScript to enable community
interaction via a comment system.
Regarding stability, in theory javascript should be OK. In practice the
All I'm saying here is don't be an ass
wipe with redesigning the web
site.
:)
Contributions appreciated, as the old arch saying goes "patches are
welcome!" or "put up or shut up" applies as well.
Calvin Morrison
JS engine built into a given browser can leak memory
quite badly--for me
this manifests as having to regularly restart Firefox, which gets to be
quite a nuiscance over time. TDE might end up (randomly) being the site
that pushes the user's system over a memory limit, and nothing says
"professional" like a site appearing to crash the users' browser.
Firefox has long lost any control over it's ability to manage memory. As of
the latest builds, it can no longer be compiled on a 32bit system because
the linker uses 3gb+ of memory.
:)