da-x

Why not `thiserror` for executables as well? It happened to me a few times that I started to write an executable program, but then realized I want to embed its functionality in a library. Converting from `anyhow` to `thiserror` at that stage would be extra work that can be avoided.

Occasionally I post some utility for devs working in Linux/MacOS terminals. Here's my recent one:

https://github.com/da-x/foldity

A utility for folding terminal output to fit the screen.

LALRPOP is one of the friendliest syntax parser generators that I ever worked with in any language.

If only issue [1] would be fixed, it would make it much better.

[1] https://github.com/lalrpop/lalrpop/issues/195

Perhaps not impossible - sometime after 2040, a deep learning model reconstructs the entire "Titanic" (the James Cameron film) from a total of 1,000 frames, the script, and voice samples of the actors.

"... And no longer use swap partitions by default." [1]

Finally! I've installed a 256GB RAM desktop recently, and swap is so 90's...

[1] https://fedoraproject.org/wiki/Releases/33/ChangeSet

Yes it is similar, however it targets editing commits that already exist instead of operating on the index or worktree.

Thanks! This is really needed in a world of constantly distractedly updated news feeds and doomscrolling. I'll try having this in a tab, F5 once a day. Just to get that feel of "I know what's going on".

Assuming that Github static pages infrastructure is maintained without breaking CNAMEs for the next half century, and assuming you pay for your domain 50 years in advance, maybe the static website can remain for that long?

> * They ship a ton of mingw-w64 libraries. It's super nice to not have to cross-compile a bunch of dependencies when I'm building something for Windows.

Still shipping, however they dropped EPEL7 support for it :( Issue about it here:

https://pagure.io/fesco/issue/2333

Nice! Looking forward to it.

The bundling of 1980's synth music is also nice. Why I find synthwave so alluring, perhaps it promotes nostalgia which chronologically depicts times that are most farther than the horrors of the 1940's and the troubled times of present day 2020.

That's true. The effort was very concentrated.

Those days in late 2003 were crazy. Waking up at noon to work on it for until 9:00pm, and then off to a night shift writing boring tests script stuff until the morning. And also weekends. It was like a full time job with extra hours during that month. Was full head-on stamina at age 21, and I don't even drink tea or coffee.

Interestingly, if it wasn't for the boring night shift job I had back then, I would have never found all the time back at home during the day time to do all this. And once I figured out how I want to write it, nothing stopped me until it worked.

These two are not mutually exclusive. To be more exact, coLinux is a VM running under a device driver. The driver is mainly just a bridge to get into the privileged execution path and manage the resources it needs.

There's an interesting thread [1] on github.com regarding this.

Here is a copy of the comment I added there:

I was not surprised when Microsoft took the approach with WSL2, as I've gone a similar path when writing coLinux. I've considered extending an existing project named LINE, which is more similar in architecture to WSL1. Not having the full resource of a development team, I took the easier cooperative VM approach. Re-implementing stuff is a pain. Integrating is more fun.

However I think both WSL1 and WSL2 have their added value being active projects. WSL1, is good for being more 'in the Windows domain of things' compared to WSL2, and not requiring a hardware-accelerated hypervisor behind the scenes. For WSL2, back when writing coLinux, I've imagined the things that could have been gained if I had had access to the Windows internals, especially regarding memory management. I believe that the Windows dev team has a much better chance to make Linux more compatible and smoothly integrated in a performant way with this approach.

Perhaps it's too late, but I wish that the two approaches would have had different names so to not suggest that one is entirely newer or better than the other.

[1] https://github.com/microsoft/WSL/issues/4022

I'm the original author of this project. It warms the heart to see that it helped so many fellow hackers to introduce themselves to Linux!

Recalling this, it makes me feel quite a old hack, when I started this back in December 2003, without Git, through mailing lists, and on sourceforge - oh boy. Would have definitely been easier maintaining this project with all the tech, the reach, and the amount of potential contributors that we have today.

A few years after the project was created, I was contacted occasionally by people who wanted to assist in developing a 64-bit port. This required the same technical depth in kernel hacking as recreating the thing, and quite a lot of work. Unfortunately I was occupied with other things and it never fell through. Also, hardware-assisted virtualization came about the same years and made the project somewhat obsolete. It was still very good for its time!

It's useful, but makes you wonder why they haven't taken it one step forward and allow you to edit the diff too while you're at it.

Back a year and a half ago when Tesla short sellers were thriving on twitter, it often happened that links to ZeroHedge started a negative newscycle regarding various rumors. I wonder if the operators of ZeroHedge are part of this short-sellers community.

It's 2020, and I'm still waiting to see an impressive proof of work out out of a quantum computer that I can easily verify on my traditional computer (two different files with identical SHA-512, for example?).

Maybe a few years from now?

I think this should be taken with a grain of salt. You can't be physically shedding large quantities of virus if you are not coughing or sneezing, and being exposed to large quantities is essential for infection.

I wish this could be extended to "Learn X in Y minutes coming from already knowing Z". However this (X,Z) matrix is hard to maintain...

There's a difference between

    let _ = <expr>;

and:

    let _x = <expr>;

The first one drops ownership over the variable right after `let`, and the second drops in the end of the scope where the `let` is contained. It was mentioned in an open Rust github issue, but I can't seem to find it.

Correlates with the rise of the 'Like' button somewhat. But could be a false correlation.

Choose a distro that doesn't have middle-men between the packages you use and upstream open source. Like Fedora or Debian. For what I mean by middle-men, I'll give a counter-example: Kubuntu, that is based on Ubuntu, that is based on Debian, that is based on upstream projects. I think that these chains add unnecessary complication to all parties.

I recommend Fedora due to the superb packaging done by the Fedora community (and supported by Red Hat giant). And if you like a desktop environment like KDE, you can just install it, or start straight from their KDE Plasma Desktop spin.

Various kinds of medicine also save many people, while killing small few who are unexpectedly sensitive to it. Does not mean we should abolish medicine altogether, right? Same goes for autonomous cars, after they are proven to be safer by average.

Thanks!