mattfysh

input:
  sequence:
    inputs:
      - generate:
          count: 1
        processors:
          - http:
              verb: GET
              url: ${! env("CONSUL_ENDPOINT") }/v1/kv/${! env("CONSUL_KV_KEY") }
              headers:

choult

input:
  broker:
    copies: 1
    inputs:
      - http_client:
          url: "https://mas.to/api/v1/streaming/public"
          stream:
            enabled: true
            reconnect: true
            codec: "delim:\n\n"

choult

input:
  broker:
    copies: 1
    inputs:
      - http_client:
          url: "https://mas.to/api/v1/streaming/public"
          stream:
            enabled: true
            reconnect: true
            codec: lines

graninas

At the beginning of 2030, I found this essay in my archives. From what I know today, I think it was very insightful at the moment of writing. And I feel it should be published because it can teach us, Rust developers, how to prevent that sad story from happening again.

---

What killed Haskell, could kill Rust, too

What killed Haskell, could kill Rust, too. Why would I even mention Haskell in this context? Well, Haskell and Rust are deeply related. Not because Rust is Haskell without HKTs. (Some of you know what that means, and the rest of you will wonder for a very long time). Much of the style of Rust is similar in many ways to the style of Haskell. In some sense Rust is a reincarnation of Haskell, with a little bit of C-ish like syntax, a very small amount.

Is Haskell dead?

stettix

Things I believe

This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.

Agree? Disagree? Feel free to let me know at @JanStette. See also my blog at www.janvsmachine.net.

Fundamentals

Keep it simple, stupid. You ain't gonna need it.

alecholmez

Incremental xDS Implementation Plan

• Authors: Alec Holmes
• Reviewers: (names here)
• Status: Planning

Contents

• Go Control Plane
  • Introduction
  • Motivation

mkolod

#include <iostream>
#include <iomanip>

#include <dlfcn.h>

using std::cout;
using std::cerr;
using std::endl;

void* h = []() {

trptcolin

Recap

• We found a Node.js bug. When Object.defineProperty was monkeypatched, in certain situations other things would break. For example, using console.log after the monkeypatch but not before (if console.log also appeared before the monkeypatch, it would work).
  • which was triggered by that kind of monkeypatch mistakenly being attached due to a syntax error in the Ruby uglifier gem’s es5.js shim (v2.7.1 - fixed by https://github.com/lautis/uglifier/commit/31a53a92da537af3776711471d6e9582d96dc49d, released in uglifier v3.0.0)
  • which was used as the js compressor for our static jekyll blog - luckily a direct dependency, and upgrading had no dependency conflicts - easy fix.
• Introduced in Node 11.12.0 by: https://github.com/nodejs/node/commit/c14aa07b94d684de8e2a23a54d0e6a3c25a2e460
• Fixed in Node 12.0.0 by: https://github.com/nodejs/node/commit/908292cf1f551c614a733d858528ffb13fb3a524
• [I was running Node 11.14.0.]

Details / How

trptcolin

TL;DR: what was the bug? (spoilers!): https://gist.github.com/trptcolin/6039cd454acfe6e820d13cbdce5e4064

• Minor text change for the company blog; let’s get it done!
• JEKYLL_ENV=production bundle exec jekyll upload -e staging
  • Liquid Exception: ExecJS::ProgramError in /_layouts/default.html
  • execjs, hmm, do i have node installed?
• node --version
  • yes, v11.14.0
• bundle open jekyll-s3-upload to read code & see this command is doing
  • looks like it builds before uploading (Jekyll::Commands::Build.build(site, jekyll_config)) - https://github.com/8thlight/jekyll-s3-upload/blob/60dd52f937db21d1265cb9a7fdcdf438730e32d2/lib/jekyll/commands/s3_upload.rb#L51
• bundle exec jekyll build

mkolod