3 ms·
> I still feel like this way of thinking can work only up to a certain point. Don't you need to get to a more precise problem definition at a lower, more techni
by karmakaze 6y ago
> I still feel like this way of thinking can work only up to a certain point. Don't you need to get to a more precise problem definition at a lower, more technical level?
> Not really, no. When you're solving a problem, even as you get to a more technical level, you always keep in mind why you are solving it.
I have mixed feelings about this. On the one hand this pretty much describes many applications built with a lisp. Everything is built to solve the original problem. Every construct made ad-hoc only handling the cases that are relevant, even making up effect partial languages suitable for the subject at hand.
On the other hand, we don't end up with globally shared libraries that have 'completely' solved a particular technical problem space. We actually lose the 'science' of computer science and everyone is an application developer.
Based on the popularity and effectiveness of libraries and ecosystems, I'd say our universe is winning. I do however enjoy quickly making partial implementations that perfectly satisfy an application's needs up and running quickly. Sometimes the complete solution would be unapproachable but the needed one clean and simple.
Perl is an exception--it has a vast ecosystem of partial implementations.
- MereInterest 6y agoWhile that's a good point, I think that many libraries still have the overall design goal baked into them. These aren't independent libraries that solve an abstract problem somewhere out in the aether, but rather libraries that are intended to fit into specific designs. Consider a serialization library, for reading and writing objects from memory. This library could aim to have a minimal memory footprint, and may fit into the design of an embedded device. This library could aim to have maximal throughput, and would best fit into the design of a server application. This library might aim for usability by new users, and handle its own memory allocation for the serialized object. But, that would imply serializing the entire object at once, rather than streaming it to disk or to a network socket, so that impacts what designs can use it. Libraries tend to be implemented such that they fit neatly into some original design. Figure out what that original design is, and that gives you a better sense for how it will fit into the design you're making.
- wrnr 6y agoIt can go the other way, like I started of creating a POC of a 3D app with three.js and then simplified the code by just creating my own typed array that is send to the gpu. There are many software designers, they are just not famous because no one would understand what they do.
- meheleventyone 6y ago> On the other hand, we don't end up with globally shared libraries that have 'completely' solved a particular technical problem space. IME the more general a library tries to be usually the worse it is to actually use. Opinionated AKA designed libraries that have some specific intention behind them are more immediately usable and it's much more straightforward to see the pitfalls in using them as they tend to typically be intentional.
- jrochkind1 6y agooh yes so much this. and yet, the most popular libraries tend to be very general, and libraries that are popular tend to try to get more and more general. What's this about? Why are we chasing a different direction than the quality that comes from focused, opionated libraries?
- wpietri 6y agoHuh. I don't see much of a contradiction here. Even the most design-y of software designers isn't going to be picking out artisanally selected sand grains for inventing a new kind of silicon-based processor. At some point you say, "Well, these generic components are good enough, let's use 'em." That choice of components still requires keeping the purpose and context in mind, of course. But if I want to get anything done for the user, at some point I hit bottom and return my attention to getting something done and out there.