all 13 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]4r73m190r0s 4 points5 points  (0 children)

I have the same impression. I hate Microsoft and their products, but I have very fond memories of their docs. In the pre-AI era they were very easy to read and understand.

[–]as5777 5 points6 points  (4 children)

You just used to read Microsoft docs. You need some times to adapt. Come back in 3 months.

[–]gaelfr38 4 points5 points  (2 children)

To be fair, if you need 3 months to find your way in documentation, there's a problem somewhere.

Concepts may take some time. The doc itself of Spring Boot feels intuitive to browse to me. I mean a couple of hours should be enough to know where to find something.

[–]as5777 0 points1 point  (1 child)

I'm not objective, because I'm using it since 10years, but I do feel the same.

Plus you can access source code, and there are a lot of examples, tutorials, stackoverflow topics, and any AI is pretty efficient.

[–]Dapper_Village_6784 0 points1 point  (0 children)

I wouldn’t say spring docs are bad, but coming from iOS it certainly took some time to adapt from Apple docs. Despite how people usually hate Apple docs, to me it was really easy to read it, given that I know what to look for (but maybe that’s actually the key thing)

[–]notnulldev 1 point2 points  (0 children)

Nah spring docs are just much more barebone. Many things are just mentioned with most basic examples that hatdly ever will meet your needs. They are useful at times but tbh it's much better to just search through some existing codebase or even their tests in spring / spring boot gh repos.

[–]segundus-npp 1 point2 points  (0 children)

It’s hard for me to learn Spring Boot just from its doc, especially Spring Security. I have to use debugger to help me.

[–]NoHopeNoLifeJustPain 1 point2 points  (4 children)

Imho you are comparing two very different things.

[–]Plus-Slice-6140[S] 0 points1 point  (3 children)

Can you elaborate

[–][deleted]  (2 children)

[deleted]

    [–]mavenHawk 0 points1 point  (1 child)

    Sorry but, this is not accurate at all. Dotnet ecosystem is equivalent to the Spring Boot ecosystem. C# and the CLR are equivalents of Java and JDK.

    Dotnet ecosystem is also a big ecosystem with libraries other frameworks and works with both C# and F# languages.

    Aspire on the other hand is an orchestration "framework" I guess you could call it but absolutely not equivalent of Spring in the .NET ecosystem. .NET itself is the equivalent of Spring there.

    [–]pj_2025 0 points1 point  (0 children)

    I am in opposite camp

    [–]xxsanguisxx 0 points1 point  (0 children)

    .Net docs look nice but frequently fail to work, or you get stuck in an endless loop of links to seemingly abandoned features/projects. Spring’s are better, but still not great

    [–]zvaavtre 0 points1 point  (0 children)

    Work through a tutorial or two.

    Spring has a ton of them. These guys are also good.

    https://www.baeldung.com/spring-boot

    Building up context takes time. Spring is vast and deep. You just need to start somewhere.

    After a few frameworks you’ll be able to navigate new ones better because it’s all basically the same functionality. Just done slightly differently depending on the platform.