kierenj

12 ms·

121.
by kierenj 10y ago
I see what the feature is, but I don't see the use case or benefit - in this particular case! The social, payment, consumer storage, I definitely do. But it feels a little like the age-old example of abstracting away your database la
122.
by kierenj 10y ago
It's a nice feature-set, looks well-designed, and handy - but anyone using one of these APIs would find it super trivial to implement this themselves? I'm not sure I see the cost-benefit making sense here? I'm keen to be co
123.
by kierenj 10y ago
Sounds intuitive to me - trigger all pain receptors in the animal, or cut off the ability to feel pain, which is more painful?
124.
by kierenj 10y ago
I respectfully disagree. You don't need constructors and certainly not destructors (really not sure what you mean by this in the context of React, can you elaborate) and these are not really the main OO concepts. Polymorphism, inheri
125.
by kierenj 10y ago
If you read the article, you'll see many of the things you refer to aren't applicable
126.
by kierenj 10y ago
Indeed, there's really nothing about how the app went from $20k/day to $2/day, which is precisely what the title promises.
127.
by kierenj 10y ago
I've been spending some time putting together a framework for .NET Core API/platform development. The main problem with it currently is the lack of compatible libraries - I've had issues with DI containers, cloud provider li
128.
by kierenj 10y ago
Not quite (I think): .NET Standard is an API definition, or rather a versioned set of them. ".NET Framework" (e.g 4.5) "implements" that definition, with some extra features to boot. ".NET Core" also implemen