Note
This gist has graduated to a proper repo: preactjs/preact-root-fragment
This is a standalone Preact 10+ implementation of the deprecated replaceNode parameter from Preact 10.
It provides a way to render or hydrate a Preact tree using a subset of the children within the parent element passed to render():
| # This file contains pin mappings and reasonable defaults for Prusa i3 MK3S | |
| # printers. It will work with MK3 (non-S) by selecting the alternative filament | |
| # sensor. References to common community mods are included as well. | |
| # | |
| [include mainsail.cfg] | |
| [skew_correction] | |
| [force_move] |
| /* | |
| Adapted from https://github.com/sindresorhus/github-markdown-css | |
| The MIT License (MIT) | |
| Copyright (c) Sindre Sorhus <sindresorhus@gmail.com> (sindresorhus.com) | |
| Permission is hereby granted, free of charge, to any person obtaining a copy | |
| of this software and associated documentation files (the "Software"), to deal | |
| in the Software without restriction, including without limitation the rights |
| import React, { useState, useEffect } from "react"; | |
| import ReactDOM from "react-dom"; | |
| import makeHookCompat from "./src"; | |
| // make a hook as usual | |
| function useMedia(query) { | |
| let [matches, setMatches] = useState(window.matchMedia(query).matches); | |
| useEffect(() => { | |
| let media = window.matchMedia(query); |
So, I was reading Why You shouldn’t use lodash anymore and use pure JavaScript instead, because once upon a time, I shifted from Underscore to Lodash, and I'm always on the lookout for the bestest JavaScript stdlib. At the same time, there was recently an interesting conversation on Twitter about how some of React's functionality can be easily implemented in modern vanilla JS. The code that came out of that was elegant and impressive, and so I have taken that as a message to ask if we really need the framework.
Unfortunately, it didn't start out well. After copy-pasting the ~100 lines of code that Lodash executes to perform a
find, there was then this shocking claim:
| class Frame extends Component { | |
| componentDidMount() { | |
| this.iframeHead = this.node.contentDocument.head | |
| this.iframeRoot = this.node.contentDocument.body | |
| this.forceUpdate() | |
| } | |
| render() { | |
| const { children, head, ...rest } = this.props | |
| return ( |
Traditionally virtual machines and containers are exposed on a bridge which is solely available behind a single IP address exposed behind network/port address translation (NAT/PAT). This is, in general an acceptable practice but leads to some configuration challenges when testing out technologies like network booting of hosts, firewalling, equal cost multipath, etc.
This configuration will allow a user to move the IP address of the host to an internal bridge
| /*Compile with: cc -lncurses pong.c -o pong | |
| Sources used: | |
| https://github.com/vicentebolea/Pong-curses | |
| */ | |
| #include <ncurses.h> | |
| #include <string.h> | |
| #include <time.h> |
| #!/bin/bash | |
| # Add an LVM cache pool on and attach it to the root volume | |
| # Including LUKS encryption | |
| # Assumes you are using an "all on root" setup | |
| # If you are not, adapt it if you like | |
| # | |
| # Script licensed GPL3 or later | |
| # © Adrian Wilkins May 2015 | |
| # Pass the name of the disk device you are using as a cache |
