nezirus

I've used them professionally during 0.9 times (2008.) and it was already quite useful and very stable (all advertised features worked). 17 years looks pretty good to me, Proxmox will not go away (neither product or company)

For some context, Passt is used by podman for rootless networking (by default from Podman 5.0)

It is a noticable improvement for traffic heavy containers.

https://github.com/containers/podman/blob/main/docs/tutorial...

Maybe this could be useful to libraries like psycopg3 to use something more simple/natural instead of this:

https://www.psycopg.org/psycopg3/docs/api/sql.html

(while I also agree it gets crowded with yet another string prefix)

SuSE was my first Linux system and it helped a lot to spark my interest. Yast (software manager) and SaX (XFree86 configuration tool) were a Godsend for a noob like me in 199x.

It's still solid today, and I hold it in high regards, even if I moved to greener Linux pastures.

Podman beeing mostly compatible with docker was a wise choice. If you run rootless no way to break fw/network like docker can.

With podman in mind, one ought to try buildah and skopeo. Again, buildah can run Dockerfiles, but you are not constrained to the weird Dockerfile syntax.

Dunno, in new normal Germany, a refugee* from Palestine, seeking asylum from apartheid and maybe citizenship would first need to recognize the right of their occupator to exist. It is obviously much more important to fix sins from the past than help the living people. Politicians are full of ....

All while marches AfD closer to power every year.

* Lets pretend they could exit Gaza ot Eeast Bank.

Maybe shout out to HAProxy people, like many they've observed performance problems with OpenSSL 3.x series. But having good old OpenSSL with QUIC would be so convenient for distro packages etc

https://github.com/haproxy/wiki/wiki/SSL-Libraries-Support-S...

The cynical voice inside me says it works as intended. The purpose of k8s is not to help you run your business/project/whatever, but a way to ascend to DevOps Nirvana. That means never-ending cycle of upgrades for the purpose of upgrading.

I guess too many people are using k8s where they should have used something simpler. It's fashionable to follow the "best practices" of FAANGs, but I'm not sure that's healthy for vast majority of other companies, which are simply not on the same scale and don't have armies of engineers (guardians of the holy "Platform")

So when I "sideload" HAProxy with my application, handling (incoming!) and outgoing http(s) and tcp connections, balanving, failover, logging and what not, that is cool now and I get to call it Ambassador Sandwich Pattern.

You coveniently ignore the events leading to and the reasons for sanctions and bombardment:

https://en.m.wikipedia.org/wiki/NATO_bombing_of_Yugoslavia

This was actually the second time NATO has bombarded serbian forces, the first time was in Bosnia, which eventually led to Dayton peace agreement later that year:

https://en.m.wikipedia.org/wiki/Operation_Deliberate_Force

It been long since I have stopped following grsecurity, but I would not be surprised if segment registers are still used (e.g. Pax UDEREF)

https://forums.grsecurity.net/viewtopic.php?f=7&t=3046

https://pax.grsecurity.net/docs/PaXTeam-H2HC12-PaX-kernel-se...

You can use pasta mode for rootless https://docs.podman.io/en/latest/markdown/podman-run.1.html#...

Yeah, lets treat all "sides" equally, since they are all bad (sarcasm ends)

Go to https://www.icty.org/, read about cases, verdicts and pleas:

https://www.icty.org/en/cases/key-figures-cases care to search for the GENOCIDE word in there?

Serbia did bad the things in Slovenia, Croatia, Bosnia, and was going to do the same in Kosovo until NATO bombarded them. (Kosovo was already critical in 80ies)

That doesn't absolve any party of the commited (war) crimes, but it is perfectly clear who was/is the regional bully and who commited aggression against neighbours.

I also don't buy tipical lines "they all hate each other", or this is the revenge for what " they" did to "us" in WW2, WW1, during Ottoman times, during Roman times ... Historical crimes are not excuse for new ones, vicious circle must stop somewhere.

Dunno about others, but I always ask myself where these companies would be if their software was under non free license from the start.

This is hostile to end users, small people an companies, not just big megacorps wanting the "steal" the code and run it as a service. Be successful in running and using Hashicorp's software, and they decide to shut you down if you are deemed a competitor.

