Date

Monday, December 16, 2024 - 9:30am ET / 2:30pm UK

// Second Monday of every month

Attendees

Meeting notices

• FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

• All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

• FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact [email protected] with any questions.

• FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

• (5 min) Convene, roll call, welcome new people.
• Display FINOS Antitrust Policy summary slide
• Review Meeting Notices (see above)
• (5 min) Approve previous meeting minutes.
  • Approved by acclamation.
• (5 min) Got a message from Neil Kanungo on LinkedIn asking to populate a survey on AI-assisted programming kdb+.
  • Will be very interesting to see if KX can get an LLM to understand q code better than what's currently out there!
  • Listed various IDEs / editors, but Emacs was not among them.
  • Most open source integrations with GitHub Copilot just use the "language server".
    • https://stackoverflow.com/questions/76741410/how-to-invoke-github-copilot-programmatically
    • That only supports "completions" and not "chat".
    • Completions model is GPT-3.5 Turbo.
    • Not as advanced as the chat model, GPT-4o.
• (10 min) qStudio is now free?!
  • https://www.timestored.com/b/qstudio-is-now-free/
  • https://github.com/timestored/qstudio
  • Would it be better to follow Jo Shinonome's lead and drink the VS Code Kool-Aid?
    • https://github.com/jshinonome/vscode-q
    • KX has a VS Code extension as well.
      • https://marketplace.visualstudio.com/items?itemName=KX.kdb
      • Might have limited uptake at enterprise customers that require custom authentication.
    • kdb Studio still quite heavily used for data exploration.
      • https://github.com/finos/kdb-studio
    • VS Code more popular for code development.
  • AWS Q Developer may work on some kdb/q questions.
    • Fully supported languages listed on FAQ page.
      • https://aws.amazon.com/q/developer/faq
  • Jo Shinonome's language server connects to a q process to see functions and namespaces.
    • Can hover over a symbol to get a definition.
    • KX extension has a hover over as well.
  • AI-powered tools still require the developer to iterate on ideas.
    • The 70% problem: Hard truths about AI-assisted coding
• (10 min) PyKX 3.0 Officially Released
  • Might be interesting to try the free tier of FinSpace to compare what AWS vs tickerplant-launching classes of PyKX.
    • https://aws.amazon.com/finspace/features/managed-kdb-insights/
    • https://code.kx.com/pykx/3.0/api/tick.html#pykx.tick.BASIC
• (5 min) Ryan Hamilton taking issue with PyKX being branded as "open source".
  • https://www.linkedin.com/posts/justryanhamilton_pykx-is-closed-source-what-do-you-think-activity-7272927475511259137-dzNl
  • https://github.com/KxSystems/pykx
    • This work is dual licensed under "Apache 2.0" and the "Software License for q.so", users are required to abide by the terms of both licenses in their entirety.
  • Naive interpretations of "open source" are disingenuous given the recognition of organizations like OSI, Linux Foundation, etc.
    • https://opensource.org/
    • https://www.linuxfoundation.org/
  • Just call it "source available" so that users can adapt the code to their local setups.
  • Many .q_ files in the repo aren't "source code".
    • Should separate these into their own repo with a different license.
• (10 min) qPython updated for numpy/1.24 based on suggestion from AI assistant.
  • Suppress deprecation warnings for numpy 1.24 qPython#22
  • Should be straightforward search/replace after release of that to update for numpy/2.0.
  • Agentic AI SWE went down a bit of a rabbit hole...
• (5 min) Broken link to "KX Whitepaper On Using IPC With kdb+"?
  • https://kx.com/blog/kx-whitepaper-on-using-ipc-with-kdb/
  • Available on Archive:
    • https://web.archive.org/web/20210413162939/https://code.kx.com/q/wp/ipc/
• (5 min) AOB, Q&A, Adjourn.
  • Typo in verbose.q #86 .
    • disambuguate -> disambiguate
  • PyKX words might clash with user variable names.
  • Would have to be conditional / explicitly activated.
  • Unfortunately, only .q namespace allows infix.
    • Would be useful to allow "blessing" of other namespaces.
  • Might be interesting to use AI Coding Assistant to learn how Shakti parser works.

Join Zoom Meeting

• https://zoom.us/j/94523415326?pwd=NkJDaUtUUlZTcHVwcUJHdG0yRFJUdz09
• Meeting ID: 945 2341 5326
• Passcode: 361990
• Find your local number: https://zoom.us/u/abTtYRZ0B6