minus7

Is it really, or do you just think so and it could actually mislead you and your LLM the next time? In my experience, the information in the comments tends to be quite redundant, often even with other comments in the same file

If you don't think about it, it doesn't seem like a bad idea. If you do, you realized how incredibly complex the whole thing is

It's just using libvte like gnome-terminal and lxterminal, so I doubt it's much different from them.

>Note that if an "Ephemeral Device" exists for more than 4 hours continuously, it consumes 0 minutes, and is billed as a tagged device. The docs are being upgraded to change the language around this.

Thanks for explaining, that makes the limit very reasonable. I updated my comment

This is potentiallya bit of a downgrade if you are using the Personal or Standard plans for infrastructure:

- Reduction from 100 to 50 tagged devices on Personal (was 100 total devices before)/Standard (was 100 + 10 per user before)

- ~~Limit to 1000minutes/month (16.6 days) for ephemeral devices (simply counted towards the total device limit before), meaning you can't even have a single permanently connected ephemeral device anymore on Personal/Standard~~ This is incorrect, see comment below

- Limit of 3 ACL groups on the Personal plan (previously no limit), but also allows 10 ACL groups on the Standard plan (previously had no access to the feature)

Unfortunately, the pricing for extra devices and ephemeral devices is "contact sales".

The `eval` alone should be enough of a red flag

Issues I observed, mostly using GoLand:

- syntax errors displaying persistently even after being fixed (frequently; until restarted; not seen very recently)

- files/file tree not detecting changes to files on disk (frequent; until restarted; not seen very recently)

- cursor teleporting to specific place on the screen when ctrl is pressed (occasionally; until restarted)

- and most recently: it not accepting any mouse/keyboard input (occasionally; until killed))

JetBrains should stop building stupid AI shit and fix their IDEs. 2025 versions are bordering on unusable.

All code is inherently not concurrency-safe unless it says so. The http.Client docs mention concurrent usage is safe, but not modification.

The closure compiler flag trick looks interesting though, will give this a spin on some projects.

In my experience that's because most users run their monitors on 100% brightness instead of turning that down. I prefer light mode unless it's really dark.

I was excited that Firefox finally exposed its local translations as API, but it's Chrome-only (still?). Will be nice for userscripts, for example to replace Twitter's translation button that hardly ever works

If you consult with someone over their project, then proceed to fork it behind their back, that's just being a dick, even if it was perfectly legal. We should not accept that kind of behavior. And that's even ignoring that the consultation was unpaid and the project was actually even stolen.

There's a pinned comment on the video about the cable:

    For everyone that's interested, the included USB cable is wired like this:
    
    GND    -------> GND
    D+  -------> VCC
    D-   -------> VCC
    VCC -------> VCC
    
    So it is a non-standard cable! I measured by checking continuity between the USB A plug, and the USB C connector with a USB A adapter on it. None of my probes are small enough for a USB C connector's pins directly.

    There was a bit in the video about this that ended up on the cutting room floor, my bad!

No one's gonna pay just for the sidebar being collapsible. Maybe someone is going to because it was the last straw, but most are just going to be annoyed. Better ask for money only for something with real value (which I'm sure the pro tier also includes).

Hey,

I found your library a few weeks ago when I was annoyed by nothing like this being built into the standard library. It’s been a breeze to use so far.

A neat trick I found to gauge bottlenecks in pipelines is using Buffers between steps and running a goroutine that periodically prints `len(buffered)/cap(buffered)`