Not talking about which one sounds smarter. talking about which one you’d actually rely on when the answer genuinely matters to you. which one and why? submitted by /u/aiprotivity_ [link] [留言]
Sharing my personal fetch wrapper I use in all my projects. I also added some Axios features to reduce my dependencies and wrote a guide about it submitted by /u/patchimou [link] [留言]
Today, June 8th, InfoQ celebrates 20 years. This is not a comprehensive history, but a deliberately selective look at the technologies and practices InfoQ identified early, where they sit on the adoption curve in 2026, and how that curve may evolve over the next five to ten years. By InfoQ
Automating labor is not going to move billions of tonnes of earth required to mine increasingly degraded ore grades of critical industrial minerals. People need to stop with this 'abundance' gaslighting. Without breakthroughs in material science, there will be no 'abundance'. Just mass resource inflation as people start consuming more because robots can manufacture anywhere. AI based automation is surfacing the real bottlenecks that there is no getting around. Stop pretending this will all be magically solved. It won't be solved until it's solved. And so far, despite all these trillions being invested, we haven't seen any breakthroughs. Hopium is not a solution. submitted by /u/kaggleqrdl [link] [留言]
Hello everyone, i'm in the process of implementing a Sellsy integration on my app which is, for those who don't know, a service to generate and send invoices, estimates etc ... They have an API that i'm using. Right now i'm using the API keys and account the commercial is using for generating its documents but i add "TEST" prefix to the clients i'm working on while developing so it doesnt collide with existing data. My question is more of an architectural implementation question: how would you guys approach not colliding with production data in dev and staging environments. For example: if i need to work on the API integration, to prevent generating and sending invoices or if i need to generate them but prevent colliding with production data. Should i create another Sellsy account ? DEV or STAGING prefixes ? Any ideas are welcomed PS: i already asked AI, looking for human answers only submitted by /u/armlesskid [link] [留言]
Microsoft announced Logic Apps Automation at Build 2026, a new SKU at auto.azure.com packaging workflows, AI agents, knowledge services, and model access into a managed SaaS experience. Agents integrate via agent-loop orchestration, Foundry agents, and managed sandbox. Knowledge as a Service provides a fully managed RAG pipeline. By Steef-Jan Wiggers
HashiCorp has released Terraform 1.15, introducing dynamic module sources, a formal deprecation mechanism for variables and outputs, a new inline type conversion function, type constraints for output blocks, and native Windows ARM64 support. The release addresses several long-standing requests from the Terraform community. By Matt Saunders
Rocicorp has released Zero 1.0, a stable version of its sync engine after two years of development. This update introduces a schema change hook for Supabase and includes bug fixes. Zero operates by pairing a client library with a read-only Postgres cache. Community feedback highlights positive developer experience but raises concerns about production readiness and existing limitations. By Daniel Curtis
PM at a mid-size startup here. Didn’t really notice how bad it got until this week. My workflow now: Claude for ideation ChatGPT for rewriting specs Cursor for implementation Perplexity for research Notion AI for docs Atoms AI for larger tasks None of these tools actually replaced my work. They just redistributed it. I’m still the one dragging context between all of them. Yesterday I literally caught myself pasting the exact same requirement into 4 different tools and thinking… this can’t be how it’s supposed to work. I don’t even think any single tool is bad. It just feels like we hired 6 smart interns and completely forgot to get a manager. submitted by /u/billa01_i [link] [留言]
You know the ways AI is regularly talked about—how much can it really do? How much will it cost? Environment? Bubble? We get that. But the Electronic Frontier Foundation wants to have a different conversation about AI. EFF's background on AI is deep. In 2017, we launched a detailed project to Measure the Progress of AI Research , encouraging machine learning researchers to give us feedback and contribute to the effort . That project was archived for lack of bandwidth, staffing, and the complexity and time required. But just five years later and the "progress of AI" is a global concern/topic, and everyone, including EFF, is thinking about it. Here's how *we* think about it, from the perspective of protecting civil liberties AND innovation. What do you think, and what are we missing? This is our summary: AI technologies are affecting our civil liberties as never before. Ensuring that AI serves people, not power, starts with cutting through the hype. AI technologies are not magic wands—they are general-purpose tools. If we want to regulate those technologies to reduce harms without shutting down benefits, we have to focus on who uses AI, what products they use, and how they use them. Where we see potential benefits, like improving weather forecasting, facilitating medical research, identifying systemic bias, or fostering accessibility, we work to ensure those benefits can be realized. Where we see potential harms, we consider the practical and legal tools we already have, like pressure campaigns, privacy lawsuits, and transparency measures. If we need new tools, we should create protections tailored to the actual problem – not just to the latest outrage. For example, if policymakers are worried about AI accelerating systemic privacy violations, they should enact real and comprehensive privacy legislation that covers all corporate surveillance and data use, and close the data broker loophole to limit government surveillance. And to keep the window open for a better futu
Benchmark proxies for reliable, target-specific scraping Discussion | Link
submitted by /u/Active-Fuel-49 [link] [留言]