GitMurf

/*
****************************************************************************************
****************************************************************************************
****************************************************************************************

NOW HOSTING CODE VIA MY MAIN GITHUB REPOSITORY FOR ROAM SO THAT USERS CAN LINK DIRECTLY TO THE CODE AND AUTO UPDATE

GO HERE FOR INSTALLATION INSTRUCTIONS: https://github.com/GitMurf/roam-javascript#installation

****************************************************************************************

GitMurf

document.addEventListener('click', function (evt) {
    if (evt.target.className === 'bp3-icon bp3-icon-filter') {
        function sleep(ms) {
            return new Promise(resolve => setTimeout(resolve, ms));
        }

        async function removeFilters(event) {
            var filteredButtons = event.target.parentElement.parentElement.parentElement.getElementsByTagName('BUTTON')

            if (filteredButtons.length == 0 || filteredButtons == null) { return }

mandarg

/* sidenotes.js: standalone JS library for parsing HTML documents with Pandoc-style footnotes and dynamically repositioning them into the left/right margins, when browser windows are wide enough.
Sidenotes are superior to footnotes where possible because they enable the reader to immediately look at them without requiring user action to 'go to' or 'pop up' the footnotes; even floating footnotes require effort by the reader.
sidenotes.js is inspired by the Tufte-CSS sidenotes (https://edwardtufte.github.io/tufte-css/#sidenotes), but where Tufte-CSS uses static footnotes inlined into the body of the page (requiring modifications to Pandoc's compilation), which doesn't always work well for particularly long or frequent sidenotes, sidenotes.js will rearrange sidenotes to fit as best as possible, and will respond to window changes.
Particularly long sidenotes are also partially 'collapsed'.

Author: Said Achmiz
2019-03-11
license: MIT (derivative of footnotes.js, which is PD)
*/

swyxio

Full Livestream Recording here

(see YouTube channel for individual videos)

Github | Site | Discord | YouTube |

calebporzio

details summary {
  cursor: pointer;
  outline: none !important;
  display: inline-block;
  padding: 8px 12px;
  padding-top: 10px;
  border-radius: 4px;
  overflow: hidden;
  background: #F09825;
  color: white;

dotcomputercraft

the best way (I've found) to completely uninstall node + npm is to do the following:

go to /usr/local/lib and delete any node and node_modules
go to /usr/local/include and delete any node and node_modules directory
if you installed with brew install node, then run brew uninstall node in your terminal
check your Home directory for any local or lib or include folders, and delete any node or node_modules from there
go to /usr/local/bin and delete any node executable
You may need to do the additional instructions as well:

sudo rm /usr/local/bin/npm

tonymtz

# first:
lsbom -f -l -s -pf /var/db/receipts/org.nodejs.pkg.bom | while read f; do  sudo rm /usr/local/${f}; done
sudo rm -rf /usr/local/lib/node /usr/local/lib/node_modules /var/db/receipts/org.nodejs.*

# To recap, the best way (I've found) to completely uninstall node + npm is to do the following:

# go to /usr/local/lib and delete any node and node_modules
cd /usr/local/lib
sudo rm -rf node*

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

micahgodbolt

$foo: 1;
$bar: 6;

@while $foo < $bar {
    h#{$foo} { // do something
        font-size: ($bar - $foo)+em;
    }
    $foo: $foo + 1; // advance a counter
}

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style