anchor.diff:          var quotes = getQuotes(fortunes.size()).await().indefinitely();
   
           //we append each quote to each fortune
  -        for(int i=0; i  < fortunes.size();i ++){
  -            fortunes.get(i).title+= "   -  "+quotes.get(i);
  +        for(int i=0; i  < fortunes.size(); i ++){
  +            fortunes.get(i).title += "   -  " + quotes.get(i);
           }
           return fortunes;
       }
  -
   }
   ----
   
  
positive.code:         var quotes = getQuotes(fortunes.size()).await().indefinitely();
  
          // we append each quote to each fortune
          for(int i=0; i  < fortunes.size();i ++){
              fortunes.get(i).title+= "   -  "+quotes.get(i);
          }
          return fortunes;
      }
  
negative.code: == A point about performance
  
  Our experiments seem to indicate that Quarkus with virtual threads will scale better than Quarkus blocking (offloading
  the computation on a pool of platform worker threads) but not as well as Quarkus reactive.
  The memory consumption especially might be an issue: if your system needs to keep its memory footprint low we would
  advise you stick to using reactive constructs.
  
  