John

@mbtrhcs @spartanatreyu well Java Streams try to, but it’s not too hard to get them to accidentally process too much, or even blow up completely.

(This isn’t a comment on coding styles or the article though)

@expr this is from 10 years ago https://youtu.be/7Zlp9rKHGD4

@dandi8 @JackbyDev Most of the criticism in the article talks about side-effects using a far stricter (and imo more useful) definition than Martin did.

I tend to agree, and would avoid both side-effects and writing code like Martin. However this book targets the mainstream, and afaik the mainstream hasn’t yet accepted the new definition of side-effect.

Martin has since embraced FP more than the mainstream. So he’s somehow both ahead of and behind the curve.

@agressivelyPassive if you routinely call indirections abstractions, then ‘premature abstraction is the root of all evil’ holds. If you separate the two concepts, you might think differently.

If my team’s codebase had a business logic class that had a concrete dependency on an EntityBuilderFactory, I’d vomit a little, but I wouldn’t delete it (can’t piss off too many people all the time). But I would route around the damage by allowing the class to depend on the EBF *or* something else.

@agressivelyPassive moving from ‘storing a user in postgres’ to ‘storing anything in postgres’ is a step up in abstraction. Same with moving to ‘storing a user somewhere’ or moving to ‘storing anything anywhere’.

Moving from ‘storing an entity’ to ‘storing an entity via a FacadeBuilderFactory’ is not a step up in abstraction, it’s only an extra indirection.

@arendjr

1. abstraction != indirection. Abstraction allows you to do a deferred architecture: store this user “somehow”. Indirection is just early architecture with more steps: MyUserDatabase class is coupled to one way of doing things - it’s concrete, not abstract.

2. yet another article advocating ‘pure functional’ flavour, not a pure functional PL. Recommending purity in an impure language is like recommending memory safety in C. All the work is on the programmer.

@vitonsky this link is political. Do not click it! (You know, for security reasons)

@atzanteol @kogasa bullshit

@DmMacniel @vzq

> Given the nature of JS running only on a single thread.

No no, I think you found the language flaw.

@armchair_progamer

Awful naming. Forgetting the fortune 500 company you’re already thinking of, there’s already a Meta Lang, abbreviated to ML.

Besides that, does it have any ‘meta’ features? E.g. Homoiconicity?

@Windex007
> You as the writer, you don’t know either?
Not until the compiler tells me.

> Or is the argument that nobody but the compiler and god need know? That having an awareness of the types has no value?
No, I want to know, because knowing the types has value. If the compiler has inference, it can tell me, if not, it can’t.

@Windex007

lexer :: Parser LexState (Vector Int, Vector Token)
lexer = do
(positions, tokens) <- _ nextPositionedToken
…

What goes where the underscore is in the above snippet?

@Windex007 @snowe

Yes. Type-inference typically *knows better than me* what the types should be.

I frequently ask the compiler what code I need to write next by leaving a gap in my implementation and letting the compiler spit out the type of the missing section.