I interpreted the comment a bit more generously.
I interpreted the comment a bit more generously. The admonition wasn't to avoid using higher level tools, but not to try editing the low level output of a high level tool. I prefer writing in C to writing in assembler, but I would never want to modify the assembler produced by a compiler. Similarly, I prefer scheme to C, but I would prefer handwritten C to editing the output of the Chicken-to-C compiler. That comes back to the complaint about the auto-build tools. Using the tools, by themselves, is perfectly reasonable. On the other hand, writing Makefiles by hand isn't particularly onerous. What is frustrating, however, is when I'm expected to edit a Makefile that was generated by a tool without having access to the script that generated said Makefile.
Posted by rprospero on Apr 10, 2015, 5:09 PM
Tags
Related issues
- I wish there was a link to the repo included on the website.
- > but I wish there was a middle ground between it and VK There's WebGPU (probably the best option for teaching), D3D11 and Metal.
- Decent article.
- I understand and previously agreed with Mozilla's hard line privacy and security stance.
- ☂️ Reinforcement: Add more basic components to the core framework
- Adding templating to more notification providers
Raise real-world problems, find people facing the same issue, and discuss solutions.7,000 issues0 comments
complaint (Software)
I wish there was a link to the repo included on the website.
> but I wish there was a middle ground between it and VK There's WebGPU (probably the best option for teaching), D3D11 and Metal.
Decent article.
I understand and previously agreed with Mozilla's hard line privacy and security stance.
☂️ Reinforcement: Add more basic components to the core framework
Adding templating to more notification providers
Code Push / Hot Update / out of band updates
My first programs were written in FORTRAN II.
I interpreted the comment a bit more generously.
I interpreted the comment a bit more generously. The admonition wasn't to avoid using higher level tools, but not to try editing the low level output of a high level tool. I prefer writing in C to writing in assembler, but I would never want to modify the assembler produced by a compiler. Similarly, I prefer scheme to C, but I would prefer handwritten C to editing the output of the Chicken-to-C compiler. That comes back to the complaint about the auto-build tools. Using the tools, by themselves, is perfectly reasonable. On the other hand, writing Makefiles by hand isn't particularly onerous. What is frustrating, however, is when I'm expected to edit a Makefile that was generated by a tool without having access to the script that generated said Makefile.
Comments (0)
No comments yet. Start the discussion.