3 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

In my post on when it is appropriate to reinvent the wheelmy post on when it is appropriate to reinvent the wheel I list a number of advantages of a reimplementation. I think those advantages apply especially for framework libraries. For example, it is often impossible to isolate the use of a framework library inside a small part of you application. Instead, they tend to dictate the structure of the client source code, and therefore it is desirable to have full control over the library.

In my post on when it is appropriate to reinvent the wheel I list a number of advantages of a reimplementation. I think those advantages apply especially for framework libraries. For example, it is often impossible to isolate the use of a framework library inside a small part of you application. Instead, they tend to dictate the structure of the client source code, and therefore it is desirable to have full control over the library.

In my post on when it is appropriate to reinvent the wheel I list a number of advantages of a reimplementation. I think those advantages apply especially for framework libraries. For example, it is often impossible to isolate the use of a framework library inside a small part of you application. Instead, they tend to dictate the structure of the client source code, and therefore it is desirable to have full control over the library.

2 replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
source | link

In my post on when it is appropriate to reinvent the wheel I list a number of advantages of a reimplementation. I think those advantages apply especially for framework libraries. For example, it is often impossible to isolate the use of a framework library inside a small part of you application. Instead, they tend to dictate the structure of the client source code, and therefore it is desirable to have full controlfull control over the library.

In my post on when it is appropriate to reinvent the wheel I list a number of advantages of a reimplementation. I think those advantages apply especially for framework libraries. For example, it is often impossible to isolate the use of a framework library inside a small part of you application. Instead, they tend to dictate the structure of the client source code, and therefore it is desirable to have full control over the library.

In my post on when it is appropriate to reinvent the wheel I list a number of advantages of a reimplementation. I think those advantages apply especially for framework libraries. For example, it is often impossible to isolate the use of a framework library inside a small part of you application. Instead, they tend to dictate the structure of the client source code, and therefore it is desirable to have full control over the library.

1
source | link

In my post on when it is appropriate to reinvent the wheel I list a number of advantages of a reimplementation. I think those advantages apply especially for framework libraries. For example, it is often impossible to isolate the use of a framework library inside a small part of you application. Instead, they tend to dictate the structure of the client source code, and therefore it is desirable to have full control over the library.