今日已更新 212 条资讯 | 累计 24871 条内容
关于我们

标签:#dev

找到 3011 篇相关文章

AI 资讯

gitwink — a read-only tray git glance for the AI-agent era

I used to live in VS Code with GitLens pinned — the branch graph, heat-mapped blame, the lens annotations. That was my git workflow. Then 2026 happened. With Cursor, Claude Code, and Codex doing the actual editing, the editor itself became optional. The only thing dragging me back was GitLens. That felt wasteful — booting an entire IDE just to peek at commit history. The agent runs the git commands now; I only need to sanity-check the result, occasionally, when something looks off. So I built gitwink — the smallest possible tool for that loop. A tray icon that expands into a glance, hands the commit off as AI context, and gets out of the way. Read-only by design. It cannot commit, push, merge, or modify anything. If I need git surgery, I tell the agent. The 0.5-second confirm loop agent commits → tray click → inline expand → "Copy as AI context" → paste into Claude/Codex/Cursor → "did the agent do this right?" No window switching. No IDE boot. The whole loop fits inside a glance. What's in it Tray-resident (Windows tray / macOS menu bar) — click to toggle, global hotkey Ctrl+Shift+G to summon from anywhere. Right-click the tray icon for Reset position / Open settings file / Quit. First-run discovery that walks your usual code dirs ( source , Documents , Projects , Code , Dev , repos , Desktop , every non-system drive on Windows; ~/Projects , ~/Code , ~/Developer on macOS) and caches the result in SQLite. No "add repo" friction. Unified commit timeline across all repos, with chips above for filtering by Repo (search + pinning), Time range (24h / 3d / 7d / 30d / All), and Authors (multi-select with counts). Per-row markers — ● commit · ◆ merge · ★ tagged — and branch label badges when a commit isn't on the currently checked-out branch. Single-repo DAG view — pick a repo and the panel switches to a per-branch graph with a custom SVG lane drawer (eight-colour palette, hashed from branch name; main / master / develop kept neutral). Inline expand on click — commit body +

2026-05-28 原文 →
AI 资讯

Why Hytale Treasure Hunts Explode In Production (And How We Fixed It)

The Problem We Were Actually Solving Treasure hunts in Hytale arent just about generating loot. Theyre about generating simultaneous loot across thousands of players while keeping the world state consistent. We started with the assumption that events are stateless notifications: a hunt starts, we fire an event, clients react. That model worked fine when we had 200 concurrent players. At 2,000 players, the event bus turned into a 40 MB/s firehose of JSON blobs. Each loot drop required serializing the entire chunk state—blocks, entities, metadata—so clients could render the drop in real time. The JVMs G1GC couldnt handle the allocation rate. Every 47 minutes, a GC cycle would pause for 4.2 seconds, the chunk cache would fragment, and the server would hard crash with an OutOfMemoryError in net.minecraft.server.MinecraftServer#processQueue. The real problem wasnt the hunt logic. It was the architectural laziness of treating events as a catch-all glue layer instead of a boundary layer with explicit interfaces. What We Tried First (And Why It Failed) We tried Kafka as the event bus. The plan was to shard hunts by region and stream loot drops as compacted topics. The first run worked for about 6 hours before the compacted topics started to bloat. Each hunt was generating 700 KB of serialized chunk state per drop. At 30 drops per hunt per minute, thats 21 MB per hunt per minute. With 400 active hunts, the brokers couldnt keep up. The lag grew to 12 seconds, clients started rubber-banding, and we got a flood of Discord reports: You sank my boat! The event stream was now the bottleneck, not the event source. Next, we tried Redis Streams with a Lua script to aggregate loot drops per chunk. Within 30 minutes, we hit the 4 GB maxmemory limit because Lua scripts were stacking dropped items in memory while waiting for the next batch. The script was elegant—O(1) per drop—but the memory footprint made it unusable in production. Finally, we tried a sidecar service: a small Go process

2026-05-28 原文 →
开源项目

XGroundControlStation

