Nick-Gabe

 const pombify = (phrase) => {
   return phrase
     .split(' ')
     .map((word) => {
       const wordLetters = word.split('')
       return wordLetters
         .map((letter, index) => {
           const charCode = letter.charCodeAt(0);
           const binary = charCode
             .toString(2)

getify

Comparing: array method chaining, generator delegations, and transducing

I'm writing this quick post to respond to a recent twitter conversation where claims were made about the merits (or lack thereof) of transducers, as they relate to composing list comprehensions (map, filter).

For comparison sake throughout the rest of my post, below you'll find three (actually four!) implementations of a simple list operation demo:

• Array Method Chaining (jump to analysis)
  • Alternate: Array Method Composition (jump to analysis)
• Generator/Iterator Delegations (jump to analysis)
• Transducing (jump to analysis)

raphlinus

The not-too-clever programmer

This is a translation of grugbrain.dev into clear English. All props to the original author.

Introduction

This is a collection of thoughts on software development, originally written by an pseudonymous author styling themselves the "grug brain developer," but then translated into clear English by Raph Levien.

I am not an extremely smart developer, but I have many years of experience and have learned some things, although still don't know everything.

getify

In defense of blocks for local scopes (Part 1)

---

[EDIT: I've added a part 2 to this blog post, to address some of the feedback that has come up: https://gist.github.com/getify/706e5e10822a298375da40f9cc1fa295]

---

Recently, this article on "The JavaScript Block Statement" came out, and it received some good discussion in a reddit thread. But the general reaction seems to be against this approach. That saddens me.

sorki

# Module for configuring libvirt with static NixOS networking
# instead of using libvirt managed bridge.

{ config, lib, pkgs, ... }:
with lib;

let
  cfg = config.virtualisation.libvirtd.networking;
  v6Enabled = cfg.ipv6.network != null;
  v6PLen = toInt (elemAt (splitString "/" cfg.ipv6.network) 1);

Widdershin

In the olden days, HTML was prepared by the server, and JavaScript was little more than a garnish, considered by some to have a soapy taste.

After a fashion, it was decided that sometimes our HTML is best rendered by JavaScript, running in a user's browser. While some would decry this new-found intimacy, the age of interactivity had begun.

But all was not right in the world. Somewhere along the way, we had slipped. Our pages went uncrawled by Bing, time to first meaningful paint grew faster than npm, and it became clear: something must be done.

And so it was decided that the applications first forged for the browser would also run on the server. We would render our HTML using the same logic on the server and the browser, and reap the advantages of both worlds. In a confusing series of events a name for this approach was agreed upon: Server-side rendering. What could go wrong?

In dark rooms, in hushed tones, we speak of colours.

martinwoodward

```mermaid
sequenceDiagram
    participant dotcom
    participant iframe
    participant viewscreen
    dotcom->>iframe: loads html w/ iframe url
    iframe->>viewscreen: request template
    viewscreen->>iframe: html & javascript
 iframe->>dotcom: iframe ready

jmatsushita

###
### [2023-06-19] UPDATE: Just tried to use my instructions again on a fresh install and it failed in a number of places. 
###.   Not sure if I'll update this gist (though I realise it seems to still have some traffic), but here's a list of 
###.   things to watch out for:
###      - Check out the `nix-darwin` instructions, as they have changed.
###      - There's a home manager gotcha https://github.com/nix-community/home-manager/issues/4026
###

# I found some good resources but they seem to do a bit too much (maybe from a time when there were more bugs).
# So here's a minimal Gist which worked for me as an install on a new M1 Pro.

tomdaley92

Proxmox - SPICE client setup for MacOS

1. Install a working (and compiled) version of virt-viewer. You may view the homebrew package's upstream source on GitHub.

   brew tap jeffreywildman/homebrew-virt-manager
   brew install virt-viewer

2. Once that's installed should be able make a call remote-viewer with a pve-spice.vv file downloaded from proxmox web interface

bsless

#!/usr/bin/env bash

USERNAME="$1"
PASS="$2"

for f in  *.ovpn 
do    
        name=`basename -s .ovpn $f`;
        nmcli connection import type openvpn file $f
        nmcli connection modify "${name}" +vpn.data connection-type=password-tls