Pains
726 pains collected
Refresh token revocation on user password change
4When users change passwords, refresh tokens may be revoked by OAuth providers, forcing applications to handle re-authentication. Graceful re-auth flows must be implemented to prevent user frustration.
Missing session persistence in Gemini CLI
4Gemini CLI does not automatically save sessions, requiring users to manually manage conversation state. This reduces continuity and forces workarounds to maintain context across CLI invocations.
Generated code contains excessive comments (poor for agentic coding)
4Gemini models (especially 2.5-Pro) generate code with excessive comments, which is good for learning but poor for production agentic coding. The verbose commenting style makes AI-generated code immediately identifiable and impractical for autonomous agents.
Undocumented Safety Settings Surprise
4Safety settings in the Gemini API have unexpected behavior and are inadequately documented compared to other vendors, causing confusion during implementation.
Confusing product naming (AI Studio vs Vertex AI) creates friction
4Google offers Gemini API access through two confusing product names (AI Studio and Vertex AI) with unclear differences for developers. This naming confusion adds unnecessary cognitive load during onboarding and increases time to first API call.
Low tool adoption due to limited awareness of available security solutions
4Developers lack awareness about available npm security tools, with some respondents admitting they don't know what options exist. This contributes to only 40% satisfaction with current security tools despite available solutions.
No local/offline deployment option available
4Gemini API requires internet connectivity with no local or offline alternative. Applications cannot function without a network connection.
No Phone Support for Non-Enterprise Customers
4Phone support is only available for enterprise contracts, leaving smaller teams and individual developers without direct communication channels for critical issues. This limits support options compared to competitors offering broader support tiers.
Missing built-in linear algebra functionality
4Python lacks built-in linear algebra functionality, requiring developers to rely on external libraries like NumPy for mathematical operations.
Increased code verbosity due to explicit type annotations
4TypeScript requires explicit type annotations and generates boilerplate code for common patterns (interfaces, generics), resulting in significantly more verbose code compared to JavaScript.
Lack of Tooling Suggestions for Type Definitions
4TypeScript tooling never suggests how to type something properly, unlike other typed languages such as ReasonML and Flow. Developers must manually hunt down and write correct type definitions, which is time-consuming and error-prone.
Gap between tooling needs and actual bottlenecks
4Developers report needing better testing solutions and CI/CD tools, but these aren't always flagged as primary blockers. Unclear signal about where tool investment matters most.
Compilation overhead and build time impact in large TypeScript projects
4TypeScript adds a compilation step to the development workflow that can take seconds or minutes in large projects, slowing down the development cycle. While modern tools like esbuild, swc, and Vite help reduce build times, this overhead remains a consideration for project setup.
Slower Response Times for Complex Queries
4Claude 3.5 Sonnet averages 3-5 seconds for complex responses versus GPT-4's 2-3 seconds. This latency difference becomes noticeable in real-time chat applications and high-frequency API calls, impacting user experience in customer service scenarios.
Conservative Content Policies Limiting Creative Use Cases
4Anthropic's safety-first approach results in overly cautious responses for creative writing, marketing content, and edgy humor. Users report 23% more declined requests compared to GPT-4 for legitimate creative tasks, frustrating marketing and creative professionals.
HTTPS-only redirect URI requirement hinders local development
4Some OAuth providers (e.g., Box) require HTTPS for redirect URIs, making it difficult or impossible to test locally with HTTP URLs like `http://localhost:5001`.
Prompt cache TTL of 5 minutes creates inconsistent cache hits
4Anthropic's prompt caching has a 5-minute time-to-live, meaning low-traffic endpoints may not see consistent cache hits. Even minor whitespace changes invalidate cached prefixes, requiring exact matching across calls.
Misleading TypeScript type errors for valid code patterns
4TypeScript reports compilation errors for hardcoded values that clearly match their expected types (e.g., a hardcoded string 'compact' matching the literal type 'compact'), causing false positive errors and frustration.
Slow or confusing redirect flows degrade user experience
4Poor redirect flow performance or UX causes user frustration and abandonment. Developers must optimize and clarify the post-authorization redirect experience.
Difficult and unintuitive access revocation UX
4Users struggle to revoke application access if the revocation flow is not straightforward. Poor revocation UX reduces user control over permissions.
Error handling complexity with multiple HTTP status codes and transient failures
4Developers must implement robust error handling covering multiple HTTP status codes (400, 403, 429, 500) with different retry strategies. Implementing exponential backoff and graceful error catching adds complexity to error handling logic.
TypeScript standard library lacks Temporal type definitions
4TypeScript's standard library type definitions have not kept pace with JavaScript's TC39 proposals. Temporal began shipping in JavaScript engines but TypeScript issue #60164 shows the type definitions are still missing, creating a gap between runtime capabilities and type safety.
API auto-generates unwanted Q&A output during function calls
4OpenAI API unexpectedly auto-generates questions and answers during calls, producing output that wasn't requested and requiring developers to implement additional filtering logic.
GPT-5 performance degradation on simple tasks
4GPT-5 can feel slower than GPT-4o for simpler, everyday queries and coding tasks. Community backlash occurred regarding performance degradation for simple coding tasks before OpenAI fine-tuned model routing.