This is a submission for the GitHub Finish-Up-A-Thon Challenge What I Built XGroundControl Station is a professional Ground Control Station (GCS) application built specifically for macOS, designed to provide full control over UAV systems. The project started as an attempt to create a more optimized, native experience for drone control on Mac devices, focusing on performance, usability, and precision. The application allows users to connect to flight controllers, monitor real-time telemetry, perform calibration, test motors, and configure flight parameters in a seamless and efficient workflow. For me, this project represents a step toward building a complete UAV ecosystem, including both hardware and software solutions. Demo You can explore the project and its features through the following: GitHub Repository: https://www.github.com/agaafar7/xgroundcontrolstation.git The Comeback Story Before this challenge, the project was partially implemented with core communication and UI components in place, but it lacked refinement, stability, and several critical features. During the Finish-Up-A-Thon, I focused on completing missing functionalities, improving the communication layer with flight controllers, optimizing performance on macOS, and polishing the UI for a smoother user experience. I also worked on fixing bugs, enhancing telemetry handling, and ensuring reliable real-time interaction with the system. My Experience with GitHub Copilot GitHub Copilot played a significant role in accelerating development, especially when working with complex logic such as telemetry parsing, communication handling, and structuring reusable components. It helped reduce development time by suggesting boilerplate code, assisting with debugging, and providing quick iterations when experimenting with different implementations. Overall, it allowed me to stay focused on architecture and system design rather than repetitive coding tasks.

2026-05-28 原文 →
AI 资讯

Closiq Discord Agent: An AI Customer Support Monolith 🚀

This is a submission for the GitHub Finish-Up-A-Thon Challenge What I Built I built the Closiq Discord Agent , a full-stack modular monolith engineered to transform a Discord channel into an automated, AI-driven customer support inbox and lead management system. When a customer messages your Discord support channel, the backend captures the conversation, handles data persistence, and fetches highly relevant context from a self-hosted Qdrant vector database (which indexes knowledge base documents stored in MinIO). It then leverages OpenRouter or OpenAI-compatible models to dynamically draft and deliver accurate, context-aware responses right back to the customer via a Discord bot. Demo GitHub Repository: ErOr-0/closiq-discord-bot Local Web Dashboard: http://localhost:5173 (Tip: Insert a GIF or a couple of screenshots here showing off your React dashboard interface, your MongoDB message log view, or the Discord bot replying live in a channel!) Tech Stack At A Glance Frontend: React + Vite Backend: Node.js + Express + TypeScript Databases & Storage: MongoDB (Metadata), Qdrant (Vector Embeddings), and MinIO (Object Storage) Integrations: discord.js & OpenRouter / OpenAI SDK The Comeback Story This project started as an ambitious idea but quickly stalled out. Before dusting it off for this challenge, it was just a loose collection of database models, basic tools, and a primitive, unoptimized LangChain loop sitting in a graveyard of unfinished local folders. It completely lacked a front-end management layer, and the architecture was fragile. To bring this project to life and cross the finish line, I focused heavily on stability, user experience, and structural boundaries: Modular Monolith Refactoring: Reorganized the entire Express backend into strict, clean module boundaries ( messages , knowledgebase , agent , infrastructure ) to make the codebase highly maintainable. Built the Web Dashboard: Created a comprehensive React interface from scratch so users can visually mon

2026-05-28 原文 →
AI 资讯

Document photos are a tiny image-processing problem with sharp edges

Disclosure: I work on Passlens, a browser-first passport and ID photo maker. This post is about the product decisions behind that workflow, not a neutral review of every tool in the space. A passport photo looks simple until you try to make one that an upload form will actually accept. It is a headshot, yes, but it is also a small chain of constraints: physical size, pixel size, background, head position, print scale, and whatever the destination country's portal decides to reject that week. That is why generic photo editors feel slightly wrong for this job. They can crop. They can resize. They can export. The hard part is not any one of those actions. The hard part is keeping all of them tied to the document rule the user picked. The unit problem For developers, document photos are awkward because two units matter at the same time. A user may need a 2x2 inch passport photo. A visa portal may ask for 600x600 pixels. A print sheet may need 35x45 mm photos at 300 DPI. These are not the same request, but people often treat them as if they are. If the app only thinks in pixels, the print can come out the wrong physical size. If it only thinks in millimetres or inches, the digital upload can be rejected for the wrong pixel dimensions. A good workflow has to keep both ideas alive: the document size and the export target. That is the main reason Passlens keeps presets and print layouts as first-class pieces of the workflow instead of treating them as labels on a crop box. The crop is not the output Another small trap: the crop the user sees is not always the final output. For a digital upload, the crop usually becomes one image file. For printing, the same crop may become several photos arranged on 4x6, A4, or Letter paper with spacing, margins, and optional cut marks. If that print sheet is scaled by the browser or printer dialog, the whole thing is wrong. So the editor needs to separate three things: the face and shoulder crop the finished document-photo size the print s

