<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Osman Bineev</title>
    <description>The latest articles on Forem by Osman Bineev (@algebraicbrain).</description>
    <link>https://forem.com/algebraicbrain</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F132556%2F33cd891f-0b7b-4ab2-864c-823b622d819d.jpeg</url>
      <title>Forem: Osman Bineev</title>
      <link>https://forem.com/algebraicbrain</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/algebraicbrain"/>
    <language>en</language>
    <item>
      <title>Why I built a local terminal workspace instead of using tmux</title>
      <dc:creator>Osman Bineev</dc:creator>
      <pubDate>Wed, 22 Apr 2026 05:59:43 +0000</pubDate>
      <link>https://forem.com/algebraicbrain/why-i-built-a-local-terminal-workspace-instead-of-using-tmux-288l</link>
      <guid>https://forem.com/algebraicbrain/why-i-built-a-local-terminal-workspace-instead-of-using-tmux-288l</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fyf69ei6mst087gj5ey19.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fyf69ei6mst087gj5ey19.png" alt="mtrm" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I wanted a terminal workspace that behaves more like a normal desktop app.&lt;/p&gt;

&lt;p&gt;Something that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;keeps tabs and splits&lt;/li&gt;
&lt;li&gt;restores layout and working directories after restart&lt;/li&gt;
&lt;li&gt;uses normal Ctrl+C / Ctrl+V with the system clipboard&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I tried tmux for a while and realized it solves a different problem.&lt;/p&gt;

&lt;p&gt;It’s great for remote sessions, long-lived processes, and connection resilience. But my workflow is strictly local. I don’t need to keep processes alive or reconnect to sessions — I just want a workspace with predictable behavior.&lt;/p&gt;

&lt;p&gt;I also didn’t like the configuration model. Getting comfortable meant setting options, remembering configs, and often adding plugins. For a personal tool, that felt like unnecessary overhead.&lt;/p&gt;

&lt;p&gt;So I built a small tool around this idea:&lt;br&gt;&lt;br&gt;
&lt;a href="https://github.com/algebrain/mtrm" rel="noopener noreferrer"&gt;https://github.com/algebrain/mtrm&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It runs local shells, supports tabs and splits, restores layout and working directories on restart, and keeps things simple.&lt;/p&gt;

&lt;p&gt;If you’ve built your own terminal setup or found a different approach, I’d be curious to hear about it.&lt;/p&gt;

