View mode: basic / threaded / horizontal-split · Log in · Help
December 10, 2012
dlang.org Library Reference
Is anyone else noticing e.g. std.datetime taking upwards of 30 seconds 
to render the blob of links at the top? It's freakin freezing my entire 
browser.
December 10, 2012
Re: dlang.org Library Reference
On 12/09/2012 08:10 PM, Ellery Newcomer wrote:
> Is anyone else noticing e.g. std.datetime taking upwards of 30 seconds
> to render the blob of links at the top? It's freakin freezing my entire
> browser.

Yeah, I see it.

Not browser stalling though, just annoying.

It renders without the links, freezes the page, turns white, adds the 
links and becomes visible.

The whole process only takes 5-7 seconds here.
December 10, 2012
Re: dlang.org Library Reference
On Sunday, December 09, 2012 18:10:42 Ellery Newcomer wrote:
> Is anyone else noticing e.g. std.datetime taking upwards of 30 seconds
> to render the blob of links at the top? It's freakin freezing my entire
> browser.

The link situation definitely needs to be fixed. People keep making noise abouet 
it, but nothing has yet actually made it into dmd or d-programming-
language.org to fix it. Also, std.datetime should be split up into sub-modules, 
but I don't want to do that until some form of DIPs 15 or 16 is implemented. 
That way, no code will break or be be forced to change as a result.

http://www.prowiki.org/wiki4d/wiki.cgi?LanguageDevel/DIPs/DIP15
http://www.prowiki.org/wiki4d/wiki.cgi?LanguageDevel/DIPs/DIP16

But until the link situation is fixed or std.datetime is split up, I'm not 
aware of anything that can really be done to fix the problem.

- Jonathan M Davis
December 10, 2012
Re: dlang.org Library Reference
10.12.2012 6:10, Ellery Newcomer пишет:
> Is anyone else noticing e.g. std.datetime taking upwards of 30 seconds
> to render the blob of links at the top? It's freakin freezing my entire
> browser.

Personally I disable JavaScript for dlang.org a long time ago and happy 
now. At least because the hyphenation is just terrible.

Also consider bootDoc generated Phobos documentation:
http://jakobovrum.github.com/bootdoc-phobos/

-- 
Денис В. Шеломовский
Denis V. Shelomovskij
December 10, 2012
Re: dlang.org Library Reference
On Monday, 10 December 2012 at 03:18:30 UTC, 1100110 wrote:
> On 12/09/2012 08:10 PM, Ellery Newcomer wrote:
>
> The whole process only takes 5-7 seconds here.

"Only" is not the right word to use here.
December 10, 2012
Re: dlang.org Library Reference
On Monday, 10 December 2012 at 02:10:43 UTC, Ellery Newcomer 
wrote:
> Is anyone else noticing e.g. std.datetime taking upwards of 30 
> seconds to render the blob of links at the top? It's freakin 
> freezing my entire browser.

ddox* on dlang.org, anyone?
http://vibed.org/temp/phobos/index.html

* https://github.com/rejectedsoftware/ddox
December 10, 2012
Re: dlang.org Library Reference
On Sun, 09 Dec 2012 18:10:42 -0800
Ellery Newcomer <ellery-newcomer@utulsa.edu> wrote:

> Is anyone else noticing e.g. std.datetime taking upwards of 30
> seconds to render the blob of links at the top? It's freakin freezing
> my entire browser.

It only takes about a second or two for me in FF2. I'm not seeing
any blob of links at the top though.
December 10, 2012
Re: dlang.org Library Reference
On Mon, Dec 10, 2012 at 12:34:13PM -0500, Nick Sabalausky wrote:
> On Sun, 09 Dec 2012 18:10:42 -0800
> Ellery Newcomer <ellery-newcomer@utulsa.edu> wrote:
> 
> > Is anyone else noticing e.g. std.datetime taking upwards of 30
> > seconds to render the blob of links at the top? It's freakin freezing
> > my entire browser.
> 
> It only takes about a second or two for me in FF2. I'm not seeing
> any blob of links at the top though.

'cos you're running with JS turned off. :-)

Also, I think the actual results depends on your system. If you have a
high-powered system you probably wouldn't notice too much lag. It "only"
takes about 3-4 seconds for me on a dual-core 3.4GHz Intel machine. But
older machines will probably see a bigger lag.

But anyway, I think all of this is kinda missing the point. The point is
that the blob of links at the top of the page is plain unhelpful. It is
only useful if you already know what you're looking for, in which case
you could just use your browser's search function to find the matching
text instead. Much more useful is a broken-down categorization (with
proper nesting, etc.) of the functions, classes, structs, etc., of the
module. Something like what std.algorithm does.


T

-- 
Perhaps the most widespread illusion is that if we were in power we
would behave very differently from those who now hold it---when, in
truth, in order to get power we would have to become very much like
them. -- Unknown
December 10, 2012
Re: dlang.org Library Reference
On Mon, 10 Dec 2012 09:45:06 -0800
"H. S. Teoh" <hsteoh@quickfur.ath.cx> wrote:

