siddheshgunjal

I'm an ML engineer with almost 6 years of experience in the field and I use only Sublime+Terminal for all my development (ML, Web, Flutter, etc.) Yes, even for flutter I do not use VS code or Android Studio, only Sublime (with LSP)+Terminal.

- The reason is, when I was a newbie in the world of ML, I had a laptop worst than a potato laptop. So, I had to preserve as much resources as I can for actually ML tasks. That forced me to keep things simple & lightweight.

- At that time I tried to use PyCharm, VS Code, etc. but all of them resulted in consuming a lot of resources and very little left for actual model to run.

- Fast forward to today, I now have a decent laptop for coding & a good workstation for my ML related workflows, but I still chose to use only Sublime+Terminal for all my tasks

- To be honest, setting up Conda to work with PyCharm & VS code is sometimes pain in the a*. Some of my students still come to me with problems of conda and other env management tools not working properly with VS code & PyCharm.

- The thing is I like to keep things simple and lightweight. In my experience, Sublime is an excellent code editor with excellent package support. I find running scripts, managing envs, docker, DBs, etc, simpler and quicker directly from Terminal...

- I do not understand why people use VS code or PyCharm if they have to take additional steps to make their tools work with it, let's say Conda (environment management tool). Whereas same task can be done with just Vanilla terminal without any hassle.

So Am I insane for using only Sublime+Terminal in my dev environment while entire world is using various(God knows how many) tools for development. Or is it just a developer inside who got used to keeping everything so optimised at each level, that anything that consumes resources unnecessarily makes my wanna avoid using it...

- I am really curious to know what tools you guys are using in your dev environment? And what's your reason for that setup?

If you're a Linux user (like me) opted for Wayland display server, you might have encountered a frustrating crashes when you try to screen share during huddles. This issue has been a there since April 2023 release (Slack 4.31.155) for Linux and it's still not fixed till the date of submission of this post. I have tried multiple ways to make it work but in the end it still crashed.

Screen sharing is something which was very important to me as I cannot always create a google meet link for small discussions with my team. That's why we have huddle in slack.

I even tried to switch to X11 on my fedora workstation, but then I had to do the workarounds for gestures for touchpad with touchegg (sudo dnf install touchegg) and GNOME extension (https://extensions.gnome.org/extension/4033/x11-gestures/) and the results were not as smooth as they were on wayland. I always preferred wayland because of its performance and also noticed better battery life with it than X11.

After searching the web for hours, I finally found the solution on this issue tracker on github: https://github.com/flathub/com.slack.Slack/issues/196#issue-1684889894

The trick is simple, Just rollback to the version 4.29.149 with: sudo flatpak update --commit=b95d24a8a354db07b95b065b3e57e9442c9fbaf851a49cbe6e7b1aa0afcab591 com.slack.Slack and then just mask the package so it does not updates to latest version. flatpak mask com.slack.Slack

Now your screen sharing should work with wayland session. You can test to verify the working from Preferences -> Audio & Video -> Troubleshooting -> Run an audio, video and screensharing test or just start a huddle in an empty channel to test the screen sharing.

Devs hinted that the fix is in work with the latest Slack 4.34.115 release on 5th September 2023 (https://slack.com/intl/en-in/release-notes/linux), till it lands in production, we'll have to use Slack 4.29.149 for working screen sharing in wayland session.