tydira

Getting started with Linux kernel development

Prerequisites

The Linux kernel is written in C, so you should have at least a basic understanding of C before diving into kernel work. You don't need expert level C knowledge, since you can always pick some things up underway, but it certainly helps to know the language and to have written some userspace C programs already.

It will also help to be a Linux user. If you have never used Linux before, it's probably a good idea to download a distro and get comfortable with it before you start doing kernel work.

Lastly, knowing git is not actually required, but can really help you (since you can dig through changelogs and search for information you'll need). At a minimum you should probably be able to clone the git repository to a local directory.

ESM modules in node: npm edition

The proposal you’re about to read is not just a proposal. We have a working implementation of almost everything we discussed here. We encourage you to checkout and build our branch: our fork, with the relevant branch selected. Building and using the implementation will give you a better understanding of what using it as a developer is like.

Our implementation ended up differing from the proposal on some minor points. As our last action item before making a PR, we’re writing documentation on what we did. While I loathe pointing to tests in lieu of documentation, they will be helpful until we complete writing docs: the unit tests.

This repo also contains a bundled version of npm that has a new command, asset. You can read the documentation for and goals of that comma

Vim without NERD tree or CtrlP

I used to use NERD tree for quite a while, then switched to CtrlP for something a little more lightweight. My setup now includes zero file browser or tree view, and instead uses native Vim fuzzy search and auto-directory switching.

Fuzzy Search

There is a super sweet feature in Vim whereby you can fuzzy find your files using **/*, e.g.:

:vs **/*<partial file name><Tab>

A non-exhaustive list of WebGL and WebGPU frameworks and libraries. It is mostly for learning purposes as some of the libraries listed are wip/outdated/not maintained anymore.

Engines and libraries ⚙️

Name	Stars	Last Commit	Description
three.js	![GitHub

One thing that surprises newer programmers is that the older 8-bit microcomputers from the 70s and 80s were designed to run at the speed of random memory access to DRAM and ROM. The C64 was released in 1982 when I was born and its 6502 CPU ran at 1 MHz (give or take depending on NTSC vs PAL). It had a 2-stage pipelined design that was designed to overlap execution and instruction fetch for the current and next instruction. Cycle counting was simple to understand and master since it was based almost entirely on the number of memory accesses (1 cycle each), with a 1-cycle penalty for taken branches because of the pipelined instruction fetch for the next sequential instruction. So, the entire architecture was based on keeping the memory subsystem busy 100% of the time by issuing a read or write every cycle. One-byte instructions with no memory operands like INX still take the minimum 2 cycles per instruction and end up redundantly issuing the same memory request two cycles in a row.

This demonstrates the implementation of full text search for documents in Indexed DB.

Word-breaking and stemming is used to create a list of terms for each document.
Document records are annotated with the list of terms when added to the database.
A multi-entry index on the list of terms is populated.
A query is similarly processed into a list of terms.
A join over the terms is implemented using multiple cursors on the index.

The necessity of annotating records with the word list to populate the index is a limitation of the current Indexed DB API. A feature request to support custom

	/**
	* Export all data from an IndexedDB database
	*
	* @param {IDBDatabase} idbDatabase The database to export from
	* @return {Promise<string>}
	*/
	export function exportToJson(idbDatabase) {
	return new Promise((resolve, reject) => {
	const exportObject = {}
	if (idbDatabase.objectStoreNames.length === 0) {

	// ------------------------------------------- IMPORTANT -------------------------------------------
	// This is a development file to be minified using https://javascript-minifier.com/ and inlined in
	// the index.html file. This file is not compiled or processed by webpack so it should be treated as
	// low-level precompiled es5-compatible javascript. The code here is not meant to be clean, it's
	// meant to be as light and fast as possible since it runs in the head tag.

	// HACK: This file a hack to ensure that home-screen apps on mobile devices gets refreshed when they
	// start. It works by forcing a load of the service-worker.js file and use the precache-manifest
	// file name as an application version, just like a desktop browser like chrome would do. When
	// when it detects a change in the application version, it reloads the page and bypass the browser's

	import React from 'react'

	function Login({onSubmit}) {
	return (
	<div>
	<form
	data-test="login-form"
	onSubmit={e => {
	e.preventDefault()
	const {username, password} = e.target.elements

	to check if the server works - https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice

	stun:
	stun.l.google.com:19302,
	stun1.l.google.com:19302,
	stun2.l.google.com:19302,
	stun3.l.google.com:19302,
	stun4.l.google.com:19302,
	stun.ekiga.net,
	stun.ideasip.com,