42e6e8c8-f7b8-4

I like hand saws and I like circular saws/Skil-saws. I use them for different things.

People talk about services like libraries aren't a thing. That exact same statement with `s/services/libraries/`.

"Write small, well tested libraries..."

If you have a library with a solid, small public interface and you carefully maintain compatibility on that interface with great testing, you can be decoupled. Plus you don't have 2 network interfaces and the internet injected into a call to the interface.

Every flask REST implementation I've seen has been a bespoke library combinatorics mess compared to something that could have been written in Django REST framework.

I think that says more about the maintainers than libraries vs framework. Some maintainers value backwards compatibility and some don't. Some value the time of their users more than the purity of their platform/framework. React as a framework seems to value it's users -- upgrading isn't that hard. Angular 1 to 2 didn't. Microsoft and x86 worship backward compatibility -- 30 year old programs frequently run without a hitch on the PC platform, thus showing that they value backward compatibility. Anything written against a Google sdk or api or platform will need to be reworked every 2-3 years or the app will break.

Once you go to the grocery store and pick the 25 different libraries fundamental to your application, congratulations! You've created a completely new interaction between those sets of libraries and you get to debug those interactions instead of your own code for a portion of your time.

I've seen this with python flask REST environments where folks pull all these tiny pieces off the shelf and stitch them together. Meanwhile Django REST Framework has a mostly common baseline that you adopt and then diverge from as needed.

Seems like an opportunity to teach that it is folly to "Keep up with the Jones."

Wait till they hear that they can make purchases in other areas to "Keep up with the Jones" - fancy cars and McMansions. By then they will be fully enslaved to debt, but boy will they have that glorious glorious status.

So hilarious. My car probably does too. And my other frugal behaviors. Guess I'll keep buying assets instead of liabilities.

Freudian slip.

It may be the end of Twitter if google or apple don't like him -- they may delist twitter.

To paraphrase Mao, "Let 2, only 2, and exactly 2 flowers bloom."

Clearly I'm trading low quality/cheaper for more time in sauna, since it does take more time to heat you up. I put a towel around the neck hole to accumulate heat, but I'm dripping with sweat in 25 minutes. I may not be Finnish, but the model I'm using really does get me going.

What you're describing is obligations under GPL'd code, not LGPL'd code. Qt is mostly LGPL'd code.

Not at all hypocritical. The people who authored the code release most of it under LGPL, the intention of which is to allow closed-source dynamic linking against the LGPL'd library. I didn't decide this. The users didn't decide this. The people who actually wrote the code decided this.

Or... comply with the LGPL with regard to dynamic linking and the other LGPL requirements and don't use any GPL'd components.