SShortSingh.
Back to feed

Developer Builds BoltOS: A 64-Bit Hobby OS With Doom Port and Custom Drivers

0
·1 views

BoltOS is a 64-bit hobby operating system built entirely from scratch using C and Assembly language. The project was created and shared by its sole developer, who goes by adriantips on GitHub, where the source code is publicly hosted. The OS is designed as a higher-half kernel, a common architectural choice in hobby OS development. Notable achievements include a full Doom port and custom hardware drivers, highlighting the project's technical depth. BoltOS represents the developer's personal challenge of building a functioning operating system from the ground up.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

How to Build a TypeScript-Native Async Tracer for AI Agent Observability

A technical guide published on DEV Community walks developers through building a lightweight Node.js tracer to capture causal execution trees in TypeScript-based AI agents. The tutorial explains why simple timestamp logs are insufficient, as parallel async operations can obscure the true parent-child relationships between agent decisions and their spawned tools. It uses Node.js's AsyncLocalStorage to propagate immutable trace context across asynchronous boundaries without modifying every function signature. The design introduces separate span-start and span-end events, a controlled error category schema, and a pluggable sink interface to keep tracing off the application's critical path. While intentionally smaller than a production observability library, the approach is meant to avoid common architectural mistakes seen in minimal tracing examples.

0
ProgrammingDEV Community ·

Developer builds open-source CLI tool to catch leaked API keys and broken env files

A developer has released envcheck, a zero-dependency Node.js CLI tool designed to prevent two common engineering mishaps: missing environment variables causing production crashes and accidental secret commits to code repositories. The tool compares .env files against a committed .env.example template, flagging missing keys, duplicates, empty values, and unfilled placeholder defaults. It also recursively scans repositories for leaked credentials, detecting known token formats from providers like AWS, Stripe, and GitHub, as well as high-entropy strings that may represent undocumented secrets. Matched secrets are redacted in output so reports can be safely stored as CI artifacts, and common noise sources like node_modules and minified files are automatically excluded. The tool integrates with CI pipelines via standard exit codes and is available for use with GitHub Actions and other automation systems.

0
ProgrammingDEV Community ·

Developer builds open-source CLI tool to catch leaked API keys and broken env files

A developer has released envcheck, a zero-dependency Node.js CLI tool designed to prevent two common but costly mistakes: missing environment variables that crash production deployments, and API keys accidentally committed to code repositories. The tool validates .env files against a reference example or a JSON schema, flagging missing keys, duplicates, empty values, and unfilled placeholder defaults. It also recursively scans repositories for leaked secrets using pattern matching for known token formats — including AWS, Stripe, GitHub, and Google keys — as well as high-entropy strings that may represent unrecognized tokens. To reduce false positives, the scanner automatically skips node_modules, lockfiles, and minified files, and redacts matched secrets in its output so reports are safe to store as CI artifacts. The tool is designed for easy integration into CI pipelines via standard exit codes and works with systems like GitHub Actions.