plasma
Joined 15 years ago
Joined 15 years ago
Pros: one click setup for devs jumping between projects after you get the devcontainer setup process working, takes some fiddling, trial and error.
Has felt good for some older projects to be wrapped in the devcontainer and once it’s working feel comfortable the environment is stable, and also moving everyone to new environments has been easy.
Keeping a haywire dev/npm script away from your main machine is also good, but I know it’s not foolproof.
Cons: Codespaces CPUs are usual cloud slow so you need to pay more and single threaded perf won’t be as good as your laptop, a real shame. I think GitHub competitors would have better CPUs.
Very rarely but Codespaces can have a technical issue and you can't do your work (inaccessible), and to avoid it sleeping during the day due to inactivity you may leave it running most of the day but it demands a shutdown after 12 hours or so, so very long dev sessions can be interrupted.
GitHub also dropped support for using JetBrains IDEs which was not cool, so it’s just vscode which is usable but would have preferred other IDEs.
If Codespaces team is reading would love to see some improvements here.
https://about.gitlab.com/blog/gitlab-discovers-widespread-np...
I’m curious if you’d also move into API testing too using the same discovery/attempt approach.
On the Data tab it says "no schema defined yet."
The Schema tab doesn’t seem to have a way to create a schema.
Most of the other tabs (except for Sources) looked blank.
I did see the chat on the right and the "51 items" counter at the top, but I couldn’t find any obvious way to view the results in a grid or table.
Check out https://chat.openai.com/share/34091576-036a-4e82-b4e3-a8798d...