Which comment in the issue thread leads you to believe that?
The developer’s closing comment is that it wouldn’t be worth it to implement that feature in Lemmy.
Which comment in the issue thread leads you to believe that?
The developer’s closing comment is that it wouldn’t be worth it to implement that feature in Lemmy.
One way would be by implementing features the Lemmy devs have no interest in such as better interoperability with other fediverse platforms. If any added feature turns out to be well received and in demand, it would pressure the others to implement similar.
as we know bandwidth is extremely expensive
No. You very obviously don’t know how bandwidth is handled for large providers. They don’t pay per gb, and instead have peering agreements with other networks. Google generally doesn’t have to pay these other networks, as Google has the web applications that the other networks’ customers expect to be able to use.
Oh, I obviously interpreted that as meaning a hard disk drive (which SSDs are still commonly referred to as HDDs) since we were discussing modern PCs. Many years ago external physical file transfer mostly transitied away from using actual spinning disks to USB storage, and even that has been mostly supplanted by network connected storage for several years.
it doesn’t have a disc drive
False. Only the least expensive model has eMMC for the built-in storage. The other models have replaceable (upgradable) NVMe SSDs.
Sure, committing to a deadline is reasonable if you are included in the decision calculus of scope vs time. Part of that should be to include space for learning as needed to understand anything you’d copy.
Omitting that is a recipe for low quality garbage and not only will the code suffer, but the organization also will while all the staff fall behind any competitors who make the investment.