Honor X7

[...] The screens looks fantastic. [...] I read a lot of software books that are 10"x7" (I believe that's the standard size for a lot of them) and they can get bulky to hold and carry around when you're not just reading at home. [...]

Here's what robotic mowers blades look like to understand how they work - We just got a Sunseeker X7 to do 4 acres of grassed area but probably 2 acres will be garden beds and roads etc The hardware is there, it's all software now. People talk about updates and the robot improved amazingly, comments like - "these scuffs are from pre-update" These are Elon's updateable cars, they will get better with time. (Sunseeker is also camera not yet LiDAR) Robotic mowers are better than humans, there are a few if's and buts, grass nerds compare the cuts on a grass blade on YouTube for instance. [...] but that might have been my price bracket. [...]

I've used Leuchtturm1917 notebooks (1) as my journals for several years and recommend them; the paper is smooth and good for writing and drawing. [...] The hardcover versions are sturdy, which is perfect because my notebook goes everywhere with me. [...]

[...] Everything works rather well (including gfx/audio/sleep/hibernate), except the camera, which I haven't bothered with. [...] One thing to note w/ this model is you'll need the OEM keyboard to install linux since there's only one usb port; which will be required by the install media. Once you've installed though you can use any bluetooth or usb keyboard you want. Another thing is any micro-usb charger should work but I wouldn't rely on just 1amp, go w/ a 3amp. [...]

[...] The software is garbage, the car is too fancy (electric folding seats) but poorly implemented so it’s just frustrating. [...] New battery is $700. Can only use a BMW battery installed by a BMW technician with computer access (they are coded and only a tech with the keys can pair the new battery to your car). [...]

[...] Thought that it’d be a goner for sure, but no, just scratched up the corner of the frame, it had a soft and rubbery quality to it (at least compared to regular plastic). It was actually a really nice phone, good battery life and everything, except for the part where the battery eventually turned into a pillow and since it’s not exactly easily used serviceable I just moved on. Since, I started to like iOS but my ideal setup functionality wise would still be something one step closer to a brick with a big battery and a protective exterior (glueing a power bank to my current iPhone case would be a bit silly though).

[...] And I'm sure an electric minivan would be better than an electric SUV, except at signaling you can afford to forego the extra utility.

this would be unacceptable for os kernels Depends on the boundary. I can give a non-Linux, microkernel example (but that was/is shipped on dozens of millions of devices): - prior to 11.0, Nintendo 3DS kernel SVC (syscall) implementations did not clear output parameters, leading to extremely trivial leaks. Unprivileged processes could retrieve kernel-mode stack addresses easily and making exploit code much easier to write, example here: - Nintendo started clearing all temporary registers on the Switch kernel at some point (iirc x0-x7 and some more); on the 3DS they never did that, and you can leak kernel object addresses quite easily (iirc by reading r2), this made an entire class of use-after-free and arbwrite bugs easier to exploit (call SvcCreateSemaphore 3 times, get sema kernel object address, use one of the now-patched exploit that can cause a double-decref on the KSemaphore, call SvcWaitSynchronization, profit) more generally: - unclearead padding in structures + copy to user = infoleak so one at least ought to be careful where crossing privilege boundaries

[...] When Atom was new, it had absolutely pitiful performance - much worse than what we got from its contemporaries, particularly considering how much power they took. [...] Even their later Atoms, like the Atom x7-E3950, were bad in real world performance, often being beat by low power AMD CPUs that were years older, like the Athlon 5350. I'm surprised that Intel kept the Atom name after delivering such poor performance that "Atom" became synonymous with "woefully underpowered", but it seems to make sense that Atom is now just a low power, node optimized version of a previous full performance architecture.

[...] Oh, and a genuine systemd peeve; the infamous ctrl-alt-del burst nonsense, where rapid succession (x7) reboots the system, even with the screen locked (unless with physlock).

[...] It is a way to make you work hard and allow to be treated like dirt for less money. [...] I got laid off in a round of cuts just before my options kicked in and thought it was unjust, but a year later the company was sold to a competitor and the investors got a nice return, the founder got another pot of gold, and the employees with stock options got nothing, because it was a private sale and not an IPO. [...]

The camera on my phone isn't so great, I have an Honor X7, it's a few years old. It's ok but I really prefer using a 'traditional' camera.

They both have 0.25TBps memory bandwidth & huge GPUs. They very much are in the same space. I'm very Team Red (AMD) but I dig & respect the 4x 40Gbps USB ports here. Its not popular but it is a good way to attach pretty fast storage. Also the 200Gbps connect-x7 is just awesome. Users can add what they will to Strix Halo, but it's neat seeing good connectivity on chip. I hope AMD can get better about USB4 & Thunderbolt 4. It really feels like it should be part of their APUs. Apple shipping 6x TB5 ports on the new M3 Ultra is a beautiful example of what life should be like.

[...] I didn't play the other X games until years later. [...]

I wrote something like this for fun years ago, although I don’t think I published it. I think my library had a scale defined by a root note and a set of steps. A chord could be constructed from a scale and a root note, with modifiers such as inversions and others like X7, Xb513, etc. The scale has the blueprint and the notes follow. You already have the primitives with notes and intervals. Parsing chords from notes is more difficult, as are most parsing tasks.

I read (30 years ago) the book "Microprocessor Design" by Nick Tredennick. He was the architect and wrote the microcode for both the 68K and the S/370. The S/370 was based on his recent design experience with the 68K, but it wasn't just a microcode swap. In the book he describes his process where he would write the ucode for each instruction on a 3"x5" card (or was a 4"x7"). At times he'd find sequences that were too clunky and then go back to the circuit design folks and ask for them to add some extra logic for that corner case to make the ucode more efficient. The book also had a glossary section in the back and a number of the entries were funny. One I recall was his definition for "methodology", which was something like "A word people use when 99% of the time they mean 'method'."

[...] They're cheap, and portable. [...]

so it's easy to go round in a few minutes x7 days a week. But it's not just the time in the store, it's also whatever detour there is to get to it. At walking speed. Whatever the wait time is at checkout. less if you know exactly what you want. So now, I also increase my mental load because I need to know what I'm cooking tonight an hour or even two hours before I do so? I have to have my meal planned out hours in advance. And if there is another pandemic like event, I'm also constrained to the one day's supply of food that I have in my house at any given moment (maybe less than that, realistically). And it's still a fucking pain if I'm anything other than single. There was a point in my life not so many years ago, when we were going through about 4 gallons of milk per week. Hell, some of the things that we like to eat, that we should be eating for health reasons... you can't even buy those in single meal sizes. We'll probably have 3 (plastic) bags of vegetables home for salad.

SUVs are not pickup trucks though and have better visibility of the road ahead (due to higher eye level and higher headlights) than cars and minivans. As for internal storage, I am content with the internal storage in a midsize SUV already. Third row in X7 is pretty cramped, if you are regularly driving 7 adults around you better get something with more seating capacity, few people need that IME.

Here's that TECO macro (have fun!): [4 [5 [6 [7 [8 [9 +0U7 0,0X4 10U4 [4 ETU4 [4 EDU4 [4 EUU4 [4 ^D ET&(12864321^)5121682ET ED"G 0ED ' @^U5/U9 ET1ET 27^T Q9^T ET&(1^)ET/ @^U6/.U8 ZU4 -3U6 ^^HM5 13^T ^^KM5 10^T ^^KM5 13^T :G4 < ^TU7 !F! Q7^T ZJ Q7@I%% Q7-10"E 13^T ^^KM5 -1%6 ' Q7-21"E Q6^W 0U7 0; ' Q7-127"E -D Z-Q4"N -1AU9 -D Q9-27"E 32U9 ' Q9-31"G ^^DM5 ^^KM5 1+ ' 0"E 13^T -Q6-2< ^^KM5 ^^AM5 10^T 13^T :G4 Q4,ZT ' ' ' Q7-27"E ^TU7 Q7-27"E !F0! 27@I%% Q4,ZX4 ^^HM5 13^T -1U7 0; ' Q7-^^?"E ^T^[ @O!F0! ' @O!F! ' Q4,ZK Q8J Q7/ 0,0X7 G ^YX8 ^YK 0,0X9 ^^HM5 13^T ^^=M5 < !A! 0U4 0U6 !B! 1U5 ET32ET ^TU7 ET&(32^)ET Q7"L -1^W ^TU7 ' !V! Q7-127"E .-Q5"L .U5 ' -Q5D @O!A! ' Q7-31"G Q7@I%% @O!A! ' Q7-26"E 0; ' Q7-21"E 0K @O!A! ' Q7-11"E Q5K @O!A! ' Q7-8"E Q5L .-1"G 2R ' @O!A! ' Q7-4"E Q5K @13I%% 10@I%% 2R @O!A! ' Q7-3"E 0; ' Q7-27"N Q7@I%% @O!A! ' ^TU7 Q7-^^C"E Z-.-Q5"L Z-.U5 ' Q5C @O!A! ' Q7-^^D"E .-Q5"L .U5 ' Q5R @O!A! ' Q7-^^?"E ^T&3132U7 Q7-^^0"E Q5L @O!A! ' Q7-^^1"E Q5-1"E 0U5 ' Q5J @O!A! ' Q7-^^2"E ZJ @O!A! ' Q7-^^3"E 0L @O!A! ' Q7-^^4"E -Q5L @O!A! ' Q7-^^5"E Z-.-Q5"L Z-.U5 ' Q5D @O!A! ' Q7-^^6"E @FR%% @O!A! ' Q7-^^7"E Q5< 13@I%% 10@I%% 2R @O!A! ' Q7-^^8"E Q5P @O!A! ' Q7-^^9"E Q5-1"E ^TU5 ' Q5@I%% @O!A! ' Q7-045"E @^U4%Search: % M6"F @O!A! ' G4 ^Y-2X8 ^YK @O!S! ' Q7-^^."E 0U6 !S! Q5:@S%^EQ8%^[ Q6"N Q6^W ' @O!A! ' @O!A! ' Q7"D 0U5 < Q510+Q7-^^0U5 ^TU7 Q7"D ' @O!V! ' 0U8 Q7-^^A"E -1U8 ' Q7-^^B"E 1U8 ' Q8"N Q5Q8U5 Q6"E 0U7 .U8 0L Q8-.%6< 0A-32"L 0A-27"N 0A-9"E 6-(Q7&7)%6^[ -2U7 ' %7 1%6 ' ' C %7 ' Q5L -Q6U9 0U7 Q6< .-Z; 0A-32"L 0A-13"E 0; ' 0A-27"N 0A-9"E 6-(Q7&7)%9^[ -2U7 ' %7 1%9 ' ' C %7 1%9"G R ' Q9; 0U4 @O!B! ' Q7-^^Q"E @^U4%Command: % M6"F @O!A! ' G4 ^YX9 ^YK @O!C! ' Q7-27"E 0U6 !C! ]4 Q4EU ]4 Q4ED ]4 Q4ET ]4 Q4-10"N ^O ' M9 10U4 [4 ETU4 [4 EDU4 [4 EUU4 [4 ^D ET&(12864321^)5121682ET ED"G 0ED ' -1EU Q6"N Q6^W ' @O!A! ' Q7-^^R"E G7 @O!A! ' Q7-^^P"E Q4"E .+1U4 ' Q5L Q4-1,.X7 Q4-1,.K G7 0U6 @O!B! ' ET16ET ^^M5 ^^YM5 23+32^T 0+32^T ^^KM5 13^T !Z! ]4 Q4EU ]4 Q4ED ]4 Q4ET ]4 Q4-1

Nick Tredennick is mentioned in the article. I read a book he wrote about his experience in the design of the IBM 370 on a chip. The lore was that it was a 68000 with different microcode, but the book makes it clear that it was a new harddware design, but incorporated a lot of the approach used when making the 68000. Tredennick was a funny guy and so it kept the book lively, at least as compared to what one might expect from such a book. It talked about both the way the microcode was developed (he had a 5"x7" card for each 360 instruction and it contained his latest version of microcode for that instruction) and how writing the microcode was intertwined with the hardware design. For example, some particular instruction had awkward microcode, so he'd change the underlying hardware to do a little bit of special case logic for that on instruction. In the back half was an idiosyncratic glossary of terms. I no longer have the book, but one I recall was along these lines: "Methodology: a pompous way to say method."

What version(s) of Corel's apps used the ribbon? Not CorelDraw 2024 according to this screenshot: (I'm a happy user of CorelDraw X7 on my Win7 machine ;-)

If the two ALUs could feed results into each other, that would make things really interesting, especially when you consider the way it would affect reordering. Imagine if the OP's benchmark had two of those multiplication chains on independent registers: mul x1, x0, x0 // a mul x2, x1, x1 // b mul x3, x2, x2 // c mul x4, x3, x3 // d mul x6, x5, x5 // e mul x7, x6, x6 // f mul x8, x7, x7 // g mul x9, x8, x8 // h If you had two independent ALUs, my intuition is that you'd want to dispatch the instructions as AEBFCGDH, interleaving the two chains. But, if the two ALUs could feed each other, perhaps you'd actually want to leave it in ABCDEFGH order? Hmm.

the text says it's reverse mode, but it's wrong. what the code in the post implements is forward mode I see. It's actually worse than both forward and reverse mode. Let's say you have the simple program x1+x2+x3+x4+x5. Internally the program calculates x6=x1+x2, x7 = x6+x3, x8=x7+x4 and result = x9 = x8+x5. In forward mode you get all the partial derivatives for all intermediate variables w.r.t the inputs x1 through x5, so you get things like dx8/dx2, but you never calculate (or store in memory) dx8/dx6. In reverse mode you get the derivatives of the result w.r.t. all intermediate variables, so things like dx9/dx8, dx9/dx7, etc, but again you never need to calculate dx8/dx6. In this library you calculate recursively all dxj/dxi and store them, as long as xj has a direct or indirect dependency on xi. This is a strict superset of the derivatives calculated in both forward and reverse mode. Good catch.

EDIT: Something weird is going on here. When compressing zstd in parallel it produces the garbage results seen here, but when compressing on a single core, it produces result competitive with Brotli (37M). See: I just took all PDFs I had in my downloads folder (55, totaling 47M). These are invoices, data sheets, employment contracts, schematics, research reports, a bunch of random stuff really. I compressed them all with 'zstd --ultra -22', 'brotli -9', 'xz -9' and 'gzip -9'. Here are the results: +------+------+-----+------+--------+ | none | zstd | xz | gzip | brotli | +------|------|-----|------|--------| | 47M | 45M | 39M | 38M | 37M | +------+------+-----+------+--------+ Here's a table with all the files: +------+------+------+------+--------+ | raw | zstd | xz | gzip | brotli | +------+------+------+------+--------+ | 12K | 12K | 12K | 12K | 12K | | 20K | 20K | 20K | 20K | 20K | x5 | 24K | 20K | 20K | 20K | 20K | x5 | 28K | 24K | 24K | 24K | 24K | | 28K | 24K | 24K | 24K | 24K | | 32K | 20K | 20K | 20K | 20K | x3 | 32K | 24K | 24K | 24K | 24K | | 40K | 32K | 32K | 32K | 32K | | 44K | 40K | 40K | 40K | 40K | | 44K | 40K | 40K | 40K | 40K | | 48K | 36K | 36K | 36K | 36K | | 48K | 48K | 48K | 48K | 48K | | 76K | 128K | 72K | 72K | 72K | | 84K | 140K | 84K | 80K | 80K | x7 | 88K | 136K | 76K | 76K | 76K | | 124K | 152K | 88K | 92K | 92K | | 124K | 152K | 92K | 96K | 92K | | 140K | 160K | 100K | 100K | 100K | | 152K | 188K | 128K | 128K | 132K | | 188K | 192K | 184K | 184K | 184K | | 264K | 256K | 240K | 244K | 240K | | 320K | 256K | 228K | 232K | 228K | | 440K | 448K | 408K | 408K | 408K | | 448K | 448K | 432K | 432K | 432K | | 516K | 384K | 376K | 384K | 376K | | 992K | 320K | 260K | 296K | 280K | | 1.0M | 2.0M | 1.0M | 1.0M | 1.0M | | 1.1M | 192K | 192K | 228K | 200K | | 1.1M | 2.0M | 1.1M | 1.1M | 1.1M | | 1.2M | 1.1M | 1.0M | 1.0M | 1.0M | | 1.3M | 2.0M | 1.1M | 1.1M | 1.1M | | 1.7M | 2.0M | 1.7M | 1.7M | 1.7M | | 1.9M | 960K | 896K | 952K | 916K | | 2.9M | 2

Minivans are not small, if you have problems with the SUV size then why is a minivan suddenly okay? It's the same size car with a differently styled body and without towing capacity. E.g. Toyota Sienna is the same width and length as BMW X7 and less than 4" shorter in height. And Chrysler Pacifica is longer and wider than either of these (also less than 3" shorter in height than X7). And X7 is a big SUV that I rarely see, most SUVs on the streets around me are something like Toyota RAV4, which is half foot narrower than Pacifica, shorter in length more than a foot and shorter in height than any of the above.

A ton of Walmart's "Mainstay" brand items from China got price-jacked even before their earnings call. [...] I have a price tracker that watches a bunch of this stuff. Some of these items are now completely out of stock, even after the prices went up x3 or x7.

If you want to know the differences between Express One Zone and normal, check this blog post. I had no idea this even existed. tl;dr: it's x7 expensive.

[...] 5, possibly triggering widespread auroras. [...]