HStone32
Honestly, I’ve only ever had problems with Wayland so far. So many times when I look up the issue tracker for a software I’m having issues with, the solution is always “switch to a DE that uses Xorg.”
I get that it’s not a mature software yet, but neither should people be pushing to use it until it is.
you either go back to windows, or turn into this guy. There is no 3rd option.
its the things I hear from real software developers that concern me:
- You will spend your entire career chasing trends.
- The market is volatile. People are constantly getting abruptly laid off. SD has never been very stable, so you should plan on getting a new job every few years.
- Software companies are constantly looking for ways to make SD easier. As a result, your value will decrease over time, in preference for bootcampers and 2 year degree graduates.
- Nobody listens to developers. Your manager’s beliefs about SD come entirely from consultants, magazines, and Elon Musk tweets.
- Nobody cares about quality software. If you take the time to make your code efficient and lightweight, all your manager sees is you taking longer to make something than your peers. After all, we can just raise hardware requirements if the software is slow.
the more i learn about software development, the more i feel I’ve dodged a bullet by changing my major to electrical engineering.
You know, I’ve always loved C and doing my own memory management. I love learning optimization techniques and applying them.
But you know what? Everybody around me keeps saying I’m being silly. They keep telling me I won’t find any jobs like that. They say I should just swallow my juvenile preferences and go with what’s popular, chasing trends for the entire rest of my career.
I don’t think you can blame people for trending away from quality software. Its clearly against the grain.
You know, when I typically ask a question on SO, its because I want to learn how that thing works, or how to write it myself. I usually say as much, but the SO folks are too focused on the ends, they completely neglect the means. Chances are I’m already aware of that no-code solution, but that’s not what I’m asking for.
SO in a nutshell:
“I need to do X”
“Have you tried Y?”
“No, because I don’t need Y, I need X.”
“Well you can do Z if you can’t do Y.”
“OK, sure. But how do I do X?”
“Why do you need to do X?”
(Explains why in my hyper-specific situation, I need to do X, and Y and Z won’t work)
This question has been marked as a duplicate of “How to do Y”
If I could, I’d compile all my software from source. Unfortunately, it seems a lot of open source developers don’t like writing software in C, which means the burden of sorting through dependancy-hell has been deferred to my shoulders instead.
i read a blog post by a former MS employee who shed some light on the situation. apparently the windows dev team is entirely made up of junior developers. As soon as anybody gets any experience, either MS tries to promote them to management, or they leave to find a better job.
what that means is there is nobody at MS who has deep knowledge of the Windows kernel. So instead of re-writting, re-factoring or making additions, all they know how to do is add things on top of the existing OS.