I am so pissed by this move, it is totally against the spirit of free software and GPL. Using additional contracts to subvert the free software licenses. You get to see the software, but you can't share it further. RedHat would not be here if someone behaved like this 25+ years ago.

I would prefer a variant of GPL which strictly forbids this (imo it should already be forbidden, these are clearly additional restrictions). Let's put "GPL v2 or later" to good use...

Interesting read. I'd like to know more about alpine problems (even just to confirm my bias against it, unless space savings are the most important thing).

For me, Hetzner is mostly baremetal provider. They have dedicated RX line, and if you have base load, a couple of those could run it all (use hetzner cloud instances for scalling and failover)

Kafka doesn't do any stupid tricks, but uses the underlying platform for the full potential: https://kafka.apache.org/documentation/#linuxflush

With the usual recommended settings, XFS filesystem, 3 replicas, 2 "in-sync" replicas, etc., it is rather safe. You can also tune background flush to your liking.

The above tradeoffs are very reasonable and Kafka runs very fast on slow disk s(magnetic or in cloud), and even faster on SSD/NVMe disks.

Even simpler idea is just to disable turbo for "quiet" mode.

That is exactly the point, you should not use general string templating system for SQL queries, together with "roll your own" escape and validation mechanisms. I really don't see why they included that part, if not to show how to shoot yourself in the foot.

That database stuff looks horrible. Why do they feel the need to introduce DB query templating into string templates? No matter what you do on the client side, the database engine itself should escape/validate the data. Didn't we learn that lesson with PHP?

In addition to that, not every database needs prepared statements for safe queries e.g. "Parametrized queries" in PostgreSQL (available in libpq as PQExecParams and exposed in many other higher level languages)

... on the third hand it's better not to roll your own list in any language ;-)

Joking aside, some stuff are currently really hard in Rust, but the rate of change slowed down, and all I can see now is everyday ergonomic improvements, so there is hope for (slightly) simpler syntax in the future.

My experience with indexing is similar. Up to lets say 1M docs it works fine, but after that it goes south. Even with auto-batch I had to manually prepare large bulk updates and wait for completion during inserts to not overload MS. (I am using Rust client).

Other than that, it is simply great. Ranking stuff is great, simple, I only need custom weights there, some additional functions (not just asc/desc) and it would be perfect.

You saved me from stating the same thing. As for the daily hot showers, they aren't good for your skin anyways.

If I was living down there, I'd chose the interval approach, taking oportunistic showers to manage smell :-D

That is funny since poetry modus operandi is 'poetry run python ...'

On topic, "Cargo for Python" should be official, singular (no competing standards), opinionated and fast (tm).

Reading this is really depressing. I just want Cargo for Python. Poetry it is for now, but it has quirks, and it is dog slow...

Better late than never :)

FB people have great experience with introducing typing into weakly typed languages (e.g. PHP vs Hack). So I actually started using pyre-check in place of mypy. The tool is really great and fast. I also like pysa quite a lot.

Pyright only came into focus because it was best Python LSP implementation for NeoVim, and it is also the default for helix-editor which I play with. It's also nice that I could suggest pyright for some younger colleagues using VisualStudio Code (with strict mode enabled of course).

P.S. I'm also using other interesting tools and libraries from FB (Instagram) like libcst [1] or fixit [2]

[1] https://github.com/Instagram/LibCST/ [2] https://github.com/Instagram/Fixit

I can vouch for use of Pyright as LSP for neovim and helix. Very useful, especially the strict mode.

I usually pair it with pyre, another great tool

https://github.com/facebook/pyre-check

I would agree with the above, as an easier version of TLS fingerprinting. One could also ise nginx/haproxy to extract enough TLS info, and detect requests xoming through proxy Magic string: JA3 fingerprint

Dunno, but adding verified attribute with a setter which executes verification step looks simpler to me and covers 80% of the use cases.

For local (GUI!) tools I find XCA (https://hohnstaedt.de/xca/) excellent. It has a few ready to fo templates out of the box, and you can make your own.