While not quite panel-sized, it's much larger tiles and there's not another roof underneath. Probably makes most sense with a new roof, though. The problem is that when a roof lasts 50--80 years, that's not a very big market just for new roofs.
This concerns Widerrufsrecht, i.e. the right to cancel an order or contract shortly after signing it. For certain services you also waive this when you get to use it immediately (cellphone service, for example), and for custom-made items it also does not apply, as in this case.
This is independent of warranty (which is something the manufacturer may or may not offer), or Gewährleistung (which concerns the vendor and is typically the easiest way of dealing with damaged or defective goods).
That only helps with multiplications by statically known word sizes (4x, 8x, etc.) and not arbitrary x·y. It can help with many smaller constant multipliers if the complete is clever, but it has to be known at compile time.
Except that was done to save disk space (according to https://jeffpar.github.io/kbarchive/kb/063/Q63777/, "When EDIT.COM is executed in MS-DOS versions 5.0 and later, it invokes QBASIC.EXE with the /EDITOR switch", whereas this installs a whole new copy of the Edge browser (850 MB) on a system where in 90+% of cases it's already installed...
The hilarious side effect of this is that Intune/Defender on MacOS flags the multiple copies of edge for non-compliance. Maybe this is just something that happens to MSFT employees, not sure, but I’ve had to waste many hours filing for false positive exceptions because not a single Microsoft product can figure how to use a Mach-o shared dylib path
Oh, that's something I also did in QBasic ages ago. I since lost the source code, but it basically worked by querying the screen from bottom to top, finding snow pixels (white) and moving them down, unless there was an obstacle. The initial snow on the ground (and the snowman) were using a different color that was almost white so it wouldn't detect as snow. It worked fairly well in 320×200 at the time.
I've tried the same approach in Turbo Pascal with BGI in the hopes of having a faster language and higher resolution available. It turned out to be quite a bit slower, likely because drawing and querying pixels was a bit more involved when using an adapter layer like BGI.
A few weeks ago I tried rewriting all that in TypeScript for fun and also trying to integrate it as an easter-egg with our graph drawing library (which renders with SVG) and first had to figure out how to efficiently support arbitrary obstacles that are initially SVG as well as a potentially changing viewport of the whole scene. I got sidetracked and didn't finish it, but proper collision handling was so easy back then (just look at the pixel color), but now with vector graphics and reading pixels being a very slow operation in many cases, it was surprisingly complicated.
At least from Rostock to somewhat closer destinations you have both options. There's a bi-hourly IC to Hamburg or Berlin and another bi-hourly RE towards the same destinations. They're not terribly different in terms of travel time, but one is a regional train and one is an inter-city train.
Sure, long distances (I had to travel from Rostock to Tübingen last weekend) are typically not taken with regional trains (although you technically can; I did that as a poor student a few times, it just takes 16 hours instead of 10), but over medium distances (around 2–3 hours) you often have both options.
https://nabendynamo.de/wp-content/uploads/2021/06/20210426_1...
While not quite panel-sized, it's much larger tiles and there's not another roof underneath. Probably makes most sense with a new roof, though. The problem is that when a roof lasts 50--80 years, that's not a very big market just for new roofs.
reply