Jason Garber jgarber623

Enabling VS Code Marketplace in VSCodium and Trae

Microsoft claims Visual Studio Code (VS Code) is open source, yet it restricts the use of its Marketplace extensions in non-Microsoft products like VSCodium (telemetry/tracking free open source fork), Cursor, Windsurf, Trae, and other VS Code-based IDEs, enforcing what some see as monopolistic control. This guide provides a workaround to enable the VS Code Marketplace in VSCodium and Trae (more to be added soon), allowing you to freely use extensions. Note that using the VS Code Marketplace with non-Microsoft products may violate its terms of use, which state that extensions are intended for use only with Microsoft Visual Studio products. Proceed at your discretion after reviewing the terms.

Enabling VS Code Marketplace in VSCodium

To configure VSCodium to use the VS Code Marketplace instead of the default OpenVSX Registry, you can either set environment variables or create a custom product.json file.

I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.

I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:

SQL Tricks

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

Styling native elements

Native HTML controls are a challenge to style. You can style any element in the web platform that uses Shadow DOM with a pseudo element ::pseudo-element or the /deep/ path selector.

video::webkit-media-controls-timeline {
  background-color: lime;
}

video /deep/ input[type=range] {

Pry Cheat Sheet

Youtube Tutorial 2013

Command Line

pry -r ./config/app_init_file.rb - load your app into a pry session (look at the file loaded by config.ru)
pry -r ./config/environment.rb - load your rails into a pry session

Debugger

	# latest supported electron version as of october 2024
	LATEST_SUPPORTED_VERSION=30
	RED='\033[0;31m'
	GREEN='\033[0;32m'
	NC='\033[0m' # no color

	mdfind "kind:app" 2>/dev/null \| sort -u \| while read app;
	do
	filename="$app/Contents/Frameworks/Electron Framework.framework/Electron Framework"
	if [[ -f $filename ]]; then

	/**
	* @param {import("@11ty/eleventy/src/UserConfig")} eleventyConfig
	*/
	module.exports = (eleventyConfig) => {
	return {};
	};

	ruby '2.7.1'

	gem 'rails', github: 'rails/rails'
	gem 'tzinfo-data', '>= 1.2016.7' # Don't rely on OSX/Linux timezone data

	# Action Text
	gem 'actiontext', github: 'basecamp/actiontext', ref: 'okra'
	gem 'okra', github: 'basecamp/okra'

	# Drivers

	'use strict';

	class HTMLElementPlus extends HTMLElement {

	static defaultAttributeValue() {
	/* the name of the attribute is parsed in as a parameter */
	return;
	}

	static parseAttributeValue(name, value) {