I think it's a mistake that we've become so attached to the module = file detail, and thus small modules = small files.
-
-
Replying to @jlongster
Of course I encourage small functions. I don't care if they are all grouped into one big file or not.
4 replies 0 retweets 13 likes -
Replying to @jlongster
Unfortunately though all the tooling reinforces that modules = files. I've been enjoying in ReasonML that that boundary doesn't exist.
7 replies 0 retweets 14 likes -
Replying to @jlongster
Separate files continue (for me) to be a side effect of our effort nav/editing long files. (Aka the tools showing through)
1 reply 0 retweets 2 likes -
Replying to @KirbySaysHi @jlongster
In your view, it would be fine if a project was all in a single file?
2 replies 0 retweets 1 like -
And if the solution is a nav hierarchy that maps onto a "long file full of modules" how is that meaningfully different from files?
2 replies 0 retweets 2 likes -
Replying to @wycats @KirbySaysHi
There's obviously a happen medium, so no. I'm mainly responding to when people say "tiny modules enables a good architecture that blah blah"
2 replies 0 retweets 5 likes -
Replying to @jlongster @KirbySaysHi
People usually mean "packages", which is also a thing that people forget to think about.
3 replies 0 retweets 1 like -
Replying to @wycats @KirbySaysHi
on a side note, I had a hunch (and was hoping) you'd reply ;) Don't know why!
1 reply 0 retweets 0 likes
Mention tiny modules and I will appear.
-
-
Tiny modules?!? I'm working an example project which tries to strike balance of # funcs/file. All exportable fns.https://github.com/justsml/escape-from-callback-mountain …
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.