Its guiding principles are

• Simplicity and readability
• Minimal: there ought to be one way to write something
• Striving for orthogonality
• Programs are about transforming data into other forms of data
  • Code is about expressing algorithms—not the type system
• There is embedded knowledge and wisdom in older programming languages
• The entire language specification should be possible to be memorized by a mere mortal

Its featre are features (in no particular order):

• Full UTF-8 Support
• Custom allocators that are simple to use:
  • Memory arenas/regions, pools, stacks, etc. which can be easily added
• Context system for allocations, logging, and thread data
• Built-in types and procedures that take advantage of the context system:
  • new(type), and make use the context’s allocator (unless explicitly given)
  • Dynamic arrays and hash maps ([dynamic]int and map[string]int)
• Array programming
  • a, b: [4]f32; c := a * b
  • i := a.x * b.y
  • v := swizzle(a, 1, 2, 0)
• Explicit procedure overloading
• Introspection on all types
• High control over memory layout
  • Alignment
  • Field offsets
  • Endianness
  • Data sizes
• Endian specific integer types (useful for specific data formats)
  • u32le
  • u64be
• Decent package system and file handling
• No bad preprocessor
• Type inference
  • x: int = 1
  • x := 1 // x is deduced to be an int
• using
  • making everything a namespace (similar to Pascal’s with but on steroids)
  • Ability to have subtype polymorphism
• Multiple return values
• Clean, consistent, and fast to parse syntax
• No need for procedure prototypes
• defer statements
  • defer a statement until the end of scope (akin to D’s scope(exit))
• Nested procedures and types
• Tagged unions and untagged unions
• Ranged for loops
• Labelled branches
  • break label_name
• break by default in switch statements
  • Explicit fallthrough
• “Raw” strings
  • x := `what "the" string?`
• cstring for legacy use
• Parametric polymorphism (“generics”)
• Foreign system
• Compile time when statements
• Bounds checking which is togglable at the statement level:
  • #no_bounds_check #bounds_check
• i128 and u128 support

And lots more!

Camminare per dimagrire: 9 segreti per bruciare davvero i grassi

Camminare è il miglior modo per dimagrire, ma occorre rispettare alcune regole: 9 consigli per bruciare davvero i grassi senza soffrire.

After almost 2 years of using Telegram, I finally discovered that it is possible to enter emoji using its name after “:” character. Unfortunately I couldn’t find any complete list of available emojis anywhere, so I had to dig deep into the Telegram desktop source code to generate it. It was far more complicated than

…

Code changes and relevant files are available in this repo: https://github.com/k3a/telegram-emoji-list.

Source: Telegram emoji list with codes and descriptions – K3A

Ora la parte noiosa. Spesso mi collego (con ssh, ça va san dire) alle mie macchine di casa da remoto dove è già attiva una sessione “desktop” che oggigiorno è Wayland. Così qualsiasi programma Gnome o che usa le librerie Gtk – cioè moltissimi – verrà visualizzato sul desktop Wayland e non sul dektop remoto.

“waypipe ssh $HOST” funziona a meraviglia, ma l’aggiunta di queste righe al vostro .bashrc è utile quando non state usando una sessione Wayland (cioè Windows):

if [ -n "$SSH_CLIENT" ]; then
  if [ -n "$WAYLAND_DISPLAY" ]; then
    echo "Remote session with waypipe, everything will be OK" 
  else 
    echo "Remote session, forcing GTK to X11"
    export GDK_BACKEND=x11
  fi
fi

Now the boring part. If you log into a machine where a Wayland session is already active – I often log into my home machines remotely – any Gtk program will show on the Wayland desktop. So you use “waypipe ssh $HOST” which is cool and works like a breeze but adding those lines to your .bashrc helps when you are not using a wayland session (i.e. Windows):

if [ -n "$SSH_CLIENT" ]; then
  if [ -n "$WAYLAND_DISPLAY" ]; then
    echo "Remote session with waypipe, everything will be OK" 
  else 
    echo "Remote session, forcing GTK to X11"
    export GDK_BACKEND=x11
  fi
fi

You can use wget to download all PDFs from a webpage by using:

wget -r -l1 -H -t1 -nd -N -np -A.pdf -erobots=off --wait=2 --random-wait --limit-rate=20k [URL]

• -r: Recursive download.
• -l1: Only one level deep (i.e., only files directly linked from this page).
• -H: Span hosts (follow links to other hosts).
• -t1: Number of retries is 1.
• -nd: Don’t create a directory structure, just download all the files into the current directory.
• -N: Turn on timestamping.
• -np: Do not follow links to parent directories.
• -A.pdf: Accept only files that end with .pdf.
• -erobots=off: Ignore the robots.txt file (use carefully, respecting site’s terms and conditions).
• –wait=2: Wait 2 seconds between each retrieval.
• –random-wait: Wait from 0.5 to 1.5 * –wait seconds between retrievals.
• –limit-rate=20k: Limit the download rate to 20 kilobytes per second.

This parameters will avoid the “429: Too Many Requests” error.

convert -density 150 -quality 60 -compress jpeg Test.pdf Test-150-060-jpeg.pdf

Source: imagemagick reduce size of pdf – Stack Overflow

Well, after reading How to add a directory to your PATH written by Julia Evans I know that it is not as simple as it seems!

How to Share Virtual Extended Screen in Ubuntu 22.04 | 24.04