Hey thank you! OP here, yes I was struggling to find large enough documents to run the benchmarks on, the range currently on the benchmark data is ~106 B - ~190MB, which I think covers the majority of quick task workloads, but would love to have large documents, if there's an public ones you can thinking of I'd like to know!
Hey! This is the jsongrep author, just wanted to give a little intro to the jsongrep tool. I started this project as part of my undergrad research and kept iterating on it. I'm super happy with how performant it is and I have found it incredibly useful for my day-to-day work, for example combing through long OpenAPI specs and combining with other tools like `fzf` and `rg`. Happy to answer any questions about the tool!
I just published a deep dive on Ken Thompson’s Reflections on Trusting Trust, where he talks about the compiler-level backdoor he described in his 1984 Turing Award lecture that would let him login on compromised systems.
The post walks through how a compiler can teach itself to hide a Trojan that reproduces even after the source is “clean” and annotated snippets from Thompson’s actual code (shared by Russ Cox).
Would love feedback or corrections, especially from folks who’ve studied or implemented compiler bootstrapping or reproducible-build systems.
Been trying it out for a few hours and love it! One feature that I do miss from Kitty is the cursor trail when your cursor moves in a buffer. Excited to see what Ghostty does in the future and thank you for a great new terminal!
Recent data from Stanford's AI Index 2024 report and BLS projections suggest AI is more likely to augment software professionals than replace them. The article draws parallels with the historical impact of spreadsheets on accounting and explores how tools like GitHub Copilot Workspace might transform the industry. It challenges the common narrative of AI-driven job loss with evidence-based optimism.
I fully agree, at the end of the day whichever tool makes you the most efficient/excited to code is the best tool for you. I am still transitioning from VSCode to Neovim and I can definitely relate to VS Code feeling more easily malleable.
It looks like my submission redirected to the GitHub repo instead of displaying the full context. Here’s the detailed information about Vimtutor Sequel:
---
Hey Hacker News community,
I'm excited to share something I've been working on - Vimtutor Sequel!
After going through the original vimtutor, I felt there was a need for an extended tutorial for some more advanced topics not covered in the original tutor program.
What's Vimtutor Sequel?
Vimtutor Sequel picks up where the original vimtutor left off. It’s designed for those who already know the basics and are ready to dive into more advanced Vim features and commands.
Key Features:
- Advanced Topics: Dive into splits, spellcheck, advanced search and replace, macros, Vim scripting, plugins, sessions, and registers.
- Step-by-Step Tutorials: Hands-on lessons that encourage you to practice commands as you learn.
- Custom Vim Configuration: Comes with a custom vimrc to ensure a consistent learning experience and mimic the original vimtutor.
How to Install:
For Mac:
To get started, install Vimtutor Sequel using Homebrew:
```bash
brew tap micahkepe/vimtutor-sequel
brew install vimtutor-sequel
```
Then you can run with:
```bash
vimtutor-sequel
```
3. Make a Copy of the Tutorial:
```bash
cp vimtutor-sequel.txt vimtutor-sequel-copy.txt
```
4. Run Vim with the Custom Configuration:
```bash
vim -u vimtutor-sequel.vimrc vimtutor-sequel-copy.txt
```
Looking for Feedback!
I'd love to hear what you think! Whether you spot any bugs, have suggestions for new lessons, or just want to share your thoughts, your feedback is really appreciated. Feel free to contribute or open issues on the GitHub repo.
[1]: https://github.com/micahkepe/jsongrep/releases/tag/v0.8.0