I have a similar story but with neovim (and for the same reason as the author; growing unease with big tech). Tried and failed to make the switch a few times but made a concerted effort to stick with it throughout a specific project and now it’s second nature. I found it useful to research idiomatic (n)vim ways of doing things whenever I’d get frustrated or feel I’d be doing something more quickly in VSCode and commit them to memory by using new commands a few times over. Right now I’d say search/replace is the only thing that’s still not as ergonomic for me in vim as it is in Code. What I do is visually highlight my search phrase, hit asterisk then :%s//replaced - I learned that you can omit the search pattern using this technique.
Anyway nvim and helix are both amazing and terminal editors are both cool and sexy, so why wouldn’t you? ;)
Woah, how did I not know about that tip about omitting the search pattern? Love it and will be using that lots!
As a thank you, I'll leave you with the way I learned to search/replace, just to give you a slightly different flavour: asterisk, cgn ([c]hange [g]o [n]ext), type replaced, then . (period, to repeat) until I'm done.
Huh. I forgot about %s. I just search for a pattern and replace the first one manually. If there are fewer than ~5 occurrences, I'll just hit `n.` ~5 times and get them all. If there are more, I'll record a macro with `qqn.q`, then look at the occurence count in the bottom right corner (e.g. 50) and hit `50@q` to get them all. Sometimes the replacement text is non-constant, and this method allows for more flexibility with the recorded macro.
Sometimes it's funny to look around and see the strange local minimum of effort you've settled into.
I've written a fair bit of React and dipped in and out of Vue, Solid and Svelte over the past few years - I like to check in with different frameworks periodically, call it curiosity or FOMO. The general sentiment of the article is that React is old and slow compared to Solid/Svelte etc. While that's true, how many apps really need to squeeze that extra performance out of their underlying framework? Not many, I'd guess. For example, the ubiquitous krausest benchmark tests [0] operate on thousands of rows and the margins in results are shrinking - just today I noticed that the latest alpha from Vue has made huge strides forward.
React cannot iterate as quickly as other, smaller frameworks because of its size, but I guess that could also be seen as a positive thing. Even so, things like the React compiler are clawing back performance, taking cues from Solid, Svelte et al and these frameworks become more alike all the time.
For me the choice comes down to how I reason about the code I write. As others have pointed out, React feels closer to metal than Svelte - I find it easier to reason about because there's less magic going on behind the scenes. I really want to like Svelte, but I just can't click with it at all and I find the documentation lacking in deep, 'under the hood' detail.
On the flipside, I find Solid's docs to be superb - in depth articles on their reasoning, differences to React, etc [1][2]
On the whole, though, I find all these frameworks to be pretty good and what you can build is unlikely to be hamstrung by your choice in any way; though of course, React has a huge community behind it that you can't ignore. For hobby projects, try them all out - I had not worked with Vue 3 at all until recently, I just picked it up to try making a drum machine with the lovely Elementary [3] DSP library and I am really enjoying it! I hope we continue to see lots of development of all these frameworks and new ones pop up, because it's very clear to see how they all feed off one another, and that's good for everyone.
Shout out to Alpine.js [4] which flunks those benchmarks every time but remains my go-to for sprinkling reactivity in 'regular' websites.
Never really understood posts like this that start “x doesn’t have to be a chore”, especially when “x” falls under the category of hobby, leisure activity or something generally requiring effort to maintain which is a kind of luxury pursuit. If you find “x” a chore, don’t bother and move on and do something you find fulfilling. This just frames it in a way that makes me think it’s something people think they _should_ do.
Some people want the benefit of an activity, but they don't like the activity itself, like me and physical workouts for the purpose of a physical workouts. Finding ways of making activities "more fun" so those people don't find it to be so much of a chore sounds like a neat contribution.
Workouts are a chore, like washing clothes, it's something you need to do whether you like it or not. There are things you can do to make it better, but it's not a leisure activity you can just stop doing (at least not for extended periods without replacing it with something equivalent).
For journaling, the benefit is the enjoyment you derive from doing it. If you don't like doing it, you're not going to get anything out of it, at least not more than you would spending that time on a hobby you actually like.
Yes, and I enjoying swimming in the ocean for example. But I don't like swimming just for the sake of "it's good for you", don't know why and doesn't really matter.
Point is that some people know what's good for you, but cannot force them to do it just because it's good, we need something more :) Just because something feels like a "chore" doesn't mean you should avoid it.
This is an amazing little subthread here because in Book 2 of Plato's Republic Socrates lays out three classes of "good" in response to Glaucon. He categorizes physical training as the type "good only for their consequences" which he argues is not the highest form of good. Now, if one does genuinely enjoy the activity, he would elevate it to the highest form, which is "good both for their own sake and for their consequences".
Many in recent generations see romantic relationships as an extra, a luxury side quest. In the same overall category as journaling or home cooking and so on.
I've been trying All The Browsers lately and Arc is definitely still my favourite; I actually had no idea that development had stopped on it, that's a shame. Zen looks good, but they are off the charts on this graph! https://sizeof.cat/post/web-browser-telemetry-2025-edition/ What is going on there?
Their Privacy Policy says no telemetry, but then they have a section on those connections made at startup which apparently are "necessary for the proper functioning of the browser and are not used for tracking or profiling purposes"... they then go on to say "can be disabled through the browser flags (about:config)"
Does that mean the browser will no longer function correctly?
Among the connections made (according to the report) are x.com, google.com (plus a bunch of other google domains). reddit.com and notion.com, discordapp.com, cloudflareinsights.com
> Among the connections made (according to the report) are x.com, google.com (plus a bunch of other google domains). reddit.com and notion.com, discordapp.com, cloudflareinsights.com
Reddit, X, Discord, and Notion are all part of the default sites in the sidebar. Perhaps it's loading them to grab the favicons and such, leading to all of their calls to CDNs, analytics, etc being called.
Thanks for calling that out, I had not got as far as installing the browser so had no idea they were default favourites / shortcuts. Seems like that telemetry report has given a couple of browser vendors the kick they needed to reduce initial connections. I wonder how much of an effect this stuff has on how snappy it feels to actually open these applications. In my dock I currently have FF and FF nightly, Chrome, Ungoogled Chrome, Arc and Safari. Ungoogled loads in the blink of an eye, the rest are all shades of sluggish. I guess this is the price of having a few extensions and “quality of life” features :shrug:
I think that page on the sizeof.cat website was created before Zen removed a lot of the telemetry. Here's the PR created on April 27, after the article was created
