Braille characters would double the horizontal resolution but halve the already limited vertical resolution, which isn’t great for something that’s intended to be displayed inline with text.
I think Teletext might be even worse. IIRC, it only has three heights for its triangles.
Teletext also has the “smooth” characters that have inclined lines. I’d need to take a good look at them to understand how to use them, but if you can lose the vertical precision, it’s OK, because you pack more in the horizontal axis.
As for Braille, the last Unicode standard added Kaypro’s 2x4 mosaics, so we can stop misusing Braille for that (a huge relief to me, because the banding that often happens always annoys me).
> I switched back to main after noticing that the plugin branch adds about 1s to startup time
Very curious what’s happening there. With empty helix.scm/init.scm, there is essentially zero measurable impact on startup for me.
Bytecode caching isn’t yet enabled (it is in progress), so I can see that kind of delay if I’m giving it tens of thousands of lines of code to evaluate on startup, but it took a lot of effort to get there.
It’s easy to build from source though, I’ve been using it daily for over a year, and there already are several dozen reasonably sophisticated plugins available. You can browse a list of mine here: https://github.com/stars/waddie/lists/helix-plugins-steel-li...
Talking to the person who gave it to you, in my experience.
In my own testing, Pangram is excellent at detecting the default output styles of LLMs.
If you tell the LLM to change its output style, so it’s not full of “load-bearing spaced em dashes that aren’t X, they aren’t Y. they’re Z.” constructions (which humans are pretty good at detecting on their own), the false negative rate soars.
I’d love to see the other repo, and the prompts that led to both.
Did Godier copy the other guy’s repo, name and all, and try to pass it off as his own work? That seems like the obvious conclusion, albeit brazen to the point of insanity.
Did Claude copy the repo, in response to a prompt? If Claude copies a Claude vibe-coded project, can any plagiarism really be said to have taken place?
Or is this just what Claude is statistically likely to spit out if you prompt it to build an astronomy app and leave it to it?
You can trace back to the original repo from that thread. The key points are that the copy had
1. The same name. One was "Dark Hours" and the other was "DarkHours".
2. The same highly specific bug. I didn't investigate closely but from the description the bug sounds too unique to have been identically created in a fresh Claude-style duplication.
The duplicated name is the most damning part to me. I've never tried to copy a project with Claude, but I can't imagine the sequence of events that would lead to Claude copying the name of a repo but going to lengths to disguise other things like stripping the license. This all seems highly intentional, like someone thought it would never be noticed.
A name clash is the least damning evidence in my opinion. Last year my previous employer asked us for suggestions for naming an AI agent. Everyone produced pretty much the same list, because everyone just asked ChatGPT.
Except me. I had also asked ChatGPT, but I bothered to google the suggestions and found there were already like half a dozen AI agents for every suggestion.
(they ultimately launched what was by then the 7th or 8th AI-related product with essentially the same name)
Creativity in naming doesn’t seem to be their strongest suit.
If the copying was deliberate then why admit to the similarity? He should have just blocked the guy and continued as if nothing was wrong. Admitting the plagiarisation lead to a worse outcome every time.
> TE has no register for hedging, ownership of an opinion, or acknowledging that a reasonable person would disagree. Modality is roughly can / must / do not. […] Where a thought can't be said in STE without becoming a lie, I'd mark it and say it plainly rather than mangle it. Confidence and disagreement are the two things I'd insist on smuggling through.
My understanding was the biggest issue has always been that javac is a poor foundation for any kind of live tooling like LSPs?
It’s less “make me a Java LSP” than “rewrite javac around incremental compilation and exposing a semantic DB”. Which sounds like a much harder problem.
I was thinking of JEP 484, which I guess technically isn't a compiler API as much as it is a class file API, but that's kind of a big deal for this type of work as probably the primary work the parts of the classpath you currently aren't editing, moreso than parsing a single .java-file, and the kludges we had before this API (e.g. ASM) were incredibly fragile.
You could create a third-party tap to install wine via homebrew.
reply