They're back!
-
Slrpnk.net was my first Lemmy server! I had absolutely NO IDEA how it worked, but I was motivated by my recent departure from Facebook and Twitter.
When they went down, it kinda felt like when you go to a party with someone and it's all their friends, and then your date vanishes into thin air, and your choices are leaving the party or making awkward convo with a rodent of unusually large size by the punchbowl...
-
Congrats!
-
So happy to be home again ^^
-
We're elated to be back in business. Brace yourself, my shitposting itch has gone unabated for a while now.
I'm ready.
-
Not being able to participate anywhere on Lemmy merely because my home instance was down didn't feed very federated
Is there anything I can do to guard against that issue in the future? Is there a way to mirror an account between two instances or something?
Anyway, big props to the slrpnk admins for getting the instance back online quicker than expected. Your hard work is definitely not unappreciated or unnoticed.
-
Not being able to participate anywhere on Lemmy merely because my home instance was down didn't feed very federated
Is there anything I can do to guard against that issue in the future? Is there a way to mirror an account between two instances or something?
Anyway, big props to the slrpnk admins for getting the instance back online quicker than expected. Your hard work is definitely not unappreciated or unnoticed.
there anything I can do to guard against that issue in the future? Is there a way to mirror an account between two instances or something?
Open an alt, export/import your settings
-
I'm ready.
But my sandworms will die!
-
yay!
(lemm.ee lying dead slightly offscreen)
-
Not being able to participate anywhere on Lemmy merely because my home instance was down didn't feed very federated
Is there anything I can do to guard against that issue in the future? Is there a way to mirror an account between two instances or something?
Anyway, big props to the slrpnk admins for getting the instance back online quicker than expected. Your hard work is definitely not unappreciated or unnoticed.
It's possible to export your Subscriptions, Community/instance blocks, and saved posts/comments to an account on a different instance by exporting your account's JSON file, which you can do in your Account Settings page.
You can then import the JSON file in that same area on your alternative backup account, so that your experience is uninterrupted. Personally I would recommend making a backup account on Sopuli.xyz or Lemmy.cafe, they'll give you the most similar vibe due to how their instances are set up.
-
But my sandworms will die!
The spicy memes must flow!
-
Hell yeah, welcome back!
-
Not being able to participate anywhere on Lemmy merely because my home instance was down didn't feed very federated
Is there anything I can do to guard against that issue in the future? Is there a way to mirror an account between two instances or something?
Anyway, big props to the slrpnk admins for getting the instance back online quicker than expected. Your hard work is definitely not unappreciated or unnoticed.
I have alts. No automatic sync, but you can list your alts in your profile like I do.
On mobile make sure to use a client which makes it easy to switch between accounts (I use Thunder, which additionally shows server status in the account switcher!)
-
Yaaaaay, welcome back y'all!
-
You guys are the best. Thanks for the warm welcome back.
This post was actually how I learned slrpnk.net was back online.
-
We're elated to be back in business. Brace yourself, my shitposting itch has gone unabated for a while now.
back to the meme mines with you
-
And they want to migrate to piefed? Does it have better performance than Lemmy? That would be hilarious if python were faster than rust.
-
Great news!
-
-
And they want to migrate to piefed? Does it have better performance than Lemmy? That would be hilarious if python were faster than rust.
Tbh, the vast majority of performance issues don't come from the language but from the application itself.
While python is clearly slower than rust when it comes to pure native performance when doing exactly the same things exactly the same way and only within the language itself, the same isn't necessarily true in the bigger picture.
- Python uses C modules under the hood. A lot of the functions you call actually utilize C with C performance.
- Lower level languages allow the programmer to fail harder. While perfect low-level language code usually runs faster than perfect high-level language, the same cannot be necessarily said for bad or average code. For example, it's really hard to make an actual memory leak in Python. It's super easy to do so in languages without built-in memory management. The same applies in many other cases too. Python just gives you a lot of already-done tools that you only have to use, while other languages allow you to build the tools from scratch, which is easy to mess up.
- Most performance is lost due to using wrong algorithms or data structures. It's quite common when optimizing that you e.g. manage to eliminate a nested loop or something like that (e.g. loops hidden inside functions you call), and suddenly you improve performance by a factor of 1000. The same can't be done by switching languages, where even the most inefficient languages are only maybe 10x slower than the fastest languages.
So independent of the programming language, investing time in optimizing can improve the performance much more than using a faster language, and it's much easier to make perfectly optimized high-level language code than perfectly optimized low-level language code.
-
Tbh, the vast majority of performance issues don't come from the language but from the application itself.
While python is clearly slower than rust when it comes to pure native performance when doing exactly the same things exactly the same way and only within the language itself, the same isn't necessarily true in the bigger picture.
- Python uses C modules under the hood. A lot of the functions you call actually utilize C with C performance.
- Lower level languages allow the programmer to fail harder. While perfect low-level language code usually runs faster than perfect high-level language, the same cannot be necessarily said for bad or average code. For example, it's really hard to make an actual memory leak in Python. It's super easy to do so in languages without built-in memory management. The same applies in many other cases too. Python just gives you a lot of already-done tools that you only have to use, while other languages allow you to build the tools from scratch, which is easy to mess up.
- Most performance is lost due to using wrong algorithms or data structures. It's quite common when optimizing that you e.g. manage to eliminate a nested loop or something like that (e.g. loops hidden inside functions you call), and suddenly you improve performance by a factor of 1000. The same can't be done by switching languages, where even the most inefficient languages are only maybe 10x slower than the fastest languages.
So independent of the programming language, investing time in optimizing can improve the performance much more than using a faster language, and it's much easier to make perfectly optimized high-level language code than perfectly optimized low-level language code.
Facts right here. I love Rust and my day job is Python. Neither is too slow for most of my use cases. Though one cool thing about Rust is the super low overhead. So well-written Rust, much like well-written C, is great for low-power devices. Still, the database is going to be memory, IOPS and maybe CPU hungry as it grows. You can optimize data structures, but you still need to read said data.
