Sequel with external collaborators.

Squeal with the homies.

is there an xkcd about there being an xkcd about everything though?

great, another tool to delegate thinking to a computer program that can’t really think. Exactly what people need.

cries? You mean xeyes?

I’m using xeyes with X11 fwd to compare it with waypipe.

is that a manhattan thing, or does that apply to other boroughs?

If you write commit messages like this, at least have the decency of squashing them when merging. Thanks.

git commit -m ‘a meaningful message’

idk, I’m perceiving very similar latency and frame rates in either. xeyes doesn’t report FPS, but I’m seeing under 4 FPS with weston-simple-egl reaching out to a server proxied by cloudflare

So I’d still go with an RDP solution for any session longer than a few minutes.

cool, it works; for those trying it out, the weston package provides simple colorful demo programs like weston-simple-egl and weston-simple-shm that can demonstrate it, like xeyes and xclock can demonstrate an x11 forwarding session.

is there a way to forward wayland windows via SSH like X11 forwarding (one that doesn’t use xwayland)?

other countries deliver most things using motorbikes, it always sounded ridiculous to me to use a car to deliver food

Use the libredirect extension to redirect links automatically to an open alternative

move as much of the code structure to the top as possible

I do the opposite and move all source code to a generic named src or similar, because the alternative creates even more clutter in the root dir IMO by mixing relevant and irrelevant files. And generic names like src, docs, and tests help keeping a similar structure for different repos.

yeah, I’ve also been noticing this in the past months. The number of dotfiles in project roots is an ever growing number, to the point where we have literally dozens of files and directories and only a handful that actually mean anything to the project. It’s pure clutter.

This way, if users don’t need separate project environments, they will just run sqlpkg as is and install packages in their home folder (e.g. ~/.sqlpkg)

XDG dirs or nothing. Don’t touch my home directory.

That should be the default assumption for every service that hosts user content. Even if it explicitly says they won’t use it for XYZ, they might change it at any time.

maybe he thought it was knowyourtesties.com

yeah, I helped raise hw requirements for two servers recently, an alternative to nvidia wasn’t even on the table

we’re talking GPUs, idk why you’re bringing FPGA and CPUs in the mix