Skip to content

Instantly share code, notes, and snippets.

@simonw
Created November 6, 2023 21:31
Show Gist options
  • Star 4 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save simonw/d50c8634320d339bd88f0ef17dea0a03 to your computer and use it in GitHub Desktop.
Save simonw/d50c8634320d339bd88f0ef17dea0a03 to your computer and use it in GitHub Desktop.

The opinions expressed in the discussion revolve around several major themes in response to OpenAI's announcements, including the Assistants API, GPT-4 Turbo, pricing changes, developer platform updates, and the impact on startups.

Excitement for Assistants API

Several participants are clearly excited about the new Assistants API, and the potential it has to simplify development by reducing boilerplate code and abstracting routine tasks.

  • kevin_hu:

    "There are a lot of huge announcements here. But in particular, I'm excited by the Assistants API. It abstracts away so many of the routine boilerplate parts of developing applications on the platform."

Concerns Over Security

There's a concern about new security issues, specifically relating to prompt injection risks with the Assistants API.

  • simonw:

    "The new assistants API looks both super-cool and (unfortunately) a recipe for all kinds of new applications that are vulnerable to prompt injection."

  • burcs:

    "Do you see a way around prompt injection? It feels like any feature they release is going to be susceptible to it."

Wary of Over-reliance on OpenAI Platform

Some are wary of the increased lock-in to OpenAI’s platform, especially given the black-box nature of GPT models.

  • minimaxir:

    "Most of the products announced [...] appear to be more about increasing lock-in to the OpenAI API platform..."

Debates on Model Capabilities and Progress

There is debate over how the newly announced models compare to other offerings, including open-source alternatives, in terms of capabilities and progression.

  • coder543:

    "OpenAI offering 128k context is very appealing, however."

  • visarga:

    "Mistral + 2 weeks of work from the community. Not as good, but private and free."

Competition in Voice AI

With the release of Whisper V3, the voice AI space is also a topic of interest, and there are discussions on its strengths compared to competitors.

  • modeless:

    "Whisper V3 is released! [...] I'm excited to add it to my local voice AI."

Economical and Scale Implications

The reduced pricing and increased context lengths have also sparked conversations around the economical feasibility for startups and individual developers.

  • pchmulqdq:

    "Comparing a 7B parameter model to a 1.8T parameter model is kind of silly. Of course it's behind on accuracy, but it also takes 1% of the resources."

Concerns for Startups in the AI Space

There is a sentiment that the announcements may have a significant impact on startups focused on AI tooling, potentially rendering some obsolete.

  • whytai:

    "Every day this video ages more and more poorly... categories of startups that will be affected by these launches..."

Open Source as an Alternative

There are mentions of the relevance and trajectory of open-source solutions, and their importance as alternatives to major platforms.

  • yawnxyz:

    "I'm excited for the open source, local inferencing tech to catch up. The bar's been raised."

Legal Implications and Intellectual Property

Lastly, discussions around copyright and the legal implications of LLMs and their training data are also a theme.

  • bluck:

    "So essentially they are giving devs a free pass to treat any output as free of copyright infringement? Pretty bold when training data sources are kinda unknown."

Overall, the responses to OpenAI’s latest announcements seem to mix anticipation for the positive advancements with caution regarding potential pitfalls and broader implications for the AI and developer communities.

@kenwaytis
Copy link

Wow, this is a pretty good summary. Surprisingly, there are so many examples.

@trickster
Copy link

Actually pchmulqdq user doesn't exist, but pclmulqdq does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment