Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Side-by-side test for building dialogs: standard agent vs. agent with Modern Web Guidance ๐Ÿ Both generate similar UIs, but the guided version skips four separate event listeners in favor of `commandfor` and `command` attributes, with less code overall. Which approach would you rather maintain in your codebase? โ†’

10,917 Aufrufe โ€ข vor 4 Tagen โ€ขvia X (Twitter)

5 Kommentare

Profilbild von ๐š…๐šŽ๐š๐šŠ ๐™ฑ๐šŠ๐šœ๐šŽ
๐š…๐šŽ๐š๐šŠ ๐™ฑ๐šŠ๐šœ๐šŽvor 3 Tagen

Title: Heavy rendering glitches in embedded Chromium on a virtual display without a GPU (VNC stream) Description: Chromium runs on a Linux virtual machine with no real GPU. The display is a virtual X server streamed over VNC, under the xfwm4 window manager. Rendering glitches heavily and keeps doing it. Observed (Oct 14, 2026): The VNC stream failed its readiness check twice in a row, and the virtual display and VNC server restarted. xfwm4 couldn't reach the accessibility bus or the session manager. The kernel logs "crng reseeded due to virtual machine fork" about every 5 minutes. The Chrome debug log has no GPU or crash entries. Expected: Stable rendering with no flicker or glitching. Questions: Is --disable-gpu-compositing or swiftshader software rendering the recommended setup for GPU-less virtual displays? Can frequent virtual machine forks or display reconnects cause the compositor to glitch? Screenshots or a screen recording would make it stronger. ---- Reported on Chromium Issue Tracker

Profilbild von notgwapo
notgwapovor 3 Tagen

honestly, i'd go with the modern web guidance. less code, less hassle. ๐Ÿ’ป

Profilbild von Aditya Reddy
Aditya Reddyvor 3 Tagen

four event listeners gone, thats the kind of negative diff I wanna see

Profilbild von OnFinality
OnFinalityvor 3 Tagen

The listener count is the tell. Fewer moving parts means less for an agent to get subtly wrong, and `commandfor`/`command` keeps the wiring declarative instead of scattered across handlers. Curious whether the guided version also holds up when the dialog logic gets stateful.

Profilbild von AriesZhou
AriesZhouvor 3 Tagen

but the code generated this way is only compatible with the new version, right? how does it perform on the old version?

ร„hnliche Videos

8 rules to improve your AI coding agent. All of these rules work with Claude Code, Cursor, VS Code, and with most programming languages. Automating these rules will 10x the code quality and security produced by your AI coding agents. 1. Dependency checks - Prevent your agent from suggesting insecure libraries based on outdated training data. 2. Secret exposure - Auto-fix the use of hardcoded credentials introduced by your coding agent. 3. File and function size - Automatically refactor any files or functions that exceed a reasonable length. 4. Complexity and parameter limits - Simplify overly complex code written by the agent. 5. SQL Injection - Auto-fix all database interactions with unsanitized user input. 6. Unused variables and imports - Detect and remove dead code. 7. Detect invisible unicode characters in AI rules files - Remove zero-width spaces, direction overrides, and other invisible characters that can hide malicious behavior. 8. Insecure OpenAI API usage - Enforce use of secure OpenAI endpoints, proper authentication, and context isolation Here is how you can automate this: Install the Codacy extension. This will give you access to a CLI for local scanning and an MCP server for agent communication. From here on out, every time you need to generate some code: 1. Your agent will write the code 2. It will then call Codacy's CLI to check it 3. It will find any issues in real time 4. Your coding agent will fix the issues 5. When the code passes all checks, you are done Level of effort on your side: literally zero! Code quality and security because of this: 100x better! Here is the link to download the extension for your IDE: Thanks to the Codacy team for collaborating with me on this post.

Santiago

49,331 Aufrufe โ€ข vor 11 Monaten