I bought M1 MacBook Air. It is the fastest computer I have, and I have been a GNOME/GNU/Linux user for long time. It is obvious conclusion that I need practical Linux desktop environment on Apple Silicon.
Fortunately, Linux already works on Apple Silicon/M1. But how practical is it?
Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.
Wayland proponents make it seem like Wayland is "the successor" of Xorg, when in fact it is not. It is merely an incompatible alternative, and not even one that has (nor wants to have) feature parity (missing features). And unlike X11 (the X Window System), Wayland protocol designers actively avoid the concept of "windows" (making up incompr
| { | |
| "name": "tsquickstart", | |
| "version": "1.0.0", | |
| "description": "Boilerplate for quick one-off TypeScript projects. Just run `npm start`", | |
| "scripts": { | |
| "init": "test -f tsconfig.json || (tsc --init -t ESNext -m ESNext && npm install)", | |
| "start": "npm run init && concurrently \"npm run watch\" \"npm run serve\"", | |
| "serve": "http-server", | |
| "watch": "tsc -p . --watch", | |
| "build": "tsc -p ." |
| const colorGroups = [ | |
| // PINK | |
| "#FFC0CB", | |
| "#FFB6C1", | |
| "#FF69B4", | |
| "#FF1493", | |
| "#DB7093", | |
| "#C71585", | |
| // PURPLE | |
| "#E6E6FA", |
| read -r -p "Would you really like to reset your development database and pull the latest from production? [y/N] " response | |
| if [[ "$response" =~ ^([yY][eE][sS]|[yY])$ ]]; then | |
| wp @development db reset --yes && | |
| wp @production db export - > sql-dump-production.sql && | |
| wp @development db import sql-dump-production.sql && | |
| wp @development search-replace https://example.com https://example.dev | |
| fi |
$ uname -r
| ### | |
| ### | |
| ### UPDATE: For Win 11, I recommend using this tool in place of this script: | |
| ### https://christitus.com/windows-tool/ | |
| ### https://github.com/ChrisTitusTech/winutil | |
| ### https://www.youtube.com/watch?v=6UQZ5oQg8XA | |
| ### iwr -useb https://christitus.com/win | iex | |
| ### | |
| ### |
Use a git hook to match a Jira issue ID from the current branch, and prepend it to every commit message
Assuming the current branch contains a Jira issue ID, you can use a git hook script to prepend it to every commit message.
Create an empty commit-msg git hook file, and make it executable. From your project's root directory:
install -b -m 755 /dev/null .git/hooks/commit-msg
Save the following script to the newly-created .git/hooks/commit-msg file:
| /** | |
| * es6-weakmap.js | |
| * WeakMap (ECMA-262 6th Edition / ECMAScript 2015) | |
| * | |
| * | |
| * @version 0.9.2 | |
| * @author think49 | |
| * @url https://gist.github.com/think49/283b7374e352e09fc131 | |
| * @license http://www.opensource.org/licenses/mit-license.php (The MIT License) | |
| * @see <a href="http://www.ecma-international.org/ecma-262/6.0/#sec-weakmap-constructor">23.3.1 The WeakMap Constructor – ECMA-262 6th Edition</a> |
| openInNewTab = function(url) { | |
| var popupBlockerChecker = { | |
| check: function(popup_window){ | |
| var _scope = this; | |
| if (popup_window) { | |
| if(/chrome/.test(navigator.userAgent.toLowerCase())){ | |
| setTimeout(function () { | |
| _scope._is_popup_blocked(_scope, popup_window); | |
| },200); | |
| }else{ |