jah

Savoir-Faire (https://ifdb.org/viewgame?id=p0cizeb3kiwzlm2p) is another incredible game of hers.

I'm a huge fan of the base16 color schemes - not for their appearance (though most look great), but for their ease of integration within the shell and vim. Just clone the repos below, drop a few lines in your shellrc/vimrc, then use a single bash command to change the scheme in both. No more mucking with Xresources.

https://github.com/chriskempson/base16-shell

https://github.com/chriskempson/base16-vim

This mapping is the new default in Neovim 0.6 (https://github.com/neovim/neovim/commit/5a111c1b02bbfbc2b42d...)

You're absolutely correct about RF noise. In the US, the FCC limits the power of all spurious emissions to be at least 43dB below the power of the fundamental frequency. Typically transmitters use a low pass filter (e.g. Buttersworth or Chebyshev) to reduce harmonic content.

Some micro transmitters (at the very low mW level) omit the LPF entirely. Looking at the datasheet for the ATtiny85, the maximum output current is 40mA and maximum output voltage is 5.5v which means this transmitter could theoretically produce an output of 220mW. PWM will reduce this obviously. The harmonics should be below this value, but they should probably add a filter. I've transmitting across the Atlantic Ocean at those power levels using a sub-optimal antenna and WSPR (https://en.wikipedia.org/wiki/WSPR_(amateur_radio_software)) encoding.

You can also use the Free Internet Chess Server (FICS) as a test bed for chess engines. The interface is telnet-based, so it's pretty easy to experiment with and learn. There's also "zippy" mode in xboard that allows you to connect your engine to FICS .

The commands below will login as a guest and display all of the computer accounts. Use the finger command to find info about an account.

  telnet freechess.org
  g <ENTER>
  who C<ENTER>
  finger ACCOUNT

Sadly, FICS has been dying a slow death for the past 10 years ... but there are plenty of idle CPU accounts waiting for an opponent.

Maybe it has to do with the start of solar cycle 25? Expect to see improving HF propagation over the next 3-5 years. It's an exciting time for radio nerds.

If you have one of the popular RTL-SDR's you may be able to pick up the HF bands by enabling the direct sampling mode (allows tuning between 500kHz - 28.8MHz).

https://www.rtl-sdr.com/rtl-sdr-blog-v-3-dongles-user-guide/

I ran into two problems when trying to switch to a Raspberry Pi 4 8GB as a desktop replacement in mid-2020:

- A noticeably laggy screen update when running urxvt. Any action which caused large amounts of text to scroll on the screen (e.g. a file listing or paging through a man page) would cause a bit of a visual stutter. I was running with with XFT fonts enabled, so maybe that was a contributing factor. Web page scrolling also seemed to lag a bit too if I recall correctly.

- Lack of gamma support for blue light filters such as redshift or f.lux

I'm crossing my fingers there are improvements to these areas in the future.

There's code in the Linux FTDI driver that correctly handles the bricked FTDI clones:

https://github.com/torvalds/linux/blob/master/drivers/usb/se...

I've been running urxvt with tmux in a tiling window manager for the last decade. What features from these new terminal emulators am I missing out on?

How many months until Github only renders in Edge?

Here's a video of the Mercury-Redstone 1 "launch": https://www.youtube.com/watch?v=7O4V7JfeTSU

Here's an interesting variation that uses RTL-SDR's: https://dopplerfish.com/passive-radar/

For those interested in the 6502, Ben Eater is starting a new YouTube series in which he builds a computer around a 6502 chip.

https://eater.net/6502

Sure, but they're probably only available by car.

One of my favorite quotes from Joe:

“Make it work, then make it beautiful, then if you really, really have to, make it fast. 90% of the time, if you make it beautiful, it will already be fast. So really, just make it beautiful!”

I feel that Erlang adoption is probably the most realistic growth path for most serious Elixir developers. All of these topics you mentioned (breakers, message routing, etc) have been discussed and developed in the Erlang community for years. The only new thing that Elixir brings to the table in these areas is abstraction and syntax - both of which are arguably not needed in large complex systems.

Source: full-time Erlang developer of 7 years who spent a full year coding Elixir in its v1.0.x days

That's an April Fool's Day prank. The King's Gambit has not been solved.

I built a system that scraped projections off http://apps.fantasyfootballanalytics.net/projections and joined them with weekly salary information from DraftKings. I then ran that data through a genetic algorithm that maximized projected fantasy points while keeping the team salary under the limit.

I entered about 10 matches ... and I lost every single match.

I don't know if my projection data was bad, my sample size too small, or if I was just unlucky. I gave up after a few weeks.

His story is featured on NPR's new Invisibilia podcast: http://www.npr.org/rss/podcast/podcast_detail.php?siteId=370...

Om and React are cool, but this comparison is disingenuous. The author should have compared the Om implementation to a native (JS) React implementation.

I recently converted a React project to Om and found it to be a very enjoyable exercise. However, contrary to most tweets/blog posts, my Om code ran slower than the JavaScript version, which ultimately caused me to abandon the conversion. Full disclosure, the port was a naive implementation of a single page React component which probably wasn't the best use-case for Om ( (om/transact! ...) was causing a full page re-render to the VDOM).

Om/cljs is very beautiful and concise compared to JS ... immutability rocks! If I could achieve performance comparable to JS I'd switch in a heartbeat.

Yes, it contains an implementation of maps ... although variable keys aren't yet supported.

Threaded page loading. Mosaic needed to download all text and graphics before displaying any part of a web page. This was painfully slow over modems. Netscape's huge innovation was to partially render pages while resources (mainly images) were downloading, giving the appearance of a faster web.