Eventually, we'll have to either decide to get serious about not burning fossils, or not.
If we do become serious about it, there's no reason internal flights that can easily be replaced by slower rail today, shouldn't be pay as high taxes for fuel, as the cars do.
Cars can also be more convenient than transit, and we tax them for it.
There's a story I heard about the oil industry in not-europe. Flaring off natural gas because it wasn't economically feasible to capture it and store it for energy is just "how things were". Ever idiot can see it's a waste, but it takes a special government to see how to fix that waste.
Talk to the engineers to figure out how much it would cost to capture that natgas. Set the fine for flaring natural gas to be that, + $10,000 or so per day.
Voila! Suddenly it's economical to capture that natgas.
Yeah, golang is a particular nightmare for SIMD. You have to write plan 9 assembly, look up what they renamed every instruction to, and then sometimes find that the compiler doesn't actually support that instruction, even though it's part of an ISA they broadly support. Go assembly functions are also not allowed to use the register-based calling convention, so all arguments are passed on the stack, and the compiler will never inline it. So without compiler support I don't believe there's any way to do something like intrinsics even. Fortunately compiler support for intrinsics seems to be on its way! https://github.com/golang/go/issues/73787
> Go assembly functions are also not allowed to use the register-based calling convention, so all arguments are passed on the stack, and the compiler will never inline it.
Even if you had access to the register convention (which you kind of do), would it be of any benefit? The registers in question are general-purpose registers, not vector registers.
You're both stating things that are a bit beside the point.
Pure Go code uses registers to pass function arguments whenever possible. Large structs and/or numerous arguments can still spill onto the stack, though.
FFI (cgo) uses whatever the platform's calling convention requires. These conventions also usually favor registers.
Go has its own assembly language, which is neither of those two things. Go assembly technically supports two ABIs, one called "ABI0" and the other called "ABIInternal" [1]. The former passes all arguments on the stack and is stable while the latter passes some arguments through registers but is unstable and subject to change. Accordingly, people writing Go code outside of the Go toolchain almost always use ABI0, so that the code keeps working even when new versions of Go are released.
To be fair, Java's lack of support seems to have more to do with them needing to fix the whole primitive vs object mess rather than a lack of effort. It sounds like the Vector API will be stabilized shortly after they figure that out, but who knows how long it will take.
Changing buttons or live results are annoying, indeed.
Something I find worse: being unable to click a target while the animation is running!
Because the target only gets focus after the animation is done: you start spending you time waiting for the animations in the end.
But, the way is not working: even today flights are faster and often cheaper than trains, with less delays.
reply