From: arne@vajhoej.dk   
      
   On 2/16/2026 4:30 PM, John Dallman wrote:   
   > In article <10mt9sd$9orh$1@dont-email.me>, arne@vajhoej.dk (Arne Vajhøj)   
   > wrote:   
   >> Where do you make the cut?   
   >>   
   >> Example list:   
   >>   
   >> commercial vendor where you directly pay for support   
   >> commercial vendor with product supported   
   >> open source with multiple maintainers and recent releases   
   >   
   > There: stuff like Xerces XML, Open JDK or GCC is fine.   
   >   
   >> open source with single maintainer but recent releases   
   >> open source with single maintainer and no recent releases   
   >> open source declared EOL by author but source still available   
   >> commercial vendor with product not supported   
   >> commercial vendor no longer existing   
      
   Relative high bar, but it can be justified.   
      
   >> But if we are talking something recently developed, then   
   >> there is a good chance that with transitive dependencies   
   >> you will have 1000-5000 open source libraries included   
   >> in the solution.   
   >   
   > I'm not in the web apps business. I produce closed-source mathematical   
   > modelling libraries. I try to keep our development environments as simple   
   > as possible, aided by not having management that wants to take up every   
   > new fashion.   
      
   It is not just web. Even though web tend to be the worst due   
   the JS worlds acceptance of micro libraries (which in many's   
   opinion including mine is a a concept worse than the square   
   wheel).   
      
   But you can manage this stuff when you can focus on   
   your own libraries.   
      
   I have no idea who the users of your libraries are,   
   but it could be a lot more complex out there:   
   * various data sources: relational databases,   
      NoSQL databases, flat files   
   * various data flows: message queues, event streaming   
      system (read: Kafka), ETL tools   
   * specialized databases: search databases, time series   
      database, vector database   
   * modelling applications in Python/Fortran/C that   
      use your library and a dozen other libraries to   
      model whatever   
   * report generation: PDF, JSON, XLSX   
   * monitoring tools to keep and eye on the entire flow   
   * scheduling tools to automate runs   
   etc.etc.   
      
   Arne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)