I do not agree with @FiniteBanjo@lemmy.today’s take. LLMs as these are used today, at the very least, reduces the number of steps required to consume any previously documented information. So these are solving at least one problem, especially with today’s Internet where one has to navigate a cruft of irrelevant paragraphs and annoying pop ups to reach the actual nugget of information.

Having said that, since you have shared an anecdote, I would like to share a counter(?) anecdote.

Ever since our workplace allowed the use of LLM-based chatbots, I have never seen those actually help debug any undocumented error or non-traditional environments/configurations. It has always hallucinated incorrectly while I used it to debug such errors.

In fact, I am now so sceptical about the responses, that I just avoid these chatbots entirely, and debug errors using the “old school” way involving traditional search engines.

Similarly, while using it to learn new programming languages or technologies, I always got incorrect responses to indirect questions. I learn that it has incorrectly hallucinated only after verifying the response through implementation. This makes the entire purpose futile.

I do try out the latest launches and improvements as I know the responses will eventually become better. Most recently, I tried out GPT-4o when it got announced. But I still don’t find them useful for the mentioned purposes.

I was well aware of the age of the article and original post.

But I saw no harm in prompting the community to ask for suggestions to a software that is adding bloat in disguise of dumb features.

Cross posted this as I just noticed the “feature” on my machine.

Any suggestions for alternative software for an MX Master 3 being used with macOS.

Buying a whole other device seems wasteful as the mouse is in flawless condition, but if you have any suggestions I can take a note of it when it is time to buy a new device.

Seems like Apple’s convoluted guidelines around external payment systems is working out for them

Thanks for the list. While there are some that I read about previously, a few of the other patterns are something that I only experienced.

It is nice to know that these have been identified and labelled by others in the industry. :D

That’s a really nice thinking exercise.

Makes me wonder why the aliens didn’t come back to the planet after nuking it. Or have they already arrived?

If they haven’t, why nuke a planet that one doesn’t plan to use?

For me, desktop UI peaked at Windows 98.

Installing the 95/98 GTK theme by B00merang is one of the first things I do after a fresh installation of Linux Mint.

I do try other themes once in a blue moon. But I soon realise it is a downgrade and revert back. The last theme I tried was the Arc theme back in mid-late 2010s.

The logo/brand devolved, IMO.

Coincidentally(?), their software devolved just as much!

I don’t want to install multiple applications to just use a mouse.

Good bot.

Interesting. May I know where you are viewing this post?

This is how it looks like on Voyager:

and on Lemmy web:

For those in the unknown, this comment is in reference to an article on The Daily WTF, which ThePrimeagen “reacted” to.

This comment thread reminds me of the “hunter2” meme. :D

E: adding screenshot taken from Voyager.

Unless I misunderstood “cloud service functionality”, an Obsidian vault can be placed almost anywhere on the file system. For instance, a remote/WebDAV drive or even the Dropbox/iCloud Drive/Google Drive directory.

Migrating is as easy as moving the vault directory from one location to another, and pointing Obsidian to it.

As always, on iOS, there are some caveats as it lacks a traditional file system. So, the Obsidian app cannot access the vault directory on, say your Dropbox. But there are workarounds for it, like hosting the vault on a remote Git repository - which is what I ended up doing. Of course, this is a non-issue on Android.

Obsidian has a help page that goes in detail about what I just said.

As for the Git repository workaround, I referred to this article to arrive at my current workflow.

As an aside, I would like to touch upon my experience with using the inbuilt sync on apps like Agenda and Joplin - both offering syncing using iCloud and Dropbox while the latter offering a whole lot more. It is a flaky experience at best, wherein a significant number of notes never really sync between the devices. This forces me to use my phone to view a particular note while my computer for another. This is where the plain text file foundation for apps like Obsidian and Logseq wins me over.

Force Touch was awesome!

Poor awareness among users and adoption among developers led to its demise. I never really figured which apps had support for Force Touch until I tried using it.

It’s replacement - the long press - just doesn’t fill the shoes of its predecessor w.r.t. UX. But I guess it achieves the same result.

It indeed sucks.

I hope the fix is delivered in one of the point releases rather than the next annual one.

Also, thanks for the information on this! :-)

Thank you for sharing the article. I stand corrected, and shall reflect this in my post.

Also, upon going through one of the sources from the article you shared, I found a quote by Craig Federighi on the change

there’s no need to double tap and no magnifying glass getting in your way

Yikes!

I try to rationalise this as a side effect of System Preferences now using SwiftUI, and have given up hope on it becoming sanely usable any time soon.

Another Safari regression is the inability to scroll over video elements. Which really breaks the Voyager experience

I have noticed this as well. I didn’t realise this was an OS issue. I assumed this was because I am using the TestFlight version of Voyager.

Ah, the share suggestions never really worked for me.

I know the OS tries to intelligently identify with whom I want to share an item, based on the type of item, recency of conversation, etc. “tries” being the operative term.

The OS does not even honour the app order I manually set under “More” in the share sheet. I remember filing a feedback for this specific behaviour long back.