Not the parent commenter, but I also tried it a year or two ago and my recollection is that I had a similar experience. I have a really long history file that dates back like a decade and if remembering correctly I tried to import it, and it made using my shell very laggy so I ended up removing it. I'm not 100% positive that I'm remembering the exact way that I started experiencing the lag though, so if I have time tomorrow I'll try it out again and see if it's still something I encounter.
I think it was a combo of this + completely screwing my muscle memory haha. I'd give it another shot...but tbh, these days claude/codex are more my command line than bash/zsh.
I'm running into this again now that I'm trying it. I also have the unfortunate habit of sometimes trying to do stuff in the terminal via remote connection over a streaming server from my SteamOS handheld, and in the desktop input layout I have defined, I can really easily hit the up arrow with my thumbstick, whereas any modifier shortcuts need to be defined manually. From glancing through the config file, there does seem to be a lot of customization though, so I think it might still be viable if I can find a sweet spot in how to define the settings.
I'm curious, is using the daemon with my own frontend a supported use case? Because I had a thought...while as I mentioned above I don't use the CLI much anymore...my agents do, and having that history in a sql db would be mighty useful...
Edit: Okay, y'all are literally working on exactly what I need to build off of, perfect lmao
I wonder what's the selling point at that scale. If your ~monthly~ cloud spend ends in "M", you can easily justify hiring the talent needed to wrangle conventional bare-metal (in fact you can do so at much lower spends, but at these spends it becomes a rounding error).
Edit: my bad, read that as monthly instead of yearly. Still, a yearly spend of millions would still make sense to bring that in-house.
An in-house team is most likely competing with something like Dell or VMware, not really Oxide. A significant part of Oxide’s value proposition is that you’re buying hardware and software purpose built for each other. Unless you’re also going to go so far as to do all of that, which companies like Google do, of course, it’s not really the same thing.
This matters when your various vendors start pointing at each other when something goes wrong. Oxide is truly “one throat to choke” in a way others just aren’t, and stand by that quality.
(Not to mention other various efficiencies, like power, or removing things like the BIOS and BMC junk that’s in basically every other server you buy right now. And the ability to send attenuation from boot up through the host OS. Just tons of things they’re differentiated on that your in house team just isn’t going to do.)
VC or private equity fueled companies are weird. At my place we are spending 8 figures a year just in AWS, and it's not like they planning to move to bare metal but, they're in fact removing stuff from their old datacenter. And that bill doesn't include some of the other SaaS like Mongo or Elastic.
With bills of that magnitude, each time I do a little house cleaning and delete some old data, change storage classes, or discover some unused servers... the savings (that are barely a rounding error on their bill) could pay for a whole year of an engineer or a bunch of servers that could power a good chunk of their production traffic.
Its not about bare metal, its about owning the whole stack and giving visibility into every nook and corner, and then supporting that open sourced code. Every network switch, every interconnect, every piece or firmware or software they can attest to because they built it themselves, and that is worth its weight in gold to high criticality industries and governments. They can give you the provenance for every single hardware and software component. Every chip.
If you can roll around those possibilities in your head, you start to see how absolutely unique this is and why these extremely sensitive and important customers and industries want this.
Personally I have never been bothered by programs using my home folder. I don’t regularly ls the contents of it, and just browse by path from my shell anyway, so the clutter is barely visible to me
sure, but with unsafe Rust you have a very clear marking for the section of code that requires additional care and attention. it is also customary to include a "SAFETY" comment outlining why using unsafe is OK here
You actually kind of don't, I use like a zillion crates which have unsafe Rust in them and it's not like I'm sitting here reading every single line of their code. I like Rust for various reasons, but its memory safety is (imo) overstated, especially when doing low-level stuff.
Almost all rust (95%) is safe rust. You can opt out of array bounds checks with unsafe { array.get_unchecked(idx) } instead of just typing array[idx]. But I can't remember the last time I saw anyone actually do that in the wild. Its not common practice, even in most low level code.
Rust is bounds checked by default. C is not. Defaults matter because, without a convincing reason, most people program in the default way.
I wish it was easier to know which projects are in desperate need of funding because I love pgbackrest and totally would have donated here, and I suspect many others would have too :/
> Codeberg is a German-based nonprofit organization, and it’s hard to imagine going wrong with this choice.
I like what they're doing, however Codeberg's 14 day uptime is _97.05%_. I've heard from many that downtime is normal there, and is worse than GitHub (which is already... bad). This makes them a non-starter imo, until that improves.
With the current trend of things going down all the time, the best way to compete is just to be available.
One neat bit with Codeberg however is because they're using (actually developing) Forgejo (a Gitea fork which itself is a Gogs fork) you can easily clone the entire thing locally or on your own VPS to have as a backup.
Forgejo is even trivial to set up as it is a single self-contained binary you can throw somewhere and it'd work.
yes, it's improved a lot in the last couple of years! what in particular bothered you?
reply