
@mario.luis.guimaraes has joined the channel

If/when I return to VIM?! :slightly_smiling_face: I’ve never left, despite numerous attempts to get used to very many IDEs. I have never found anything that works for me like VIM does.


@samth Although I did happen to see that yesterday thanks for pointing it out. Both that and the Racket 7.2 announce seemed to be on HN front page for awhile yesterday. :racket-flat:

that HN post led me to all your other racket posts, @greg, which have been very helpful. thanks!

Happy to hear that — thanks for letting me know!

I’m considering Racket and Julia for desktop app and today someone in Julia channel told me he was also considering Racket but abandoned idea after hearing from some Racket dev (who is also familiar with Julia) that it is never going to be fast as Julia. does such statement hold?

@sjaniska no, I don’t think that statement holds

also I wonder who said that

@samth no matter whether we speak about Racket or Racket CS…don’t know about Racket-source

Julia and Racket are both complicated systems where performance is concerned, so some things will be faster for each

certainly there are some programs where Julia is currently faster than Racket

here is the exact quote: “I just talked at some point with some of the core devs, and they told me that racket may never be julia fast (some of them actually know julia quite well)”

I like that Racket has GUI support out of the box, while in Julia I’d probably have to use Gtk.jl since I do not like Electron and similar web/JS stuff…

> If runtime?-id is provided, then it is bound in the context of expr to #f for the compile-time instance of expr and #t for the run-time instance of expr.
What does this even mean?

(it’s from define-runtime-path
)

If you write (define-runtime-path x e id)
then at compile time e
is evaluated with id
bound to #f
, and at runtime e
is evaluated with id
bound to #t

I don’t see it being used in racket-source with that variant… when/why would you want that?

I’m poking at this because I broke up a compound define-runtime-path into 2 of them, with the latter using the former… and that blew up. I was trying to figure out the runtime vs compile time stuff and that language is… confusing

@sjaniska looking at these benchmarks I don’t see much differences between Julia and Racket - both have their strengths when it comes to performance, but I don’t think performance wise there is much to win/lose: https://benchmarksgame-team.pages.debian.net/benchmarksgame/which-programs-are-fast.html

@githree indeed. i forgot to check that language-shootout, although usually the code is not really idiomatic :slightly_smiling_face:

@sjaniska depending on what that person means by “core devs” I don’t think any of us know Julia “quite well”, but I also don’t think any of us would say that

@zenspider that form is used in several places in the core — the openssl collection and the db collection

@samth i just forwarded the info i got without any further details and want(ed) to clear the possible doubt that Racket is generally inferior to Julia when it comes to performance…btw, the person who conveyed that info also said “Racket is pretty amazing, but I stopped looking into it after I figured, that it can’t really be made fast language…”

Racket is unlikely to be as fast as C++, for example. However, I think “can’t be made fast” is false

i don’t expect C(++) performance…

Racket is quite faster than most dynamically-typed languages

@mflatt The pre-release page that I see from that URL is Racket Pre-Release 7.1.0.900 .

7.1.0.900 [3m] successfully launches. Requests permission to run.

I don’t know if it runs only because the other one’s code signature was accepted. Not sure how code signing works.

It’s a different certificate, so that’s promising. Maybe the new certificate on v7.2 will work for others who had trouble before. 7.1.0.900 was the pre-release number for 7.2, and 7.2 is now out.

noob question: is racket compiled?

the main racket implementation has an ahead-of-time compiler to bytecode, and then a JIT compiler when functions are first executed

you can also run Racket built on top of Chez Scheme, which is ahead-of-time compiled