PhilipRoman

Your process can crash or be killed at any moment anyway. Depending on in-band cleanup is not reliable.

I haven't given this more than 5 seconds of thought, but wouldn't it make sense to only enable the timing attack prevention for pseudo-terminal sessions (-t)?

It can be about as fast if you set key repeat delay to minimum and repeat speed to maximum. I used it for a while and got quite precise with it. Works well until someone else needs to use your computer for a moment...

This is completely safe: [ "${payload}" -eq 42 ]

This can evaluate arbitrary code: [[ "${payload}" -eq 42 ]]

Here is one example of a malicious payload:

  payload='a[$(touch /tmp/pwned)]'

[[...]] is non-portable and has an extremely quirky corner case with variable expansion in arithmetic contexts, what's not to love?

That's just because glibc is not designed for static linking. It works, but it doesn't exclude unused code, unlike with other libcs.

Indeed, also userspace-level atomicity is important, so you probably want to save a backup in case power goes out at an unfortunate moment. And since you already need to have a backup, might as well go for a full rewrite + rename combo.

Yeah there are, Linux supports parameters FALLOC_FL_INSERT_RANGE and FALLOC_FL_COLLAPSE_RANGE for fallocate(2). Like most fancy filesystem features, they are not used by the vast majority of software because it has to run on any filesystem so you'd always need to maintain two implementations (and extensive test cases).

Bob wants a deb. I tell him to pound sand and give him a statically linked executable and pray that DNS works. If the software is still relevant in five years, some Debian maintainer will take an ancient version, convert it to use shared libraries, apply a dozen patches and give a .deb to Bob.

>should

This word is doing a lot of lifting here. You are essentially saying "the world should be better" without even a hint of suggestion of what a minority of countries could do to achieve it (in the presence of adversarial, nuclear states)

...and other hilarious jokes you can tell yourself!

Any medium or large C project has these kinds of project-specific (or sometimes company-specific) collections of log macros, error handling macros, etc. The amount of boilerplate here is minimal compared to that.

Fun fact: <details> even works on github and similar sites with markdown-based input. You can post large inline logs in issues without cluttering the conversation.

Wow, I used to be able to search google even from terminal browsers like 'elinks'

Please let this be masterful sarcasm

Does Julia registry have active moderation? Otherwise I'd expect to see 99 different variations of DifferentialEquations.jl

It's especially fun once the service is superseded. Guess which one of these services handles MAC address allocation and storage: macaddr_db or atom-util?

Thanks for mentioning this. I built the same thing a year ago for myself in dozen lines of AWK. Looks like great minds think alike :)

In my opinion this is the most practical approach for real world projects. You get benefits like avoiding outdated documentation without huge upfront costs.

Personally I do a daily sync from the underlying gocryptfs to Backblaze B2. It's also on btrfs so I can do snapshots, etc.

How is the bootloader/peripheral compatibility on the non-SBC ARM systems these days? Can you plug in a boot disk on different machine and expect it to just work? My main problem with ARM is that many manufacturers act as if they're special little snowflakes and deserve to have their custom patched kernel/bootloader/whatever.

You can customize anything, the problem is always how maintainable your customization is. People keep making FrankenDebians (https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_Frank...) using curl|bash install scripts, alternate repositories or just plain brute force symlinking libraries with a hefty dose of chattr +i.

A properly customizable distro allows organizing and tracking patches in layers, etc.

What? Python's standard library seems far more extensive than Java's.

Not to mention overcommit has become standard behavior on many systems, so you wouldn't even get a NULL unless you really tried.

Disabled on most CPUs, plagued by security issues. I haven't used it but I assume debugging would be extremely painful, since any debug event would abort the transaction.

No idea why this was flagged. This is a really good article in terms of both form and content and I was very surprised to learn that the author is actually also a teenager.

I get it, some people dislike the appearance but c'mon, this is HN. If we can use vi(1) on a 80 column terminal, reading an html page is not an impossible task.

FWIW it's smooth on my $150 android shitbox.

I think it's coroutines as in other JVM languages like Kotlin, where yielding may be implemented internally as return (due to lack of native coroutine support in JVM).

Holding a lock/monitor across a yield is a bad idea for other reasons, so it shouldn't be a big deal in practice.

The website seems to be just AI filler, I guess this is the real GitHub repo: https://github.com/am-kantox/cure-lang

I was curious about the examples but this does not seem promising...

  def sort(list: List(T)): List(T) where Ord(T) =
      match list do
          [] -> []
          [pivot | rest] -> sort(rest)
      end

I believe refresh rate/FPS is one of those things where it doesn't really matter but human eyes get spoiled by the higher standard, making it hard to go back. I never saw issues with 30 FPS until going to 60, etc. Hopefully I never get a glimpse of 120 or 144Hz, which would require me to throw out all existing devices.

Is it really that much better than some small form AMD Ryzen with 2x32 SODIMM thrown in? I get that the M series is amazing in terms of efficiency and some people love Apple hardware but you could likely have had that performance with a $700 setup.