Which brings us to the old saying: Do not deserialize untrusted data.
In the context of Rubygems and their specs this obviously is harder to manage but dependencies such as Rubygems are and will always be part of your app's Trusted Computing Base.
> dependencies such as Rubygems are and will always be part of your app's Trusted Computing Base
This mindset is changing, in the npm ecosystem, managing and updating dependencies have become somewhat of a gamble. It is no longer if, its when you are compromised.
At this point, the current BMW has to die and reinvent themselves in a fundamentally better way. Breaks my heart as longtime BMW fan and previous owner of some older models. What have they done to the DNA of that company...
I believe they're referring to the DNS servers. The closer they are to the user, the faster a DNS resolution happens.
A good provider will have different locations across the world, and users connect to the nearest datacentre. The free DNS some domain registrars offer is, sometimes, hosted at one single location. If the server is in the US and the user is in Europe, you're adding 80-150ms to requests. If they use "anycast" servers, the user could connect to a server 1-20ms away.
MacBook Pro M5 Max, 128GB RAM + oMLX|LM Studio|Llama.cpp|etc. + Opencode|etc. + Models from DeepSeek|Qwen|Google. There are alternatives to centralized, cloud-based LLMs!
> It's not that much work to trust my root certificate on each device
Sure, but is trusting your homebrewed CA on all your devices for essentially everything really a good idea?
When your homebrewed CA somehow gets compromised, all your devices are effectively compromised and not only for local connections, but everything that uses PKIX.
Make sure all the TLS clients you use have support for name constraints. When I evaluated this in 2023, Chrome was in the process of adding support. I'd love to see a caniuse style analysis of TLS features, people assume they work but support varies.
> helping organizations build and deploy enterprise-grade AI in a secure and trusted way
> Enterprise Account contracts will no longer be offered to new customers
Seems contradictory or I just don't understand how they do product management.
My opinion: Heroku had its time but then stagnated heavily in keeping up with what was going on around it. With the rise of Container as a Service platforms there now were a multitude of more cost-efficient and flexible alternatives which were comparable to the service Heroku offered.
It's such a shame, because they had one of the best services out there. Being able to push via Git and end up with a running deployment was a killer feature. It may not have been the first (Elastic Beanstalk was way older but when it first came out it was Java only iirc, ick) but it was incredibly popular.
Seeing them now chasing AI as a "me too" after being acquired by Salesforce just shows that huge companies will acquire something then sit on it for years and let it rot.
Yup, their Git Push Deployment was really a killer concept and a huge gateway for people just writing good apps not needing to care about infra and still being able to get a production-ready setup.
Couldn’t agree more. That “git push and you’re live” moment removed a huge amount of accidental complexity, and it’s been the guiding experience behind what we’re building at Build.io.
Even when you build cool things it's respectful not to plant them in HN comments :)
I think the usual solution to this is to talk about cool stuff you've done that is only incidentally relevant to the product you're selling. For example, some detail on how you built a technical system or solved a problem, etc...
In the context of Rubygems and their specs this obviously is harder to manage but dependencies such as Rubygems are and will always be part of your app's Trusted Computing Base.