I sort of gave up on that idea mainly because those older multi Ghz scopes I could afford aren't really good day to day bench scopes. They tend to be huge, loud and take forever to boot. Also their inputs tend to be more fragile. Not to mention you need equally expensive probes for those frequencies as well.
I am pretty happy with my R&S RTM 1054.. it's plenty of scope for my needs and it didn't break the bank.
I have to agree on that. As soon as it is a scope that runs a desktop OS it tends to stop being a good every day scope. Sure there is all the performance in there but it boots slowly(not only the os, but often the scope app too)
Not necessarily. Booting can be pretty fast once the standard slow low rpm hard drive that is commonly found in Windows based scopes has been replaced with a decent SSD.
And it's not that embedded platform scopes are necessarily fast, too. For example, my new Tek MDO3000 take around as long to boot as my old LeCroy WavePro 7300A running WindowsXP.
usually is noisy and uses a lot of power.
Yes, but that is mostly because Windows scopes tend to be mid-range or high-end scopes with very fast ADCs that produce a ton of heat, and if you replaced the PC processing backend with an embedded low-power backend as found in the typical low-end scope then it would still be noisy and suck a lot of power.
Also often you can't set up all of the scope trough the front panel buttons, for some stuff you need a touchscreen or mouse to navigate extra menus.
And touchscreen (which is used on an increasing number of entry-level scopes like the Keysight DSOX3kT) is bad because? How else would you want to control all the functions that can be found in a newer high-end scope? Buttons?
I do agree that an UI that requires a mouse isn't great for using on a bench, but it's mostly HP/Agilent that relied on it (although the UI on newer Keysight Infiniiums scopes has improved a lot over the old Infiniium 54800 UI). Tek had a somewhat decent touch UI on their Windows-based scopes, and LeCroy had their MAUI which is was designed for touch right from the start.
So if you are looking to get a high end scope, you better also have some lowend lightweight scope for the case where you just want to quickly check if a 5MHz clock is running on a board or something. There is a reason they make hammers in different sizes, they are essentially the same tool but for different use cases.
As someone who uses a high end scope pretty much every day (at work and at homeI have to disagree here. I find it's much easier to just do the measurement with the high-end scope than fetching a entry-level scope, powering it up and do the measurement with it. Plus quite often even simple problems turn out to be rather more complex, in which case the tools available on the high end scope make life so much easier, even if it's just a 50MHz signal.
However, I do have to admit that it very much depends on the scope in question. Newer Keysights like the DSO-S are great, they boot fast and have a decent an easy to use touch UI. LeCroy mid-range (WaveSurfer) and high-end (WaveRunner, WavePro) scopes also make great general purpose scopes. Older Infiniiums (especially pre-DSO9k models), not so much, simply because of their poor mouse-driven UI and various hardware limitations (i.e. sample memory size drop at higher sample rates) in some models. Tek Windows scopes, while having a somewhat decent UI, are generally slow like wading through molasses in pretty much everything, and tend to lock up when under load. They aren't exactly a joy to use but that is pretty independent of the complexity of the measurement.
Scope inputs aren't really a problem with scopes with a BW of up to 3-8 Ghz, which are usually equipped with BNC or BNC-compatible connectors and have switchable 50ohms/1M inputs. Only very high bandwidth scopes come with non-BNC low-Z (50ohms) inputs only, in which case you'd need an expensive high-z adapter to be able to use a standard passive probe.
So it really depends on what your scope is.