I strongly disagree. If you double-click on a CSV, excel usually opens it in your local code page instead of UTF-8, but they got rid of/hid very well the old text import function so now it fires up PowerQuery when you import a CSV instead. PowerQuery is OK but it doesn't like irregular data. It also saves the query connection automatically. If you massage the data in PQ before you import, it's unlikely that someone who comes after you will know what to do with the query you made. They don't make it easy to can the query to use in the future with similar files. Actually, they make it pretty difficult.

LibreOffice Calc just gives you an import window with some pretty good defaults, like UTF-8. It could be better, but at least it is not worse.

Excel added useful array functions. Good luck finding anyone who can handle that.

Tables in Excel are not really first class citizens. They move differently than everything around them but they don't have an obvious interface for working with them from other parts of the spreadsheet. Within a table you can refer to rows by name, but not outside, really. If you click on a pivot table for a reference, it gives you a GETPIVOTDATA function, when you might have actually wanted E3 or whatever.

And don't get me started on "dates", "numbers", "text", etc., excels weakly strict datatypes.