Kostas Papadimitriou vinilios

David's programming examples knowledge base

Generated by code-examples-manager release 2.4.9-SNAPSHOT
659 published examples

akka-pekko

akka-actors-hello-world.sc : Simple akka hello world example
akka-capitalize-and-print.sc : dump capitalized string coming from stdin using streams
akka-http-client-json-stream.sc : Fully asynchronous http client call with json streamed response using akka-http will work in all cases, even with chunked responses !
akka-http-client-json-with-proxy.sc : Fully asynchronous http client call with json response using akka-http will work in all cases, even with chunked responses, this example add automatic http proxy support.
[akka-http-client-json.sc](https:/

Revisiting Tagless Final Interpreters

Tageless Final interpreters are an alternative to the traditional Algebraic Data Type (and generalized ADT) based implementation of the interpreter pattern. This document presents the Tageless Final approach with Scala, and shows how Dotty with it's recently added implicits functions makes the approach even more appealing. All examples are direct translations of their Haskell version presented in the Typed Tagless Final Interpreters: Lecture Notes (section 2).

The interpreter pattern has recently received a lot of attention in the Scala community. A lot of efforts have been invested in trying to address the biggest shortcomings of ADT/GADT based solutions: extensibility. One can first look at cats' Inject typeclass for an implementation of [Data Type à la Carte](http://www.cs.ru.nl/~W.Swierstra/Publications/DataTypesA

Setup modern.ie vagrant boxes

Since modern.ie released vagrant boxes, it' no longer necessary to manually import the ova file to virtualbox, as mentioned here.

However, the guys at modern.ie didn't configured the box to work with WinRM. This how-to addresses that, presenting steps to proper repackage these boxes, adding WinRM support. Additionally configures chocolatey package manager and puppet provisioner.

Pre-requisites

This post is also on my blog, since Gist doesn't support @ notifications.

Components are taking center stage in Ember 2.0. Here are some things you can do today to make the transition as smooth as possible:

Use Ember CLI
In general, replace views + controllers with components
Only use controllers at the top-level for receiving data from the route, and use Ember.Controller instead of Ember.ArrayController or Ember.ObjectController
Fetch data in your route, and set it as normal properties on your top-level controller. Export an Ember.Controller, otherwise a proxy will be generated. You can use Ember.RSVP.hash to simulate setting normal props on your controller.

Lesson 1: Affordances and Signifiers

Don't solve the problem given (as it's stated), figure out what the real underlying problem is.

To understand design, you have to be a good observer and question things. Travel with a camera and take photos. Don't use flash, use natural lighting when possible.

Affordances are the relationships (read: possible actions) between an object and an entity (most often a person). For example, a chair affords sitting for a human. Affordances enable interactions between entities and objects (similarly, anti-affordances prevent or reduce interactions). The presence of an affordance is determined by the properties of the object and of the abilities of the entity who's interacting with the object.

Signifiers are signals, communication devices. These signs tell you about the possible actions; what to do, and where to do it. Signifiers are often visible, but invisible (secret) signifiers do exist, like clicking a YT video to play

	#!/bin/bash

	network_device_v4=$(ip route show default \| awk '/default/ {print $5}')
	network_device_v6=$(ip -6 route show default \| awk '/default/ {print $5}')
	tunnel_interface="nymtun0"

	if ! dpkg -s iptables-persistent >/dev/null 2>&1; then
	sudo apt-get update
	sudo apt-get install -y iptables-persistent
	else

	// Run with scala-cli httpserver.scala
	// Save logback.xml file into ./resources dir
	// Before generating native image binary, run first as above and make a real access to the URL
	// so the native-image-agent can generate the metadata in ./resources dir.
	// Then generate native image binary with: scala-cli package --native-image httpserver.scala
	//> using scala "3.3.0"
	//> using lib "dev.zio::zio:2.0.15"
	//> using lib "dev.zio::zio-http:3.0.0-RC2"
	//> using lib "dev.zio::zio-logging-slf4j2::2.1.13"
	//> using lib "ch.qos.logback:logback-classic:1.4.8"

	DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
	Version 2, December 2004

	Copyright (C) 2011 Mathieu 'p01' Henri - http://www.p01.org/releases/

	Everyone is permitted to copy and distribute verbatim or modified
	copies of this license document, and changing it is allowed as long
	as the name is changed.

	DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE