DEV Community: Anton Reshetov

Playing a torrent while it downloads: how I got start time from 41 s to 8 s

Anton Reshetov — Thu, 29 Oct 2026 14:04:10 +0000

You hit play on a video that's still downloading, and the player immediately wants bytes you don't have. First the start of the file. Then, quite often, the end, because that's where an MP4 keeps its index. Then wherever you drag the seek bar. BitTorrent doesn't care about any of that: it grabs pieces in whatever order the swarm hands them out, rarest first.

Getting those two to cooperate turned out to be most of the work.

I needed this for Torsher, the self-hosted media center I'm building, and I gave myself one rule: on a normal home connection, playback has to start in under 15 seconds. Below is what I tried, what failed, and the numbers.

Every test used Blender's open movies (Sintel, Big Buck Bunny, Tears of Steel). They're free to share, which makes them perfect for this.

How I measured

I didn't want to click around a browser all evening, so a small script pretends to be the player:

start: grab the first 2 MB and the last 1 MB of the file at the same time, and time how long until both are in;
seek: grab 2 MB from the middle of the file, then 2 MB from 85% in.

Each run starts from scratch: torrent removed, files deleted. Two rounds per engine, swapping the order between them. Fetching the torrent's metadata isn't counted.

First try: a ready-made library

I started with an existing Rust library that already had streaming built in. Median start: 41 seconds. Worse, it was random. The same file started in 2 seconds on one run and 57 on the next. Seeking into a part that wasn't downloaded yet took 43 seconds.

So I read its source. The stream window, 32 MB, went out to peers all at once, and the piece sitting right under the playback position was no more urgent than anything else in that window. If a slow peer happened to grab that piece, the player just sat there until the request got handed to someone else, and that only kicked in once the request was ten times slower than average.

What fixed it: a responsive reader

I swapped it for a small Go service on top of anacrolix/torrent. The library handles the hard stuff (peers, DHT, picking pieces), and my code is just the HTTP API, the stream, file selection and storage.

The part that matters is the library's responsive reader. It gives urgent priority to the pieces at the read position, so whatever the player is waiting for right now jumps the queue. Each HTTP request gets its own reader:

var streamReadahead int64 = 16 << 20

func newStreamReader(ctx context.Context, file *torrent.File) torrent.Reader {
    reader := file.NewReader()
    reader.SetContext(ctx) // the player disconnects, the read is cancelled
    reader.SetResponsive()
    reader.SetReadahead(streamReadahead)

    return reader
}

For Range requests I let http.ServeContent do the work: 206, 416, Content-Range, Content-Length, all handled. One thing to watch out for: set Content-Type yourself before you call it.

w.Header().Set("Content-Type", contentType)
http.ServeContent(w, r, name, time.Time{}, reader)

If you don't, ServeContent reads the beginning of the file to guess the type. With a torrent, that means it pulls the first pieces even when the player asked for the middle.

Download a window, not the whole file

In a torrent client, picking a file usually means "download all of it". For watching, that's wrong in two ways. The rest of the file fights with the piece under the playback position for the same peers. And a 20 GB file you watched for one minute ends up sitting on your disk.

So while you watch, only a window ahead of the position gets downloaded: roughly three minutes of video, worked out from the file's average bitrate and kept between 64 MB and 1 GiB. The whole file only comes down if you explicitly hit "download".

Marking a full 1 GiB window as wanted in one go would bring back the original problem, so the window goes out in 64 MB batches (at least four pieces), closest to the position first. The batch gets recalculated whenever the piece under the position changes, and once a second on top of that, because a paused player doesn't move but the window should keep filling.

Close the stream, and the pieces outside any open window drop back to "not needed". Downloading just stops.

One thing made this a lot easier than I expected. In anacrolix, a piece's priority is the highest of three: the file's, the readers', and the piece's own. So a viewing window never clashes with a file someone chose to download in full, and the other way around.

What made it worse: prewarming

