Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My Blog Engine Is the Erlang Build Tool

ferd.ca

Post reply on HN
Print view View original

11–16 of 16 posts

Re: My Blog Engine Is the Erlang Build Tool

#11

Post by jolmg »

toast0 wrote: post #10
jolmg wrote: post #9

Earlier quoted context omitted.

Not familiar with Erlang, but from reading I imagine that rebar3 understands those `{% extends ... %}`, and uses them to determine what needs to be updated. With a Makefile, you'd express those dependencies in the Makefile rather than each file. Although, one can probably write a Makefile such that it loops through each file, greps or otherwise obtains the `extends` and generates the Makefile rules that way.

> Although, one can probably write a Makefile such that it loops through each file, greps or otherwise obtains the `extends` and generates the Makefile rules that way. You can do it with grep and what nots, but it gets icky fast. Much better is to have the compilers output dependency information while they're compiling, and use that. The compilers have to know the actual dependencies, because they're opening them, an…

> have the compilers output dependency information while they're compiling, and use that.

It'd be moot after they've been compiled. You're saying compile to get the information to decide if you should compile.

Re: My Blog Engine Is the Erlang Build Tool

#12

Post by toast0 »

jolmg wrote: post #11
toast0 wrote: post #10

Earlier quoted context omitted.

> Although, one can probably write a Makefile such that it loops through each file, greps or otherwise obtains the `extends` and generates the Makefile rules that way. You can do it with grep and what nots, but it gets icky fast. Much better is to have the compilers output dependency information while they're compiling, and use that. The compilers have to know the actual dependencies, because they're opening them, an…

> have the compilers output dependency information while they're compiling, and use that. It'd be moot after they've been compiled. You're saying compile to get the information to decide if you should compile.

The information is for the next invocation.

If you compiled it and it used these files and none of those changed, you don't need to compile it again.

When you add a new file, it clearly doesn't have an output file, so it needs to be compiled. Where it gets a little less clear is when you've got something that depends on all the input files --- if you just use the compiler's dependencies, when you add a new input file, Make (or whatever) wouldn't care, because last time it compiled (or linked), that file wasn't used, because it didn't exist.

So you still need some rules that are based on directory scans, if that's how you want to roll.

Re: My Blog Engine Is the Erlang Build Tool

#13

Post by lkuty »

paradox460 wrote: post #4

It's very impressive how expressive and flexible the compilers in the BEAMverse are. Elixir extends this rather far, and there are whole utilities such as Surface[1] that are built atop and make heavy use of custom compilers For more germane blogging and ssg in elixir/beam, I use and recommend the excellent tableau generator[2], by Mitch Hanberg. I use it to power my own personal site[3], and publish the source[4] fo…

Thanks for sharing. I think I will use it for my blog. I wanted to create a programming blog for a long time and focused on Hugo to build the static site but I could not decide myself since the doc is not good enough IMO and thus I didn't feel comfortable enough to start it. And I want something minimal. Now using Elixir seems like a good idea since it has already been my main programming language for the last few years.

Re: My Blog Engine Is the Erlang Build Tool

#14

Post by paradox460 »

lkuty wrote: post #13
paradox460 wrote: post #4

It's very impressive how expressive and flexible the compilers in the BEAMverse are. Elixir extends this rather far, and there are whole utilities such as Surface[1] that are built atop and make heavy use of custom compilers For more germane blogging and ssg in elixir/beam, I use and recommend the excellent tableau generator[2], by Mitch Hanberg. I use it to power my own personal site[3], and publish the source[4] fo…

Thanks for sharing. I think I will use it for my blog. I wanted to create a programming blog for a long time and focused on Hugo to build the static site but I could not decide myself since the doc is not good enough IMO and thus I didn't feel comfortable enough to start it. And I want something minimal. Now using Elixir seems like a good idea since it has already been my main programming language for the last few ye…

Tableau is pretty good. It has a couple of rough edges, but nothing too bad, and can be easily extended or overridden where needed to do what you need to do
Post reply on HN