Edwin Kofler
@hyperupcall.bsky.social
Software Developer. Co-maintains SchemaStore, git-extras. Writer of a LOT of Bash. asdf contributor. I want to solve important problems.
Should have probably said, a significant subset of developers in the first sentence
July 1, 2025 at 11:49 PM
Should have probably said, a significant subset of developers in the first sentence
It's proprietary, which is generally disfavored among developers. It's also owned by Microsoft, which has made various moves that displace or discourage the use of existing open-source software. I've also been noticing that GitHub has become more slow and buggy
July 1, 2025 at 11:48 PM
It's proprietary, which is generally disfavored among developers. It's also owned by Microsoft, which has made various moves that displace or discourage the use of existing open-source software. I've also been noticing that GitHub has become more slow and buggy
Hmm, I didn't know about that perspective, even though I prefer savory foods! I like them as long as they're easy to remember and used frequently
May 19, 2025 at 3:45 AM
Hmm, I didn't know about that perspective, even though I prefer savory foods! I like them as long as they're easy to remember and used frequently
That looks so cool! Thanks for sharing
April 20, 2025 at 10:22 AM
That looks so cool! Thanks for sharing
That way, I could have, say, light/dark purple for ESlint warns/errors, yellow/red for TypeScript warns/errors. I feel it would work better across other ecosystems like C++ and Rust as well
April 15, 2025 at 10:11 AM
That way, I could have, say, light/dark purple for ESlint warns/errors, yellow/red for TypeScript warns/errors. I feel it would work better across other ecosystems like C++ and Rust as well
Maybe VSCode already has this, but if I really wanted to differentiate errors visually, I would prefer setting configuration manually that would allow me to set an underline color based on some "linterName", "builtinLinterSeverity" values
April 15, 2025 at 10:09 AM
Maybe VSCode already has this, but if I really wanted to differentiate errors visually, I would prefer setting configuration manually that would allow me to set an underline color based on some "linterName", "builtinLinterSeverity" values
I'm kind of torn. The reasoning makes sense, and in general I think would be good to differentiate errors that actually identify runtime errors vs. other logical errors.
But on the other hand, I really do prefer only two options that mean "errors that break the build" vs "errors that do not";.
But on the other hand, I really do prefer only two options that mean "errors that break the build" vs "errors that do not";.
April 15, 2025 at 10:06 AM
I'm kind of torn. The reasoning makes sense, and in general I think would be good to differentiate errors that actually identify runtime errors vs. other logical errors.
But on the other hand, I really do prefer only two options that mean "errors that break the build" vs "errors that do not";.
But on the other hand, I really do prefer only two options that mean "errors that break the build" vs "errors that do not";.
Thanks! This is very useful
April 11, 2025 at 11:46 AM
Thanks! This is very useful
Maybe ghlint, ghcheck, or even forgelint? This would be useful! I personally have some checks[1] for hiding the "projects" or "wiki" tabs but nothing more comprehensive like this
[1] github.com/fox-incubati...
[1] github.com/fox-incubati...
April 11, 2025 at 1:03 AM
Maybe ghlint, ghcheck, or even forgelint? This would be useful! I personally have some checks[1] for hiding the "projects" or "wiki" tabs but nothing more comprehensive like this
[1] github.com/fox-incubati...
[1] github.com/fox-incubati...
Jasmine Rice is sooo good! One of my favorites
January 22, 2025 at 5:36 AM
Jasmine Rice is sooo good! One of my favorites
Reading the recipe 100% through helped me a lot! And visualizing the steps. idk maybe its obvious to some 😭
January 6, 2025 at 2:20 PM
Reading the recipe 100% through helped me a lot! And visualizing the steps. idk maybe its obvious to some 😭
I do a little bit and I feel the same way. Usually I have to make the dish a few times, and optimize the "scheduling" (if you will) of the substeps to actually get close to the "predicted time". Maybe its the little bit of ADHD in me
January 6, 2025 at 2:17 PM
I do a little bit and I feel the same way. Usually I have to make the dish a few times, and optimize the "scheduling" (if you will) of the substeps to actually get close to the "predicted time". Maybe its the little bit of ADHD in me
Git's builtin aliases are so useful! I think the only necessary shell alias would be `g='git'`
January 2, 2025 at 10:35 PM
Git's builtin aliases are so useful! I think the only necessary shell alias would be `g='git'`
TIL pkill accepts a pattern!
January 1, 2025 at 8:16 PM
TIL pkill accepts a pattern!
Your response was so goated
December 31, 2024 at 2:18 AM
Your response was so goated
a watch with a countdown timer. it only vibrates from timers, no phone notifications etc.
December 30, 2024 at 8:52 PM
a watch with a countdown timer. it only vibrates from timers, no phone notifications etc.