This one looked obvious. As soon as a torrent is added, read the start and the end of the file, so they're already there when the player asks. I measured it, and the median start went from 8.3 to 20.3 seconds. The prewarm requests were fighting the player's own requests for the same peers. I took it out, and it stays out until a benchmark says otherwise.

Results

	Start, median (range)	Seek, median (range)
Rust library	41 s (2–59)	43 s (6–70)
Go + responsive reader	8.3 s (3.4–19.5)	3.8 s (1.3–6.9)
Go + prewarm	20.3 s (5.4–33.0)	10.9 s (4.2–18.2)

For reference, a popular streaming server built on the same library did 6.0 s to start and 3.0 s to seek on the same files. So I'm still a couple of seconds behind. What bugs me more is how much the start time jumps around. My guess is that other pieces compete with the first ones early on, and that's what I'm measuring next.

Usual caveats: one machine, one home connection, one evening, two runs per file. Swarms change over time.

Two things that bit me

Library callbacks run under its lock. anacrolix calls some callbacks while it holds the client lock. Touch the client from inside one, and the engine deadlocks.

A panic in an HTTP handler can leave that lock held. net/http recovers panics in handlers, so the process keeps running, /health still says OK, and everything that needs the lock hangs forever. Now any panic in a route takes the whole process down, a watchdog checks the lock every 5 seconds and exits if it's been stuck for a minute, and the parent server restarts the engine.

Where this lives

This is the engine inside Torsher, an open-source media center that runs in one Docker container and starts from the TV. The engine is in engine/, the window logic in engine/window.go.

If you've beaten the start-time spread some other way, I'd really like to hear how.

Why I Rewrote My Email Editor from Scratch: From Blocks to Atoms Rewrite

Anton Reshetov — Mon, 16 Feb 2026 16:08:35 +0000

Hi there!

Six years ago, I launched MySigMail Card as a commercial product.

To be honest, it didn't take off as I hoped. I struggled to attract enough users to make it sustainable. Eventually, I lost motivation and abandoned it to focus on my other open-source project, massCode.

For years, the project gathered dust. But besides the marketing struggles, it also had a "ticking time bomb" in its core architecture.

It was built entirely on Presets.

The Problem: The "Preset Trap"

In the initial version, if a user wanted a header, they dragged a "Header Block". If they wanted a testimonial, they dragged a "Testimonial Block". Under the hood, these were rigid, hard-coded HTML chunks.

This led to several "dev nightmares":

The Variation Explosion: Want the image on the right? I had to code a new block. Want 3 columns instead of 2? Another block.
The Maintenance Ceiling: I became the bottleneck. Every "small change" requested by users required me to push a code update.
Rigid Data Structure: The JSON was tied to the visual representation, making migrations a headache.

The Solution: Embracing Atomic Design

I realized that to make the editor truly powerful, I had to decouple Layout from Content. I scrapped the old engine and rebuilt it using a recursive, hierarchical system:

Block (The Root): The top-level section wrapper that handles full-width backgrounds and vertical spacing.
Row (The Grid): Defines the horizontal structure and manages column gaps and mobile collapsing logic.
Cell (The Flexible Container): The powerhouse of the layout. It controls alignment, dimensions, and—crucially—can contain nested Rows, allowing for complex, multi-level grid structures.
Atom (The Content): The actual elements: Text, Image, Button, Menu, and Divider.

This recursive structure (Block -> Row -> Cell -> Row...) means you aren't limited to simple columns. You can build advanced layouts like "Sidebar + Main Content" or complex product grids without writing a single line of code.

The Tech Stack

I wanted this version to be modern, fast, and developer-friendly:

Vue 3 (Composition API): For a reactive and modular UI.
TypeScript: For a robust data schema (vital for complex email structures).
Tailwind CSS: Using the latest v4 for blazing fast styling.
Shadcn Vue: For accessible UI components.
Clean Email Output: It generates production-ready, table-based HTML that actually works in Outlook.

Why Open Source?

I’m building this in public as an Open Source project (AGPL-3.0).

Why? First, because I believe the world needs a powerful, embeddable email builder that isn't locked behind a $500/month SaaS subscription.

