I would say that a Lotus "View" is an analogous to a SharePoint List View. In that they both define which "columns" to display and sort/grouping/filtering etc.
I would add SharePoint "List" as a feature that Lotus is sorely missing. I would describe a SharePoint List as an "in-site database". They are actually very simple in concept, very simple to create and manage and so ultimately very powerful for the business. You could argue that a SP List is like a Lotus Form - and it's difficult to argue against that, however the main difference being that you create your list in the browser and all the ease of use that goes with them.
Another feature worth mentioning are the Web Services. SP is built on services and they are all pretty much available to developers - and excitingly available for "in client" development.
I would say that a Lotus "View" is an analogous to a SharePoint List View. In that they both define which "columns" to display and sort/grouping/filtering etc.
I would add SharePoint "List" as a feature that Lotus is sorely missing. I would describe a SharePoint List as an "in-site database". They are actually very simple in concept, very simple to create and manage and so ultimately very powerful for the business. You could argue that a SP List is like a Lotus Form - and it's difficult to argue against that, however the main difference being that you create your list in the browser and all the ease of use that goes with them.
Another feature worth mentioning are the Web Services. SP is built on services and they are all pretty much available to developers - and excitingly available for "in client" development.