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.

pocotan001

• 🎨 when improving the format/structure of the code
• 🚀 when improving performance
• ✏️ when writing docs
• 💡 new idea
• 🚧 work in progress
• ➕ when adding feature
• ➖ when removing feature
• 🔈 when adding logging
• 🔇 when reducing logging
• 🐛 when fixing a bug

sritchie

// Playground - noun: a place where people can play

import Cocoa

var str = "Hello, playground"

// Here's take 1. First, I defined the algebra like I would in
// Scala, as separate protocols:
protocol Semigroup {
    typealias T

Fristi

{-# LANGUAGE TypeFamilies #-}

import Data.Function (on)
import Control.Applicative

data EventData e = EventData {
    eventId :: Int,
    body :: Event e
}

NickLaMuro

#!/bin/bash
 
EMAIL="[email protected]"
API_TOKEN="API_TOKEN"
DOMAIN_ID="your_domain.com"
RECORDS=(123456 234567 345678) # Replace with the Record ID
IP="`curl -s -S http://v4.ident.me`"
STORED_IP_ADDRESS_FILENAME="$HOME/.current_external_ip_address"
 
# Loop through each record id in the array