Why do you suppose it was originally written the way it was? To my eyes, that seems like a horrible approach. Doing file IO and parsing strings in every call? What?! And yet I assume the original author was a smart person who had a reason why this made sense to them, and my inability to guess why is my own limitation and not theirs.
You are spot on that the original author had a valid reason: at the time, it was literally the only way to do it.
The method in question (Java 1.5) was released in September 2004. While the POSIX standard existed, it only provided a way to get total CPU time, not the specific user time that Java needed. You can read about it more in the history section here: https://norlinder.nu/posts/User-CPU-Time-JVM/#a-walk-through....
But it's worth noting that while this specific case can be "fixed" with a function call, parsing /proc is still the standard way to get data in Linux.
Even today, a vast amount of kernel telemetry is only exposed via the filesystem. If you look at the source code for tools like htop, they are still busy parsing text files from /proc to get memory stats (/proc/meminfo), network I/O, or per-process limits. See here https://github.com/hishamhm/htop/blob/master/linux/LinuxProc....
I knew about using proc for all that other information. I just wouldn’t have imagined using it for critical performance path. Unless, that is, that’s the way you have to get the information.
I was once hired to manage a build farm. All of the build jobs were huge pipelines of Jenkins plugins that did various things in various orders. It was a freaking nightmare. Never again. Since then, every CI setup I’ve touched is a wrapper around “make build” or similar, with all the smarts living in Git next to the code it was building. I’ll die on this hill.
Or honestly, anything involving a hashmap. Of course you can write those in C, but it’s enough friction that most people won’t for minor things. In Rust, it’s trivial, so people are more likely to use them.
I think that's the key. Healthy skepticism is always appropriate. It's the outright cynicism that gets me. "AI will never be able to [...]", when I've been sitting here at work doing 2/3rds of those supposedly impossible things. Flawlessly? No, of course not! But I don't do those things flawlessly on the first pass, either.
Skepticism is good. I have no time or patience for cynics who dismiss the whole technology as impossible.
I think the concern expressed as "impossible" is whether it can ever do those things "flawlessly" because that's what we actually need from its output. Otherwise a more experienced human is forced to do double work figuring out where it's wrong and then fixing it.
This is not a lofty goal. It's what we always expect from a competent human regardless of the number of passes it takes them. This is not what we get from LLMs in the same amount time it takes a human to do the work unassisted. If it's impossible then there is no amount of time that would ever get this result from this type of AI. This matters because it means the human is forced to still be in the loop, not saving time, and forced to work harder than just not using it.
I don't mean "flawless" in the sense that there cannot be improvements. I mean that the result should be what was expected for all possible inputs, and when inspected for bugs there are reasonable and subtle technical misunderstandings at the root of them (true bugs that are possibly undocumented or undefined behavior) and not a mess of additional linguistic ones or misuse. This is the stronger definition of what people mean by "hallucination", and it is absolutely not fixed and there has been no progress made on it either. No amount of prompting or prayer can work around it.
This game of AI whack-a-mole really is a waste of time in so many cases. I would not bet on statistical models being anything more than what they are.
"Black lives matter" is an excellent example. I think the reactionary phrase "White lives matter" might be even better, as while almost everyone would (and should) agree with it without context, in the context of people complaining about "Black lives matter", lots of people would disagree with it or be unsure about it.
I mean, I'd count myself among them. If you asked me if I agree that white lives matter, yes, of course we do. If you asked me about it in a political poll about other reactionary phrases, I might have to think long and hard about what it's really saying in that context.
> he was reacting to a poll according to which a sizeable proportion of black people disagreed with the statement "it's ok to be white".
The context of that poll was an alt-right uplifting of the phrase "it's OK to be white", as though they were being oppressed and were finally removing the yoke of hatred they'd endured. A similar poll might ask about the phrases "not all men" or "me too". In isolation, who could possibly have a problem with either of those?, but these things aren't taken in isolation.
I'd be curious about a followup question like "is it acceptable for someone to be white", which is asking the exact same question, on the surface, but in context is asking something completely different.
So much this. They gave my mom an effectively unlimited supply of opiates when the time called for it, and we convinced her that it was perfectly OK and good to use them. One need not suffer without help, unless that happens to be personally important to them. Like, I can imagine religious objections, maybe, or perhaps an addict who wants to “go out clean” knowing that they beat the cravings. But if those don’t apply, pain meds are good and plentiful now.
I am truly sorry for your loss. That must’ve been a nightmare, and I can imagine someone exploring outside their usual lines in such a situation. I hope you and your child are well now.
reply