n3dst4

// we'll be playing with this happy little object in these examples
const foo = {
    bar: 1,
    baz: 2,
    corge: 3,
};

// 1. basic destructuring
{
    const { bar } = foo;

n3dst4

Ubuntu Linux EFI Grub Windows dual boot chaos

Situation: I had Ubuntu 18.10 successfully dual-booting with Windows 10. Tried to do_release_upgrade to 19.04 but it couldn't complete, probably because I had a million *-desktop packages installed and they'd trodden all over each other.

So I decided to install a fresh 19.04, using all defaults for everything. Install went smoothly but on reboot, there was no GRUB menu, just straight into Ubuntu.

After MUCH experimenting, it seems that the problem was that the default install was creating an "efi" partition which was effing it up somehow. The fix was to re-run the install, but instead of accepting the option to delete the previous Ubuntu and install over it, choose to "do something else", and manually the pick the partition to nuke and recreate. Do not create an efi partition.

It will piss and moan about not having an efi partition, but ignore it. It's fine, it will boot fine. Once you're up and running, pop a terminal and do:

n3dst4

// 1: how could you rewrite the following to make it shorter?
if (foo) {
  bar.doSomething(el);
} else {
  bar.doSomethingElse(el);
}

n3dst4

If you start getting shitty fucking error messages like

manpath: can't set the locale; make sure $LC_* and $LANG are correct

whenever you start up a WSL shell, your system locales are all fucked to insane buggery and you need to unfuck them pronto.

You can do this by running the official locale-unfucking command:

n3dst4

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsStore]
"RemoveWindowsStore"=dword:00000000

n3dst4

// What is the console output of this code?

function switchFoo (foo) {
  switch (foo) {
    case 1: 
      foo = 5
      console.log(foo)
    case 2: {
      console.log(foo)
      break

n3dst4

Deleting a tree of folders using rimraf can be pretty fraught on MS Windows; the OS itself can lock files randomly, and there may be various processes getting in the way, like virus checkers or cloud file syncing apps. rimraf itself will do an exponential-backoff-and-retry for EBUSY and ENOTEMPTY errors on Windows, but you can still see EPERM and others. If you want to do exponential-backoff-and-retry for any error, see the below recipe, using node-retry.

n3dst4

package main

import (
    "fmt"
    "math"
)

func Sqrt(x float64) (float64, int) {
    last := 0.0
    z := 1.0

n3dst4

#!/bin/bash

# set this to the problem folder
BASE=/c/Users/ndc/Dropbox/projects/delete-me

cd $BASE
for i in `find $BASE -depth`
do 
  DIR=`dirname $i`
  FILE=`basename $i`

n3dst4

Response.Cache.SetExpires(DateTime.UtcNow.AddDays(-1));
Response.Cache.SetValidUntilExpires(false);
Response.Cache.SetRevalidation(HttpCacheRevalidation.AllCaches);
Response.Cache.SetCacheability(HttpCacheability.NoCache);
Response.Cache.SetNoStore();