b_van_b

joined 2 years ago
[–] b_van_b 41 points 1 week ago (3 children)
  1. You need to use the latest tech to stay relevant
  2. Aim for maximum theoretical purity or pattern adherence
  3. You must adhere to Uncle Bob's clean code rules at all times
  4. 100% code coverage is something that matters
  5. You should always optimize for performance
  6. You should always optimize for web scale
  7. AI is about to replace all programmers
[–] b_van_b 2 points 2 months ago* (last edited 2 months ago) (1 children)

I haven't used it, but from the documentation, it looks like you should do this:

type("a", Key.CTRL + Key.SHIFT)

https://sikulix-2014.readthedocs.io/en/latest/keys.html#key-modifiers-modifier-keys

[–] b_van_b 5 points 2 months ago* (last edited 2 months ago)

Many examples are listed on Wikipedia: https://en.m.wikipedia.org/wiki/Alphabetical_order#Language-specific_conventions

For French, the last accent in a given word determines the order.[14] For example, in French, the following four words would be sorted this way: cote < côte < coté < côté. The letter e is ordered as e é è ê ë (œ considered as oe), same thing for o as ô ö.

[–] b_van_b 3 points 2 months ago

Looks like a positive outcome overall.

[–] b_van_b 20 points 3 months ago* (last edited 3 months ago)

Additionally, PopOS and Garuda were polled, but didn't appear in the final list. Based on the spreadsheet provided, PopOS should be #16 and Garuda should be #24.

Place Distro Average Score Has been Tried
1 SteamOS 4.19 27%
2 Fedora 4.18 65%
3 Arch Linux 4.04 60%
4 Bazzite 4.04 15%
5 Linux Mint 4.03 73%
6 Endeavour OS 3.92 31%
7 CachyOS 3.87 11%
8 Asahi Linux 3.84 7%
9 Fedora Silverblue 3.77 18%
10 Nobara 3.73 22%
11 Alpine 3.71 19%
12 OpenSUSETumbleweed 3.67 29%
13 Debian Stable 3.63 63%
14 Debian Testing 3.63 23%
15 NixOS 3.52 23%
16 PopOS 3.41 49%
17 Tuxedo OS 3.36 10%
18 Gentoo 3.26 16%
19 Ubuntu 3.23 88%
20 MX Linux 3.14 16%
21 Linux lite 3.13 9%
22 Puppy Linux 3.13 16%
23 OpenSUSE Leap 3.11 19%
24 Garuda Linux 3.09 18%
25 Slackware 3.00 10%
26 Peppermint 2.99 9%
27 ZorinOS 2.94 29%
28 Vanilla OS 2.93 13%
29 KDE Neon 2.85 30%
30 Rhino Linux 2.83 4%
31 Mageia 2.81 4%
32 Solus 2.74 9%
33 elementary OS 2.71 28%
34 Manjaro 2.64 53%
35 Chrome OS Flex 2.03 21%
36 Deepin 1.97 15%
[–] b_van_b 4 points 3 months ago (1 children)

How did you calculate $1200 from this?

[–] b_van_b 6 points 8 months ago
[–] b_van_b 10 points 8 months ago

I only know about the developers of Slay the Spire switching to Godot. Not the biggest name, but still well-known.

https://www.pcgamer.com/games/card-games/slay-the-spire-2-ditched-unity-for-open-source-engine-godot-after-2-years-of-development/

[–] b_van_b 4 points 8 months ago

I assume that left joystick up/down is axis 1, correct?

[–] b_van_b 4 points 10 months ago (2 children)

What would you suggest as an alternative?

 

I'm going through the interactive version of The Book, and I'm confused by the results of an exercise in Ch 4.3 - Fixing Ownership Errors.

The following code does not work, and they say it's because it would result in the same heap space being deallocated twice:

fn main() {
    let s = String::from("Hello world");
    let s_ref = &s; // reference s
    let s2 = *s_ref; // dereference s_ref
    println!("{s2}");
}

But in my mind, this should be equivalent to the following compilable code, which transfers ownership of s to s2 :

fn main() {
    let s = String::from("Hello world");
    let s_ref = &s; // reference s
    let s2 = s; // move s directly
    println!("{s2}");
}

If s_ref is a reference to s, then dereferencing s_ref should return the String s, shouldn't it? Why can't s be moved to s2 with either the above code or let s2 = *&s;, which fails in the same way?

view more: next ›