> On Mon, Dec 10, 2012 at 12:34:13PM -0500, Nick Sabalausky wrote:
> > On Sun, 09 Dec 2012 18:10:42 -0800
> > Ellery Newcomer <ellery-newcomer@utulsa.edu> wrote:
> > 
> > > Is anyone else noticing e.g. std.datetime taking upwards of 30
> > > seconds to render the blob of links at the top? It's freakin
> > > freezing my entire browser.
> > 
> > It only takes about a second or two for me in FF2. I'm not seeing
> > any blob of links at the top though.
> 
> 'cos you're running with JS turned off. :-)
> 

<g>

It makes the web 10x faster, 10x more practical and 10x less
obnoxious - it's the "Make the web instantly better" checkbox ;) It's
almost magical!

> Also, I think the actual results depends on your system. If you have a
> high-powered system you probably wouldn't notice too much lag. It
> "only" takes about 3-4 seconds for me on a dual-core 3.4GHz Intel
> machine. But older machines will probably see a bigger lag.
> 

Yea, at the same time though, if it takes a dual-core 3.4GHz (with
two levels of cache, out-of-order execution, pipelineing, branch
prediction, SIMD, external GPU, etc) 3-4 seconds to render a few pages
of formatted text, then something in computing has gone very, very
wrong.

> But anyway, I think all of this is kinda missing the point. The point
> is that the blob of links at the top of the page is plain unhelpful.
> It is only useful if you already know what you're looking for, in
> which case you could just use your browser's search function to find
> the matching text instead. Much more useful is a broken-down
> categorization (with proper nesting, etc.) of the functions, classes,
> structs, etc., of the module. Something like what std.algorithm does.
> 

Looking at it with JS on, yea, I see what you mean now. Not so nice,
not so helpful, and definitely not worth the rendering lag. The
new-style baked-in summaries on pages like std.algorithm are much, much
better.
December 10, 2012
Re: dlang.org Library Reference
On Mon, Dec 10, 2012 at 01:58:30PM -0500, Nick Sabalausky wrote:
> On Mon, 10 Dec 2012 09:45:06 -0800
> "H. S. Teoh" <hsteoh@quickfur.ath.cx> wrote:
> 
> > On Mon, Dec 10, 2012 at 12:34:13PM -0500, Nick Sabalausky wrote:
> > > On Sun, 09 Dec 2012 18:10:42 -0800
> > > Ellery Newcomer <ellery-newcomer@utulsa.edu> wrote:
> > > 
> > > > Is anyone else noticing e.g. std.datetime taking upwards of 30
> > > > seconds to render the blob of links at the top? It's freakin
> > > > freezing my entire browser.
> > > 
> > > It only takes about a second or two for me in FF2. I'm not seeing
> > > any blob of links at the top though.
> > 
> > 'cos you're running with JS turned off. :-)
> > 
> 
> <g>
> 
> It makes the web 10x faster, 10x more practical and 10x less
> obnoxious - it's the "Make the web instantly better" checkbox ;) It's
> almost magical!

Heh. I used to browse with no JS. But due to the annoying bandwagon
jumping trend that is a common pathology in people involved with
computers, more and more websites are starting to depend on JS and are
mostly (or completely) dysfunctional without JS. So I grudgingly turned
it back on.

Mind you, though, what with browser bloat and JS memory hogging plaguing
my browsing experience recently, I've tentatively switched back to no JS
by default, and enable only on a per-site basis (Opera is good for that
kinda thing). There have been websites that outright crash my browser or
soak up all available RAM and then some (causing the browser to be 99%
I/O bound and the pig which is X11 to essentially grind to a halt), and
then I ban JS for that site, and boom, it's instantly better. Just like
you said. :-P


> > Also, I think the actual results depends on your system. If you have
> > a high-powered system you probably wouldn't notice too much lag. It
> > "only" takes about 3-4 seconds for me on a dual-core 3.4GHz Intel
> > machine. But older machines will probably see a bigger lag.
> > 
> 
> Yea, at the same time though, if it takes a dual-core 3.4GHz (with
> two levels of cache, out-of-order execution, pipelineing, branch
> prediction, SIMD, external GPU, etc) 3-4 seconds to render a few pages
> of formatted text, then something in computing has gone very, very
> wrong.

I said the same thing when Java first came out, and the earlier JVMs
used to gobble up 2GB of RAM and 99% CPU upon startup, all just to
display a "hello world" message. :-)


> > But anyway, I think all of this is kinda missing the point. The
> > point is that the blob of links at the top of the page is plain
> > unhelpful.  It is only useful if you already know what you're
> > looking for, in which case you could just use your browser's search
> > function to find the matching text instead. Much more useful is a
> > broken-down categorization (with proper nesting, etc.) of the
> > functions, classes, structs, etc., of the module. Something like
> > what std.algorithm does.
> 
> Looking at it with JS on, yea, I see what you mean now. Not so nice,
> not so helpful, and definitely not worth the rendering lag. The
> new-style baked-in summaries on pages like std.algorithm are much,
> much better.

I would go so far as to propose that we get rid of those unhelpful link
blobs completely. They make the page slow to load, and for no real
benefit. Sounds like a lose-lose proposition to me. But I'd probably get
lynched for saying that. :-P


T

-- 
English has the lovely word "defenestrate", meaning "to execute by
throwing someone out a window", or more recently "to remove Windows from
a computer and replace it with something useful". :-) -- John Cowan
« First   ‹ Prev
1 2 3 4 5
Top | Discussion index | About this forum | D home