IshaGupta18

Google Summer of Code'19 Work Product: Isha Gupta

The GSoC period might be coming to an end, but the journey is not over yet. Here's the summary so far...

Project Details

• Student: Isha Gupta
• Github: IshaGupta18
• Project Title: Sensor Data Upload & Display Libary
• Project Proposal: Proposal

rexagod

Google Summer of Code 2019 Public Lab Final Work Product: Pranshu Srivastava

Project Details

• Title: matcher.js library and Leaflet.DistortableImage overhaul
• Repositories created (and contributed to): matcher-core and matcher-cli
• Repositories contributed to: Leaflet.DistortableImage

Project Description

matcher-core

matcher-core essentially employs the ORB(Oriented FAST and Rotated BRIEF) algorithm to mine patterns using the well-known [FAST(Features from Accelerated Segment Test)](http://homepages.inf.ed.ac.uk/

getify

Building That Better Web

In honor of the 30th anniversary of the web, I wanted to share a few thoughts about what a better web could aspire to be, and challenge us to move toward it.

The Worser Web

It's tempting to frame "better" simply in terms of improvement and progress, as in how far the web has come over the last 20+ years. As a developer, I like many others get all too excited about fancy new features like Service Workers, WebRTC, and yes, even CSS Grids. The pace of change is dizzying, but it feels like a great problem to have too many awesome features to learn and use!

So in one practical respect, a better web is one that empowers developers and users alike to express themselves and connect with others more fluently.

Sixl-Daniel

How to create an HTTPS certificate for localhost domains

This focuses on generating the certificates for loading local virtual hosts hosted on your computer, for development only.

Do not use self-signed certificates in production ! For online certificates, use Let's Encrypt instead (tutorial).

danielkhan

const fs = require("fs");
setImmediate(() => {
  process.stdout.write(`setImmediate (after poll phase)\n`);
  process.nextTick(() => {
    process.stdout.write(`nextTick (nested registered in setImmediate())\n`);
  });
});

setTimeout(() => {
  process.stdout.write(`setTimeout (timers phase)\n`);

meribold

These are notes regarding my "Email Workflow Demo" video. The following parts of my dotfiles are relevant for the workflow shown in the video:

• NeoMutt config: /home/config/neomutt
• Super+Shift+M keybind: /home/xbindkeysrc#L91-L92
• Vim
  • /home/vim/init.vim#L20-L34
  • Contact completion: /home/vim/autoload/mailcomplete.vim
• [/home/vim/ftplugin/mail.vim](https://github.com/meribold/dotfiles/blob/ea6c94490ebc2f28672f1ee1dfe8c45eaf52aa2a/home/vim/ftplugin/ma

mmalecki

for (var i = 0; i < 1024 * 1024; i++) {
  process.nextTick(function () { Math.sqrt(i) } )
}

datagrok

"Vendoring" is a vile anti-pattern

What is "vendoring"?

From a comment on StackOverflow:

Vendoring is the moving of all 3rd party items such as plugins, gems and even rails into the /vendor directory. This is one method for ensuring that all files are deployed to the production server the same as the dev environment.

The activity described above, on its own, is fine. It merely describes the deployment location for various resources in an application.

mmcdaris

usage

go build: compiles the packages named by the import paths, along with their dependencies, the binary does not end up in $GOPATH/bin it gets created in the dirs

go build [-o output] [build flags] [packages]

If the [packages] are a list of .go files, build treats them as a list of source files specifying a single package.

reachlin

  // For all the confusing Prometheus configuration and
  // regular expressions,
  // explained in examples.


  // Remember, there are default values for each item if it's missing.
  // regex is (.*),
  // replacement is $1,
  // separator is ;
  // ,and action is replace