10,008 karma · joined September 23, 2014
It's not as simple as your reductive analogy. It's for a court to decide.
I don't remember the last time I used a software package as smooth and clean and tidy as C4D.
It's a totally reasonable investment as long as they are within shooting distance of the market leaders, but the more they lag behind (i.e. the longer it takes for them to release their next model on par with industry leaders) the more hurt they're going to be in.
If they can't materialize returns off the tens of billions of dollars they just raised then it will come back to bite them hard.
Luckily they have a ton of options (such as selling compute) but it's still not a great look and the market is going to hammer them given the opportunity.
There's no mention of sharding whatsoever. Without that this has very little to do with Planetscale and is much closer to your average managed DB (RDS etc.). There's also no mention of a bouncer/gateway/reverse proxy, which is necessary for zero downtime.
I get that Planetscale hosts "vanilla" Postgres instances but naturally those are limited by single instance size limits. I imagine this is predominantly a marketing strategy for them, acting as a funnel for their sharding products.
But perhaps that's the goal with this project, to not be Planetscale at all, and to focus on the single node. If that's the case, then great, best of luck, but the roadmap is missing some important pieces for me to take this seriously. In either case I find drawing comparison with Planetscale to not be very helpful or illustrative of the project and its goals.
Do you have a lift in your garage?
The finding in TFA was the result of a security audit.
This is a poor measure of quality. I've spent considerable time knee-deep in these issues in particular and the vast, vast majority of them are feature requests, bug reports awaiting more information from the submitter, or bug reports that cannot easily be reproduced (likely conflicts with other software). On the whole, Tailscale does an excellent job of "just working" in practically every possible environment. They do an incredible job thriving in the diverse ecosystem of software networking and their work will naturally never be remotely done. There will always be gaps, it's the nature of the beast. I'm not aware of any other product that does a better job here.
If you've spent any time dealing with enterprise software you'd know that there is an infinite firehose of these sort of issues. We're lucky that Tailscale keeps these public. Many other vendors track these sort of issues privately.
If there are particular issues which jeopardize the security posture of Tailscale deployments that have been open for a significant amount of time, my clients and I would love to know. Please share!
> We very much fear at $work that there are vulnerabilities in the Tailscale product awaiting discovery. Especially as, AFAIK, Tailscale have never had a formal security audit on their software.
I can't take this seriously. If you were a customer you could, you know, ask them? Or inspect their SOC2 documents?
I absolutely guarantee they undergo regular formal security audits. There's no question.
> So we install it on hardened bastion hosts in an old-school "jump host" model. So people can still get access to where they need to be, but we don't need to install Tailscale's unaudited shit on every single server / vm / etc.
Bastion hosts are a terrible model in 2026. I can't take this approach seriously.
> we don't need to install Tailscale's unaudited shit on every single server / vm / etc.
You never need to do this. Simply create an exit node into your subnet, and everything you want becomes routable.
It sounds to me like your architecture struggles with a zero-trust network approach if you view this as a blocker. I've got some slots available if you need a consultation!
> In terms of SSH, we use old-school OpenSSH and SSH certificates. Its really not that difficult and its really not expensive, you can do offline signing with Yubikeys, no need for expensive HSMs.
It's expensive in terms of engineer-hours, especially compared to Tailscale. It's also easy to get wrong, and end up with the same vulnerability as TFA, or worse.
But my main issue is that if you see this as equivalent it's telling me that you're not really the target audience. Your set-up is far more vulnerable than the out-of-the-box experience you get with Tailscale. If you don't mind, then I'm happy for you.
Lastly, I don't work for Tailscale and I'm not affiliated with them in any way beyond being a happy user that has solved a lot of problems very easily with their product. I highly recommend it to practically everyone. It's great.
I'm having a hard time taking your comment seriously. It just seems like non-constructive FUD.
It's easy to blame the engineer, but all too often they don't deserve it.
Sorry that happened to you.
Many people communicate differently in different contexts. It's common to try and match the style of the community in which you participate.
I am not convinced that having your identities merged for you is inevitable.
Time for a rewatch I suppose.
Draper sabotages Ginsburg because he's threatened by him. In the elevator Don is masking his insecurities, as he deeply fears Ginsburg's talent. His own creativity, and confidence, has been crumbling. It's all ego.
If your immune system becomes suppressed or you become injured, then you're skating on very thin ice.
We've known this for a very long time. There's a reason refrigerators are popular.
I love the "show source" toggle!
I'd love to see this go to court.
What you want isn't skill files for LLMs, though. Just write docs for humans. Write a migration guide, for humans.
It's going to take us a while to realize they should be the same things, skill files and docs.
It's unfortunate that there is so little transparency that even if they deny there was a leak we will never know for certain.
I've been involved with the build out of several office spaces in new and old buildings. We always took this sort of thing seriously and measured each room independently for a week (many at a time) ensuring we accounted for periods of high occupancy.
This let us tune the HVAC systems to operate more efficiently, ensuring comfortable temperatures and air circulation. Every time I've seen this done there were structural deficiencies that required remediation, some times it meant adjusting duct work.
Most modern office buildings are designed to be a platform for constructing spaces, as spaces usually evolve and change between leases and tenants. They're designed to accommodate this sort of thing.
However I've found that no build out nails this the first time. It's very hard! Often times things look fine but once you get people in the space things change drastically. It requires time and effort to address.
Several of my offices had such good air that I'd prefer being there over pretty much anywhere else -- even outside on poor AQI days.
I've also found that a lot of offices don't do any of this and their air quality is noticeably poor. And lastly I've found that the oldest buildings, including schools -- and I'm talking really old -- have very good air because they are so incredibly leaky. They're usually harder to cool and heat, though.
GOMEMLIMIT works very well if you set it to around 90% of available memory as a rough heuristic. You should definitely profile your application to fine tune this number (e.g. if you link with C libraries that hold large memory pools then Go doesn't account for that) but also to identify sources of spikey/leaky allocations. For example, encoding/json is notorious for it's inner sync.Pool hanging on to outsized buffers. There's usually a lot of low hanging fruit.
In my experience Go can be extremely stable in terms of memory footprint at both small (~O(1MiB)) and large (~O(256GiB)) scales, and it takes only a small amount of effort.
As far as GC languages go, it is by far the easiest to work with.