Salesforce CEO Marc Benioff and co-CEO Bret Taylor announced plans for a non-fungible token (NFT) cloud service according to this CNBC article, but no official word from Salesforce.

Why?
One source told CNBC that Salesforce wants to develop a product similar to the OpenSea NFT marketplace. Tools that allow you to manage transactions in the NFT collection itself can reduce the need to use OpenSea.
(Reference)

Reactions
When people knew about Salesforce's new plans, they weren't very happy about it. In fact, over 400 employees have signed an open letter, protesting the announcement. Some employees even said that they will quit Salesforce if this actually happened.
The main reason is the fact that cryptocurrencies require large amounts of energy to maintain a decentralized platform. Researchers estimate that a single NFT emits more than 200 kilograms of carbon dioxide. This is equivalent to driving 500 miles on a petrol car.
(Reference)

Here is a video showing how bad is cryptocurrencies to our environment.

As Salesforce developers, we sometimes prefer to build flows rather than write code since flows are easier to deploy and maintain. However, sometimes you will have to write apex classes or triggers to get your work done. So, here is an important consideration while building a flow: a flow can execute only up to 2,000 components. This means that the maximum number of nodes that a flow can pass through in a single context is 2,000. You might think this is a big number, but, unfortunately, you will sometimes need more!

Imagine you have a bunch of records to iterate on and run some logic for each of them. For a collection of 500 records, you can have at most four components in each iteration. Thus, you have to call an apex class to do logic with mass data.