If you’d like to learn more about Haptic, why it’s being built, what its goals are and how it differs from all the other markdown editors out there, you can read more about it here.
As others have noted, the app doesn’t work on mobile yet. Anybody willing to share the content here for mobile users?
That basic idea is roughly how compression works in general. Think zip, tar, etc. files. Identify snippets of highly used byte sequences and create a “map of where each sequence is used. These methods work great on simple types of data like text files where there’s a lot of repetition. Photos have a lot more randomness and tend not to compress as well. At least not so simply.
You could apply the same methods to multiple image files but I think you’ll run into the same challenge. They won’t compress very well. So you’d have to come up with a more nuanced strategy. It’s a fascinating idea that’s worth exploring. But you’re definitely in the realm of advanced algorithms, file formats, and storage devices.
That’s apparently my long response for “the other responses are right”
The configuration is often committed to the repo. And some repos heavily rely on the precommit actions running before you can push or have pipelines function correctly
100%
I know a guy that considers git pre-commit hooks a form of code injection and thus a security risk. So he disables them on repos he works with. And to be fair, it’s absolutely a viable vector for attacking developer machines. I think a tasks.json fits into that exact same bucket.
These kinds of automations are suuuper useful and I do like to use them. But also review a code base before cloning!
deleted by creator
Interesting. When I first viewed this post, there were 3 downvotes and only 2 upvotes. Is this not the type of content that people want to see here?
I’ll check back again later and see if/how those numbers change.
A complicated plugin ecosystem (e.g. Jenkins) makes for a terrible use experience. It’s annoying to configure a bunch of config files. Managing dependencies can be a complete nightmare. these problems also complicate your ci/cd.
So I’ll offer a slightly different answer. I prefer a single file instead of splitting up the config. And I’ll use OpenTelemetry as an excellent example of why. the plugins are compiled right into the app binary. This offers a ton of advantages, including a great reason to merge all of your app configs in a single file.
This really only works well if you have a good app though.
My pleasure. Thanks for posting! And feel free to ask more questions as you tackle this one.
I’m on my phone so I can’t really test these out. But this should give you a few methods for printing the list of files changed.
Here’s a similar page to show the changes for a specific file. I expect that git blame will be similarly useful.
A few others that may help you get started as well:
git —help
git rev-parse
git log
git history
Yikes! Is this a one-time task?
Well this is definitely a bit odd. Send like those comments should be included with the original change. Or maybe they shouldn’t be recorded as comments at all and they should be a git commit message. And where does that hard copy report come from? Anyways, back to your actual question.
At this point, I’m still suggesting a tiny utility to assist with adding the comments. It looks like %ATTCHANGE and %REM are part of a very sort list of possible values. If so, a little cli tool can definitely help there. It could also handle the general comment structure and the changed value easily. Do these comments ever include something besides #ACCEPTED?
The tricky part is the ‘12.24/4’. It sounds like you go through the report and then find the files/lines to create these comments. Is that right? It would be tricky to code a cli tool for doing that because you need to jump around between files.
Last note for now, some simple git commands can definitely help you here. You could easily generate a list of changed files and lines. Another could show you the changed text. For any given change. Etc.
Can you give an example of the change and your comment for a single file?
2000 is a lot of files. If you need to do this often, it might be best to build a small cli tool to make this easier or fully automated. It really depends on how you choose to create those comments.
pop-ups (which disappear when I start typing) or a dedicated diff-view which takes up too much space on my small monitor
What kind of experience are you looking? Apparently, something small that persists while you type. Think you could share some more details?
I think GitLens has some features based on git diff , though I haven’t personally explored them much. Note that many of its features are locked behind a paid license. They’ll give a trial though to test everything for free. But the free features are definitely quite nice!
For debugging across disparate app, hosts, etc.,x I think the best current option is spans and traces. If you aren’t already familiar, look into general observability, logs/metrics/traces, and definitely opentelemetry!
Wait. Who’s genocidal here?
I certainly don’t have an answer for you. Sorry 🙂
I’m super curious about your motives and goals though. Why do you want to do this??
Well that’s cool. Sounds like the workspace extensions are inspired by the tools.go pattern. Something that I recommend any go developer dig into!
I recently discovered k3d. It’s a light wrapper around k3s, which is kubernetes on docker. It’s amazingly easy to use! If you have docker installed, you can learn the commands and create a k8s cluster in under 5 minutes.
For anyone like me that likes k8s, k3d is a fantastic alternative to docker compose!
I’m really not sure if “Failed to load media” is a voyager error or the real post 🫠