> We use IBM MQ at work and I wouldn't exactly call it simple.
2nd'd & 3rd'd ...
You hired a 50 man lumberjack crew to cut down a sapling.
I've been spending a some time to remove IBM MQ out and going to "simpler" queuing solutions. First of all, cost. Guess what, we're not getting anything out of licensing per year to justify the cost.
With improving the end points, we don't need all that complexity. With 5 9's uptime on the network and smarter end points, retrying messages isn't expensive.
It's a significantly different segment than the Quest or Valve Index-- somewhere in between a Varjo and a Valve Index.
With better economies of scale, we would be able to drop the price more/introduce more segmentation. As is we just have too many NRE costs that drive the price up.
Very reminisce of the 6502 "issue" of jumping with an address on a page boundary.
Per Wikipedia:
the processor will not jump to the address stored in xxFF and xxFF+1 as expected, but rather the one defined by xxFF and xx00 (for example, JMP ($10FF) would jump to the address stored in 10FF and 1000, instead of the one stored in 10FF and 1100). This defect continued through the entire NMOS line, but was corrected in the CMOS derivatives.