HN user

dcassett

213 karma

A fan of HN, in awe of the mind share that it provides

Posts18
Comments83
View on HN
news.ycombinator.com 7mo ago

How best to report website data breach?

dcassett
2pts0
blog.djhaskin.com 1y ago

Release Common Lisp on Your First Day (2023)

dcassett
1pts0
drewdevault.com 1y ago

The Free Software Foundation is dying (2023)

dcassett
6pts1
theconversation.com 2y ago

Einstein must be wrong: In search of the theory of gravity

dcassett
3pts0
www.arsouyes.org 4y ago

Digitize analog cassettes (VHS or 8mm) with Linux

dcassett
4pts0
blog.hubspot.com 5y ago

Unique Strategies for Reaching Inbox Zero

dcassett
1pts0
www.eejournal.com 5y ago

Updating the Centuries-Old on/Off Switch

dcassett
3pts0
www.tomshardware.com 5y ago

Intel to Outsource 'Atom and Xeon Based SoCs' to TSMC

dcassett
15pts3
seekingalpha.com 5y ago

Xilinx acquires Falcon Computing Solutions to expand developer community

dcassett
1pts0
www.scientificamerican.com 5y ago

Vision and Breathing May Be the Secrets to Surviving 2020

dcassett
4pts1
www.hpcwire.com 5y ago

Seagate Announces New Object Storage Software: Cortx

dcassett
2pts0
gigablast.com 5y ago

Cloudflare, Google, Bing Destroying the Infrastructure of the Free Web

dcassett
102pts43
www.youtube.com 6y ago

The Model Checking Paradigm [video]

dcassett
1pts1
www.wired.com 6y ago

A Startlingly Simple Theory About the Missing Malaysia Airlines Jet (2014)

dcassett
2pts0
pages.cs.wisc.edu 6y ago

Lambda Calculus Part 1 (2013)

dcassett
1pts0
news.ycombinator.com 7y ago

hbr1.com Radio on since 2003, now victim of ransomware

dcassett
5pts0
github.com 7y ago

Configuring and hardening Firefox privacy, security and anti-fingerprinting

dcassett
110pts22
www2.washjeff.edu 7y ago

Berwick's Problem of the Seven Sevens [pdf]

dcassett
1pts0

Perhaps because I'm still on Debian 12 (or more likely I did something wrong), I had trouble getting it working by compiling the icl/ocicl sources with sbcl. It complained "Failed to connect to Slynk after 10 seconds". I tried running a Slynk server in sbcl, but icl froze up, and the server said "slynk:close-connection: end of file on #<dynamic-extent STRING-INPUT-STREAM (unavailable) from "#A">. Then I tried running a swank server, and got the icl prompt (good), but then tab completion invoked the debugger: "Package SLYNK does not exist". Finally, I ran the swank server after first running "(asdf:load-system :slynk)" and everything seems to work.

One thing I immediately miss (that rlwrap provides) are the keyboard functions such as reverse-search-history (usually mapped to C-r) and history-search-backward (have this mapped to M-p). History recall only seems possible with the up arrow.

Also, be in for some surprises if you try to paste some lisp code into the REPL, especially if there are long lines. The interaction is apparently meant for a human typing, not pasting.

However, the 386 uses a different approach—CMOS switches—that avoids a large AND/OR gate.

Standard cell libraries often implement multiplexers using transmission gates (CMOS switches) with inverters to buffer the input and restore the signal drive. This implementation has the advantage of eliminating static hazards (glitches) in the output that can occur with conventional gates.

The form gives the option to identify as an individual, an organization, or anonymous, and below the selections gives this note: "Note: If you choose to identify as Anonymous, the option to enter your email address for submission confirmation is not available."

Have used VLC for at least 20 years. Recently I upgraded an old Dell 9400 laptop that dates from around 2006 to Debian Bookworm (the end of the line for the 32-bit machines). It has a nice 1600x1200 display, but the Nvidia Graphics (Geforce Go 7900 GS) is poorly supported and mpv now requires --hwdec=no, making 720p videos barely playable. VLC now uses a fraction of the CPU as mpv does for video, which makes even 1080p videos playable. For some reason VLC chokes at the beginning of every video (tries to play before everything is ready), but by pausing the video and backing up to time zero it plays perfectly. All of this to say that VLC has saved the day as it frequently has over the years.

