Check out Asahi Linux, they run on Apple Silicon and have translation for 32 and 64 bit x86, so they even go further than what Rosetta achieved. Open Source as well.
The article states that they added a computational correction step which is run whenever a result might be incorrect but skip it most of the time.
I am wondering whether this might cause problems for small real-time systems that do not have an FPU. If the runtime cost of an operation depends on the input, it is very hard to figure out whether deadlines can be met in all operation conditions.
Great post, the fusion of scale with unit is a mess.
When using it as a factor, for example when describing attenuation or amplification it is fine and can be used similar to percent. Though the author is right - it would be even more elegant to use scientific notation like 1e-4 in this case.
For using it as a unit it would really help to have a common notation for the reference quantity (e.g. 1mW).
But I guess there is no way to change it now that they are established since decades in the way the author describes.
I could see that in the coming years the value of Waymo for Google is not actually in collecting revenue from transportation fees but to collect multi modal data to feed into its models.
The amount of data that is collected by these cars is massive.
The position of the guitar in stereo is all over the place, higher frequency elements appear to come from the left while other parts are more centered.
At the same time France had to buy loads of electricity from Germany in the last year because several nuclear plants had to shut down due to a) maintenance problems and b) low rivers that could not provide sufficient cooling.
You also pay for quality control.
Cheaper brands often have decent audio quality on average but high variation in between individual pairs of headphones. They also tend to fall apart after 1-2 years of use in my experience.
You can modulate the brightness without flicker, you can try it yourself with a lab power supply.
It is just that filtering the output of the regulator is “expensive” as you need a relatively large capacitor. If this is omitted in combination with a low frequency PWM, you will experience flicker.
I assume the author of the library works under a hard real-time constraint. Under such circumstances (an example would be low latency audio) you can not tolerate the latency impact of a sporadic syscall.
According to an article at Ars [0], longer sessions are more likely to output undesired responses from bing chat. So the limits might simply be a workaround to avoid articles about strange behaviour.
I would argue that the people who use AI generated assets and combine them for a bigger thing such as a video game are still artists. They are simply realizing their vision on a higher level.
Boston dynamics also published a making of video. There it is explained why the luggage scenario is still far away: The robot has perfect knowledge of the object it is transporting (size and weight distribution). In order to be able to transport any object, the control algorithms need to be able to estimate themselves where to grip an object and what the objects weight distribution is.
Very interesting read. The author notes that double pumping the 512 bit instructions to 256 bit execution units appears to be a good trade-off.
As far as I understood ARMs new SIMD instruction set is able to map to execution units of arbitrary width. So it sounds to me like ARM is ahead of x86 in flexibility here and might be able to profit in the future.
Maybe somebody with more in-depth knowledge could respond whether my understanding is correct.
I am also curious how this period in movies will hold over time. Older movies with more practical effects (such as Star Wars) still have a very crisp look to them while newer movies look blurry and bloomy due to the heavy post processing.