<commit_before>#lang scribble/base

@(require "shared.rkt")

@; -----------------------------------------------------------------------------
@(define (rurl x) (format "http://docs.racket-lang.org/reference/index.html?q=racket/~a" x))
@(define (rkt) @hyperlink[(rurl "")]{racket})
@(define (rkt/base) @hyperlink[(rurl "base")]{racket/base})
@(define (rkt/gui) @hyperlink[(rurl "gui")]{racket/gui})

@title{Some Performance Hints}

When you write a module, you first pick a language. In Racket you can
 choose a lot of languages. The most important choice concerns @rkt/base[]
 vs @rkt[].

If you are writing a script, try to use @rkt/base[]. The @rkt/base[]
 language loads significantly faster than the @rkt[] language because it is
 significantly smaller than the @rkt[].

If your module is intended as a library, stick to @rkt/base[]. That way
 script writers can use it without incurring the overhead of loading all of
 @rkt[] unknowingly.

Conversely, you should use @rkt[] (or even @rkt/gui[]) when you just want a
 convenient language to write some program. The @rkt[] language comes with
 almost all the batteries, and @rkt/gui[] adds the rest of the GUI base.


<commit_msg>[Style] use `racketmodname' to link to a language name<commit_after>#lang scribble/base

@(require "shared.rkt")

@; -----------------------------------------------------------------------------
@(define (rkt) @racketmodname[racket])
@(define (rkt/base) @racketmodname[racket/base])
@(define (rkt/gui) @racketmodname[racket/gui])

@title{Some Performance Hints}

When you write a module, you first pick a language. In Racket you can
 choose a lot of languages. The most important choice concerns @rkt/base[]
 vs @rkt[].

If you are writing a script, try to use @rkt/base[]. The @rkt/base[]
 language loads significantly faster than the @rkt[] language because it is
 significantly smaller than the @rkt[].

If your module is intended as a library, stick to @rkt/base[]. That way
 script writers can use it without incurring the overhead of loading all of
 @rkt[] unknowingly.

Conversely, you should use @rkt[] (or even @rkt/gui[]) when you just want a
 convenient language to write some program. The @rkt[] language comes with
 almost all the batteries, and @rkt/gui[] adds the rest of the GUI base.



{'fraction_non_alphanumeric': 0.17585301837270342, 'fraction_numerical': 0.0, 'mean_word_length': 3.2908067542213884, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4906172', 'n_tokens_mistral': 687, 'n_tokens_neox': 671, 'n_words': 289}