qtxie on master
FIX: issue #5153 ([Regression] … (compare)
qtxie on IO
FIX: more error handling when c… (compare)
qtxie on IO
FIX: remove some debugging logs. (compare)
struct!datatype, which would be more memory friendly than
block!and would provide named accessors to all values.
[1 2 3 4 5 6 7 8 9]vs
[[1 2 3] [4 5 6] [7 8 9]]. Nesting, and keys vs positional values, add overhead, but also information. There is no single solution that it best in every case, so it will be interesting to see what comes of your work.
Everyone I hear using the M1 are a bit shocked at how fast it is, even on a Mac that only has 8 GB RAM. The key to the design is very wide memory buses and of course having all the memory right on the main chip. Also, each CPU core can saturate the memory controller that can handle around 60-70 GB/s. An intel/AMD CPU core can only do 15-25 GB/s. That's pretty astounding.
Then of course is the low TDP of less than 30 W can make it do long running tasks with little cooling needed. The GPU isn't very powerful though. The cost is also presently only a maximum of 16 GB RAM.
What is even more interesting is that Mx series CPUs will grow much faster in the near future, if Apple's CPU speed ramp will be maintained from the earlier Ax CPUs. There's lots of low-hanging fruit left for Apple to pick.
We are in the plateau region of the development curve, where almost nothing changes. If you put more than 10 cores in a chip you don't get much useful work out of it, so we are flattening out everywhere in the computer biz.
We have still a large margin of improvement in software. Algorithms are tuned for single processor tasks. Once they will move to multi-core operations we will see again a lot of improvements.
formatexploration. In addition to the typing issue, it's universal but also universally unknown. :^\ One thought I had in
$could be literal for that symbol, but
¤could be replaced based on a locale setting.