sweep VS miryoku

What's the difference with https://sweep.dev ?

- https://sweep.dev have a bot where you create a GitHub comment and it writes the PR to fix it. They have between 30% and 70% success rate. This is pretty bad but they're one of the best today

6️⃣ Sweep AI 🧹

https://github.com/sweepai/sweep arguably already does the work of an "average" programmer

The GitHub repo I researched and found was a repo that utilizes UI to create code changes based on user bug reports https://github.com/sweepai/sweep. This feature works with small errors and is aimed to eliminate developers from opening tickets that involve small bug fixes or refractors. I know that learning a new language often has many set backs and learning curves. After finding this project I believe I can learn some basics of Python while also utilizing UI.

I wanted to share how we got Sweep, an AI-powered junior developer, to use the latest pytorch documentation. We wrote a simple webcrawler using Playwright, which bypasses a lot of issues while scraping. Also, because we only need to crawl documentation, we can filter out common tags in markdown. This lets us accurately crawl and index any docs site. Try it now at https://github.com/sweepai/sweep! You can add docs by going to your sweep.yaml and adding both the keyword and the url.

We have that! You can directly append to our system prompt here to customize Sweep https://github.com/sweepai/sweep/blob/main/sweep.yaml

I've seen https://github.com/manna-harbour/miryoku but it doesn't appear to be easily modified.

A 75% keyboard still require quite a lot of wrist movement, which is not ideal in your situation. It's better to learn to use layers, you could still have all the function keys and such with a 36 or 34 keys. With with such a small keyboard you don't need to move your wrist while typing. A Corne or even a Ferris Sweep can do the job with a proper keymap, like Miryoku.

If you prefer to have semicolon on Base you'd substitute custom Base, Nav, and Sym layers, swapping semicolon and slash, with https://github.com/manna-harbour/miryoku/discussions/85.

The Miryoku layout [1] has a dedicated number layer which turns the left half into a number pad. Practical (once you get used to it) and portable.

[1] https://github.com/manna-harbour/miryoku

It's understandable if some people would prefer a larger layout. I wouldn't argue people should be using smaller keyboards.

It's "I don't mind moving my hand to hit the key" vs "I don't mind holding down some Fn key to hit the key". (Or with F1-F12 on Macbooks, you need to both hold down a Fn key and move your hand).

For an example of "36 keys ... how", I think the popular miryoku layout is fascinating. https://github.com/manna-harbour/miryoku/tree/master/docs/re... -- Often, mnemonics for particular keys aren't all that complicated.

Except for those who use Miryoku, which is not optimized for software development, probably every single person here will have its own custom keymap.

The keyboard on the other desk is a wireless Corne low profile kit I built up a while back using a couple nice!nano controllers and their low power display too. For general typing I don't have much of a problem going back and forth between the two, but the Corne is only 34 keys and I use a complex layout called Miryoku to get access to most symbols and functions I have by default on my 360.