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.

IMO (neo)VIM is great for writing text as well, when all you need is markdown level formatting. Personally I use vimwiki a lot (many years by now).

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.

Assuming one hears their own voice in recorded form enough times, that “strange” feeling it might give at first subsides.

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

Oh boy… can’t promise you that I will last that long. I know it sounds pathetic, but is replying to one’s own comment an option (just for stress testing)?

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.

Kinda, but that’s “rainbows”.

Status quo (your comment): 8 x 7 + 1 = 57 sure is bunch of stripes.

I see. 9th rainbow, here we go.

Oh wow, even if you put it in landscape? In either case, lemmy’s web interface hides a lot of context by default when answering via the “messages” notifcation. So in a sense, with that one could reply endlessly. Then again, that’s not part of our experiment I’d say.

Right, that’s how it all started.

I just unfolded everthing. Seems we are on the 8th rainbow. Almost looks like on my phone, while in potrait mode, 10 rainbows will likely have it filled up.

Alright, second season, here we go!

Ha, for sure I missed the other comment…

Yeah, that browser zoom. And I too used / use Firefox. I’m not saying these kind of sites are common, but nevertheless I’ve encountered them occasionally. Back then, the most pragmatic workaround was to use desktop zooming of Xfce.

My intention on the previous comment was simply to give some examples of desktop zooming that go beyond the typical accessibility viewpoint (e.g. vision impairment).

Yeah, AFAIR, the issue of “windows messing up grub” could happen when it’s installed on the same disk (e.g. on a laptop with one disk). Something about it overwriting the “MBR sector”. At least that was a problem back before UEFI.

I too have been dual booting Windows 10 and Linux for many years now, each having their own physical disk, Linux one always being first in boot order. Not once did a Windows 10 update mess up grub for me with this setup.

Not the same as “on demand zooming”, which let’s one stick with a high, native resolution, but zoom in when required (e.g. websites with small text that can’t be zoomed via browser’s font size increase; e.g. referencing some UI stuff during UI design, without having to take a screenshot and pasting + zooming it in e.g. GIMP).

One takeaway from this surely is that such deeply nested endeavours sure are easily missed.

I do wonder if there’s a hard limit at some point regarding “nested replies”…

Nice, bit over half way point here.