dblotsky
dblotsky on Hacker News
Hard agree with the idea of greppability, but hard disagree about keeping names the same across boundaries.
I think the benefit of having one symbol exist in only one domain (e.g. “user_request” only showing up in the database-handling code, where it’s used 3 times, and not in the UI code, where it might’ve been used 30 times) reduces more cognitive load than is added by searching for 2 symbols instead of 1 common one.
Those all sound plausible! But...
1) I suspect GNU Make will be installed on any system where node code will run.
2) You don’t have to .PHONY anything that will never be a real file.
3) My bet is the Makefile will be shorter and clearer, but I am of course biased since I’m used to the syntax.
Is there any design decision of Make that makes it not suitable for executing programs?
The `./make` shell script kills me. Why not just use Make?
Yeah, that tradeoff between generality and correctness really seems tyrannical.
It kind of feels like the best trajectory is to start small with a general build system, and upgrade as needed? And then if you are confident the project will grow, starting with the specific build system fine too.
I am personally not convinced that any build system can be correct and general, but perhaps that’s my lack of experience speaking.
On that 30 minute note though: so, how big does the project need to be in order for Make not to be enough? And at that size, why wouldn’t the project invest the extra week it takes to get the Makefile correct?
How big does the project have to be in order for this system to have benefits over Make?
It sounds like the last point, about disobeying the rules when appropriate (my reading of it), was meant exactly to cover these corner cases.
Can this all be explained by the cost of labor being uniform (since humans are humans in all industries)?
So if one industry demands more labor, all others will feel the rising price of labor?
They inserted spaces though, between characters and words. In this problem, all spaces are removed.
You’re missing the huge “works incorrectly” space of outputs.
Facetious answer: Are there any good examples of projects using Parcel for a web app? ;)
Real answer: probably, but a ton of production code is closed-source.
But why restrict to web apps? Most influential software projects in the world use Make.
Make can run all the tools like babel, uglify, etc.
Just use Make.
Takes just as long to learn, and is transferrable everywhere.
He’s called for some disciplines (e.g. women’s studies, anthropology) to be boycotted by students and ultimately removed.
I find objectionable his “slippery slope” argument about pronouns and his calls for silencing disciplines with which he disagrees.
Peterson said many other things that are objectionable. If he only said what Zhukov said, Peterson would also be in a more favourable light.
The one I often go for is: “What is the reason you’re not using sshd?”
It implies that I understand there is a reason, that I don’t know the reason, and that I’m ready to be surprised if indeed there is no good reason.
1). It doesn’t work in all shells, so you have to think about your environment before you use it.
2). I often start with `bar < foo`, so if I need to add more arguments to `bar`, I need to always skip over the input.
3). If I just want to delete all processing and look at the input, I can’t just backspace away the processing because `< foo` is invalid.
How vast are the differences in expenses needed to live (due to climate or otherwise)?
The title says “GDP Per Capita, PPP”.
China is investing in Belarus. They build factories and infrastructure, likely to get easier access to the European markets.
The “PPP” in the graph is easy to miss, but is what makes the comparisons possible.
What makes it useless? It’s functionally the same but makes it easier to author pipelines, which I think is a valid use.
We often forget, but even the world’s top professionals get tired, cut corners, and make mistakes.
But also, what substantial gains would have come from adopting the techniques in this article?
In this case, I mean the POSIX standard. But yes, shipping by default in operating systems is how things (eventually) make it into the standard!
You’re right, and I’m not at all against having custom tools in any controlled environment. In fact, I think enhancing a controlled environment with custom tools is extremely productive.
My point was more about education. I think becoming an expert in the standard tools should come before learning any custom ones, because it is a transferable skill.