this post was submitted on 28 Aug 2024
346 points (98.3% liked)
Technology
59099 readers
3181 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- 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
view the rest of the comments
Not as drastic as the headline makes it out to be, or at least so they claim.
We'll see how that actually works out. Tumblr’s backend has always seemed rather... makeshift, so I'm curious to see how they manage to do that. Given Tumblr’s technical eccentricities, a backend migration could probably do a lot of good for the functionality of the site, if done properly. I have my doubts that WordPress' engineers will be given the time and resources to do a full overhaul/refactor though, so I'm fully expecting even more janky, barely functional code stapling the two systems together.
WordPress is built on decades of hacky code, probably more so than Tumblr. I would be shocked if this is an improvement.
is it decades of hacky code, or decades of battle tested code?
I haven't touched wordpress in... many years, but I've seen far too many developers look at old code and call it junk... only to break things horrifically when they attempt a rewrite.
Both honestly. Very spaghetti, but noone can deny that it just works from a user perspective. Would I want to maintain the code? Hell no! Do use it as an end user? Hell yeah!
Nah, not touching that with a 10' pole. There have been far too many exploits for me to feel comfortable putting any of my important data on it. And it's not just that it's popular, the level of sophistication for these attacks are... alarmingly low.
It's a public site that'll be backed up regularly, what kind of important data would you be putting out publicly?
If it's an e-commerce site, than people's payment info, name, and address. If it has a login, then their login information (which they're most likely reusing elsewhere). Even if it's just a static site, than any data that might be hosted on the same server.