davidfowl

Minimal APIs at a glance

This document now exists on the official ASP.NET core docs page.

• Application
  • WebApplication
  • WebApplicationBuilder
• Request Handling
  • Routing
  • Parameter Binding

danielrw7

#!/bin/sh

command="${*}"
printf "Initialized REPL for `%s`\n" "$command"
printf "%s> " "$command"
read -r input
while [ "$input" != "" ];
do
    eval "$command $input"
    printf "%s> " "$command"

VonC

@echo off
setlocal enabledelayedexpansion
rem set pkg=github.com/jroimartin/gocui
set pkg=%1
if "%pkg%"=="" (
	echo expect package name github.com/user/project
	exit /b 1
)
if exist "vendor/%pkg%" (
	echo '%pkg%' already vendorized

mwinkle

text_file = sc.textFile("hdfs://sandbox.hortonworks.com/user/guest/install.log")
counts = text_file.flatMap( lambda line: line.split(" ")) \
.map(lambda word: (word, 1) ) \
.reduceByKey(lambda a, b : a + b)
counts.saveAsTextFile("hdfs://sandbox.hortonworks.com/user/guest/output1.txt")

MattMcFarland

Table of Contents:

• Why FLUX?
• About this Guide
• Library Dependencies
• Directory Structure
• store.js
• constants.js
• dispatcher.js
• actions.js
• app.js

non

What is the appeal of dynamically-typed languages?

Kris Nuttycombe asks:

I genuinely wish I understood the appeal of unityped languages better. Can someone who really knows both well-typed and unityped explain?

I think the terms well-typed and unityped are a bit of question-begging here (you might as well say good-typed versus bad-typed), so instead I will say statically-typed and dynamically-typed.

I'm going to approach this article using Scala to stand-in for static typing and Python for dynamic typing. I feel like I am credibly proficient both languages: I don't currently write a lot of Python, but I still have affection for the language, and have probably written hundreds of thousands of lines of Python code over the years.

carols10cents

Thanks to @seejee for making this for me!!!

C# to Rust Cheat Sheet

The goal of this is to have an easily-scannable reference for the most common syntax idioms in C# and Rust so that programmers most comfortable with C# can quickly get through the syntax differences and feel like they could read and write basic Rust programs.

What do you think? Does this meet its goal? If not, why not?

Variables

vaskoz

package main

import "strconv"
import "fmt"

type Color string
type Make string
type Model string

const (

rocketraman

import com.google.common.base.MoreObjects;
import com.google.common.base.Objects;

public class Address {

    ...

    @Override
    public boolean equals(Object obj) {