Open post ljs @ljs@social.kernel.org · 29mo ago Replying to @bagder@mastodon.social on hacker news: https://news.ycombinator.com/item?id=40112383 @bagder@mastodon.social truly incredible what a bad take machine that site is. And they all think they're so very clever...
Open post ljs @ljs@social.kernel.org · 30mo ago Replying to @AndresFreundTec@mastodon.social I was doing some micro-benchmarking at the time, needed to quiesce the system to reduce noise. Saw sshd processes were using a surprising amount of CPU, despite immediately failing because of wrong usernames etc. Profiled sshd, showing lots of cpu time in liblzma, with perf unable to attribute it to a symbol. Got suspicious. Recalled that I had seen an odd valgrind complaint in automated testing of postgres, a few weeks earlier, after package updates. Really required a lot of coincidences. @AndresFreundTec you sir, are a legend among men.
Open post ljs @ljs@social.kernel.org · 35mo ago Replying to @Aissen@social.treehouse.systems @parismarx @ljs AI isn't the issue here. Having a for-profit medical insurer is. Using the worst tool for the job that increases profits is only a byproduct of that. @Aissen @parismarx you can have more than one problem at once. 'AI' is absolutely a problem, this is hardly the only example.
Open post ljs @ljs@social.kernel.org · 35mo ago Replying to @Aissen@social.treehouse.systems @ljs @parismarx I cannot disagree, but I find that addressing a leaf issue instead of the root cause is waste of time and energy. @Aissen @parismarx I don't disagree, but the point was about AI and you're getting distracted :) If you want an alternative that's less distracting, 'self driving' technologies have already killed people.