RScholar

That's not true, it was published in 2016. I just happen to know because I bought it last week to support the Lua Foundation in the wake of doing some work on Scribunto modules at the Wikimedia projects. They're using Lua 5.1.5, but I figured the author would indicate the feature introduction points and I was correct about that.

I'm only just over halfway through but if I'm being honest, I can't offer much praise for the depth of the material or the treatment it's given: other authoritative volumes I've previously consulted (strangely, Mastering CMake comes to mind first among that cohort) were much more effective at communicating the underlying philosophies of construction and other unobvious practical realities of their subjects. Nevertheless, I do still value having a comprehensive reference at hand to refresh my memory on what's in fact possible when working with a language that I make use of as infrequently as this one.

I sure do. I believe it's the first season episode "When the Bough Breaks," (S01E16). That show tackled so many heavy topics right out of the gate... I respect the hell of of the courage to try, even if it produced some pretty epic whiffs along with the home runs and standing doubles.

I can see how you might suspect that, but I got a different read from it. The constant references to the topic as the "IPv6 Cat" struck me as another in the long tradition of authors who became too attached to a clumsy and ineffective analogy they thought was good enough™ and banged it like a drum. That strikes me as an all-too-human thing to do (especially since I've been guilty of it myself before) rather than an AI artifact. I enjoyed the piece nevertheless, and I agree with its premise that market forces are not enough to continue the trend of IPv6 penetration growth and that public policy carrots and sticks are both needed and justifiable to ensure it comes to pass.

On another matter, whose brainchild is IPv6+? I haven't heard of that one before.

> Software developers are the wizards and shamans of the modern age. We ought to use our powers with the austerity and integrity such power implies.

This is one of the most powerful truths underlying the world we currently inhabit. The sooner we can agree to behave accordingly, the better our prospects for ripping the reigns of society from the hands of those whose only animating principles are avarice and exploitation.

One of my favorite works of literature and television adaptations. If someone ever had the perspicacity to create a streaming service showing nothing but Ian McShane performing scenes from Ken Follett books, I'd just hand them my wallet and never leave the house again, haha.

[email protected] Roguescholar@sbcglobain and and and and and and and l.net

Maybe I'm just getting old, but my reaction to this article had nothing to do with LLMs but was instead that this is an indictment of the state of medicine in America. At each diagnostic milestone it seemed obvious that the conclusion didn't adequately explain the totality of the boy's condition and the search needed to continue for the real culprit. Instead it seems like each one of these diagnosticians felt they'd found the "real problem" and pushed ahead with treatment as such.

Now I'm not saying that back in the day all doctors were Gregory House or holders of forgotten knowledge, but I have to think that the lower pressure to make medicine behave like a business and deeper ties one would form with their patients would've benefitted this family. For this to have gone on for three years without getting escalated to the attention of one of the real-life Dr. Houses out there is appalling. I feel like ChatGPT got the answer right because it allowed her to input all of the minor observations from the charts; perhaps had the doctors done likewise they'd have connected the dots as well.

When I was growing up and in my early 20s you went to the doctor and they got you talking about your life, teasing out the observations you had on your own life and addressed things from there. Then about 15 years ago everything changed and doctor visits became this twisted form of speed dating where you never see the same person twice and any question or answer that takes longer than ten seconds to express is taboo. I hate it, and I can't believe that we keep moving along like it's acceptable.

Trakt.tv

Personally, I'm going to spend the rest of the day looking for those people walking around with the faces of squid...they sound terrifying.

Kind of creepy, but you just described, step for step, how I ended up running Fedora's KDE Spin on all my boxes over the past year. I really wanted to like Manjaro, I mean the AUR is incredible and their visual design even uses all my favorite colors, but despite my best efforts it felt alien to me in a way I can't well articulate.

Now enter Fedora for the past 4-5 months and I have to say I'm rather impressed. In particular, their package archives seem to keep current with a lot of the software I rely on far better than Debian/Ubuntu. Using dnf feels much more familiar than pacman ever did, and as of now I feel like my search for a daily driver has ended. I would recommend anyone else that's not happy with the experience of Ubuntu anymore to do likewise and see how Fedora feels in its place.

Just because you were civil in your expression of it doesn't mean that your opinion itself isn't in poor taste to communicate, especially for someone involved in open source. You may be indifferent to criticism which exists only as a means of self-expression, but when silence costs nothing it's difficult to see exactly how your thought couching your criticism of the e-book ecosystem as a distaste for this long running, free and fairly popular piece of software was going to advance the conversation.

There's a term in Portuguese for a crying baby that's held to a breast but who continues to cry, without even trying to suckle; it's what came to mind when I read your original comment. It's not used for flattery, I'm afraid...

...1987, of course that's when interest would've spiked. IIRC, that's the year MacGyver debuted on TV.

Man, if Gimlet Media hadn't gotten flushed down the Spotify crapper, this thread would've made for the most sublime episode of Reply All.

I think a lot of that can be chalked up to the fact that the minds behind CMake are pretty consistently top-notch--most of the Kitware folks have at least one post-grad CS degree and have not insignificant levels of experience approaching design problems from a more abstract/academic POV than your average dev team. I think over the years it's kept them from making the truly awful implementation blunders that send projects scrambling for another alternative just to 'never have to do THAT again.' Hence, CMake has had the time to seep into the way projects organize themselves in ways the "flavor of the month" build systems (qmake, scons, et al.) couldn't.

What I'd like to know is where this supposedly excellent documentation for Meson is that the author refers to. The times that I've needed to use Meson have been uniformly unpleasant precisely because I found the official docs to have a ton of holes and also assumed an unrealistic level of familiarity with their underlying logic. Give me the CMake docs anyday; at least I can be relatively sure the answer's in there instead of hiding in a GitHub issue regarding some design flaw that'll be solved in the next release.

I'm not sure that the criticisms for the article and parent comment are quite so easy to dismiss wholesale, but I do concur that many of them are actually criticisms of the GNOME DE and not so much Linux itself. In my experience as a daily Linux user it was somewhere between 2-3 years ago that KDE Plasma surpassed GNOME as the most productive desktop environment for Linux, and the distance between the two only appears to widening still. I would love to see what impact the simple choice to swap plain Ubuntu for Kubuntu would have had on their conclusions.