This isn't about timing the market by being clairvoyant about the timing of a madman's tariffs.
This is about taking reasonable risk calculations as a small business with extremely high tariff exposure, when a president who did a bunch of high tariffs last time wins and election and says he'll do it again.
Sure multi-trillion-dollar financial institutions didn't run for the hills because they get paid when it goes up and paid when it goes down.
Yeah I think it's better to think of Tailscale as an access control company which is utilizing networks as the utility vector, not a network utility company that also has access controls.
It would be nice if there were a common way for essentially feature-complete SaaS businesses to carry on and maintain some expected level of quality, security updates, and support without endless pressure to expand revenue or slash costs.
A lot of the pressure to expand revenue comes from within thanks to the flaws of permanent employment - you hired permanent employees at a discount compared to the equivalent contractor/temporary workforce in exchange for a promise of perpetual employment. These people will thus do their best to ensure their perpetual employment (they will never say "hey I think we've finished building your product, now you can lay us off to make profit").
You can of course sidestep that and use contractors for the initial build out - plenty of agencies and freelancers will give you a quote with various terms. It'll cost way more in the short term because you're essentially paying upfront the years of salary they would otherwise earn building the same thing as permanent employees, but at least it's an upfront, honest transaction with no expectation of loyalty. You can then hire a permanent skeleton crew for the continuous upkeep.
Want a turnkey Vimeo you can deploy on a cloud or truckloads of servers you can just rack up in a colo? If you have a spare 1.4B laying around, I'm sure that can be arranged.
Does RAMP or CURE offer any possibility of conditional writes with CRDTs?
I have had these papers on my list to read for months, specifically wondering if it could be applied to Garage
I had a very rapid look at these two papers, it looks like none of them allow the implementation of compare-and-swap, which is required for if-match / if-none-match support. They have a weaker definition of a "transaction". Which is to be expected as they only implement causal consistency at best and not consensus, whereas consensus is required for compare-and-swap.
When I was there, DigitalOcean was writing a complete replacement for the Ceph S3 gateway because its performance under high concurrency was awful.
They just completely swapped out the whole service from the stack and wrote one in Go because of how much better the concurrency management was, and Ceph's team and codebase C++ was too resistant to change.
Unrelated, but one of the more annoying aspects of whatever software they use now is lack of IPv6 for the CDN layer of DigitalOcean Spaces. It means I need to proxy requests myself. :(
I would say if you're going to charge a pretty penny for the box, you have to make it ridiculously seamless to run every app the way a user wants, without issue.
TrueNAS sort of half-accomplishes this but as soon as you have to start configuring Redis and Postgres parameters to install Immich or understanding how to set permission on every layer of the filesystem so you can SMB share, the idea of a normal person being able to do this goes completely out the window.
My advice is to go ahead and just open-source everything. You won't on being closed-source anyway. You'll win on the experience for nontechnical users (or tehcnical users that don't want to spend time fiddling). You'll stomp out these complaints on Reddit and HackerNews so people don't get a bunch of negative comments when they google your company.
Kagi's Orion browser is 1.0 on Mac and working on the first full Linux release - it's built on WebKit.
That WebKit is a "third party" dependency but it's still a break from the browser monoculture and it doesn't seem like Mozilla has as much interest in pushing the browser engine space forward after pulling back from Servo.
> The latter is what my Copilot suggested when I addressed complaints about higher gas prices
I would suspect this is because it is most mainstream recommendation from economists on how to disincentivize fossil usage without destroying your society & economic stability in the interim. Not because it's "lefty".
The yellow vest protests in France were basically what happens when you try to do A without also doing B.
This is about taking reasonable risk calculations as a small business with extremely high tariff exposure, when a president who did a bunch of high tariffs last time wins and election and says he'll do it again.
Sure multi-trillion-dollar financial institutions didn't run for the hills because they get paid when it goes up and paid when it goes down.
reply