gnome-shell-wsmatrix VS turbo

Workspace Matrix extension makes my day, every day.

I just had NixOS break in a weird way for me. Ok, it was more that Gnome 42.4 broke the wsmatrix extension, which caused Gnome to shit itself[1] on login.

It's a little bit of a double edged sword. NixOS lets me use pretty much straight upstream packages, which sometimes break due to not having thorough integration testing like a traditional distro would. On the other hand, I was able to just boot up an older configuration to get back to functional, and that let me figure out wtf was wrong.

[1]: https://github.com/mzur/gnome-shell-wsmatrix/issues/236

Implement the Workspace Matrix extension for GNOME https://github.com/mzur/gnome-shell-wsmatrix in Sway, possibly looking at Sway Overview for inspiration.

Hej, recently updated my laptop to 22.04 but after some years getting use to unity and 2 extra screens now seems i cannot find my way to have a decent wall of workspaces... i found a nice extension that works fine (https://github.com/mzur/gnome-shell-wsmatrix) but only seems to create the workspace wall on the latop screen and not on the other external screens...

Release info: https://github.com/mzur/gnome-shell-wsmatrix/releases

My main concern is a 2D grid for workspaces, with workspace previews in the workspace switcher popup. Workspace Matrix does an excellent job of adding this to GNOME.

it will assign a new font to the extension. Then you may use an icon font, such as Font Awesome, Icofont or icomoon (which also allows you to create your own!). You can then change the workspace names with dconf-editor with the characters from the font. PM me if you need any help :)

On GNOME there's a way to get native 2 dimensional workspaces, but AFAIK the only way to enable this is with an extension like workspace matrix. For ctrl+alt+arrow-like shortcuts be sure to set keybindings for switch-to-workspace-arrow and move-to-workspace-arrow in org.gnome.desktop.wm.keybindings. However, I had some issues with GNOME 40 like: - Changing workspaces with mouse scroll jumps to an adjacent workspace up/down (as expected). Without a device that has horizontal scroll (like a touchpad) you can't go to adjacent workspaces left/right. - There are multiple issues with the workspace thumbnails in the overview.

Ok, so, I'm using Workspace Matrix for a workspace grid.

Supermemory has three main modules, managed by turborepo:

From a structural viewpoint, we use a monorepo (Turborepo) to manage packages, even though we currently have only one Next.js app. We chose this setup because it prepares us for future developments, which will include additional apps. This arrangement helps keep the packages well-separated and self-contained.

# src Dockerfile: https://github.com/vercel/turbo/blob/main/examples/with-docker/apps/web/Dockerfile FROM node:18-alpine AS alpine # setup pnpm on the alpine base FROM alpine as base ENV PNPM_HOME="/pnpm" ENV PATH="$PNPM_HOME:$PATH" RUN corepack enable RUN pnpm install turbo --global FROM base AS builder # Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed. RUN apk add --no-cache libc6-compat RUN apk update # Set working directory WORKDIR /app COPY . . RUN turbo prune --scope=web --docker # Add lockfile and package.json's of isolated subworkspace FROM base AS installer RUN apk add --no-cache libc6-compat RUN apk update WORKDIR /app # First install the dependencies (as they change less often) COPY .gitignore .gitignore COPY --from=builder /app/out/json/ . COPY --from=builder /app/out/pnpm-lock.yaml ./pnpm-lock.yaml COPY --from=builder /app/out/pnpm-workspace.yaml ./pnpm-workspace.yaml RUN pnpm install # Build the project COPY --from=builder /app/out/full/ . COPY turbo.json turbo.json RUN turbo run build --filter=web # use alpine as the thinest image FROM alpine AS runner WORKDIR /app # Don't run production as root RUN addgroup --system --gid 1001 nodejs RUN adduser --system --uid 1001 nextjs USER nextjs COPY --from=installer /app/apps/web/next.config.js . COPY --from=installer /app/apps/web/package.json . # Automatically leverage output traces to reduce image size # https://nextjs.org/docs/advanced-features/output-file-tracing COPY --from=installer --chown=nextjs:nodejs /app/apps/web/.next/standalone ./ COPY --from=installer --chown=nextjs:nodejs /app/apps/web/.next/static ./apps/web/.next/static COPY --from=installer --chown=nextjs:nodejs /app/apps/web/public ./apps/web/public CMD node apps/web/server.js

Following this example: https://github.com/vercel/turbo/tree/main/examples/with-docker/apps/web. Except I'm using pnpm. Edit Reddit Codeblocks are horrible and keeps removing all formatting.

The Dockerfile might seem a bit complicated (it is), but the reason for that is mostly just turborepo and the need for good caching. Realistically, you will only need to change the last line, if at all. It is based on this awesome Github Issue.

PURISTA is organized in a monorepo. During the development and build process, Turbo is used to execute different tasks and steps on multiple packages with one command.

Turbo repo

Previously we mapped each Vercel project to a single Supabase project. With this release, we're introducing the concept of project 'Connections'. Supabase projects can have an unlimited number of Vercel Connections. This is especially useful for monorepos using Turborepo.

One detail I enjoy from this post is that sometimes you can just call a CLI[0]. It's easy to spend a lot of time figuring out how to expose some Rust/C code as a library for your language, but I like the simplicity of just compiling, shipping the binary and then calling it as a subprocess.

Yes, there's overhead in starting a new process to "just call a function", but I think this approach is still underutilized.

[0]: https://github.com/vercel/turbo/blob/c0ee0dea7388d1081512c93...