My experiences with Kilo Code CLI TLDR; don’t bother, this is unusable. Take the model switcher for instance. You might expect to type /model and then be prompted with a list of models to choose from. You might use arrow or vim keys to navigate the list, maybe even type to filter the list. Well fuck you, that’s not happening. It brings up a help menu which claims you need to use /model select <modelname> to select a model. You type that, autocompleting the select command, expecting to get a model list to choose from just like you got a subcommand list. No can do, delete what you typed, you need to use the list command to actually get the model names. You then manually copy the model name from that (If you’re unlucky, you have to use the awful pagination system, typing /model list next a few times. ...
Video.md Basic idea I have an idea for a video editing tool based on markdown. It works the following way: Transcribe the video using AI into a timestamped subtitle file. Convert that subtitle file into a markdown file, preserving the timestamps in a format that is both human and machine readable. Now I can read the entire video in text form. After making edits to the markdown file, the program can edit the video itself according to the edits I made to the markdown file. ...
I marvel at the inability of huge publishers to build what should be a simple app. Sure, taken as a whole, what a store does is pretty complex, but it can be broken down into smaller problems, each of which has been solved already. Those problems were not easy to solve, it took thousands of hours of work from talented and smart people. Why do you try and fail to solve them yourself? ...
UPDATE This article is an early idea of what the tool could be. Since I wrote it, it has evolved and changed a lot. Stay tuned for more infos about the current version of the tool. The tool has since been renamed to ins The problem I do not trust many cloud save systems. Partially that’s not their fault. I am on Linux, so everything EpicGames is janky (even more than on Windows). Steam is pretty good, but even there, the cloud save system occasionally refuses to sync. ...
Are there really none? We are now years into the transition to wayland, yet one problem still remains: There is no dmenu replacement. Instantmenu is based on dmenu, which remains stuck on X11, which is becoming a problem. You might say ’look at fuzzel/rofi/whatevershinynewthing’, but they are not what dmenu was truly good at: Not interrupting my workflow. Instantmenu was truly tiny. And the very first thing it did was to grab my keyboard input. I could make it part of my typing flow, as I could use it purely from muscle memory without thinking about it. This is not possible with the wayland equivalents of it. They all take a variable and non-negligible amount of time to load. This means that if I continue typing before they loaded, the first few keystrokes will go to whatever application is currently in focus. Depending on what that application is, this could be annoying to disastrous. It also means those characters are not in the menu when it eventually opens. Double bummer. ...
UPDATE This article is an early idea of what the tool could be. Since I wrote it, it has evolved and changed a lot. Stay tuned for more information about the current version of the tool. The tool has since been renamed to ins Idea I want to unify lots of instantOS things into an instantCLI the base command will just be instant Dotfiles I wrote about ideas for dotfile management a while back. I thought about it some more. I am abandoning the “home dir as git worktree” approach. It’s just not flexible enough. ...
Edit This is an early draft of what the new ins arch instantOS installer actually became. The new installer works a bit different but is inspired by this scribble I did on my phone. Post This is written on my phone, really quick, dirty thoughts Rust installConfig struct instantosconfig { user: userconfig partitions: partitionconfig } serializable to toml -> reusable trait from_answers { fn from_answer(answers) -> Result Self } struct instantOSInstall { user: UserConfig } UserConfig = { username: string password: string } trait AskStep { fn collect_choices fn validate fn prompt } struct AskStepInfo { optional: bool AskStepType } enum Question { Input { default: Option<string> } SelectMultiple { choices } SelectOne { choices } YesNo } struct QuestionData { choices: map(QuestionType, data) answers: map(QuestionType, answer) } Enum QuestionType { UserName(UserNameQuestion), UserPassword(PasswordQuestion) } Alternative approach type StepId = string answerRegistry = Map<AnswerKind, Answer> ActiveQuestions = [AnswerKind] NodeRegistry = [AnswerKind, Node] build_dependencies while get_unsatisfied(unsatisfied) for step in step if step.conditions.active if step.unanswered return step struct stepCondition ValueEquals(stepID, val) ValueNot(stepID, val) ValueIn(stepID, vec val) goback() for answer in get_active() if active[i+1] == currentstep currentstep = active[i] trait Leaf<data> data: data leafkind: enum fn verify fn get_choices enum leafkind YesNo Input ChooseOne ChooseMulti Custom(lambda stuff) askLeaf(leaf) match leafkind YesNo data = gum ask SelectOne data = gum choose get_choices verify SelectMultiple data = gum choose get_choices verify struct Step { junction: Option<Vec<AskDependency>>, question: Option<Leaf(askstuff)> } struct AskDependency { name: string dependencies: [dependency] } partitionconfig depends on rootpartition bootloaderpartition fn get_unsatisfied(ActiveQuestions, NodeRegistry) sort active_questions by leaf first, junction second for question in active_questions if question.unsatisfied return question tech stack duct for commands gum for UI
My experiences with Cline Cline is an open-source AI-powered coding agent living in VS Code. I find VS Code rather annoying to use compared to Neovim and Zed. Cline is the thing making me keep a resource-hogging instance of VS Code open next to the other two. KiloCode and Roo Code made it seem like Cline is basically Debian, very conservative and purposefully behind in terms of features. From my experience that doesn’t seem to be the case. Cline has the most or most competent developers behind it compared to the other VS Code coders, and being mostly upstream from them has some features earlier or plain better than the others. ...
It’s horrible Stay away from it. They are not capable of delivering anything resembling good service. Horrible UI The UI is terrible. There is a dropdown menu called “Actions” at the top which for years has only contained a single action called “Delete”. Why not replace that with a button called “Delete”? By default the entry management UI shows a whopping 5 entries. There is a button which allows it to display all of them. So it’s either 5 or potentially hundreds or thousands, depending on what you’re using your domain for. No paging. ...
The state of Wayland I started instantWM in (I believe around) 2019. Wayland adoption was low. It had major open issues. Screen recording. Screen sharing. No support from Nvidia. No distros using it by default. No software ecosystem with utilities coming even close to what Xorg had. Some of these are still issues. Flameshot does not work by default on Wayland. It still complains after applying a few fixes. Espanso is really hacky on Wayland. Some features straight up do not work. ...