I thought moving from i3/x11 to sway/wayland but from this post is looks like screen sharing still not resolved yet completely on wayland. How much time is worth to wait until UX with wayland will be good enough to not worry about that kind stuff?
I can't say how much time it is worth to you, sorry. What I can say is that screen sharing works fine under Wayland and Gnome for me (AMD hardware all the way), so I'm inclined to say that Wayland is not the showstopper here.
anyway, if one of the majors tiling wm managers struggling to share specific window it looks like it could be more edge cases like that. Probably, I can deal with those things but I fully understand struggle of this article author so just wanna upgrade to it when possibility of struggle will be minimal for me.
I use both, while Obsidian is good and has lot in common but for some reason org-mode still feels more useful and permanent. If it something important for me personally I most likely will put it in 'org' but if I just need write something of temporary nature like documentation peace for work I might prefer Obsidian for that. Also org-mode TODOs/agenda stuff very helpful for triage of tasks and prioritization (I think it's just habit that has some 'migration' cost so I not really considering it as big benefit over other tools)
You can only use IDEA when you need to do major refactoring or debugging, which isn't that frequent on average. There's nothing special about navigation in IDEA that text editors can't do.
IDEs aren't perfect - they often have performance issues, new bugs with every update and do confusing things like marking completely valid code as errors. One of the reasons why I stopped using IDEA after many years of being a fanboy is that I found these unexpected behaviors and bugs getting in the way of actual work. For example, you might reopen your project in the morning to find out that everything that worked perfectly in the evening is suddenly broken, and then you have to spend half the day reinstalling previous versions of plugins and cleaning caches. While editors might be a bit simpler, they're always works reliably.
>At work we are forced to use a specific IDE. It's a niche programming language not supported by any other software.
one good thing that I heard about McIntosh, is that even after 10-20 years of owning it, you can contact their support to buy some spare parts for fixing, and they will sell and even would be helpful to figure out what exactly needed (even in case if you are not original buyer). Unlikely that Bose would be interesting continue doing that kind of level of support.
I had several Tumi items. When I got them, I was told they had a "lifetime warranty," and I actually exercised it, a couple of times (broken zipper, one time).
Isn't the point of buying brands like that that you shouldn't need to fix after only 10-20 years? I have a denon receiver from the late 90's that I upgraded from and has been my garage/shop amp for the last 15 or so years. It is covered in dust and dirt and still cranks like the day I got it.
I also bought a 10+ year old Denon amplifier and overall it's great, but over time it developed some minor issues with components like Alps potentiometers and switches. Unfortunately, Alps doesn't produce some of those parts anymore (like the ones discussed here: https://www.diyaudio.com/community/threads/source-for-alps-a...), so it's really not easy to source parts for repairs. It would be nice if you could simply ask the manufacturer to sell these components to you directly.
Well, yeah. I know I have a lot of 20+ year old audio stuff still going strong.
Some things like capacitors have a lifespan just due to their nature.
A McIntosh owner might also enjoy knowing that accidental "user error" type stuff can be repaired. It's pretty difficult to actually blow out an amplifier unless you're doing some real torture test type stuff; the fuses should blow before you can do any real damage. But still, after having plunked down megabucks on an amp, it's probably nice to know that your $10K or $20K investment can be repaired if you really manage to screw something up.
Not that I personally would ever consider owning McIntosh gear. I'm sure it's nice, but at the prices they're asking... I'm good.
sure that the case in lot of countries but is something really wrong with idea to have 2+ clients as minimum because reason why work done in that way is because person doing it don't wanna agree on terms that 'employment' contract is required and if that 'single' client is gone he always can get another one in few months. Sometimes you work with few clients in single year but sometimes it just one for 2-3y. And worth part that in some places taxes on self-employment might be higher.
noise actually not that bad with some bios configuration tricks - I used to run dell r720 and r420 together with ~20 HDDs near my desk table and most of the day noise was close to some non-silent gaming PC/workstation. Only problem was if is some need to reboot it, in that case it just blow fans to full power and it's loud like vacum cleaner that you for sure don't wanna to use at middle of the night.
almost at any place that rate is not really stable over time and overall if you have something close to 65-70% then it's probably just average situation.
From my experience places where more programing happening are:
- mid-big companies where you role could be very specialized
- small companies with focus on creating tech products or where tech has lot of impact on end customers (like if fixing few bugs could instantly lead to making additional money for a company)
Companies from non-tech word usually value non-coding stuff much more.
(I currently have about 50/50 rate and sometimes even less)
reply