2026-05-28 原文 →
开发者

Relevant Trustworthy News Sources?

Hey all, I want to setup a feed to stay on top of whats going on in specifically the software/web sector. Currently for this industry, I've only followed Cybernews, which is nice for what's going on with cyber security. However, I would also like to follow tech sources that generally have good writers and report on existing languages such as React, Vue, Django, Ruby, PostgreSQL, etc; as well as upcoming languages. Yes, I could search around and find whatever pops to the top of my search, but I would like to know what is actually reliable vs what might just look good. Also a plus if you can recommend any apps or sites that can create an organized feed or dashboard for news outlets. Things change quickly in this industry, so I'm trying to be a little more proactive to stay somewhat on top of things. Thanks! submitted by /u/Snowdevil042 [link] [留言]

2026-05-28 原文 →
AI 资讯

Client used http

I made a funnel site for a client in a pretty tough niche. It's honestly a waste of money, but he pays. I felt bad so I did a total design refresh because I wanted his business to do better. His invoice was due yesterday. He sent me a text saying his site has been down all month and sent me a screenshot. I could clearly see http:// and immediately corrected him. He said "oh it's working now with https. Do you think people will know to type that?" people click links to this, it will never be an issue if your site was down all month why didn't you tell me user error I'm about *this* close to terming this one and putting on some Amazon affiliate links. Edit: just redirected https to http. Thanks everyone! ✌️ submitted by /u/ihateroomba [link] [留言]

2026-05-28 原文 →
AI 资讯

For global marketplace owners, how do you handle your marketplace payouts?

Hey guys, the past few months I've been building a marketplace (selling mainly digital assets) and I've been running to some issues with deciding on a payment system. I've heard from some friends that standard options like Stripe Connect is terrible for international vendors. I was doing some research but got stuck as it seems that the payment provider sector moves quickly, and I'd rather avoid using anything outdated. Would love to hear some recommendations, thanks guys. submitted by /u/mirror_mirror248 [link] [留言]

2026-05-28 原文 →
开发者

Have you worked with a system that has both loose lot \ handling unit and dual inventory system?

Is there a system that can handle this? Handling units where one row in the DB can have both pieces and kg ex. HU Code 001; Article PART1; Lot code ABC; Location X; tracking qty 5pc; base qty 200kg Loose lot ex. Article PART2; Lot code XYZ; Location Y; tracking qty 100pc; base qty 2000kg This should be configurable per article family and inherited in the article... So i can have a part of articles in HU and part in loose lot... both carying 2 inventory unit of measurments.. submitted by /u/dirtyfrank22 [link] [留言]

2026-05-28 原文 →
AI 资讯

Part 2: Replacing 3.4MB video with 40kb of scripted GSAP animations: adding a camera.

Part one hit 69K views, 250 upvotes here. The comments were better than the post. A lot of you asked about SEO, accessibility, performance, and whether GSAP is even necessary. Several pointed out the demo was missing something. You were right. Part one had a cursor clicking through scenes on a flat stage. No depth, no focus. This post adds a camera: zoom into the action on right-click, pan to follow the cursor through a save dialog, zoom into the result on the destination board, pull back and loop. Still under 40 KB. Still no video files. What part two covers: Zoom wrapper architecture — why gsap.to(frame, { scale: 1.4 }) breaks responsive scaling Pan math — the formula to center any target in the viewport at a given zoom level "Stay zoomed, pan to follow" — zoom in once, pan through the interaction, zoom out once. Not PowerPoint. Easing philosophy — why camera pans need sine.inOut , not power2.inOut , and the full easing table by motion type Cursor alive during camera moves — a frozen cursor during a zoom makes the whole thing feel mechanical. 30% drift fixes it. Graceful loop lifecycle — outro pattern instead of snap-reset SEO — every button label and heading in the demo is indexable DOM text, not a black box video Accessibility — prefers-reduced-motion support, autoAlpha for screen readers Performance — live FPS stress test you can run in your browser (8 → 24 → 48 elements with zoom + pan + stagger), not much performance drop The agent split — I wrote ~60% (the directing), an AI agent wrote ~40% (the tedious timeline code). Still a lot of manual editing, but way better than recording a video and the maintenance The full post has 4 interactive demos you can pause and inspect, including side-by-side comparisons of easing curves and cursor behavior during zooms. Full writeup with live demos: https://spanthi.com/blog/gsap-choreography-part-2 Production examples: https://costumary.com and https://costumary.com/web-clipper Skill for AI agents if anyone wants to save ti

