dimitrieh

100%

We recently created a survey website for the community survey results for Node-RED making it completely dynamic and segment-able. Creates lots of value and allows everyone to look at the data through their own lens. It uses DuckDB with WASM under the hood. Awesome technologies.

https://nodered.org/community-survey/

Jujutsu comes in handy here for the same usecase:

https://github.com/jj-vcs/jj

https://www.stavros.io/posts/switch-to-jujutsu-already-a-tut...

Also found https://github.com/gitbutlerapp/gitbutler

Node-RED has recently completed an extensive community survey to better understand how to improve Node-RED together for its users. All results are completely filterable and segment-able so everyone can draw their own conclusions and discuss those.

Related Node-RED blogposts that take these results into account:

https://nodered.org/blog/2025/12/01/modernization-survey-res...

https://nodered.org/blog/2025/12/03/node-red-roadmap-to-5

PS: It uses DuckDB with WebAssembly so everything runs inside the browser.

Thanks, exactly this! Stay tuned!

Interesting! Please, open an issue if you're interested!

Great to hear this! Please leave any feedback in our issue tracker mentioned in the article!

It's one of the problems we are trying to solve. Git is hard, so a guided experience can prove valuable.

See for more information https://gitlab.com/gitlab-org/gitlab-ce/issues/47307 and https://gitlab.com/gitlab-org/gitlab-ce/issues/46122 for example in how we are improving this starting with 11.1

Keep an eye out at the issue tracker mentioned in the article if you want to be most up to date on development

We are hard at work! Time and iterations are needed. A lot is coming your way, it is a very exciting project!

https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...

This is currently being resolved!

Happy to hear so! GitLab.com should be able to offer all the features you need if you wish not to self-host!

Happy GitLabbing!

Hi, GitLab UX Designer here. I would like to add that GitLab has put tremendous efforts in optimizing for performance lately. These performance optimisations optimise GitLab instances big and small. These improvements were triggered by having literally millions of users and projects on GitLab.com which is our hosted solution.

For self-hosted GitLab instances run on a smaller scale, there should not even be a chance of performance hits :).

Just to give a good overview of what GitLab is offering for both self-hosted as well as our hosted solution of GitLab.com please look at https://about.gitlab.com/features/

I am happy to hear that the CI/CD integration, which is our native solution for CI/CD and beyond is being well received! We want to persuade not force users to use our native solutions.

Hi, I am from the GitLab UX team. You may be happy to hear that since and even before the implementation you described we have been busy on a real upgrade for navigation across the whole of GitLab.

Rest assured, that we are hard at work at this (see for more information https://gitlab.com/gitlab-org/gitlab-ce/issues/32794). Even better, if I am correct, there will be a new navigation concept (first alpha iteration) released in 9.4! This will be hidden in a feature flag, which will be accessible from your personal settings.

In the coming months (and thus releases, every 22nd!) we will continue to improve upon this concept, to eventually enable it by default for everyone to enjoy.

We know that the shortcomings of the hamburger icon are suboptimal, but also know that reverting is not always the correct choice. With the new navigation concept we focus on getting a clear distinction between global and contextual navigation. We did proper UX testing to be able to clear out multiple bumps in the road/implementation and are pretty stoked about finally getting it in!

Again check for more information this issue https://gitlab.com/gitlab-org/gitlab-ce/issues/32794. The scope of revising navigation is pretty far reaching and has been on the minds of almost everyone on gitlab!

Note that colors, functionality and any specifics can change throughout the process of implementing over the coming months :)

thanks! Will keep these things in mind!

Hi, i am sorry to hear your experience have been as it is thusfar. We are hard at work improving the product constantly. We though have to prioritise ;)

You can't add comments on unchanged parts of the code in the diff-view.

Please join the discussion at https://gitlab.com/gitlab-org/gitlab-ce/issues/26722 and https://gitlab.com/gitlab-org/gitlab-ce/issues/14396

You can't see the what is changed in response to your comment between two MR uploads.

and

You can't add comments when you view the diff between two uploads of an MR. My list of complaints is endless.

For the following issues I created these gitlab issues to start the conversation. Internally and on the issue there may be a reference to already existing issues covering these subjects.

Thanks for your feedback! You can always join the conversation and/or contribute in order to get things like this shipped faster!

See: https://gitlab.com/gitlab-org/gitlab-ce/issues/32399 and https://gitlab.com/gitlab-org/gitlab-ce/issues/32400

Github PRs are light years ahead of Gitlab merge requests

I would love to know more about your thoughts on this statement ;) in order to get to actionable issues on which we can improve!

Improvements are high on our priority and are actively being worked on. To get to know more about our efforts, please take a look at our youtube channel https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg

Hi, we are moving more and more into the direction of going multi repo/multi project. Subgroups is the most significant step forwards for this. Expect to see cross project pipelines, management feature, monitoring etc

Give it a read and then check out the Gitlab Repo

https://gitlab.com/dimitrieh/curriculumvitae-ci-boilerplate

;)

Results :)

Medium post: https://medium.com/@dimitrieh/a-curriculum-vitae-latex-types...

Gitlab repo: https://gitlab.com/dimitrieh/curriculumvitae-ci-boilerplate