mtmk

Very cool. Coincidentally, I was looking into starting to use Midnight Commander (again). When I run it in a repo, I still see my overall PRs, etc. Is there an option to get it to focus on the current repo?

When I saw 'Sydney 2052' for a split second I felt like I was in a sci-fi movie :D

Reminds me of the day when RIPE NCC announced that they had run out of IPv4 addresses. [1]

[1] https://www.ripe.net/manage-ips-and-asns/ipv4/ipv4-run-out/

Nothing like the good old days of CRT monitors, buzzing floppy drives, loud hard disks, and the good ol' DOS prompt C:>.

I'm really pleased to hear about this and looking forward to the updates in my daily tooling. I feel like for decades I haven't seen a fundamental improvement in diff/merge tooling. It will finally be great to not parse the change in my head. For example, one diff problem I keep noticing has been the curly brace shift when you add a new function or a block. Even if it can only identify those, that would be a win for me.

hah, I'm the same too, straight to 'perl -lne'. I believe that was one of Larry Wall's goals when creating Perl:

> Perl is kind of designed to make awk and sed semi-obsolete.

https://github.com/Perl/perl5/commit/8d063cd8

I did follow FASTER implementation long ago. I thought it was very promising as a persistence library for a proof of concept project with high performance requirements I was working on then. BTW, it looks like both efforts are lead by the same person [1]

[1]: https://github.com/badrishc

It's intended for 'cloud-native' deployments, as I understand it, so I concur that it's quite disappointing. The concept of downloading compilers via NuGet doesn't sit well with me either. However, I've observed performance enhancements in applications compiled AOT, and I remain optimistic that future versions of .NET will bring further improvements.

I primarily use JetBrains Rider for my daily tasks, and I agree that while you can use VS Code or even Vim with LSP support for many projects, working with substantial ones such as the runtime or ASP.NET Core development might practically necessitate using Visual Studio. By the way, the Visual Studio Community Edition is available for free for virtually all projects I can think of, mainly for personal, non-commercial, or open-source usage. The license details can be somewhat unclear, but that's my understanding of it.

This is excellent news for people who needs to run Redis (or compatible in this case) directly on Microsoft Windows Server, without relying on WSL2. Previously, there was a Redis port available [1] (which is now in archive status) that had memory usage issues (mainly because of memory-mapped files AFAIK) and, of course, is no longer supported.

It's also quite intriguing for me to see it's written in C#, as that's my native tongue. I'd be keen on dedicating some time to delve into the code.

[1]: https://github.com/microsoftarchive/redis

This brings back memories of my initial foray into the Internet, when I was part of establishing a modest ISP. We used a satellite link, a Cisco router, and a couple of Sun workstations. Oh, and I mustn't overlook the 33.6 kbps modem server hooked up to a bunch of analog phone lines. Configuring Sendmail, Qmail, Bind, and web servers (specifically a Netscape server), along with CGI programming using Perl 4, was part of the experience. I also delved into learning about IPv4 static routing, followed by BGP, among other things. That was fun.

I recently faced a similar hurdle with Nix, particularly when trying to run a .NET 8 AOT application. What initially seemed like it would be a simple setup spiraled into a plethora of issues, ultimately forcing me to back down. I found myself having to abandon the AOT method in favor of a more straightforward solution. To give credit where it's due, .NET AOT is relatively new and, as far as I know, still has several kinks that need ironing out. Nonetheless, I agree that, at least based on my experience, you need a solid understanding of the ins and outs before you can be reasonably productive using Nix.

Thanks, didn't know about this. I guess Netmaker (or similar) manage the keys for you which would make the admin a lot easier. In a previous job we setup and managed wg across a few Windows and Linux boxes using Ansible. It was OK but was getting a little messy in the end.

> ...or in a cardboard box

When I saw the picture of the server mounted in a cardboard box, my first thought was about fire hazards. It turns out that might not be as big an issue as I initially thought, since paper won't spontaneously catch fire until reaching ~200C [1], and the operating temperatures of computers generally shouldn't exceed 100C. However, I'd still be a little wary about a cardboard setup, considering the potential for electrical faults, the heat generated by power supplies and the risk of inadequate ventilation leading to hotspots. These factors could present a significant fire risk. My initial judgment of the setup may have been too quick but not entirely unfounded I guess!

[1] https://en.wikipedia.org/wiki/Autoignition_temperature

IDEs such as JetBrains Rider and Visual Studio offer a .http file feature for making HTTP requests, reducing the necessity of tools like Postman and Bruno, particularly for basic scenarios. Regardless, I'm happy to see Bruno as an alternative. I don't often need to test HTTP APIs but when I tried Postman in the past signing up was just too painful when I only needed to use it for a few basic calls.