I find that I like working with the directory stack and having a shortened version of the directory stack in the title bar, e.g. by modifying the stock Debian .bashrc

  # If this is an xterm set the title to the directory stack
  case "$TERM" in
  xterm*|rxvt*)
      if [ -x ~/bin/shorten-ds.pl ]; then
    PS1="\[\e]0;\$(dirs -v | ~/bin/shorten-ds.pl)\a\]$PS1"
      else
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h:   \w\a\]$PS1"
      fi
      ;;
  \*)
      ;;
  esac
The script shorten_ds.pl takes e.g.
  0  /var/log/apt
  1  ~/Downloads
  2  ~
and shortens it to:
  0:apt 1:Downloads 2:~

  #!/usr/bin/perl -w
  use strict;
  my @lines;
  while (<>) {
    chomp;
    s%^ (\d+)  %$1:%;
    s%:.*/([^/]+)$%:$1%;
    push @lines, $_
  }
  print join ' ', @lines;

That coupled with functions that take 'u 2' as shorthand for 'pushd +2' and 'o 2' for 'popd +2' make for easy manipulation of the directory stack:
  u() {
    if [[ $1 =~ ^[0-9]+$ ]]; then
      pushd "+$1"
    else
      pushd "$@"
    fi
  }

  o() {
    if [[ $1 =~ ^[0-9]+$ ]]; then
      popd "+$1"
    else
      popd "$@" # lazy way to cause an error
    fi
  }

Have an old Victoreen Geiger counter and have seen some interesting things: - Munich: Chernobyl (obvious high background radiation) - Arizona: Fukushima (noticeably higher background radiation)

Also, my wife had a test requiring an injection of a radioisotope and the meter was moving (many counts per second) when placed within several feet of her. So an EDC motive might be to monitor whether a colleague got such an injection and decided to come to the workplace.

That was at UT Austin, where Dr. Roth was a professor. Another thing about that course - the problems that were given by the TAs for the 90% proficiency checks seemed pretty challenging and weren't in the book. You really had to know your material, yet there were no big surprises.

I had such a self-paced course in the '70s based on the book "Fundamentals of Logic Design" by Charles Roth, Jr. It should be noted that the book was specifically written for self-paced study, and as such acted as a sort of tutor by carefully laying out a sequence of reading short segments, answering short questions about the material, then doing more involved problems. I found this course to be very effective and motivating for me, especially given the undergraduate class sizes.

Agreed, but prior to the change the "apparently random" as described in the documentation was similar to using random(fixed_seed), rather than the new behavior of random(system_time), which made the output of the script non-reproducible given the same inputs. The change to Perl's behavior was made for security reasons.

(Edited for clarity)

I saw this question only once, as the first of 4 problems on the final exam for my very first EE introductory course. The course had covered an infinite ladder of resistors, but at the time it seemed like quite a leap to apply that knowledge to this problem.

San Francisco specifically:

"I prompted ChatGPT to give me recommendations. Prompt: ... The final build will be located at my residence in San Francisco, CA, ..."

For non-fuzzy options:

I've found bash's history-search-backward and history-search-forward very useful. They complete commands that begin with what you have typed. I have them mapped to M-p and M-n.

I also find myself using bash's insert-last-argument command, which can be repeated to fill in the last argument of previous commands. I have it mapped to M-_.

Another feature I've been using is the dabbrev-expand function, which xterm (and some other terminals) have. This allows string matching on the terminal output including the scroll buffer. It's useful for forming a new command that uses previous arguments that are not last arguments, or that are outputs of previous commands. I have it mapped to M-/. I've tweaked the matching algorithm on my local xterm to allow tokens enclosed in quotes or braces (which programs often output) to be matched (xterm by default only considers non-whitespace).