WARNING This list outdated, for the up to date version visit https://haskellcosm.com
Types of work:
- RD - research&development
- PR - product
- IP - in-house product
- CO - consulting
App configuration in environment variables: for and against | |
For (some of these as per the 12 factor principles) | |
1) they are are easy to change between deploys without changing any code | |
2) unlike config files, there is little chance of them being checked | |
into the code repo accidentally | |
3) unlike custom config files, or other config mechanisms such as Java |
WARNING This list outdated, for the up to date version visit https://haskellcosm.com
Types of work:
import Html exposing (..) | |
import Html.App exposing (..) | |
import Html.Attributes exposing (..) | |
import Html.Events exposing (..) | |
import Html.Attributes exposing (..) | |
import Http | |
import Task exposing (Task) | |
import Json.Decode as Json exposing ((:=)) | |
type Msg |
It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.
Roots for record 0 (stored at leaf 0): [ 0 ] | |
0: 0 | |
Roots for record 1 (stored at leaf 2): [ 1 ] | |
0: 0─┐ | |
1 | |
1: 2─┘ | |
Roots for record 2 (stored at leaf 4): [ 1, 4 ] | |
0: 0─┐ |
"""Mux/demux protocol toy example with Trio. | |
Naively done and just about working! Probably buggy. There is not much by way | |
of error handling however it does showcase an approach for multiplexing a | |
streamed connection with multiple channels. All messages that are sent over the | |
stream are tagged with a channel ID. Each Protocol and Channel instance have | |
their own incoming and outgoing queue. | |
I'm trying to work towards having a robust mux/demux implementation and need | |
some help. Any comments on this would be greatly appreciated. Hopefully this |