-
Notifications
You must be signed in to change notification settings - Fork 16
Article on Mechanical Process Section Three from Hegel's Logic
#165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Mechanical Process Section Three from Hegel's Logic
content/hegel/reference/mechanical-process/the-formal-mechanical-process/section-three.mdx
Outdated
Show resolved
Hide resolved
content/hegel/reference/mechanical-process/the-formal-mechanical-process/section-three.mdx
Outdated
Show resolved
Hide resolved
| The previous section concluded the moments of `action` and `reaction` with the | ||
| moment of `rest`. Undoubtedly, another nod to Newton's laws of motions, though | ||
| this time to the first law of motion. What exactly the connection is between | ||
| Newton and Hegel in the development of the `formal mechanical process` is a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence isn't really informative. Consider dropping
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what do you mean by "dropping?"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deleting, removing.
content/hegel/reference/mechanical-process/the-formal-mechanical-process/section-three.mdx
Show resolved
Hide resolved
content/hegel/reference/mechanical-process/the-formal-mechanical-process/section-three.mdx
Outdated
Show resolved
Hide resolved
| determinations of the `Concept`. This positing also brings the | ||
| `mechanical object` into the sphere of necessity, and out of the contingency of | ||
| the opening of `Mechanism`. Suffice it to say, that Hegel sees the | ||
| `product of the formal mechanical process` as heralding the moment of necessity |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
product of the formal mechanical process all in backtics seems a bit much. Do you mean that there is explicitly a category of that name or did you refer to a section of the text? Perhaps it's better to just put product in backtics - seems like that should be a category at this point?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that the full title would be the proper name of the category - there will also be a product of the real mechanical process.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about designing shorthands like formal product and real product? These come a bit more naturally and are less verbose.
| `mechanical object` into the sphere of necessity, and out of the contingency of | ||
| the opening of `Mechanism`. Suffice it to say, that Hegel sees the | ||
| `product of the formal mechanical process` as heralding the moment of necessity | ||
| into `Mechanism`, and that the basic conceptual reason for this is connected to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove backtics from Mechanism or de-capitalize it. Currently, it's ambiguous as to whether you're referring to the body of text called Mechanism or the category mechanism
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is my thinking: capitalising it refers to the chapter, and the backtics are helpful for when people want to search for it.
But as I say this, people shouldn't have a hard time finding it because it is an article inside Mechanism.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
backtics are helpful for when people want to search for it.
Search for it how? Manually with their eyes or searching in text with the browser? The website has a search mechanism built in, so you needn't worry about things on that end.
The backtics are there to convey meaning: "here I refer to a category or concept in its technical sense".
Your usage here is ambiguous - are you referring to the piece of text or the category? It cannot be both.
content/hegel/reference/mechanical-process/the-formal-mechanical-process/section-three.mdx
Show resolved
Hide resolved
| themselves. This reflection into itself makes the objects in the mechanical | ||
| process more determined. | ||
|
|
||
| The establishment of the `product of the mechanical process` is the hinge-point |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comment above about product of the mechanical process
| for the transition into the `real mechanical process`. The objects within the | ||
| mechanical process now stand in a more determinate relationship to each other. | ||
| That means a few things: One, it means that they are no longer immediately | ||
| identical. At the beginning of `Mechanism`, there was no difference between the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comment above about Mechanism
content/hegel/reference/mechanical-process/the-formal-mechanical-process/section-three.mdx
Outdated
Show resolved
Hide resolved
content/hegel/reference/mechanical-process/the-formal-mechanical-process/section-three.mdx
Show resolved
Hide resolved
Firgrep
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good but a bit on the short side. Some final thoughts.
- Given it's so short, why even split the sections into different articles (files)? What do you think about merging it into one formal mechanical process article?
- There are no citations from the text in this one. I think we should have at the very least one or two to back up your statements.
- So far in your writing there has been no engagement with secondary literature. Including some of that would help unpack both the basics and the nuances at work here. Where is Ross!?
Updated some things as per Filip's comments
ridetoruin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as always, gold standard feedback.
Guidelines and Checklists (click to expand)
📝 Guidelines for Philosophical/Literary Contributions
License Agreement
By submitting this PR, you agree to license your content under the
CC BY-NC-SA 4.0 License.
Required Steps
##heading for the title, like so:Optional
Consider adding the Stub component to encourage further contributions, like so:
💻 Guidelines for Code Contributions
Recommended Steps
License Scope
The Apache License 2.0 applies to all code except content within
content/**folder (excluding/contributing/**,_meta.ts,acknowledgements.mdx,index.mdx,privacy.mdx,team.mdx,terms.mdx). This primarily covers technical implementations rather than content, literature, or philosophy.License Agreement
By submitting this PR, you agree to license your content under the
CC BY-NC-SA 4.0 License
and your code under the
Apache License 2.0.
Notice
🪄 Formatting is automatically applied by scripts. If you find there has been an error, create an issue or contact us by email.