TheGrassyKnoll's comments

On: New JFK assassination revelation could upend the l...

[TheGrassyKnoll]

Don't forget the OPM hack (2015)

https://en.wikipedia.org/wiki/Office_of_Personnel_Management...

On: The story in pictures of the Hughes H-4 Hercules, ...

[TheGrassyKnoll]

Hoover Dam 1931-1936 $49 million

Golden Gate Bridge 1933-1937 $35 million

Spruce Goose 1942-1947 $23 million

On: Gordon Moore has died

[TheGrassyKnoll]

https://en.wikipedia.org/wiki/Dick_Fosbury

On: Yellen says government will help SVB depositors bu...

[TheGrassyKnoll]

Mike Tyson, the epitome of sound fiscal management. ($300 million lifetime earnings, had to declare bankruptcy)

[Apocryphon → TheGrassyKnoll]

Sounds like he’s in the perfect position to know the fruits of such errors.

On: 🥺: the best sudo replacement

[TheGrassyKnoll]

I had to:

  $sudo apt-get install -y systemd-container

to get machinectl

On: Notes against note-taking systems

[TheGrassyKnoll]

I've got an 80,000 line text file full of notes (probably half blank lines). Would never work without the Emacs 'occur' command.

On: Ask HN: In what ways is programming more difficult...

[TheGrassyKnoll]

Turbo Pascal was a GREAT tool; it was like a breath of fresh air. It was 'fast' even on an 8086.

On: Why Rust strings seem hard

[TheGrassyKnoll]

COW == Copy on Write

  Its interesting that certain file systems use COW schemes:

  https://en.wikipedia.org/wiki/Btrfs

On: Why Rust strings seem hard

[TheGrassyKnoll]

Thanks for the code snippet, however (kind of a Rust newbie here)

  $ cargo install unicode_segmentation (chokes)

  $ cargo install unicode-segmentation (seems to work)

  and in Cargo.toml
  [dependencies]
  unicode-segmentation = "1.7.1" (seems to work)

  yet in the code, its:
  use unicode_segmentation::UnicodeSegmentation;

  Why couldn't they be consistent using a dash vs. an underscore ?

[estebank → TheGrassyKnoll]

Identifiers in Rust can't have dashes (rustc will never rely on whitespace for proper tokenization). It is arguable that because of that crates should not have dashes in their name. cargo was changed to automatically convert dashes to underscores for convenience because some dislike underscores in names. I personally think this is an unnecessary source of confusion and now I would make all tools (mainly cargo) treat them interchangeably.

[a1369209993 → estebank]

> rustc will never rely on whitespace for proper tokenization

Huh? That seems clearly untrue, eg `fnfoo` vs `fn foo` or `x && y` vs `x & &y` or `x<<shift_or_type > ::foo` vs `x < <shift_or_type>::foo`? Presumably for some or all of those, one version ends up being a error (eg bitwise and with a pointer from `x & &y` probably doesn't work), but that's not at the level of tokenization.

[ChrisSD → a1369209993]

Given the context, I think they simply mean that a-b is interpreted the same as a - b.

It can't be interpreted as a single identifier.

[steveklabnik → TheGrassyKnoll]

You don’t cargo install libraries; the cargo.toml line is the right thing.

You can’t use -s in Rust identifiers, so they need to be normalized to _ to be referred to in code.

[mvolfik → TheGrassyKnoll]

this is way too common in Python world too - packages (crates) use dashes (they look nicer?), but the packaged library is named with underscores, because `-` is math operation and can't be in a name

On: Ask HN: What to use instead of Bash / Sh for scrip...

[TheGrassyKnoll]

I tried using Python with import sh for awhile, but...meh.

  https://amoffat.github.io/sh/sections/faq.html