I'm curious to hear your opinion of SharePoint, if you have one. I'm new to the C# world and I'm pleasantly surprised that it's not as bad as Java like I though

I'm curious to hear your opinion of SharePoint, if you have one. I'm new to the C# world and I'm pleasantly surprised that it's not as bad as Java like I thought it would be, but I've mostly been focused on the language and core libraries. I think I like it for the reason you describe: it's libraries, rather than frameworks. But I've started getting into some ASP.NET code and the frameworkiness is starting to appear. In my case it's entity objects which don't seem to do more than structs, interfaces for classes which talk to the entity objects, implementation classes to implement the interfaces which just copy data from entity objects into their own properties, business objects which talk to the interfaces to get to the entity data, and UI objects/templates that talk to the business objects, probably through another layer of interface/implementation. From what I can tell, SharePoint is another big layer of framework on top of ASP.NET, governing the way your application must be designed and function.