</description>
      <category>terminal</category>
      <category>productivity</category>
      <category>rust</category>
      <category>cli</category>
    </item>
    <item>
      <title>Writing a plugin for the Faqtor task runner</title>
      <dc:creator>Osman Bineev</dc:creator>
      <pubDate>Tue, 11 Jun 2019 17:50:12 +0000</pubDate>
      <link>https://forem.com/algebraicbrain/writing-a-plugin-for-the-faqtor-task-runner-537a</link>
      <guid>https://forem.com/algebraicbrain/writing-a-plugin-for-the-faqtor-task-runner-537a</guid>
      <description>&lt;p&gt;Writing a plugin for Faqtor is a simple and straightforward process. Schematically, it looks like this (TypeScript code):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="nx"&gt;faqtor&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="err"&gt;“&lt;/span&gt;&lt;span class="nx"&gt;faqtor&lt;/span&gt;&lt;span class="err"&gt;”&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; 

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;createFactor&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(....&lt;/span&gt;&lt;span class="nx"&gt;arguments&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt; &lt;span class="nx"&gt;faqtor&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;IFactor&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;

    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;run&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="p"&gt;():&lt;/span&gt; &lt;span class="nb"&gt;Promise&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nb"&gt;Error&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="p"&gt;....&lt;/span&gt;&lt;span class="k"&gt;do&lt;/span&gt; &lt;span class="nx"&gt;some&lt;/span&gt; &lt;span class="nx"&gt;work&lt;/span&gt; &lt;span class="nx"&gt;here&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;

    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;factor&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;func&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;run&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Let us examine this with the example of the faqtor-of-rollup plugin, intended, as the name implies, to use Rollup bundler in our projects. &lt;a href="https://medium.com/@bineev/writing-a-plugin-for-the-faqtor-task-runner-4c8e967546b9"&gt;Continue reading&lt;/a&gt;&lt;/p&gt;

</description>
      <category>typescript</category>
      <category>javascript</category>
      <category>node</category>
      <category>npm</category>
    </item>
    <item>
      <title>HyperOOP SPA framework: now with detailed and more explanatory Readme </title>
      <dc:creator>Osman Bineev</dc:creator>
      <pubDate>Mon, 27 May 2019 19:39:35 +0000</pubDate>
      <link>https://forem.com/algebraicbrain/hyperoop-spa-framework-now-with-detailed-and-more-explanatory-readme-34fc</link>
      <guid>https://forem.com/algebraicbrain/hyperoop-spa-framework-now-with-detailed-and-more-explanatory-readme-34fc</guid>
      <description>&lt;p&gt;Since my last posting about HyperOOP, I have received many complaints about the Readme file. Now the file is more complete and (I hope) clearly describes the &lt;a href="https://github.com/hyperoop/hyperoop"&gt;framework&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>frontend</category>
      <category>spa</category>
      <category>javascript</category>
      <category>typescript</category>
    </item>
    <item>
      <title>Hyperoop: OOP-style SPA micro-framework.</title>
      <dc:creator>Osman Bineev</dc:creator>
      <pubDate>Mon, 20 May 2019 19:11:52 +0000</pubDate>
      <link>https://forem.com/algebraicbrain/hyperoop-oop-style-spa-micro-framework-di9</link>
      <guid>https://forem.com/algebraicbrain/hyperoop-oop-style-spa-micro-framework-di9</guid>
      <description>&lt;h3&gt;Quick start&lt;/h3&gt;

&lt;pre&gt;
  git clone https://github.com/HyperOOP/starter myapp
  cd myapp
  npm i
  npm start
&lt;/pre&gt;

&lt;h3&gt;More examples&lt;/h3&gt;

&lt;p&gt;Look at &lt;a href="https://github.com/hyperoop/hyperoop"&gt;Readme&lt;/a&gt;&lt;/p&gt;

</description>
      <category>frontend</category>
      <category>spa</category>
      <category>javascript</category>
      <category>typescript</category>
    </item>
    <item>
      <title>Faqtor: Promise-based task runner. Easy to use, easy to extend. </title>
      <dc:creator>Osman Bineev</dc:creator>
      <pubDate>Mon, 28 Jan 2019 17:07:23 +0000</pubDate>
      <link>https://forem.com/algebraicbrain/faqtor-promise-based-task-runner-easy-to-use-easy-to-extend--3lj7</link>
      <guid>https://forem.com/algebraicbrain/faqtor-promise-based-task-runner-easy-to-use-easy-to-extend--3lj7</guid>
      <description>

&lt;p&gt;&lt;a href="https://github.com/faqtor/faqtor"&gt;Faqtor&lt;/a&gt; is Promise-based task runner / build automation system for the NodeJS ecosystem. Existing plugins support &lt;a href="https://www.npmjs.com/package/faqtor-of-rollup"&gt;rollup&lt;/a&gt;, &lt;a href="https://www.npmjs.com/package/faqtor-of-uglify"&gt;uglify-js&lt;/a&gt;, &lt;a href="https://www.npmjs.com/package/faqtor-of-browser-sync"&gt;browser-sync&lt;/a&gt;, &lt;a href="https://www.npmjs.com/package/faqtor-of-handlebars"&gt;handlebars&lt;/a&gt; and some other tools. I would appreciate any feedback or support.&lt;/p&gt;


</description>
      <category>npm</category>
      <category>javascript</category>
      <category>taskrunner</category>
      <category>buildautomation</category>
    </item>
  </channel>
</rss>
