this post was submitted on 11 Oct 2023
398 points (98.8% liked)

Technology

59446 readers
4144 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] AlmightySnoo@lemmy.world 52 points 1 year ago* (last edited 1 year ago) (45 children)

I hope they kill off VBA too. I still see some teams in banks implementing Monte Carlo simulators or PDE solvers in straight VBA 🀒

[–] driving_crooner@lemmy.eco.br 21 points 1 year ago (15 children)

I'm migrating some VBAs to python/pandas and reducing some process times from half an hour to 3 minutes.

[–] AlmightySnoo@lemmy.world 17 points 1 year ago (11 children)

Yup that's normal because VBA is single-threaded, doesn't take advantage of vector instructions and even its interpreter is slow. So when someone writes numerical code in VBA working in single precision, and assuming they have an 8 core CPU with AVX2, they're using only 1/64-th of their CPU's processing power. On the other hand with Python, while it's still interpreted, the interpreter is much faster on its own, and you have modules like numpy that use precompiled routines that take advantage of vector instructions (and possibly multiple cores).

load more comments (7 replies)
load more comments (10 replies)
load more comments (39 replies)