vince14

> and energy storage

What do you think this means? It doesn't mean what you think it means.

Quoting LCOE and ignoring system costs disqualifies you for any discussion on this topic, sorry.

That is not the case. There are LCOLC, LFSCOE and others which land on renewables being way more expensive. Even without your made up claim about "assuming cheap and fast to build nuclear power".

Storage is not just 'a problem', it doesn't exist and won't for many many decades.

The planned solution is hydrogen power plants, but no one wants to build them because the infrastructure, including electrolysers, is way too economically unfeasible.

Therefore, Germany is and will continue to be dependent on coal and gas, as these are the main producers every night. That's your 'grid backup fee' for you.

Because projects like these were missing back then, I got creative with nginx and do not need any config changes to serve new projects:

  server {
    listen 80;
    server_name ~^(?<sub>\w+)(\.|-)(?<port>\d+).*; # projectx-20201-127-0-0-1.nip.io
    root sites/$sub/public_html;
    try_files $uri @backend;
    location @backend {
      proxy_pass http://127.0.0.1:$port;
      access_log logs/$sub.access;
    }
  }

Configuration is done via the domain name like projectx-20205-127-0-0-1.nip.io which specifies the directory and port.

All you need to do is create a junction (mklink /J domain folder_path). This maps the domain to a folder.

Fire-and-forget?

Creating clips from tv recordings:

    ffmpeg -ss 01:59:00.000 -i "interlaced.ts" -ss 00:00:12.000 -t 26 -max_muxing_queue_size 1024 -c:a libopus -b:a 96k -c:v libx264 -crf 20 -vf "yadif=1" -profile:v baseline -level 3.0 -pix_fmt yuv420p -movflags +faststart -y clip.mp4

Make clip compatible with WhatsApp:

    ffmpeg -i in.mp4 -map 0:v:0 -map 0:a:0 -map_metadata -1 -map_chapters -1 -c:v libx264 -preset slow -tune film -crf 32 -c:a aac -b:a 128k -profile:v baseline -level 3.0 -pix_fmt yuv420p -movflags +faststart out.mp4

Copying in various terminals:

    PuTTY: select
    tmux: Shift + select
    cmd: select + Enter in quick edit mode
    Windows Terminal: select + Right Click

whoami

> Introduced arbitrary code execution via ${jndi:ldap://... inside any logged string.

hehe

Me too, that's why I always have `html { overflow-y: scroll; }`.

> no threads

> node does not have a concurrency and parallelism story

> standard library is tiny

Also claims like "async makes your program more difficult to reason about" without any explanation.

I hereby claim that goroutines and mutexes make your program more difficult to reason about.

> the ecosystem is an absolute dumpster fire

I am super curious which ecosystem that person would consider better.

I think many people feel threatened by the success and the pace of the Node.js ecosystem.

Most arguments, even in this thread already, are just wrong. Obviously they have never had any experience with the Node.js ecosystem and another.