Hacker Newsnew | past | comments | ask | show | jobs | submit | ac130kz's commentslogin

That's an Ubuntu issue though, they ship lots of outdated software. Nginx, PHP, PostgreSQL, Podman, etc, the critical software that must be updated asap, even with stable versions they all require a PPA to be properly updated.


It's works great until you need that one option from Docker Compose that is missing in Podman Compose (which is written in Python for whatever reason, yeah...).


You can use the real compose (Go) with Podman now. The Python clone is not your only option.


Well, is this Podman's "service mode" also fully compatible with Docker Compose file functionality though?


Looks like the compose `watch` option is not yet supported[1]. Huge blocker for adoption in local development.

[1]:https://github.com/containers/podman-compose/issues/792


What do you mean by "the real compose"?


I assume Docker Compose v2 from Docker.


Podman compose isn't compatible with Docker compose, end of story.


ASRock has Zen 5 CPUs dying with stock settings from brief core voltage spikes on idle (max core frequencies). I believe either PBO has to be enabled to allow undervolting headroom or VSOC has to be permanently fixed to a value lower than 1.2V.


Are they out of their minds? How can a tiny startup without their own actual product (nowadays anyone can strap OpenAI/Anthropic API or fork open source models, such as Deepseek, on top of web scraping) buy the largest browser used by billions made by a company making trillions?


It’s simple, they can’t. This is a publicity stunt


Gitlab is an easy way to scale things related to code. There's also this new thing Radicle.


I can't imagine searching with Google these days unless it's something very niche. Even free AI with web search are marginally better, even with the traffic spam they create, Google Search has made itself unbearable.


>URLs up to ~2000 characters

Exactly, this approach doesn't scale well without trickery involved. You have to have some sort of weird encoding in place to compact it down.


Yup, ASP's "__VIEWSTATE" hidden form parameter comes to mind. It was base64-encoded and POSTed because it could get loooong (hundreds of KB).

Terrible for browser navigation/refresh though, because pretty much everything was a form POST. Thus no URL state sharing, either.


Also a terrible idea to execute code from the client, even if it's supposedly signed.

https://darkatlas.io/blog/critical-sharepoint-vulnerability-...


Somewhat solved by type annotations + a good static type checker, such as pyright (it's 2025, there must be type annotations everywhere), and dynamic cases (very rare, probably due to poor or unfortunate design decisions) can be solved with validators, e.g. the aforementioned Pydantic. This isn't a silver bullet, but it works really well.


Yeah, exactly. There isn't a single good reason not to use type annnotations in Python these days. Yes, they might not be as powerful as TypeScript's type language yet, but they are getting there.


An easier/moderate approach: make a proper base DTO model, which can be extended by validators, such as Pydantic, and the db model is the Domain is just whatever an ORM offers/dataclasses.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: