iambvk

What he probably means is data-races in go can result in memory/type unsafe accesses -- I suspect, likely due to slice types -- not sure if that is true/false.

I like this approach. Thank you.

Would it work if a user's device that is already connected to the VPN, but has custom DNS override to say 8.8.8.8 ? How can I allow my users to be able to use 8.8.8.8 DNS override and still work seamlessly?

There used to be a Debian Live iso builder website for building custom Debian Live isos. It probably is discontinued, I can't seem to find it anymore.

Only looked at the first two examples. No language can save you when one writes bad code like that.

Thank you.

> No, it does not always crash.

Can you give me an example that I can reproduce?

> No. It's undefined behaviour, it may do anything or nothing.

This is clearly nonsense.

Doesn't null-pointer-dereference always crash the application?

Is it only an undefined-behavior because program-must-crash is not the explicitly required by these languages' specs?

What is the justification to call `Null pointer dereference` as a memory safety issue?

My favorite monospace font is "Ubuntu Mono" for ages.

As an engineer, I like to see -- for the lack of better word -- some taste instead of characters being too formal and too symmetric. Ubuntu and Ubuntu-Mono satisfy this to a good extent without being too much, like in comic sans.

The closest font with similar taste, which I found recently is Mononoki

This is a necessary condition for CBDC goals (now being marketed as Stablecoins).

I am actually more interested in removing/reducing even more features from Go than adding more features.

Is anyone able to get streaming audio to text conversion working with whisper.cpp?

I tried several times to get this into a reasonable shape, but all have been failures. If anyone has pointers I really appreciate it.

Peter does this every few months on Hackernews.

I am not a sysadmin -- so I keep forgetting the command to see logs cause I only need it once every 3 months.

So, systemd change is a pain for me.

IMO there is another level in between 3 and 4 where config file allows for cross referencing among config values, forming a graph.

   foo.password = xxx
   bar.password = yyy
   wifi.ssid = foo

Yeah, they sure forget their faults fast.

The amount of hatred Dems showed openly during 2016 election run was truely something special.

I am working on implement on-disk B+Tree for the last few months. Man, keeping the on-disk state consistent with proper locking is a real challenge -- specially when we want to avoid IO-holding-mutex. And forward/backward iterators make me doubt the correctness.

All this with just fixed size keys/values. I am yet to start on variable sized keys and values, but I already want to give up on my initial performance targets.

> The total hosting cost for the conference was USD 42.92 + tax and the BBB testing in the lead-up to the conference was USD 3.11 + tax, so a total of USD 46.03+tax. The web node and the livestreaming node are kept as 1GB nanodes the rest of the year (USD 5 x 2 servers + tax, so USD 110). Very manageable.

How does this compared to all other conf costs?

Cool. Thanks.

Does this support the non-standard key-press, key-release, etc. events proposal by kitty project? They are necessary for nicer terminal UI projects.

Thanks for this information. I wasn't aware that using 64-bit ints makes such a big difference in performance. Thank you.

Golang folks, after looking at the code, I am surprised and don't understand why Go version is slow compared to C/C++/Rust. Can anyone please explain? Thank you.

What are the downsides of just adding new methods on the `Config` structure?

    func (c *Config) WithFizz(...) {...}

    func (c *Config) WithBazz(...) {...}

> ...since they can't be bothered to write the 3 lines of code...

They actually think saner devs have not-invented-here syndrome :0

It is: two writes for write ahead log vs. log-n (tree-height) writes for CoW

After being through weapons of mass-destruction narrative sold to us by mainstream media to justify the Iraq war, it is very disappointing to see younger Americans parroting every mainstream media narrative, without a question nowadays.

I sometimes wonder if I should just leave US forever, to not be part/beneficiary of its future atrocities.

A system with shared libraries also needs an update for the security fixes. There is no avoiding the update step. However, the only difference is the size of the update. If update process is robust, size of the update shouldn't matter, isn't it?

Destination port number should be sufficient.

For example, imagine if there are two sockets established between server and client processes (due to multiple ips or roaming, time lags, etc.), then in theory, request received from one socket could be responded through another socket. From application pov it doesn't need to care about the socket. We can do this over TCP, but connection-oriented nature of TCP makes this weird.

Good to learn a bit of history about TCP.

It always felt weird developing RPC layers on top of TCP cause requests and responses end up tied to the underlying socket -- which doesn't need to be the case ever.