liftm

Ignore the JS bashing (it is deserved but irrelevant here).

I was referring to the part explaining the 2028-2040 METAL system where "we" gained 4% execution speed because we stuffed all things into a asm.js VM in kernel that can skip syscall overhead. But it's a joke video anyway.

Wait, so I've been lied to? https://www.destroyallsoftware.com/talks/the-birth-and-death...

> His name is a portmanteau of Mario's name and the Japanese word warui (悪い), meaning "bad".

If nobody notices, did you really blow up the pipeline?

How do you best use this in practice? Quadtree-split the rendering area while checking edges?

9p-based folder sharing is (used to be?) possible with qemu, too.

> When you run a container on Kubernetes, you don’t specify which computer they run on; you (hopefully) don’t care.

And then you want to deploy something rack aware and you have to deal with `requiredDuringSchedulingIgnoredDuringExecution` in your yaml. Even greater fun ensues if you need some kind of special-purpose hardware.

Sounds quite simple already. I still wonder if for FLAC there's an equivalent of what QOI is to PNG.

How do you run Flink on it anyway?

A quick, entirely unrepresentative look at the user count for uBlock Origin and uBlacklist in Firefox make me somewhat less optimistic than you are. Or is there a more popular way of blocking sites from search results than uBlacklist out there, which I simply don't know about?

Roller coaster cars with electrical motors? I somehow like the idea. Could mess with Gs in one more direction.

Out of curiosity, are there any nuclear reactor cogeneration plants in operation?

Given that the potential disgruntled admin already has access to nukes, this seems useless.

Tinygo is neat, but the one time I tried to use it in practice, it failed me. The following program will panic when compiled to wasm:

  package main  
  import "encoding/json"  
  func main() {  
          var parsed interface{}  
          json.Unmarshal([]byte(`{"test":42}`), &parsed)  
  }

(It's been a while, so I forgot the problem with it was.)

I'm curious what kind of text parsing you do. I ended up rolling with valyala/fastjson, but that's very much not what I was imagining. Lots of existing libraries don't work either, and finding out what does and what doesn't is pain. Is there some trick to working with it?

I've misused it as a load generator before: yes '{"some":"json"}' | kafkacat -P -t bleh (Though in my case, ~100 MB/s were enough.)

Maybe. Or the language will fall into obscurity and everyone will just use the C compiler.

I'm ignorant to the history here, but GCC includes Fortran, Ada, and D compilers, right? I don't see widespread adoption of those…

Open this thread in full, Ctrl+F, "Plutonium", read each post that hits and the one it answers to. That should answer those two questions.

I see some useless use of pv there. dd status=progress is neat.

The rest of hackernews seems to have decided that plutonium is a step on the way to solve the waste problem. What's your take on that?

Not only does the guide not mention it, it seems to actively disagree with you:

> The cargo-outdated tool must be used to check dependencies status. Then, each outdated dependency must be updated or the choice of the version must be justified.

Especially for open source projects, there are also some other arguments against vendoring, see e.g. https://blogs.gentoo.org/mgorny/2021/02/19/the-modern-packag...

If there's something that's missing mention, it is imho that the Cargo.lock files should be committed, and also included e.g. in docker builds. (I don't believe in offhanded "cargo update". And even if you did accidentally type it, nothing will be built/executed yet. There's ample opportunity to git restore Cargo.lock.)

Hm, good point. (It's implemented as a Once (which is an atomic usize) and an UnsafeCell for holding the actual data.) And while using SyncOnceCell normally might incur some small checking overhead on each access, you can use it to obtain a &'static. https://play.rust-lang.org/?version=nightly&mode=debug&editi...

But then, by tialaramex's logic, isn't it just as bad as Box::leak? (Maybe not quite as, because it can leak maximally one thing. You can't do this in a loop.)

> In a secure Rust development, the code must not leak memory or resource in particular via Box::leak.

Uh, so is Box::leak forbidden in general? Because creating a &'static in some initialization code that lives for the rest of the program is a rather common use case… https://docs.rs/log/0.4.17/src/log/lib.rs.html#1408

Or is it only forbidden if it's actually a leak?

I think we may have different definitions of what significant power means. I managed to break the metal rod inside my plastic pedals one time… But yeah, I used an 8 speed hub gear with a toothed belt for ~7 years, which I don't see breaking any time soon. (Though I did have to walk home a few times due to other reasons, e.g. clogging the gears up with snow or flat tires.) But it doesn't switch gears when under power, and if you start giving power while it hasn't fully switched yet, it makes very unhealthy sounds.

I suspect I'm just not taking good enough care - both while riding and with maintenance. Rusty bowden cables causing misalignment and the chain jumping into weird places… (I've also used some sketchy bikes. One literally had the rear derailleur bolted on because the mounting mechanism didn't fit the holes on the frame. I ended up completely twisting that one.)

I cannot count the number of times I trashed my gears. And the fail-safe is walking. (I assume you're using a fixie?)

Does this work with large semi-transparent objects? (My 10-year-old experience with 2D game engines was that 10k objects wasn't really a problem, unless you were trying to make clouds or fog from ~200x100px sized, half-transparent images. Have a 100 of those, and you'd run at 5 FPS.)

ninja solves that parallelism-issue quite nicely. So do most IDEs.

I'm all for bashing autotools, but in this one case, I'd throw Symantec (SEP?) into the fire first.

And the solution to all build systems being bad is imho not to use C/C++. It's model for platform independence is fundamentally broken. It's not like snafu doesn't exist elsewhere too (Python), but other systems are clearly less troublesome (Go, NPM, Cargo).

If that's the core proposition, yes, I want data on it. If that data is obvious and boring, then so is the proposition.

Besides, the panel can't move, only rotate and tilt. Have you actually read the article? (With rotate and tilt only, pointing directly at the sun should maximize the power output from a single panel even with shade from other objects. You can get a very small amount of movement from the fact that the point of rotation is outside of the plane of the panel. But that's not mentioned at all, is it?)

In any case, if you solve a problem with machine learning that already has a non-machine learning solution, you will get this kind of comment. If on top of that you don't compare the existing solution and yours and show that yours significantly improves performance, it just looks like doing ML for the kicks.

No evaluation then.