ktpsns

To be honest, three nested RDPs sound like a terrible hack. In an ideal world, this would be two port forwardings and one RDP (thinking about ssh, which is still underrepresented in windows world). In an even more ideal world, this would be an IPv6 direct access ;-)

Zotero is my primary reference keeping system. As a research group/company we switched from bibtex to zotero because it allows to put the PDFs also into the collection and has web based browsing included without custom software.

However, the interop with bibtex could be much more seamless. The zotero db feels a bit like a silo, which is sad. Thankfully it is open source so somebody (including me) could improve this in the future.

If you run the ancient software on modern Windows, you might consider windows sudo, which is a thing nowadays.

I wonder whether you cannot use Windows user permission ACLs. They are pretty fine grained. Might be hard to find the right set of permissions, but for me this sounds the more relevant place compared to PAM.

If this is also some ancient Windows version, such as w2k, I would isolate the overall machine and stick with admin permissions.

To clarify, a good title would be "Loading Doom entirely from DNS records"

Neither one plays Doom over DNS nor is the first paragraph in the README correct, because DNS is only abused for storage, not for computing/processing/executing instructions:

> At some point, a reasonable person asked "DNS resolves names to IP addresses, what else can it do?" The answer, apparently, is run DOOM.

Krita is amazing. Anybody who struggles with GIMP UI should give Krita a try.

Same here. What I hate most is the fact how tooling decides what should be hidden files and what not. Hiding important configuration files (also done by some SSGs) is a bad habit which makes it hard to explore a new project. At least such files should be refered to in some README.

Traffic for the static payload is super cheap. And the insane amount of requests is handled easily by modern event-based architectures. The operation costs are most likely only a tiny amount of the overall economics of the tracker's buisness model. The generated tracking data is certainly worth an order of magnitude more then it takes to generate it.

The tragedy of the commons affects not only grey-haired astronomers but everybody who wants to learn about nature. Light pollution is already so real that I assume the majority of people in "industrialized states" haven't seen milky way with naked eyes if they cannot afford traveling to very remote areas (me included, despite I have a PhD in astrophysics, which makes me technically a grey-haired astronomer).

Of course technology will eventually solve the problem and space-based observatories are superior, despite more expensive and thus makes it more difficult to make science inclusive.

The big question is: Will the shift to orbit exclude a big part of mankind from participating? Capitalism most likely days "yes" and this is, in fact, a tragedy.

Amazing work. I feel this is still something where human engineering genius is required and AI cannot honestly do that. But I might be wrong.

Glad to see this. We can do better then git.

I wonder whether this requires particular GUI toolkits to be used, such as WFC. In any GUI there are enough "bad boy" toolkits which just "draw lines" and thus are not accessible at all.

To be honest, the same applies when a developer gets promoted to team lead. I made this experience on my own that I no longer got in touch with the code written. Reasons are slightly different (for me it was a lack of time and documentation)

Yes definetly! CDs are still commercially available and really affordable as "hardware mixtapes". Heck, even my old car still has a CD player.

Slightly off-topic: https://tonies.com/en-gb/ is a very popular physical music box for children coming from Germany. I guess (not sure) it pioneered figures with NFC chips which then let the wifi-connected speaker stream the music from their platform. Prices are crazy (like EUR30 for a 45min audio play) but wealthy middle class parents happily play it to avoid their children to control their streams from our sad addictive mobile screen world.

As an 1980s child I would love to see more (also cheaper) solutions coming up to make music physical again.

cat &

A UNIX fork is actually a clone of the process, in the first place.

(SCNR)

Monthly AI subscription fees will most likely quadruple in two years. This will fan out the greyscale of AI assistant quality much more.

Who can afford to use a $1k/month agent for a side project?

This post summarizes the economics of AI pretty well, describing the lock-in effect we will observe: https://merveilles.town/@lrhodes/116086521256156934

Quite offtopic, but: I found UUIDs being overused in many cases. People then abused them to store data, making them effectively "speaking IDs" or "multi column indices".

CSS in 2025: Let's write html inlined styles as if it was 2005 and separation of formatting/representation was never invented. I talk of tailwind, of course.

I used telnet(1) as a generic TCP text client for many years before switching to GNU/BSD netcat. Nowadays, netcat is more prominent then telnet, and telnet had its corner cases with control characters.

Never heard about https://jetmore.org/john/code/swaks/, thanks for the tip.

I don't think YAML syntax is the core problem but understanding them as text files and not as serialized dicts/maps and lists.

Hell starts to open when people use string template languages to generate YAML files, such as in Helm charts. This is stupid because the templating language is not aware of the host language semantics. It is quite similar to the SQL or HTML injection problem we fought 20yrs ago and finally overcame with templated queries and auto-escaping.

There is nothing wrong in "the old way" if "it works for me". Issues can probably start in a team but even then, old tools can rock. I remember when people introduced poetry in our dev team in an absurdly complicated way (wasn't poetrys fault but the all-wrong non-portable way of pinning decency versions). Sometimes, simpler is better.

Sometimes new tools make it simpler not harder. uv is such a candidate in my feeling and I think that's a major reason why it took off.

I also assume AI here. There is no visible scientific connection, no references and it all sounds nonsense. I have a PHD in fluid dynamics but cannot relate.

Documentation and APIs can be both machine and human readable at the same time. For my impression, MCP is compating symptoms. In a well constructed system, there would be no need to write dedicated documentation or APIs for LLMs.

By the way, I am new to GraphQL and was amazed how it reduced the boilerplate I had to write for REST in my (classical ORM) project. In a single-person team, this allows me to rapidly write frontends. With libraries such as https://gqty.dev/ I basically write no more glue code. These are probably not the needs you have as an enterprise.

It's a shame that within +20yrs of widespread IEEE 802.11, no extension to standardize terms acknowledgement, login flows, etc could make it.

Thus we are left with this captive errnous detection. It feels similarly stupid as NAT in a post-IPv4 world.

Nice article. Some passages have LLM smells (short sentences. No em dash but smells of em dashes). I wonder whether this comes from having an LLM improve the English formulation/typos/etc. I don't like the way how LLMs typically write. One can steer it to certain degree with a longer prompt, that's my impression.

I discovered Perl directly after PHP before Web 2.0 days. Compared with the extreme, Java or (contemporary) Go, Perl codes (can) have a soul. Interestingly, modern ECMAScript (JS) brought in a few of the nice breweties from Perl world which I haven't seen a long time.

Best luck! My year of the Linux desktop has been 2006, so it's now 20 years (with a short 5yrs relapse around 2012). I never look back.

(Similarities to smoking cessation are neither coincidental nor intentional, but unavoidable.)

Nice numbers and it's always worth to know an order of magnitude. But these charts are far away from what "every programmer should know".

And yet Java is more then Java. There are lots of more modern languages on the JVM. The ecosystem is huge and still has lots of inertia.

Pip is not Linux specific, it's the same on Win/Mac. I prefer AppImages because they are just statically compiled binaries. I prefer Apt&friends because it is good old packaging. But flatpak and snap? Hell no. I see so little advantage there.