Wikipedia lists all 12 subs as having Rolls Royce Pressured Water Reactors.
Your PWR reuse idea is is kind of where Rolls Royce is looking to go with Small Modular Reactors (https://www.rolls-royce.com/innovation/small-modular-reactors.aspx).
I suspect refurbishing decades old PWR reactors would be far more expensive than just building new ones, for example a SpaceX Merlin engine costs $1 million and a Blue Origin BE-4 costs $15 million. Nasa argued it would be ‘cheaper’ to reuse Shuttle components for the Space Launch System (SLS). Refurbishing Shuttle RS-25 engines has cost Nasa $50 million dollars per engine, restarting a production line is costing $100 million for each new RS-25 engine.
Natural scrolling is the first thing I disable when forced to use a Mac, windows, gnome, kde, xfce, etc… all scroll in one direction.
Macos has a unique keyboard and a lot of unique non obvious and non discoverable behaviour. For example I use a lot of windows laptops, left and right click involve pushing the trackpad downon the left or right. Someone had to show me right click on a Macbook was a two finger touch. These deliberate non standard behaviours make switching devices really annoying.
I would argue KDE defaults should follow the most common behaviour across multiple platforms, with the option to implement specific quirks.
The move to default double click brings the KDE default into alignment with other platforms (single click isn’t the default anywhere else).
I would suggest a bigsur global theme that implements macos keyboard shortcuts, mouse actions, etc… would be a better compromise.
Tesla actually market it as a positive.
Car manufacturers have to setup different manufacturing lines to provide different feature levels. Tesla argue this makes them more expensive. Tesla cars have all features installed, just disabled and the optional extra packages are cheaper compared to their rivals as a result.
To be honest there is a certain logic, if you’ve ever been in a Ford Focus LX (bottom range) its pretty clear they had to spend quite a bit of money on more basic systems. I honestly thought each LX was sold at a loss
Activity Pub has a few parts, Lemmy implements the Threaded message part.
Mastodon implements a short messaging (posts) part. Meta’s Threads will implement this.
KBin implemented both parts, within KBin you’ll see microblog as an option for magazines (communities/subredits). This shows either ‘posts’ made to the magazine or posts with hastags associated with the magazine.
The posts and threaded message parts have overlap in how they work so mastodon users can see certain threaded messages and comment on them.
Reading the article that isn’t the goal.
They are working on controlling access to the wider internet. The goal is to push people off of western services on to ones they control. This is so they can control the information their citizens see
They wouldn’t stop Russian bot farms or hacking.
Engineering is tradeoffs.
A command shell is focused on file operations and starting/stopping applications. So it makes it easy to do those things.
You can use scripting languages (e.g. Node.js/Python) to do everything bash does but they are for general purpose computing and so what and how you perform a task becomes more complicated.
This is why its important to know multiple languages, since each one will make specific tasks easier and a community forms around them as a result.
If I want to mess with the file system/configuration I will use Bash, if I want to build a website I will use Typescript, if I want to train a machine learning model I will use Python, if I am data engineering I will use Java, etc .
You’ve just moved the packaging problem from distributions to app developers.
The reason you have issues is historically app developers weren’t interested in packaging their application so distributions would figure it out.
If app developers want to package deb, rpm, etc… packages it would also solve the problem.
Nice out of date dependencies with those lovely security vulnerabilities!
KBin/Lemmy should provide a combined local view for duplicated magazines/communities across the fediverse. Treating the concept like a hashtag.
The point of the fediverse is to distribute content so no one has a monopoly. People squatting on communities/magazines don’t understand there is nothing stopping people creating one on a hundred other instances.
Each kbin/lemmy instance decides to follow magazines/communities from others through activity pub and stores it locally for the instance.
Having the UI retrieve all local posts with the same magazine/community name (e.g. m/star_trek@kbin.social c/star_trek@lemmy.world). Wouldn’t be hugely difficult, I believe Kbin uses postgres database as the local store and suspect it would be a tweak to the SQL query it runs.
Even if that wasn’t an option, there is a means to get all of the magazines/communities from the kbin UI/lemmy REST API. As well as retrieve all posts for a specific magazine/community. So you could do it entirely in a web client, for KBin it would be more work.
The combined view wouldn’t change how you comment on specific posts. The issue is where do you post and what view would take dominance (e.g. if a magazine had themed itself).
The solution here would be to default your local instance if it exists or the instance providing the most posts/comments. Perhaps with a drop down so users can choose.
I would also configure things so instances can select a site wide default if they can’t moderate it effectively. For example pushing all posts to the star trek instance rather than local magazine with a mod who is MIA.
This would remove most of the concerns users have about the fediverse, since they wouldn’t be confronted by different instances. To them the fediverse is <insert instance> it would also encourage distribution of content.
Its a really immature and niave response from Kev. Information is power, he’s chosen to operate without knowledge for internet points.
Meta think there is potential to enlarge their market and make money, Kev’s response won’t impact their business making decisions.
Kev should have gone to the meeting to understand what Meta are planning. That would help him figure out how to deal with Meta entering the space.
I don’t expect he could shape their approach but knowing they want to do X, Y or Z might make certain features/fixes a priority so it doesn’t impact everyone else
If you signup to social media it will pester you for your email contacts, location and hobbies/interests.
Building a signup wizard to use that information to select a instance would seemto be the best approach.
The contacts would let you know what instance most of your friends are located (e.g. look up email addresses).
Topic specific instance, can provide a hobby/interests selection section.
Lastly the location would let you choose a country specific general instance.
It would help push decentralisation but instead of providing choice your asking questions the user is used to being asked.