| import { | |
| createContext, | |
| ReactNode, | |
| useCallback, | |
| useContext, | |
| useEffect, useMemo, | |
| useRef, | |
| useState | |
| } from "react"; | |
| import {Channel, Presence, Socket} from "phoenix"; |
This was a response to a Hacker News comment asking me what I've been up to since 2010. I'm posting it here since HN rejects it with "that comment is too long." I suppose that's fair, since this ended up being something of an autobiography.
--
What happened after 2010?
I'll preface this with three things. 1. I prefer schemes over Common Lisps, and I prefer Racket of the Schemes. 2. There is more to it than the points I raise here. 3. I assume you have no previous experience with Lisp, and don't have a preference for Schemes over Common Lisp. With all that out of the way... I would say Common Lisp/SBCL. Let me explain
Now as to why Common Lisp over Scheme
A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.
Nowadays lots of companies choose engines like Unreal or Unity for their games (or that's what lot of people think) because d
| local severity_map = { "E", "W", "I", "H" } | |
| local parse_diagnostics = function(diagnostics) | |
| if not diagnostics then return end | |
| local items = {} | |
| for _, diagnostic in ipairs(diagnostics) do | |
| local fname = vim.fn.bufname() | |
| local position = diagnostic.range.start | |
| local severity = diagnostic.severity | |
| table.insert(items, { |
Sometimes a programming language has a "strict mode" to restrict unsafe constructs. E.g., Perl has use strict, Javascript has "use strict", and Visual Basic has Option Strict. But what about bash? Well, bash doesn't have a strict mode as such, but it does have an unofficial strict mode:
set -euo pipefail
set -e
| -module(task). | |
| -export([async/1, async/3]). | |
| -export([await/1, await/2, await/3]). | |
| -opaque t() :: #{tpid := pid(), tref := reference()}. | |
| -type await_opts() :: [kill]. | |
| -export_type([t/0]). | |
| -export_type([await_opts/0]). |
| -module(systemd). | |
| % This is what you need to adopt systemd in erlang | |
| % | |
| % Do whatever you want license. If you want, you can take this code under terms of MIT license. | |
| -export([ready/0, reloading/0, stopping/0, watchdog/0]). | |
| -export([start_link/0]). | |
| -export([init/1, handle_info/2, terminate/2]). |
| Operating System: macOS" | |
| CPU Information: Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz | |
| Number of Available Cores: 8 | |
| Available memory: 16 GB | |
| Elixir 1.7.0-dev | |
| Erlang 21.0 | |
| Benchmark suite executing with the following configuration: | |
| warmup: 5 s | |
| time: 30 s |
| {-# OPTIONS_GHC -Wall #-} | |
| -- An example of representing a connection | |
| -- Types | |
| data ConnInfo = ConnInfo | |
| { connState :: ConnState | |
| , server :: String | |
| } deriving (Show) |
