I guess it's nice for non-technical people who don't know how to use `about:config` but beyond that I don't really see the need. Hopefully adding that extra layer of indirection doesn't mean the users will have to wait too long for security patches.
Readit Newszavec commented on No AI* Here – A Response to Mozilla's Next Chapter waterfox.com/blog/no-ai-h... · Posted by u/MrAlex94
zavec commented on Stacked Diffs with git rebase —onto dineshpandiyan.com/blog/s... · Posted by u/flexdinesh
Pragmatic is using the best tool for the job. Certainly subjectively, and arguably objectively, jj is the better tool in many ways.
My advice is to try it. You should like it, if you're in the majority of folks to give it a sincere shot. If you don't like it, cool. But then my advice changes. jj is probably the future. Adapt or become one of those old-timers who froze their learning in time.
Pragmatic is not bothering to switch to the shiny new thing just because it's shiny and new if your current tool doesn't give you any problems.
zavec commented on Frequently Asked Unicycling Questions vale.rocks/posts/unicycle... · Posted by u/edent
You can absolutely bunny hop (and so much more). With a 24″ or larger wheel, you can pretty confidently do short trips. If you're looking to do a few kms, 27.5″ is the sweet spot I've settled on for the size/speed/comfort trade-off.
Where I live you're even permitted to take them on the bus/train, assuming you're not being too much of a pain. Unicycles are specifically outlined in the terms.
This is exactly why I just bought one! I take the bus to work, but I live about 1.5k from the nearest bus stop and it's pretty flat.
Unfortunately it's just starting to be icy here so I probably won't be able to make much use of it for several months, but at least it's something to look forward to!
zavec commented on Frequently Asked Unicycling Questions vale.rocks/posts/unicycle... · Posted by u/edent
Thank you! Oooh, that linked site is sleek. I love the effect they've got going on.
I'm wary with this post that I've highlighted a flaw with my implementation, which is that items overlap on smaller screens when headings have small amounts of text. I was aware this could be an issue but hadn’t bothered to address it, as there were no sections with such minimal amounts of text.
If you're interested in the implementation, I've made notes here: https://vale.rocks/posts/the-implementation-of-this-site#scr...
Ooh I'm definitely going to have to give that a read for my blog! For somebody who usually hates frontend development I sure do like to tinker with small blog improvements for some reason.
> a comparable desktop experience to the commercial OSes
Isn't it alteady comparable? My Linux desktop has almost the same game compatibility that Windows has, and none of the advertising and jank. Gone are the legendary days of xorg.conf. Linux has less problems than Windows now. Support from professional software vendors (Dassault, Autodesk, et al) and Nvidia could be better, admittedly, but these restrictions aren't very relevant to me. As for Mac OS it's fine, I guess, but I strongly dislike the settings program, and it's not like you can install an nvidia card there.
> Support from professional software vendors (Dassault, Autodesk, et al) and Nvidia could be better, admittedly, but these restrictions aren't very relevant to me.
I think that's maybe what GP was getting at. If you know how to debug stuff and such then Linux is perfectly serviceable today.
With something like this, between Valve presumably publishing some docs and a big community for a single platform it should become a lot easier for people who are less familiar to search "I got xyz error on my steam box what do I do" and get help they can use. For mass adoption I think that's a big step. And then from there they can start venturing further out, if they want.
zavec commented on Bypassing the Branch Predictor nicula.xyz/2025/03/10/byp... · Posted by u/signa11
If a human wrote that here (on HN) someone would note the error and the poster would reply:
Yes, sorry, you’re correct. I’ve usually had 97 more double ristrettos by this time in the morning.
Some schools of though suggest this has already happened.
LLMs are just what happens when we hit the singularity of caffeine consumption?
Funny you say that, because I have the opposite opinion.
It is easy for any of us to quickly bootstrap a new project in whatever language. But this takes a cognitive toll, and adds friction to bring our visions online.
Recently, I went "blind" for a couple of days. My vision was so damaged I could only see blurs. The circumstances of this blindness are irrelevant, but it dawned on me that if I were blind, I could no longer code as I do.
This realization led me to purchase a Max subscription to Claude Code and rely more on LLMs for building, not less.
It was much more effective than I thought it would be. In my blurred blindness, I saw blobs of a beautiful user interface form, from the skeleton of my Rust backend, Vue3 frontend. It took my (complex backend in Rust) and my frontend scaffolding to another level. I could recognize it via the blur distinctly. And it did this in minutes / hours instead of days.
As my vision returned, I began analyzing what happened and conducting experiments. My attitude changed completely. Instead of doing things myself, directly, I set out to make the LLM do it, even if it took more time.
It is painful at first. It makes very stupid mistakes that make an experienced engineer snarl at it, "I can do better myself". But my blindness gave me new sight. If I were blind, I couldn't do it myself. I would need help.
Instead of letting that ego take over, I started patiently understanding how the LLM best operates. I discovered mainly it needs context and specific instructions.
I experimented with a DSL I made for defining LLM instructions that are more suited for it, and I cannot describe the magic that started unfolding.
Now, I am writing a massive library of modular instructions for LLMs, and launching them against various situations. They will run for hours uninterrupted and end up implementing full code bases, with complete test suites, domain separation, and security baked in.
Reviewing their code, it looks better than 90% of what I see people producing. Clear separation of concerns, minimal code reuse, distinct interface definitions, and so much more.
So now, I have been making it more and more autonomous. It doesn't matter if I could bootstrap a project in 30 seconds. If I spend a few hours perfecting the instructions to the LLM, I can bootstrap ANY project for ANY LANGUAGE, forever.
And the great thing? I already know the pattern works. At this point, it is foolish for me to do anything other than this.
The DSL sounds interesting, if you talk about it anywhere I'd definitely be interested in reading more!
Oh hey I took his crypto class in fourth year! Fantastic prof, I should check this out to refresh my memory.
I think the biggest features of the big cloud vendors is that when they are down, not only you but your customers and your competitors usually have issues at the same time so everybody just shrug and have a lazy/off day at the same time. Even on call teams reall just have to wait and stay on standby because there is very little they can do. Doing a failover can be slower than waiting for the recovery, not help at all if outage is spanned accross several region, or bring aditional risks.
And more importantly nobody lose any reputation except AWS/Azure/Google.
It's like back in school when there was a snow day!
It's possibly more likely that people mis-attribute the cause of an outage to the wrong providers when they use downdetector.
Definitely also a strong possibility. I wish I had paid more attention during the AWS one earlier to see what other things looked like on there at the time.