Re: [racket-users] Re: REPL output editor speed

2016-12-21 Thread Robby Findler
On Tue, Dec 20, 2016 at 1:58 PM, JCG  wrote:
> One thing that I have found is that an Ubuntu 16.04
> on a slighter slower iMac scrolls noticeably (feels 2x)
> faster than OSX on a faster iMac (Yes, I have multiple
> old iMacs).

Yes, I think that's a common experience, sadly. Last I heard, we
believe that the font drawing pipeline (i.e., actually drawing glyphs)
is slower on a mac than on linux. I think Matthew did some work to
improve things, but there is probably more that could be done. The
work might be inside cairo or inside the mac toolkit, tho.

Robby

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: [racket-users] Narrow radix of string->number.

2016-12-21 Thread Jos Koot
 
Or up to 60, 60 even nowadays being a commonly used radix in time notation.
Why restricting it to 36?
Jos

-Original Message-
From: racket-users@googlegroups.com [mailto:racket-users@googlegroups.com] On 
Behalf Of Dmitry Igrishin
Sent: miƩrcoles, 21 de diciembre de 2016 20:41
To: Racket Users
Subject: [racket-users] Narrow radix of string->number.

Hello,

Why the radix of string->number is narrowed to (2 16)? Shouldn't it be
(2 36)? There is a real need for it.

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[racket-users] Narrow radix of string->number.

2016-12-21 Thread Dmitry Igrishin
Hello,

Why the radix of string->number is narrowed to (2 16)? Shouldn't it be
(2 36)? There is a real need for it.

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [racket-users] Futures Mandelbrot Example

2016-12-21 Thread Robby Findler
Nothing has changed, but the future's implementation is currently
defeated by the errortrace annotation (via the "Debugging" option in
the "Show Details" part of the dialog you get after choosing the
"Language | Choose Language ..." menu item).

More generally, the section 19.1 applies to futures:
https://docs.racket-lang.org/guide/performance.html . If you try these
examples via `racket` on the command-line, you'll see the expected
results.

I've pushed a change to the docs to try to clarify this point.

Thanks,
Robby

On Wed, Dec 21, 2016 at 11:04 AM, 'Royall Spence' via Racket Users
 wrote:
> In the parallelism section of the guide 
> (https://docs.racket-lang.org/guide/parallelism.html), there's a Mandelbrot 
> set example demonstrating parallel computation with futures. I've tried it on 
> two different machines (with OSX and Linux) but I don't seem to get any 
> parallel computation. The futures visualizer shows very short "squares" of 
> work with a sync-and-switch to the other thread on both machines. This 
> pattern continues all the way to the end of computation. Both machines are 
> using DrRacket 6.7. The first example with the for/list iteration works as 
> described.
>
> Has something about futures changed since the example was written? Is the 
> problem in the example code or in Racket itself? I'd be happy to submit a PR 
> with a fixed example, but I don't understand what's happening well enough to 
> figure it out on my own.
>
> I tried to send this message with a screenshot of the futures visualizer a 
> few minutes ago, but it was immediately deleted.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[racket-users] Futures Mandelbrot Example

2016-12-21 Thread 'Royall Spence' via Racket Users
In the parallelism section of the guide 
(https://docs.racket-lang.org/guide/parallelism.html), there's a Mandelbrot set 
example demonstrating parallel computation with futures. I've tried it on two 
different machines (with OSX and Linux) but I don't seem to get any parallel 
computation. The futures visualizer shows very short "squares" of work with a 
sync-and-switch to the other thread on both machines. This pattern continues 
all the way to the end of computation. Both machines are using DrRacket 6.7. 
The first example with the for/list iteration works as described.

Has something about futures changed since the example was written? Is the 
problem in the example code or in Racket itself? I'd be happy to submit a PR 
with a fixed example, but I don't understand what's happening well enough to 
figure it out on my own.

I tried to send this message with a screenshot of the futures visualizer a few 
minutes ago, but it was immediately deleted.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.