2026-05-28 原文 →
开发者

Anyone using Drupal? Set aside downtime for core security updates now!

🚨 URGENT: Highly Critical Drupal Core SQL Injection (CVE-2026-9082) Affecting PostgreSQL — Patch Immediately! The Drupal Security Team has released a "Highly Critical" security advisory ( SA-CORE-2026-004 / CVE-2026-9082 ) fixing a severe unauthenticated SQL injection vulnerability in Drupal Core. If you are running a Drupal site backed by a PostgreSQL database, you are at extreme risk. 📌 Vulnerability Overview CVE ID: CVE-2026-9082 Drupal Risk Score: 23/25 (Highly Critical) Attack Vector: Remote, Unauthenticated (Anonymous) HTTP requests Exploitation Status: ACTIVE IN-THE-WILD ATTACKS reported globally. CISA has officially added this flaw to its Known Exploited Vulnerabilities (KEV) catalog. Over 15,000 attack probes across thousands of sites have already been detected. Root Cause: A flaw in Drupal Core's database abstraction API—specifically within the PostgreSQL EntityQuery condition handler. Attacker-controlled PHP array keys reach SQL placeholder construction without proper sanitization, allowing arbitrary SQL execution. 💥 High Impact & Risks While Drupal estimates that less than 5% of installations use PostgreSQL, this configuration is heavily concentrated in enterprise, government, and higher-education environments. Successful exploitation grants: Full Database Access: Exfiltration of session tokens, sensitive data, and password hashes. Privilege Escalation: Promotion of standard or anonymous sessions to Administrator. Remote Code Execution (RCE): In PostgreSQL environments where database permissions are misconfigured (e.g., allowing COPY FROM PROGRAM ), attackers can pivot from SQL injection to executing arbitrary shell commands on the host server. 🔍 Affected Versions The flaw impacts all supported Drupal Core branches configured with PostgreSQL, including some legacy branches: Drupal Core 8.9.0 through 10.4.9 Drupal Core 10.5.x before 10.5.10 Drupal Core 10.6.x before 10.6.9 Drupal Core 11.1.x before 11.1.10 Drupal Core 11.2.x before 11.2.12 Drupal Core 11.

2026-05-28 原文 →
AI 资讯

Is this development in a nutshell?

What comes to mind is you have some code that you want other ppl to be able to interact with, then you want to store data somewhere so you provision a database, then you need somewhere to host that code so you spin up a server then plop your code into that server and make it publicly accessible. I get that there are other parts like networking, security, RBAC/permissions, Linux commands, scalability/maintainability, API, cloud infrastructure, version and change management. But does it basically boil down to those three things: Code Database Server Thanks submitted by /u/throwaway0134hdj [link] [留言]

2026-05-28 原文 →
AI 资讯

How do you handle being internal resource against an agency?

The company I work for was bought up and in the new company, one of my responsibilities will be developing our website. The issue is that the website was built by an external agency. And almost any change to the website have to be implemented by them. And of course they charge for every change. They own both the backend and frontend side of the website. I can basically only add text and images. I wonder what exactly I should advise my new boss(whom really doesn’t like it and wants to make several changes). Is it really an option to move the site to a different hosting plattform and build another theme? Which seems like last resort. And not even sure if that is really feasible either. Hiring a developer would probably be more costly and I am decent with front end, but not enough experience with backend. So don’t think I can do it myself. Should I just cave and downgrade my position? Asking for higher access will probably be rejected. This is how they make money. Hopefully this is the correct sub, and someone have some insights and experience! submitted by /u/craigularperson [link] [留言]

2026-05-27 原文 →