Conor Dockry cdock1029

Setup

To setup debugging for Dlang programs on Windows with VsCode follow these steps:

make sure you have the D Programming Language (code-d) (VsCode extension) installed
make sure you have the C/C++ extension pack (VsCode extension) installed
create a .vscode folder at the root of your DLang project
copy the launch.json and tasks.json into it
in the launch.json at line: "program": "./my-app.exe", change my-app.exe to your executable name (look in the dub.json under name).
click on the debug tab in VsCode, then click on the debug button at the top (or press F5)

NOTE

These are NOT product / license keys that are valid for Windows activation.
These keys only select the edition of Windows to install during setup, but they do not activate or license the installation.

Index

Windows 11
RTM Generic Keys

Update 2

As of August 28th, 2025, Expert LSP has been released: https://github.com/elixir-lang/expert

Although still a work in progress, the plan is for the other three LS implementations to be archived. I may try to come up with a new way to track Expert's featureset, but I would probably contribute that back to Expert as documentation.

Update

As of August 15, 2024, it's been announced that the three projects bein compared here will soon merge! See the official Elixir blog post for more details: https://elixir-lang.org/blog/2024/08/15/welcome-elixir-language-server-team/

Deploying to Fly.io with SQLite

Deploying a Phoenix app to Fly.io is a breeze...is what everyone kept telling me. In fairness, I imagine the process would have been breezier had I just used postgres, but all the sqlite and litestream talk has been far too intriguing to ignore. "Wait", you say. "It is just a flat file. How much harder can it be?"

It is easy to make something harder than it should be. It is hard to take something complex and make it truly simple. flyctl launch does an amazing job at providing a simple interface to the utterly complex task of generating deployment resources, especially now that we are living in a containerd (erm, firecracker) world.

This gist is for anyone who, like me, thinks they know better than to read all of the documentation and therefore necessari

Replacing Create React App with the Next.js CLI

How dare you make a jab at Create React App!?

Firstly, Create React App is good. But it's a very rigid CLI, primarily designed for projects that require very little to no configuration. This makes it great for beginners and simple projects but unfortunately, this means that it's pretty non-extensible. Despite the involvement from big names and a ton of great devs, it has left me wanting a much better developer experience with a lot more polish when it comes to hot reloading, babel configuration, webpack configuration, etc. It's definitely simple and good, but not amazing.

Now, compare that experience to Next.js which for starters has a much larger team behind it provided by a world-class company (Vercel) who are all financially dedicated to making it the best DX you could imagine to build any React application. Next.js is the 💣-diggity. It has amazing docs, great support, can grow with your requirements into SSR or static site generation, etc.

	import QtQuick
	import QtQuick.Controls
	import QtQuick.Layouts
	import QtQuick.LocalStorage
	import Quickshell
	import Quickshell.Widgets

	Window {
	id: launcher
	title: "qs-launcher"

	/// <summary>
	/// Register all interfaces for a type.
	/// </summary>
	/// <returns>The original <see cref="T:Microsoft.Extensions.DependencyInjection.IServiceCollection" />.</returns>
	public static IServiceCollection AsImplementedInterfaces(this IServiceCollection services)
	{
	var lastRegistration = services.LastOrDefault();
	if (lastRegistration != null)
	{
	var implementationType = GetImplementationType(lastRegistration);

	#include <stdint.h>
	#include <stdlib.h>
	#include <stdbool.h>
	#include <windows.h>
	#pragma comment( lib, "user32.lib" )
	#pragma comment( lib, "gdi32.lib" )

	#define SCRW 640
	#define SCRH 480

	# Rails production setup via SQLite3 made durable by https://litestream.io/
	# Copy this to Dockerfile on a fresh rails app. Deploy to fly.io or any other container engine.
	#
	# try locally: docker build . -t rails && docker run -p3000:3000 -it rails
	#
	# in production you might want to map /data to somewhere on the host,
	# but you don't have to!
	#
	FROM ruby:3.0.2

	import type { Action, Loader } from "@remix-run/loader";
	import { json, parseFormBody, redirect } from "@remix-run/loader";
	import { readTodos, createTodo, deleteTodo } from "../data/todo";

	let action: Action = async ({ request, context: { session } }) => {
	let [method, body] = await methodOverride(request);
	await new Promise((res) => setTimeout(res, 1000));
	switch (method) {
	case "post": {
	let [_, error] = await createTodo(body!.name);