| General > General Technical Chat |
| [Banter] What is the worst software you have used for its price? |
| << < (14/32) > >> |
| Messtechniker:
--- Quote from: madires on May 21, 2022, 04:55:46 pm ---The Acronis versions before 2012 or so were great. After that they went downhill. --- End quote --- Und sowas von.... Agree. After dicking around with a few alternatives moved on to (paid) Macrium Reflect. |
| bd139:
I gave up on windows backup and imaging software years ago. I was just running Beyond Compare against a backup disk on data only. The rest of the OS would just get hosed if I needed to do a restore. Oh another backup turd for the list: Veeam. DC backup software. Just eats your SDN throughput, costs lots of money and doesn’t even work properly. |
| Nominal Animal:
--- Quote from: free_electron on May 22, 2022, 05:02:29 am ---I did something similar at lecroy booths. take the timebase knob, spin it fast left, fast right, fast left and repeat that like 10 times. Then walk away while the scope goes nuts zooming in and out and displaying that dreaded "triggering..." with the slowly crawling progress bar at the bottom. --- End quote --- Ah, the good ol' "let's do computation in the UI event handler" antipattern. Causes the events to be queued, slowing down everything. Drives me crazy. The correct solution is simple: you split the display update into a separate mechanism. On the web, you use window.setTimeout(). On widget toolkits, you use an idle handler. For best results, update the numeric values showing the state, but postpone recalculating and redrawing the display until the UI event queue is empty. That way, you twirl the buttons and only the numbers change immediately; it'll take that 0.1s or so of inactivity for the entire display to be recalculated and redrawn. During long computation, if there are new UI events in the queue, drop and restart the computation, unless it has been say twice the maximum duration of a full calculation. That way you always get a display update in bounded time, with the latest settings, even when twirling the button, but no event queueing beyond that, no matter what happens. This is not new, and was well known and common in the 8-bit era already, especially games. It saddens me to hear that even LeCroy fell into this easily avoided UI trap... |
| Messtechniker:
--- Quote from: bd139 on May 22, 2022, 06:28:55 am ---Oh another backup turd for the list: Veeam. DC backup software. Just eats your SDN throughput, costs lots of money and doesn’t even work properly. --- End quote --- Agree. Did work mostly, except on some puters where I experienced unsolvable .Net probs. |
| nctnico:
--- Quote from: Nominal Animal on May 22, 2022, 06:30:39 am --- --- Quote from: free_electron on May 22, 2022, 05:02:29 am ---I did something similar at lecroy booths. take the timebase knob, spin it fast left, fast right, fast left and repeat that like 10 times. Then walk away while the scope goes nuts zooming in and out and displaying that dreaded "triggering..." with the slowly crawling progress bar at the bottom. --- End quote --- Ah, the good ol' "let's do computation in the UI event handler" antipattern. Causes the events to be queued, slowing down everything. Drives me crazy. This is not new, and was well known and common in the 8-bit era already, especially games. It saddens me to hear that even LeCroy fell into this easily avoided UI trap... --- End quote --- The problem is most likely much deeper and may even be intentional. What I have seen on Windows based equipment from several brands is that the CPU load is low even when the equipment is doing heavy processing tasks (like math or analysis). It looks more like they are trying to keep the CPU cool on purpose. The slow UI response can also be a hold-off mechanism. |
| Navigation |
| Message Index |
| Next page |
| Previous page |