this post was submitted on 23 Sep 2025
764 points (98.6% liked)

Microblog Memes

9305 readers
1819 users here now

A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.

Created as an evolution of White People Twitter and other tweet-capture subreddits.

Rules:

  1. Please put at least one word relevant to the post in the post title.
  2. Be nice.
  3. No advertising, brand promotion or guerilla marketing.
  4. Posters are encouraged to link to the toot or tweet etc in the description of posts.

Related communities:

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] nek0d3r@lemmy.dbzer0.com 60 points 5 days ago (3 children)

Instead of asking why your word processor should have the ability to run arbitrary code, you just inconvenience everyone else on the chance it might. What even.

[–] CaptDust@sh.itjust.works 32 points 5 days ago

Yup, it's a shit bandaid to mitigate a shit design. The MS specialty.

[–] sp3ctr4l@lemmy.dbzer0.com 6 points 4 days ago

Yep.

A constant stream of creating problems and then creating solutions for those problems, which cause more problems....ad infinitum.

Go back and fix the root cause?

Impossible!

Then our 2nd and 3rd tier 'solutions' would have all the 'solutions' based on them not work!

[–] shalafi@lemmy.world 9 points 5 days ago (2 children)

Scripting is great in Excel, but I've never encountered or heard of a use for it in Word.

[–] Lyrl@lemmy.dbzer0.com 1 points 3 days ago

I used to work at a place where one of their test machines generated a cert in Microsoft Word with test results. They were having their lab technicians manually type in something like eight fields of information to flesh put the cert. I managed to hack together a Word VBA plus Python script to interface with the OpenOffice database I had set up so the techs only had to type in one field, and the script filled in the rest.

It was kind of a monstrosity under the hood, but it worked pretty slickly, and given the available tools I was glad the option existed.

[–] SirActionSack@aussie.zone 6 points 5 days ago (1 children)

That's partly because the API for manipulating word docs with VBA is incredibly awful.

[–] Lyrl@lemmy.dbzer0.com 1 points 3 days ago

VBA for Word is bad, but VBA for Excel graphs is worse. At small companies that can't justify the cost of any software outside Office, people will go to great lengths to get Excel to support data analysis. Not being in that situation anymore is one of my top satisfaction items with having changed jobs from a small to a large company.