This is the full version of the thread for opencart#1286, archived from notification emails.
The discussion has since been deleted almost entirely by OpenCart's developer.
Everyone who posted in it has also been blocked from the OpenCart repo.
sub crappy_async_lwp($host, $path) { | |
my $p = Promise.new; | |
my $v = $p.vow; | |
IO::Socket::Async.connect($host, 80).then(-> $sr { | |
if $sr.status == Kept { | |
my $socket = $sr.result; | |
$socket.send("GET $path\r\n\r\n").then(-> $wr { | |
if $wr.status == Broken { | |
$v.break($wr.cause); | |
$socket.close(); |
Sure, Github wins on the UI. Hands down. But, despite my initial annoyance with Gerrit when I first started using it almost a year ago, I am now a convert. Fully. Let me tell you why.
Note: This is an opinionated (on purpose) piece. I assume your preferences are like mine on certain ideas, such as:
- Fast-forward submits to the target branch are better than allowing merge commits to the target branch. The reason I personally prefer this is that, even if a non-conflicting merge to the target branch is possible, the fact that the review/pull request is not up to date with the latest on the target branch means feature branch test suite runs in the CI pipeline reporting on the review/PR may not be accurate. Another minor point is that forced merge commits are annoying as fuck (opinion) and clutter up Git log histories unnecessarily and I prefer clean histories.
- Atomic/related changes all in one commit is something worth striving for. Having your dev
This document is research for the selection of a communication platform for robot-net.
The purpose of this component is to enable rapid, reliable, and elegant communication between the various nodes of the network, including controllers, sensors, and actuators (robot drivers). It will act as the core of robot-net to create a standardized infrastructure for robot control.
Requirements:
Rich Hickey • 3 years ago
Sorry, I have to disagree with the entire premise here.
A wide variety of experiences might lead to well-roundedness, but not to greatness, nor even goodness. By constantly switching from one thing to another you are always reaching above your comfort zone, yes, but doing so by resetting your skill and knowledge level to zero.
Mastery comes from a combination of at least several of the following:
Enabling communication with API if server has Self-Signed Certificate |
- Vim is the descendant of vi, designed to be (mostly) backwards-compatible
- learning vi is useful when you need to edit a file over ssh, since vi is usually installed in any UNIX/UNIX-based system by default
- Vim’s shortcuts and design, once you learn them, help you search/create/edit/etc files quicker
- these shortcuts are also used in UNIX-based terminals, such as the man page viewer
- Vim offers flexible window management (splitting, etc) and works well with tmux, a popular terminal multiplexer
- Vim’s plugin ecosystem is thriving and full of useful tools for development in most (if not all) languages
- you can extend Vim yourself using Vimscript
;; modify ob-js to redirect to skewer if it is currently connected | |
;; this code can go in an emacs settings file | |
(require 'ob-js) | |
(require 'cl) | |
(advice-add 'org-babel-execute:js :around 'bill/org-babel-execute:skewer) | |
;;(advice-remove 'org-babel-execute:js #'bill/org-babel-execute:skewer) | |
(defun bill/org-babel-execute:skewer (oldFunc body params) | |
(if (skewer-ping) | |
(lexical-let* ((result-type (cdr (assoc :result-type params))) |