Have a ZOWIE EC2 for quite a while now:

• gaming mouse, 5 buttons
• USB compliant
• no special vendor drivers needed to use all mouse features (has buttons on bottom side for settings)

Works well on all OS.

Coincidentally, I happen to have been reading into SEO more in depth this week. Specifically official SEO docs by google:

https://developers.google.com/search/docs/fundamentals/seo-starter-guide

To be clear, SEO isn't about tricking search engines per se. First and foremost it's about optimizing a given website so that the crawling and indexing of the website's content is working well.

It's just that various websites have tried various "tricks" over time to mislead the crawling, indexing and ultimately the search engine ranking, just so their website comes up higher and more often than it should based on its content's quality and relevancy.

Tricks like:

• keyword stuffing
• hidden content just visible to crawlers
• ...

Those docs linked above (that link is just part of much more docs) even mention many of those "tricks" and explicitely advise against them, as it will cause websites to be penalized in their ranking.

Well, at least that's what the docs say. In the end it's an "arms race" between search engines and trickery using websites.

Depends on the specific plugin. I've been doing music production on Linux for several years now. Back then things looked a lot worse than now. Most popular bridge solution for Windows plugins on Linux is yabridge atm. The README is well worth a closer read, cause it will answer many questions on how to get even more modern plugins to display correctly (i.e. JUCE based ones).

In my experience, getting one can be more about politics and fulfilling certain management checkboxes than about technical skill and experience.

And it will find you the most answers online in case you have a git related question.

Just looked it up a bit: https://microsoft.github.io/monaco-editor/

AFAIU, monaco is just about the editor part. So if an electron application doesn't need an editor, this won't really help to improve performance.

Having gone through learning and developing with electron myself, this (and the referenced links) was a very helpful resource: https://www.electronjs.org/docs/latest/tutorial/performance

In essence: "measure, measure, measure".

Then optimize what actually needs optimizing. There's no easy, generic answer on how to get a given electron app to "appear performant". I say "appear", because even vscode leverages various strategies to appear more performant than it might actually be in certain scenarios. I'm not saying this to bash vscode, but because techniques like "lazy loading" are simply a tool in the toolbox called "performance tuning".

BTW: Not even using C++ will guarantee a performant application in the end, if the application topic itself is complex enough (e.g. video editors, DAWs, etc.) and one doesn't pay attention to performance during development.

All it takes is to let a bunch of somewhat CPU intensive procedures pile up in an application and at some point it will feel sluggish in certain scenarios. Only way out of that is to measure where the actual bottlenecks are and then think about how one could get away with doing less (or doing less while a bunch of other things are going on and then do it when there's more of an "idle" time), then make resp. changes to the codebase.

On top of that, 20 kHz is quite the theoretical upper limit.

Most people, be it due to aging (affects all of us) or due to behaviour (some way more than others), can't hear that far up anyway. Most people would be suprised how high up even e.g. 17 kHz is. Sounds a lot closer to very high pitched "hissing" or "shimmer", not something that's considered "tonal".

So yeah, saying "oh no, let me have my precious 30 kHz" really is questionable.

At least when it comes to listening to finished music files. The validity of higher sampling frequencies during various stages in the audio production process is a different, way less questionable topic,

Nobody can tell you in advance how far your interest in game dev will take you. Only one way to find out: start small (some tutorials, build some crappy first) and see if your interest sticks around as you up the challange.

Maybe game dev in Godot will end up being a significant chapter in your life, maybe it will just be a small sidequest. But once you've given it an honest try, no matter the outcome, you at least will know if it's something for you or not. That in itself is already worth something.

And who knows: maybe Godot is just your entry gateway to something else you discover along the way, which you wouldn't have discovered if you hadn't taken on the challange in the first place.

The past doesn't necessarily dictate the future. If the people in charge of SUSE's direction going forward think way differently than the one's back in regards to your comment, then the outcome can be different / better for the Linux community, can't it?

I'm in the same boat as you. But considering there's this thing called the "ad industry", there's bound to be a considerable portion of people that are influenced enough by ads, even just at a subconcious level, that investing money into ads is a worthwhile thing to do for businesses selling products and businesses offering ad platforms.

Git for projects

I assume the original comment meant code based projects, for which git, if repo is pushed to a remote, is a very sane choice.

Yeah, especially when considering that placebo and (in this case) nocebo effects are a real thing.

What do people think would happen when being told they will be very likely diagnosed with an incurable disease in 5 years from now? Do they think their levels of stress, anxiety, negative thinking etc. will stay as if they'd never heard of that information? No, likely not. Therefore their health will potentially be affected negatively just by knowing of that information.

But the important part here is the "incurable"! Reason being that if there's any chance one can prolong good health for longer by acting in a preventive, health supporting way couple years sooner, then yes, it likely would be better to know earlier and change something about it even if it's likely to affect one at some point.

And what makes it even trickier is that nobody really knows what future medical advances will be like. What's called inevitable and incurable now, might, with early treatment, actually no longer be in the not too distant future.