[petey283]

> Most open source C++ projects are libraries that are meant to be integrated into other applications. Plywood is the opposite of that: It gives you a workspace into which source code and libraries can be integrated. A single Plywood workspace can contain several applications – a webserver, a game engine, a command-line tool. Plywood simplifies the task of building and sharing code between them.

I think this works as a good overview.

[badsectoracula]

Well, that is implied by the title: "Plywood: A New [...] Framework". Frameworks are by definition about providing the core elements to build your stuff on top of them[0].

[0] https://en.wikipedia.org/wiki/Software_framework

[craftinator]

It has been my experience that most software posted on HN has little description of what it does, and no description of why it exists. The parent comment was highlighting the excellently concise mission statement written on the first page. I wish every project would do as well.

[arzel]

Agreed. It seems that people love to just throw around “library” “language” and “framework” now, but not know the differences.

[wtracy]

The word "framework" by itself provides no indication of how specialized the tool is, or what problem(s) it aims to solve.

The above description indicates that it is a very general-purpose framework (handling things as disparate as game engines and web servers) and that it aims to enable code reuse, not just eliminate boilerplate code.

[badsectoracula]

Eh, no, that description doesn't do that, a better description is what is above it because it actually mentions what it does and provides. The part quoted in the message i replied is largely implied by the word "framework". Of course it isn't a bad thing to be explicit (especially since some people may think that framework is just another word for library), however it isn't any clear about what the framework does.

For example think of MFC: you know what that framework is all about (Windows GUI applications), yet the description could easily fit with MFC (and indeed all of the above have been implemented on top of it).

[ngold]

So unreal engine, blender and visual studio? All talking to each other?

[e12e]

Actually, you could probably argue that Blender already is these four things (a framework, blender, unreal engine and visual studio (the latter two as part of the game engine(defunct) and editor for example)).

[m0zg]

So basically sort of like a monorepo.