Understand your Mac and iPhone more deeply by tracing the evolution of Mac OS X from prelease to Swift. John Siracusa delivers the details.
You've got two main options:
Goal: find a Linux alternative to FancyZones for Windows
Name | Recommended | Type | Supports main colum | Supports layouts | Multiple windows in same tile | Windows can span multiple zones | Notes |
---|---|---|---|---|---|---|---|
gSnap | 👍👍 | Gnome extension | yes | yes | yes | yes | Can be configured almost just like FancyZones; in the settings:
|
gTile | Gnome extension | no? | |||||
Tiling Assistant | 👍 | Gnome extension | yes | yes | yes | yes | Layout support is "experimental" and the UX is a bit unintuitive; after enabling layouts, you have to click the star icon beside a layout to mark it as a favourite before you can then hold Alt while dragging |
These examples all live in a default server block in your httpd.conf(5).
server "default" {
listen on * port 80
... # all the location blocks can together right here
}
We'll be using slowcgi(8) as the example, because with the -d
flag it helpfully spits out the FastCGI environment it got from httpd(8) and what it's planning to do with that.
I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.
I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.
Chrome 51 has some pretty wild behaviour related to console.log
in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.
In the last years I've been asked multiple times about the comparison between raylib and SDL libraries. Unfortunately, my experience with SDL was quite limited so I couldn't provide a good comparison. In the last two years I've learned about SDL and used it to teach at University so I feel that now I can provide a good comparison between both.
Hope it helps future users to better understand this two libraries internals and functionality.
:: Pick one of these two files (cmd or ps1) | |
:: Set directory for installation - Chocolatey does not lock | |
:: down the directory if not the default | |
SET INSTALLDIR=c:\ProgramData\chocoportable | |
setx ChocolateyInstall %INSTALLDIR% | |
:: All install options - offline, proxy, etc at | |
:: https://chocolatey.org/install | |
@powershell -NoProfile -ExecutionPolicy Bypass -Command "(iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))) >$null 2>&1" && SET PATH="%PATH%;%INSTALLDIR%\bin" |