wtarreau

8 ms·

31.
by wtarreau 3y ago
the same way some believe that forcing talented people to waste their time trying to use inappropriate communication tools will in the end disgust them so much they will give up trying to excel at what they used to.
32.
by wtarreau 3y ago
because the phone was more important.
33.
by wtarreau 3y ago
It certainly costs much less to the society to train for Pascal once than to make everyone burn CPU cycles running Python!
34.
by wtarreau 3y ago
This protects your machine but not necessarily the resulting binary code. Nothing prevents the malware from patching the source before building and removing the patch before the end, resulting in a binary and a package that contain code tha
35.
by wtarreau 3y ago
It's true that we can see them everywhere but you'll probably notice that you don't know what jobs such people do and that those who you know and who need to benefit from others' experience typically do not do this. I te
36.
by wtarreau 3y ago
It's not necessarily the case, it happens that most of the people who come are happy to be in the same room for a meeting, but often they still have to endure one single distant coworker that preferred to stay home and selfishly forces
37.
by wtarreau 3y ago
Thank you, I'll try that. It's all but intuitive to have to touch bbox preferences just to edit the center of an object :-/
38.
by wtarreau 3y ago
Thanks, that's useful! However that's one main issue with this tool, it's really oriented towards the UI itself. You're bounded by your mouse (or worse, touchpad) resolution to place the center and often in addition to w
39.
by wtarreau 3y ago
I'll try it. For me the best experience used to be with 0.92 and since then it has significantly degraded, with counter-intuitive things happening all the time in the UI. One of the operations I find the most complicated is to place ci
40.
by wtarreau 3y ago
Agreed. In fact it would be great if llama.cpp would drop that C++ mess that makes it harder to contribute...
41.
by wtarreau 3y ago
In fact, editors used to be one such concern, when they were limited or getting extremely slow with large files. Also old-style version control like CVS was so painful to use that the best way to avoid issues was to have each developer work
42.
by wtarreau 3y ago
It's just up to you, the author of the project. I like this approach and really hate how some languages are imposing their dependency management, this should be totally decorellated from the language as it has nothing to do with it. It
43.
by wtarreau 3y ago
As often with Rust, someone transliterates something that already exists just because they can, without providing any benefit at all. Sometimes it even results in fragmenting the community efforts to improve the project.
44.
by wtarreau 3y ago
That's very interesting to perform basic tasks at reasonable speeds or to run on smaller systems. Unfortunately it's not of the many ones based on python and transformers, so all gained resources from the compact model are wasted
45.
by wtarreau 4y ago
Just to clarify some doubts, distro packages issued yesterday all have the fix in them even if the base version number appears older.
46.
by wtarreau 4y ago
confirmed, thanks for correcting me. Dealing with such reports across many versions and copy-pasting lots of data & Git commit IDs is extremely prone to failures, even after careful re-reading.
47.
by wtarreau 4y ago
I can confirm that the code looks totally different. Anyway there's no reason someone writing a libc would waste their time with pieces of code from other provenance. It takes less time to write a minimalist printf than trying to adapt
48.
by wtarreau 4y ago
Hi! article author here, I can respond to a few questions. I didn't know about musl by then and it could definitely have oriented my choices differently. However after I started to use macro-based syscalls, I found there were very conv
49.
by wtarreau 4y ago
TCP_QUICKACK is mostly used to send initial data along with the first ACK upon establishing a connection, or to make sure to merge the FIN with the last segment.
50.
by wtarreau 4y ago
You're right, it looked completely bogus to me with things seeming to do the opposite of what I configured, until I read your message! The problem with UIs is that people can't refrain from distinguishing themselves by doing somet
51.
by wtarreau 4y ago
Many thanks! Too bad this thread was not noticed and left unresponded. I'll have a look. Thanks again!
52.
by wtarreau 4y ago
This interests me. I've long been wondering how we could do that without knowing the NIC's hash and/or without having to brute-force the ports using the NIC's hash to reverse-map them. But maybe there are kernel faciliti
53.
by wtarreau 4y ago
OK I see. Yes for some use cases that's possible. But that seriously limits your load balancing capabilities. And having to deploy Hitch or Pound for TLS still requires an extra component that's not designed to deal with traffic s
54.
by wtarreau 4y ago
I agree. I'm used to saying this to the rest of the development team: we are very critical about our own code because we receive all the bug reports, which tends to give us a feeling that there's always something to fix. But seein
55.
by wtarreau 4y ago
Indeed, that's fun at the beginning but past one point when you'd want to stop the servers taking 3 connections a day but you can't because these are the 3 most business critical connections, it starts to become much less fun
56.
by wtarreau 4y ago
For pure TCP you rarely need threads, indeed! You may benefit from TCP splicing however if you're dealing with high bandwidth.
57.
by wtarreau 4y ago
And admittedly threads didn't work great 5 years ago when we put them into 1.8. Fortunately 1.8 is dead soon, one less thing to worry about :-)
58.
by wtarreau 4y ago
Thank you, you're welcome!
59.
by wtarreau 4y ago
I agree with you. Varnish is made for being a website cache that's a real part of the application. It needs to be extremely flexible and programmable. HAProxy needs less flexibility on the caching stuff but more on the conditions to sw
60.
by wtarreau 4y ago
One approach that some users who want this mechanism use is the "on-error sudden-death" mechanism: the server responses are inspected, and upon error (from selectable types), the server can be marked dead. If all of them are dead

More ›