GitHub Codespaces Reviews

LakeFS Reviews

GitHub Codespaces mentions (152)

• OpenCode Hit 140K Stars. Why Terminal Agents Won 2026.

  First, remote dev environments became table stakes. GitHub Codespaces, Gitpod, and self-hosted dev containers became how serious teams worked. Every engineer I know who ships to production now SSHs into a box they didn't provision, edits files with whatever editor is installed, and commits from a terminal. An IDE-bound agent requires you to also forward your IDE to the remote box, which most people don't bother... - Source: dev.to / 3 months ago

• Introducing codespaces.el: The Best Way to Use GitHub Codespaces

  This package provides support for managing GitHub Codespaces in Emacs and connecting to them via TRAMP. It provides a handy completing-read UI that lets you choose from all your created codespaces. - Source: dev.to / 5 months ago

• Don't get scammed on an interview.

  GitHub Codespaces provides 60 hours of free compute time every month, which is more than enough for scoped home assignments or interviews. It’s a full VSCode in the browser at github.dev or vscode.dev. - Source: dev.to / 8 months ago

• Stop Wasting Hours on Environment Setup - These Tools Will Save Your Sanity

  GitHub Codespaces - Cloud development. - Source: dev.to / about 1 year ago

• VSCode's SSH Agent Is Bananas

  https://github.com/features/codespaces All you need is a well-defined .devcontainer file. Debugging, extensions, collaborative coding, dependant services, OS libraries, as much RAM as you need (as opposed to what you have), specific NodeJS Versions — all with a single click. - Source: Hacker News / over 1 year ago

LakeFS mentions (6)

• Ask HN: AWS S3, Cloudflare R2, GCS, Wasabi, or B2?

  I would add https://github.com/gaul/s3proxy to your list. - Source: Hacker News / over 2 years ago

• Dev / Stage / Prod is the wrong pattern for data pipelines

  * data state - this is contents of both your data and metadata at a given point in time. if your data doesn't fit into a single database, this can be difficult to manage. We use this technology to help us: https://lakefs.io/. - Source: Hacker News / almost 3 years ago

• Dev / Stage / Prod is the wrong pattern for data pipelines

  Saltcured, find these comments super insightful! > Yeah, there's a lot of hidden magic/assumptions in having a "writable snapshot of a specific version" of production data. That's absolutely a huge assumption. This technology has been a game changer for us: https://lakefs.io/ > It becomes a headache when there is too much contention to use these sandboxes, or too much manual effort to reset them to a desired... - Source: Hacker News / almost 3 years ago

• Using git to version control experimental data (not code)?

  You should not store your data in git itself, but rather use git to version your data sets. The currently best option for that is (IMHO) https://lakefs.io though there are a few others in various states of usability/maturity. Source: over 3 years ago

• How are you incrementally testing your data pipelines as you develop them?

  I mean if you're ready to adopt a new framework into your ecosystem this is one of the major usecases for LakeFS. Source: over 3 years ago