Yes, we will land on Firefox very soon, hopefully next month.
Copilot's been very useful. The extension is built on TS and lots of custom CSS. Codex is knowledgeable with browser extension APIs and it's helped me to write most CSS utility classes that change sizes, margins and paddings, so that I don't have to bundle the extension with another third-party library.
I've been using Copilot for 5 months while building another AI productivity tool. It's changed my habits my I'm becoming a bit dependent on it for autocompletion. It feels so good just hitting TAB and moving on.
I know some developers that aren't embracing it the same way I do, making judgements without even trying it. "This is the future", I tell them, "it makes your life much easier", but there's resistance.
Prompt engineering is quite interesting too, and it may turn into a job skill later. While using Codex, I understood the importance of knowing how to ask for the right things to a non-human. Is bit like talking to Alexa in the early days, in the sense that I couldn't talk to Alexa like a human yet, I had to be specific, clear and intentional. I still see that people who are less experienced with a smart personal assistant struggle to get their commands done.
If you love this technology and would love to try it for Explaining Code in your browser, check out the extension ExplainDev (https://explain.dev). It works on GitHub, StackOverflow and documentation websites.
Disclaimer: I built ExplainDev, with the help of Copilot.
I like Carbon, the option of creating new themes and saving snippets. Is the project still alive? I got a message from Open Collective [0] saying they stopped accepting donations.
kmdr-cli[0] won't go away. It's definitely our base and when we launched with it initially, we learned that people are willing to install and wanting to have something that's running in their terminal. What prompted us to focus on the browser, was that a huge number of our queries (55%) were coming from our demo page on our website. We're a team of 3, so investing in the browser extension meant a hault to progress in kmdr-cli but we fully intend to re-invest there and bridge browser and kmdr-cli. This morning we updated the kmdr-cli to leverage the same definitions available on the browser extension. Next will be to leverage the same parser.
Maker here. kmdr works on any website where code is selectable, including on GitHub or GitLab, in official documentation, StackOverflow, or web-based chat. In a pop-up window, kmdr will describe each attribute of the commands: programs, options, subcommands, operators, etc.. All feedback welcome! Thanks!
Noted. We have to add more details as to why kmdr cli today doesn't pull from your system.
The biggest obstacle for doing that is parsing manpages. Kmdr uses explainshell.com's parser for extracting options from manpages, but the parser fails to detect many options and subcommands' options. Kmdr's repository of definitions extends past man page parsing thanks to human verification and additions that help us to explain commands with subcommands, e.g. docker, kubectl, docker, git, npm, yarn, pip, etc..
And some new CLI programs don't ship with their manpages at all. I've also seen some manpages that don't match the specific version/release of a program installed on the OS.
Prompt: What's funny about this image?
Bard: Sorry, I can't help with images of people yet.