top | item 27803837

(no title)

bndw | 4 years ago

Answering as the author who also understands the fundamentals of all of the technologies involved and questions much of what goes on in the minds of today's web developers and designers--

I use Make as the standard way to interact with every repo I own. This allows me to type `make build` instead of `$some-language-specific-command-I-forget-in-2-weeks`.

I use Docker for distributing every app I build. If the app is a website I also use the nginx base image. Docker images make packaging and distribution a breeze IMO.

Regarding yarn, npx, react, and jest: I'm similarly disillusioned by the churn but I also like to remain knowledgeable as the industry evolves. React was something I hadn't touched before, so I decided to pick a simple project to give it whirl ;)

discuss

order

weejewel|4 years ago

But now you’re paying for keeping a server online, whereas a GitHub page could’ve hosted this static website for free.

cinntaile|4 years ago

He did this for fun, his motivation wasn't to find the cheapest way to host his content.

cyral|4 years ago

React is compiled to static content so this could be hosted with GitHub pages too

moltar|4 years ago

I build static sites in Docker too. But then simply extract the built files out and upload them to any static hosting I need.

This allows me to self contain all the build tooling. And allows other developers to setup a dev environment in a few easy steps.

shepherdjerred|4 years ago

There's no reason that this would have to be hosted on a traditional server.

kortex|4 years ago

> I use Make as the standard way to interact with every repo I own.

After much fussing around with many kinds of solutions, this too is what I have settled on. Download repo and run `make` will "do the needful" to get you going, and all the major entry points are make stanzas.

hootbootscoot|4 years ago

except that "making" anything, or any commands in a new language he forgot, etc = entirely unnecessary for a single static html page.

manuel_w|4 years ago

> I use Make as the standard way to interact with every repo I own. This allows me to type `make build` instead of `$some-language-specific-command-I-forget-in-2-weeks`.

I also used to do this until I switched out Make by Just[1]. I find it worth a recommendation.

https://github.com/casey/just

sneak|4 years ago

Just like perl and grep, I stick to make because it's likely to be already available everywhere I need it. Such is the tyranny of the installed base. :/

catlifeonmars|4 years ago

I second this. “just” is like make, but without the extraneous/confusing parts.

lionkor|4 years ago

make all and make run would be more standard, no?

superjan|4 years ago

I liked your page. I might even use it!