Removed by mod

There is no way legacy projects are going to switch to Deno. Even when Deno is 100% compatible, the only advantage Deno provides is slightly higher performance. Node’s complexity problem? All those configs needs to be supported for compatibility anyway. Typescript? The project already has tsconfig.json set up, so they might as well continue to use tsx. Security? I bet users will just get tired and use -A all the time.

To benefit from Deno, Node’s legacy needs to be shed.

Wine is a different case. The reason Wine makes sense is because Windows is so much worse than Linux that even with scrappy game compatibility, Linux offers a better experience. For Linux users, the alternative to Wine is not switching to Windows, it is not being able to play games. On the other hand, legacy Node projects have a very easy alternative… just continue to use Node.

And btw Bun is making the same mistake.

Check if there’s any large file in /tmp and /run/user/*?

Through compatibility, Deno established an upgrade path.

Sure, but Node compatibility needs to work, and it needs to work reliably. Which means every last detail of Node needs to be supported.

This is what I am trying to convey… the engineering effort to make an objectively better JS runtime while being Node compatible is likely too much effort. Many popular Node projects are already having issues with Deno. Now imagine how the compatibility scene will look like with every single proprietary Node project out there.

So instead of trying to replace NodeJS or offering an upgrade path for existing Node projects, incentivize formation of ecosystem around Deno.

Statistically speaking, you are right.

I am sure there are Linux users that don’t ever use ssh and would look at you quizzically if you asked them about bash.

Pretty sure these users are few and far between. I haven’t found any of them.

Now it is possible that where you live, there is an abundance of Windows/Powershell experts and novice Linux users who only use Facebook. I’ll accept if that is your reality. All I can observe is that curious/enthusiast types tend to use Linux whereas others use Windows. People who want to better their situations tend to switch to Linux.

You should criticize Windows,

That never went well for me. Criticizing Windows is like talking them down for buying a car or calling their baby ugly. If you criticize Windows, Windows users will defend it.

What does work is to just stay silent and let Linux be better at getting my job done. Curious ones will observe and switch to Linux on their own. Others will continue using Windows.

Pretending that it doesn’t have excellent built in tooling doesn’t help your case.

Tooling can be installed. It is not a big enough factor in choosing an operating system.

And pretending that Windows doesn’t have built in tooling totally helps my case. Windows users have different expectations from their operating system. Windows is expected to be GUI based, so why will it have an SSH client? (except that it does) And why will it have a decent scripting language? (except that it does) And all software is installed by double-clicking on an .exe (except that Windows has a package manager)

My case is about people, not operating systems.

For me, Windows hasn’t fixed its myriad of reliability, performance and trust issues in over a decade, no amount of built-in tooling will make me return to Windows. Windows users on the other hand will tolerate the issues, or at most make it only as severe as previous Windows version. You see how difference between the users is playing out, right? The enthusiast types observe that a better experience is possible with Linux and become Linux users, and remaining users stay with Windows, mostly tolerating whatever Microsoft adds to Windows updates. Over time, Linux users and Windows users drift apart and become very different.

I bet very few people know that there’s an openssh client already installed in Windows.

Same with Powershell, I have heard it is quite capable but in practice Windows users tend to not know powershelI. I haven’t found anybody IRL who knows Powershell.

My goal wasn’t to criticize Windows, I wanted to show how much our experience is different from Windows users. It is not about windows vs Linux, but about how windows users usually do things vs how Linux users usually do things. Relatability is a powerful social force that I hadn’t accounted for, and now it just bites me.

I miss the human connection with those around me who use windows. After years of using Linux almost exclusively, I now miss being able to relate to them. Sometimes I feel lonely because of it.

Colleagues get to resonate with all the windows slowness and reliability issues, and I can only stay silent.

“Hey, how can I do this obscure thing?” “Oh yes that’s easy… err… no, I don’t know.” So many methods that are easy on Linux are basically impractical on windows. E.g. many text file processing tasks are doable swiftly with simple shell scripts or even bash one-liners; what will a windows user do? Telling them to automate something means suggesting them to create a new Java project. Opening an SSH session means using Mobaxterm which limits the number of sessions you can create.

Testcontainers uses ‘ryuk’ to clean up containers and it needs docker socket mounted within its container to work. So if you had any hardening config that prevents the docker socket access within a container e.g user namespace or SELinux then Testcontainers doesn’t work.

And I think it would be nice if Testcontainers ‘just worked’ with Podman without any additional steps.

Nothing else. Though docker socket issue was important enough.

You have to practice switching between neovim and other editors.

You have forgotten how to use a normal editor. I am not making it up, it is a real phenomenon. Similar to when SmarterEveryDay learned to ride a backwards bicycle he forgot how to ride a normal bicycle and essentially had to re-learn it. You have to re-learn how to use a normal editor.

1. It might be a card grabber.
2. Don’t put real card details of course.

Thanks man, my brain was short-circuited on Testcontainers so I couldn’t write better. Also I am stealing the title.

I don’t get it, how would a database container run your unit tests? And unless you know some secret option to stop the database after, say, it is idle for a few seconds, it will continue running.

The purpose is to test database dependent code by spinning up a real database and run your code against that.

For me the value of podman is how easily it works without root. Just install and run, no need for sudo or adding myself to docker group.

I use it for testing and dev work, not for running any services.

It’s the same picture.

Here you go

Yes it is the ratings on winehq, https://appdb.winehq.org/

And yes, an average user probably going to fire a game, figure out it is not working, and promptly go back to windows, which makes that data less accurate, but what can we do about it?

The left axis is total number of ratings of each type (Garbage, Bronze, Silver, Gold, Platinum) in a given month (not per app). For example for month 2016-07 there were

  "Garbage" => 22
  "Bronze" => 14
  "Silver" => 13
  "Gold" => 55
  "Platinum" => 61

On right side is the average rating. So if I assign values to each rating:

  "Garbage" => 1
  "Bronze" => 2
  "Silver" => 3
  "Gold" => 4
  "Platinum" => 5

I can get an average rating, which will be between 1 to 5.

((22*1) + (14*2) + (13*3) + (55*4) + (61*5)) / (22 + 14 + 13 + 55 + 61)
 ~=  3.721

That advertisement would be interpreted as Node C’s advertisement.

The plan is to treat public keys as node’s identity and trust mechanism similar to OpenPGP (e.g. include any node key signed by a master key as a cluster member)

Right now, none of the encryption part is done and it is not a priority right now. I need to first implement transitive node detection, actually forward packets between nodes, some way to store and manage routes, and then trust and encryption mechanisms before I’d dare to test this stuff on a real network.