There aren't many OLED manufacturers making screens bigger than phones, and yields are usually lower than LCD panels. Perhaps in 10 years the display landscape will change enough to make OLED more widely used.
I think there are not that many tech manufacturers in general.. camera sensors, computer chips, lithium battery… can all be traced back to a handful of manufacturers
With continual investment on newer tech and political will I think it’s possible the drastically increase output.
After some discussion within the admin team, i think we'll have a wait and see approach in this since we're a small instance and any problem have a chance of driving newcomer away. Besides, we don't actually in critical need of the database optimisation in this new update, but the potential issue that might popup mean it will be a pita to keep track. Since World commited to the update we'll see if there's any real big issue coming up(like that security breach stuff after updated to 0.18 lol) before commit to the update.
there will be at least 5-10 minutes of downtime for db migrations though (more if the db size is huge). of course, after the long migrations the db size is reported to shrink significantly.
anyway, there's already been at least 2 easily triggered/discoverable bugs:
view context for comments does not work properly (i heard it may even crash jerboa)
all software versions in the instances list are displayed as 2.0
hopefully they will release a 0.18.4 quickly with fixes for that.
monyet already has a dev instance, so they can import the db from the main instance there, and do the db migrations to see if that'll succeed.
precautionary measures can be taken on the dev instance so it doesn't attempt to federate with all the data from here.
i can think of (for testing out db migrations on the dev instance):
run lemmy_server with the --disable-scheduled-tasks cli flag, which will prevent background federation tasks from running (so federation events will only be triggered by actual interaction, like posting, voting, subscribing, and of course such things should not be done on the dev instance)
if that's still not enough and we want to be extra sure the dev instance doesn't federate with data from over here, then just block outgoing http/https connections at the firewall while doing the db migrations try-out (also don't run lemmy-ui and just watch the docker logs for it to say migrations completed successfully)
i think the lemmy.zip admins said they're still trying to work out a way to spin a dev instance on a dedicated server, but monyet already has a dev instance, so the db migrations can be tried first to ensure safety.