But there is a deeper reason.

We live in an era of increasing vendor lock-in and centralized control. We have seen instances where entire regions are cut off from services due to geopolitical reasons, leaving developers and users stranded. Software should be accessible and reliable, regardless of borders.

Driven by a passion for open source, I want to provide a truly independent alternative to ensure that everyone has access to a powerful, self-hosted email builder.

If you’ve ever struggled with rigid email templates or want to see how we handle complex Drag-and-Drop in Vue 3, I’d love for you to check out the repo.

👉 Check it out here: github.com/mysigmail/card

I’m actively looking for feedback on the architecture and, of course, contributors are more than welcome!

Bumpy: zero-config monorepo releases powered by Git history

Anton Reshetov — Tue, 27 Jan 2026 16:21:37 +0000

Hi there!

Monorepo releases can be amazing… until the tooling feels either too heavy (extra metadata, intent files, complex flows) or too opinionated about how you should work. I wanted something lightweight that stays out of the way — especially if your Git history is already meaningful.

So I built Bumpy — a zero-config CLI for monorepo versioning that:

Auto-discovers packages (pnpm/npm workspaces, apps/*, packages/*)
Suggests the next version using Conventional Commits
Generates per-package changelogs from Git history
Uses per-project tags like project@version for precise release boundaries
Supports prereleases and --dry-run

Repo: https://github.com/antonreshetov/bumpy

Best fit: small/medium monorepos that already use Conventional Commits and want clean per-package changelogs + tags, without adopting a whole new workflow.

Why another release tool?

Tools like Changesets and Nx Release are excellent — they just optimize for different trade-offs than I needed:

Changesets: great, but it’s a file-based workflow (changeset “intent” markdown files that you commit and later assemble into releases).
Nx Release: powerful and well-integrated if you’re already in Nx; heavier if your repo isn’t.

Bumpy tries to keep the best parts (automation + safety) while keeping Git as the source of truth and avoiding extra ceremony.

How Bumpy works

At release time, Bumpy:

Scan: Finds packages in your workspace.
Locate: Detects the last tag for each package (e.g., project-a@1.2.3).
Analyze: Reads Git history since that tag.
Suggest: Recommends a bump based on Conventional Commits.
Generate: Creates/updates a package-level CHANGELOG.md.

You can always confirm the suggestion, choose a different bump type, or enter a custom version.

Quick Start

Installation

# Global
npm install -g @antonreshetov/bumpy

# Local (recommended for monorepos)
pnpm add -D @antonreshetov/bumpy

Common commands

Interactive release: bumpy
Status overview: bumpy status
Release one project (non-interactive): bumpy release project-a --type minor --yes
Dry-run: bumpy release --dry-run

Config is optional

By default, Bumpy uses your existing workspace layout. To customize behavior, run bumpy init to generate bumpy.json in the repo root.

{
  "projects": ["apps/*", "packages/*"],
  "release": {
    "ignore": ["apps/internal-tool"],
    "changelog": {
      "projectChangelogs": true,
      "workspaceChangelog": false
    },
    "git": {
      "commit": true,
      "tag": true,
      "push": true,
      "commitMessage": "chore(release): {tag}"
    }
  }
}

Where I’d love feedback

If you’ve used Changesets / Nx Release / anything similar:

Does this release flow feel intuitive?
What would you miss immediately if you switched to Bumpy?
Any edge cases you’ve hit around per-project tags or changelog structure?
What should bumpy status show to be useful day-to-day?

Repo again: https://github.com/antonreshetov/bumpy

MySigMail v2 — Open-Source Email Signature Generator

Anton Reshetov — Fri, 19 Sep 2025 12:01:07 +0000

In 2019, I launched MySigMail, a simple tool to create professional email signatures. It got some traction, but I got swept up in other open-source projects—like my code snippet manager massCode, which has grown a vibrant community. Now, I’m excited to revive app with MySigMail v2, an open-source, client-side email signature generator designed for developers who value transparency and control.

Why MySigMail?

Let’s face it: creating a professional email signature from scratch is not trivial. You’re stuck wrestling with:

Table-based layouts: Email clients like Outlook demand clunky HTML tables that are a pain to code.
Inconsistent rendering: Your signature looks great in Gmail but breaks in Apple Mail or Thunderbird.
Time sinks: Tweaking fonts, spacing, and images to work across clients is a nightmare.
Closed-source tools: Most solutions hide their code and lock you into their ecosystem.
Overpriced subscriptions: Paying monthly for something so basic feels wrong.

MySigMail solves this. It’s a free, open-source, client-side tool that empowers you to create polished email signatures with ease. I built app to make professional signatures accessible to everyone—especially developers who value customization and openness.

What You Get

Deep Customization: Tweak fonts, colors, avatar shapes, social icons, and custom fields to match your style or brand.
Ready-to-Use Templates: Kickstart your design with clean, professional layouts.
Flexible Add-Ons: Add disclaimers, call-to-action blocks, and more to make your signature stand out.
Lightweight & Client-Side: Run it locally with no server setup required, perfect for developers who want simplicity.

Get Started in Minutes

git clone https://github.com/antonreshetov/mysigmail
cd mysigmail
bun install
bun run dev

Want to test image uploads? Add your AWS S3 credentials to a .env file:

VITE_AWS_S3_URL=
VITE_AWS_S3_BASKET=
VITE_AWS_S3_ID=
VITE_AWS_S3_KEY=
VITE_AWS_S3_REGION=

Why Open-Source?

Open-source email signature generators are rare. Most tools are proprietary, expensive, or both. MySigMail is my contribution to the developer community—a transparent, customizable tool you can trust and extend. Whether you’re a solo dev or part of a team, MySigMail gives you the freedom to create signatures without the usual headaches.

Let’s Hear from You!

I’d love your feedback:

Would you use a client-side, open-source email signature tool?
What features would make it even better for your workflow?

Check out the project on GitHub: https://github.com/antonreshetov/mysigmail. I hope MySigMail helps you craft signatures that look great and feel effortless.

Cheers,
Anton

Tracks and Records Your Work Time Accurately

Anton Reshetov — Mon, 01 Apr 2024 08:58:41 +0000

The Timefall project is an open-source software that is being developed to provide users with an efficient and convenient time management tool. Created with modern software trends in mind, Timefall is a tool accessible to anyone who wants to better understand how they allocate their time and how it can be used most productively. It's a simple yet powerful tool capable of adapting to each user's needs.

Key Features:

Task Creation with Hourly Pay: Simplify your work assignment process by creating tasks with specified hourly rates, making payroll calculations more straightforward.

Task Folder Organization: Keep your tasks neatly organized by distributing them into individual folders – streamlining work management and enhancing productivity.

Detailed Reporting: Assess your work performance over different periods with our comprehensive reports. Analyze your tasks by week, month or year.

Local JSON Database: Maintain absolute control and privacy of your task data with our simple JSON database that resides on your computer, eliminating dependence on cloud storage.

antonreshetov / timefall

Tracks and Records Your Work Time Accurately

Timefall

Built with Electron & Vue.
Inspired by Timemator

Latest Release | Discussions

Support

Timefall is open source project and completely free to use.

However, the amount of effort needed to maintain and develop new features for the project is not sustainable without proper financial backing. You can support Timefall development via the following methods:

About

Development

Prerequisites

The project uses Bun for building and running. Please make sure you have Bun installed.

# Install dependencies
bun install
# Run the app
bun

…

View on GitHub

Create Stunning HTML Emails with vue-email - A Vue.js Components

Anton Reshetov — Mon, 26 Jun 2023 06:20:00 +0000

Hey everyone,

I'm excited to share a side project I've been working on - Vue Email Components.

The primary objective of this project is to simplify the process of creating emails and to make it more accessible for everyone. MySigMail Vue Email Components is a collection of high-quality, unstyled components for creating beautiful emails using Vue.

Key Features:

Reduces the difficulty of coding responsive emails: Helps ease the challenges of development and ensures consistency across various email clients, such as Gmail, Outlook, and others.
Pre-built components: This project includes a collection of components that can be used to create impressive emails without the hassle of manually creating tables and managing outdated code. Components include MBody, MButton, MColumn, MContainer, MHead, MHeading, MHr, MHtml, MImage, MLink, MPreview, MSection, MText and many more.
Client Application: This repository also contains a client application that serves as a local testing environment. Using this client, you can create email templates by selecting from pre-built components, apply styles to these components, preview the final render, and obtain the corresponding HTML code.

This project was inspired by react-email and aims to bring similar functionality to the Vue ecosystem. I'd love to hear your thoughts, feedback, and suggestions for improvements. Feel free to check out the repository and contribute if you're interested!

mysigmail / vue-email

A collection of high-quality, unstyled components for creating beautiful emails using Vue.

Vue Email Components

A collection of high-quality, unstyled components
for creating beautiful emails using Vue.

Demo

SPONSORS

Support

If you find this project useful, you can support development via the following methods:

Introduction

Reduces the difficulty of coding responsive emails, easing the challenges of development and ensuring consistency across various email clients, such as Gmail, Outlook, and others.

Motivation

Email still remains one of the most widely used and popular communication channels to this day, and its popularity shows no signs of diminishing over time.

We aim to simplify the process of creating emails and make it more accessible for everyone.

Install

pnpm add @mysigmail/vue-email-components

Use

Global

import { createApp } from 'vue'
import App from './App.vue'
import VueEmail from '@mysigmail/vue-email-components'

createApp(App).use(VueEmail).mount('#app')

Local

<script setup>
import { MButton } from '@mysigmail/vue-email-components'
</script>
<

…

View on GitHub

massCode v3 - An open source snippets manager is out 🚀

Anton Reshetov — Mon, 05 Sep 2022 18:03:05 +0000

What it is and why

massCode is a snippet manager for developers that helps you conveniently organize pieces of code and have quick access to them. Multilevel folders and tags are used for organization, and each snippet has fragments for even more granular structuring. The app supports Markdown so it can be used as a notebook if needed.

What's New

Direct support for TextMate grammars

Now massCode uses Codemirror as the basis for the editor and .tmLanguage as the grammar for syntax highlighting. This tandem opens the door to over 600 existing grammars. The application currently supports more than 160 grammars. In addition to .tmLanguage, the application supports .tmTheme for themes.

Real-time Render for HTML & CSS

Now you can see the result of HTML & CSS directly in the application. This is such a CodePen on minimal 😀

Mermaid Diagram

Added support for Mermaid - diagramming and charting tool that renders Markdown-inspired text definitions to create and modify diagrams dynamically.

Presentation Mode

massCode allows you to make a presentation out of a sequence of snippets. It's great for classroom use, team meetings, conferences or simply reviewing notes on your own.

Screnshots

Create beautiful snippet images on different backgrounds and in different modes.

Localization

massCode is available in English, Español, Português (Brasil), Русский, 中文 (简体), 中文 (繁體), 中文 (繁體香港特別行政區) & 日本語 languages.

massCodeIO / massCode

A free and open source code snippets manager for developers

massCode

Built with Electron, Vue 3 & Codemirror.
Inspired by applications like SnippetsLab and Quiver

Latest Release | Documentation | Change Log

Extensions VS Code | Raycast | Alfred

SPONSORS

Support

massCode is open source project and completely free to use.

However, the amount of effort needed to maintain and develop new features for the project is not sustainable without proper financial backing. You can support massCode development via the following methods:

Features

Organization

massCode allows you to organize snippets using multi-level folders as well as tags. Each snippet has fragments - tabs, which gives even greater level of organization.

Editor

massCode uses Codemirror as the basis for the editor and .tmLanguage as the grammar for syntax highlighting. This tandem opens the door to over 600 existing grammars. The application currently supports more than 160 grammars. In addition to .tmLanguage, the application supports .tmTheme for themes. There is also…

View on GitHub

Best regards,
Anton

massCode v2 - An open source snippets manager is out to beta 🎉

Anton Reshetov — Wed, 13 Apr 2022 18:09:23 +0000

Hi, there!

For a long time I did not have free time to develop massCode v1 and I am exited that massCode v2 is out to beta.

Goal

The v1 code base is simply obsolete. massCode v1 was written using Electron v7, Vue 2, and JavaScript. The new version of massCode is based on Electron 16, Vue 3, and TypeScript. The only option to use the latest technology is to start from scratch, since rewriting the current code base is pretty much like starting from scratch, except that a lot of time will be spent migrating to the new requirements of the technology in use. This also includes updating dependencies.

Electron v16 makes it possible to create a build for M1, Vue 3 & Vite is a very fast development and final build of the frontend of the application, TypeScript is a typing tool which gives less time for the subsequent development.

In the new version of the application I am abandoning Monaco editor in favor of Ace editor, as it is a lighter weight library. Ace also supports much more language syntax highlighting and TextMate, which is more widespread than the proprietary Monarch for Monaco editor.

The new version will have a database based on plain JSON. In v1 it was used for this purpose library NeDB, which is no longer supported by the author and has bugs. Also, new version will have API server available on localhost, which will allow integration with any third-party applications, such as Raycast or Alfred.

Features

Organization

massCode allows you to organize snippets using multi-level folders as well as tags. Each snippet has fragments - tabs, which gives even greater level of organization.

Editor

A snippet manager must not only provide organization of snippets but also have a good code editor. That's why under the hood of massCode there's Ace. Ace is a high performance code editor which supports syntax highlighting for over 170 languages. I also added a Prettier to code formatter.

Markdown

massCode allows you to write in Markdown and also provide syntax highlighting inside a code block. And of course there is a preview.

Search

It is impossible to imagine a productive snippets manager without quick access to snippets. Therefore massCode has a fast full-text search with highlighting of the search query.

Autosave

massCode automatically saves any changes you make during work, so you don't have to worry about losing changes.

Sync

You can use any service that provides cloud synchronization, such as iCloud Drive, Google Drive, Dropbox or other similar.

Database

massCode uses a simple JSON to store your data. The database files are on your local computer.

API Server

Coming soon.

I hope that my app will be useful to someone.

massCodeIO / massCode

A free and open source code snippets manager for developers

massCode

Built with Electron, Vue 3 & Codemirror.
Inspired by applications like SnippetsLab and Quiver

Latest Release | Documentation | Change Log

Extensions VS Code | Raycast | Alfred

Support

massCode is open source project and completely free to use.

Features

Organization

massCode allows you to organize snippets using multi-level folders as well as tags. Each snippet has fragments - tabs, which gives even greater level of organization.

Editor

View on GitHub

Best regards, Anton.

Image Optimizer

Anton Reshetov — Thu, 09 Dec 2021 11:25:12 +0000

Recently I decided to try Vite in tandem with Electron for self-development purposes. I ended up with a small project.

I don't doubt there are lots of cool tools like this on the net, but I think mine will complete that list. Enjoy using it

antonreshetov / image-optimizer

A free and open source tool for optimizing images and vector graphics.

Image Optimizer

Built with Electron, Vue & Vite.

A free and open source tool for optimizing images and vector graphics.

Core libs

Download and Installation on macOS

Go to Releases get the latest build, download and install.

Development

# install dependencies
yarn
# serve with hot reload
yarn dev

Build

# build application for production
yarn build

Electron Vue Vite Boilerplate

View on GitHub

massCode - open source snippets manager is out to v1.0 🎉

Anton Reshetov — Thu, 27 Feb 2020 18:12:29 +0000

Hi, there!

I am excited that massCode is released to version 1.0.

The goal of creating this application was mostly my own growth as a developer. Also, I wanted this project to absorb the best of such applications already on the market (both free and paid). At the same time, I wanted this project to be an open source project. This is also my first experience in developing applications on Electron.

I was inspired by applications like SnippetsLab, Quiver, Boostnote.
SnippetsLab & Quiver are native MacOS applications. Boostnote is a cross platform application because it is written using Electron. Inside Boostnote, it uses React.

I also took Electron as a basis to provide cross platforming. Since I'm a big fan of Vue, my app seems to be written in Vue.
massCode allows you to organize snippets using multi-level folders as well as tags. Each snippet has fragments - tabs, which gives even greater level of organization.

A snippets manager must not only provide organization of snippets but also have a good code editor. That's why under the hood of massCode there's Monaco editor. Monaco is a modern code editor from Microsoft which is used in one of the most popular editor VS Code. The editor provides IntelliSense, validation for TypeScript, JavaScript, CSS, LESS, SCSS, JSON, HTML. It's also added a super productive Emmet and Prettier to code formatter.

I hope that my app will be useful to someone.

antonreshetov / massCode

This repository is outdated and no longer maintained. A new version of massCode is available! https://github.com/massCodeIO/massCode. A free and open source code snippets manager for developers.

massCode

Project is no longer maintained, and may have bugs and security issues. Feel free to fork but no pull request or security alert will be answered.

This is the repository for massCode v1. A new version of massCode is available in this repository.

A free and open source code snippets manager for developers.

Built with Electron, Vue & Monaco editor.
Inspired by applications like SnippetsLab and Quiver

Official Website | Documentation | Change Log

Supporting

massCode is open source project and completely free to use.

Overview

The goal of creating this application was mostly my own growth as a developer. Also, I wanted this project to absorb the best of such applications already on the market (both…

View on GitHub

Best regards, Anton.

massCode – An open source code snippets manager is out to v1

Anton Reshetov — Mon, 20 Jan 2020 08:56:55 +0000

Hi there,

massCode developer here.

I am excited to introduce my app.

The main feature is a modern editor - Monaco, which is used in VS Code. Among the advantages of the editor are rich IntelliSense, validation for TypeScript, JavaScript, CSS, LESS, SCSS, JSON, HTML. For more productivity, Emmet was added.

The next feature is the tray assistant, which can be called with the help of hotkeys, thus having quick access to the snippets collection from any application.

I'll be glad to hear your feedback!

https://masscode.io/

antonreshetov / massCode

This repository is outdated and no longer maintained. A new version of massCode is available! https://github.com/massCodeIO/massCode. A free and open source code snippets manager for developers.

massCode

Project is no longer maintained, and may have bugs and security issues. Feel free to fork but no pull request or security alert will be answered.

This is the repository for massCode v1. A new version of massCode is available in this repository.

A free and open source code snippets manager for developers.

Built with Electron, Vue & Monaco editor.
Inspired by applications like SnippetsLab and Quiver

Official Website | Documentation | Change Log

Supporting

massCode is open source project and completely free to use.

Overview

The goal of creating this application was mostly my own growth as a developer. Also, I wanted this project to absorb the best of such applications already on the market (both…

View on GitHub

massCode just released to v0.3.4

Anton Reshetov — Thu, 09 Jan 2020 13:07:06 +0000

Hey folks,
massCode just released to v0.3.4

Available Mac, Linux and Windows versions.
We are waiting for feedback and bugs ))).

antonreshetov / massCode

This repository is outdated and no longer maintained. A new version of massCode is available! https://github.com/massCodeIO/massCode. A free and open source code snippets manager for developers.

massCode

Project is no longer maintained, and may have bugs and security issues. Feel free to fork but no pull request or security alert will be answered.

This is the repository for massCode v1. A new version of massCode is available in this repository.

A free and open source code snippets manager for developers.

Built with Electron, Vue & Monaco editor.
Inspired by applications like SnippetsLab and Quiver

Official Website | Documentation | Change Log

Supporting

massCode is open source project and completely free to use.

Overview

The goal of creating this application was mostly my own growth as a developer. Also, I wanted this project to absorb the best of such applications already on the market (both…

View on GitHub