Leaky abstraction Puns

This is a post dedicated for discussing this article.

Neural networks as non-leaky mathematical abstraction

Note: I make these threads since I'm yet undecided as to how to approach the comment system on the blog (e.g. emailing people everyone time there's a reply might be annoying, and checking email validity could be hard and could get my domain blacklisted for sending too many unwanated emails).

Until I figure out a way around this, I figured 80% of my readers probably have reddit accounts anyway, so I'll make these comment threads.

I'm learning about Lambda and thinking about whether to base my next full-stack web application on this technology. "Serverless" just seems like such a high-level abstraction that I worry about the Law of Leaky Abstractions coming into play.

Is anyone out there using Lambda finding that they wish they had lower-level control over server-side aspects? Anyone regret using Lambda or had to abandon Lambda due to not enough control or too much server-side "magic" happening?

For anyone not familiar with the term: https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-abstractions/

I have seen this phrase a few times in articles/discussions but no one really elaborates on what is leaky about observables and DOM elements. Can someone please elaborate?

http://jlongster.com/Removing-User-Interface-Complexity,-or-Why-React-is-Awesome

Hello fellow VueJS redditors!

Like the title of this post says... I'm starting to feel like using mapState (or this.$store.state) in place of mapGetters (or this.$store.getters) is a leaky abstraction.

 

By accessing the state tree directly...you are forced to take in to consideration how that data store is structured (aka: your component now has a dependency on the structure of your store). So if you change the stores structure... you will need to find and refactor all components that utilize that state.

The proposed solution would be to always access stuff using a getter... that way if your state structure does change... you only have to update the getters and your components would be none-the-wiser. But the obvious downside to this is it would increase the amount of boiler plate code..... since you would end up with a getter for every state.

 

Does anyone else see this as a problem?

What do you guys typically do? always use state directly and only use getters if there is some extra, repeatable logic in place (like sorting or filtering)? getters for all the the things?

Or do people just not care :-p

I'm writing a new social networking website for all species and not just humans, but my abstractions are leaking all over the place and it's going into the memory pool. I tried adding more pipes | to my OR functions, but it's still not working.