<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Search Engines Cannot Be Used To Answer Questions About Commonly Misunderstood Concepts</title>
	<atom:link href="http://ztkfg.com/2020/02/search-engines-cannot-be-used-to-answer-questions-about-commonly-misunderstood-concepts/feed/" rel="self" type="application/rss+xml" />
	<link>http://ztkfg.com/2020/02/search-engines-cannot-be-used-to-answer-questions-about-commonly-misunderstood-concepts/</link>
	<description>198.211.113.164 // 6326 273B 61A7 00AF 4CD9 5A7B 8C6C AB19 24A6 4DEC</description>
	<pubDate>Mon, 13 Apr 2026 15:04:33 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: whaack</title>
		<link>http://ztkfg.com/2020/02/search-engines-cannot-be-used-to-answer-questions-about-commonly-misunderstood-concepts/#comment-215</link>
		<dc:creator>whaack</dc:creator>
		<pubDate>Thu, 27 Feb 2020 21:28:34 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=423#comment-215</guid>
		<description>@ Diana Coman 

&gt; Just how many *more* instances of wasting time do you need in order to STOP searching for "the answer" and start aiming instead to *understand* what the question highlights? Because that's the very role of questions - to highlight something you don't yet understand, as a very first step towards gaining more knowledge, not more answers!

&gt;That aside, the title IS tedious and annoying in the extreme, indeed.

I need no more instances because digging around for an immediate answer via waddling through the swamps of search engine html is frustrating and useless, whereas reading a good source and working towards understanding is pleasurable and rewarding.

@ Mircea Popescu

&gt; Dude holy god omfg why the fuck would you discuss this problem in terms of... fucking mommentum ?!

In retrospect it is certainly the wrong way to approach the problem.

&gt; There's two kinds of tools used in basic mechanics. On one hand the scalar tools : energy (mass * speed squared) ; mommentum / impulse (mass * speed), inertia (mass) etcetera. These are generally useful in conservative approaches. On the other hand the vectorial tools : velocity (distance/time IN A DIRECTION), acceleration (distance / time squared IN A DIRECTION), force etcetera.

I was thinking of momentum in terms of a vector, I'm not sure why you listed momentum in the scalar category. (Although you define it as mass * speed whereas I was thinking of momentum as mass * velocity)

&gt; I am aware that you read a number, and on this basis assume the scale to be in the scalar business ; but IT IS NOT. The scale's in the vector business, because of how it's made, which is what decides these things. Not "how it looks", that doesn't matter. How it works, that's what matters. The fact that it's not practical to add the unit of the involved vector space next to the value measured dun change its universally omnipotent omnipresence one whit.

I understand that force is a vector.

&gt;  As the guy points out : the scale does not measure mass ; it measures... force. Force. ..(and on)

I state in my question as "the &lt;i&gt;force read&lt;/i&gt; on the scale" to make this point clear. I should have clarified that this question is meant to focus on "when is one increasing the normal force on a surface?" rather than how does a specific implementation of a scale perceive that increase.

As for the scale being placed vertically on the wall, I did not take into account that since the scale is likely a spring of some sorts, once it is placed on a wall gravity will bend it downwards slightly to take the form of a soft dick. That aside, from my understanding extending your body while lying on the floor and pressing your legs against the scale will increase the normal force on the scale because there is friction between your body and the ground that applies a force in the direction of the scale.</description>
		<content:encoded><![CDATA[<p>@ Diana Coman </p>
<p>> Just how many *more* instances of wasting time do you need in order to STOP searching for "the answer" and start aiming instead to *understand* what the question highlights? Because that's the very role of questions - to highlight something you don't yet understand, as a very first step towards gaining more knowledge, not more answers!</p>
<p>>That aside, the title IS tedious and annoying in the extreme, indeed.</p>
<p>I need no more instances because digging around for an immediate answer via waddling through the swamps of search engine html is frustrating and useless, whereas reading a good source and working towards understanding is pleasurable and rewarding.</p>
<p>@ Mircea Popescu</p>
<p>> Dude holy god omfg why the fuck would you discuss this problem in terms of... fucking mommentum ?!</p>
<p>In retrospect it is certainly the wrong way to approach the problem.</p>
<p>> There's two kinds of tools used in basic mechanics. On one hand the scalar tools : energy (mass * speed squared) ; mommentum / impulse (mass * speed), inertia (mass) etcetera. These are generally useful in conservative approaches. On the other hand the vectorial tools : velocity (distance/time IN A DIRECTION), acceleration (distance / time squared IN A DIRECTION), force etcetera.</p>
<p>I was thinking of momentum in terms of a vector, I'm not sure why you listed momentum in the scalar category. (Although you define it as mass * speed whereas I was thinking of momentum as mass * velocity)</p>
<p>> I am aware that you read a number, and on this basis assume the scale to be in the scalar business ; but IT IS NOT. The scale's in the vector business, because of how it's made, which is what decides these things. Not "how it looks", that doesn't matter. How it works, that's what matters. The fact that it's not practical to add the unit of the involved vector space next to the value measured dun change its universally omnipotent omnipresence one whit.</p>
<p>I understand that force is a vector.</p>
<p>>  As the guy points out : the scale does not measure mass ; it measures... force. Force. ..(and on)</p>
<p>I state in my question as "the <i>force read</i> on the scale" to make this point clear. I should have clarified that this question is meant to focus on "when is one increasing the normal force on a surface?" rather than how does a specific implementation of a scale perceive that increase.</p>
<p>As for the scale being placed vertically on the wall, I did not take into account that since the scale is likely a spring of some sorts, once it is placed on a wall gravity will bend it downwards slightly to take the form of a soft dick. That aside, from my understanding extending your body while lying on the floor and pressing your legs against the scale will increase the normal force on the scale because there is friction between your body and the ground that applies a force in the direction of the scale.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mircea Popescu</title>
		<link>http://ztkfg.com/2020/02/search-engines-cannot-be-used-to-answer-questions-about-commonly-misunderstood-concepts/#comment-214</link>
		<dc:creator>Mircea Popescu</dc:creator>
		<pubDate>Mon, 24 Feb 2020 05:20:59 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=423#comment-214</guid>
		<description>Dude holy god omfg why the fuck would you discuss this problem in terms of... fucking mommentum ?!

You understand it's a problem of acceleration, not of mommentum, why then are you in the wrong branch of the tree (appart from sub-par education in basic science, such as one would be exposed for instance at MIT, resulting in cluelessness as to what the fuck anything is or how it works).

There's two kinds of tools used in basic mechanics. On one hand the scalar tools : energy (mass * speed squared) ; mommentum / impulse (mass * speed), inertia (mass) etcetera. These are generally useful in conservative approaches. On the other hand the vectorial tools : velocity (distance/time IN A DIRECTION), acceleration (distance / time squared IN A DIRECTION), force etcetera. 

As the guy points out : the scale does not measure mass ; it measures... force. Force. 

I am aware that you read a number, and on this basis assume the scale to be in the scalar business ; but IT IS NOT. The scale's in the vector business, because of how it's made, which is what decides these things. Not "how it looks", that doesn't matter. How it works, that's what matters. The fact that it's not practical to add the unit of the involved vector space next to the value measured dun change its universally omnipotent omnipresence one whit.

Force (which is a vector) equals mass times acceleration (also a vector), thus therefore anything that changes &lt;em&gt;your acceleration&lt;/em&gt; wrt the scale changes your perceived weight. Scales are adjusted to measure ~normal~ force ~at rest~, and so if you hit them they give off results. 

Try it yourself : get a weight, place it on the scale. Then get the same weight, and THROW it on the scale. Or drop it on the scale from a height. Stand yourself on the scale, then jump in the air and LAND upon the scale at speed. Then get a spring, fix it vertically, measure how far it extends on its own weight, add an extra weight, measure how far it extends now, then LIFT THE WEIGHT AND LET IT GO, watch the spring go into a series of attenuated oscillations until stopping at the previously measured position. For half the time, the object "appeared heavier", though, didn't it, by the simple measure of having the spring extend below the neutral position.

Now try something else, like say place the scale vertically against the wall, and lie down next to it such that your feet are on the scale. It'll show something other than your weight, because you've violated its constructive expectations like you have before, though technically in a different way : this time, instead of using it other than at rest, you're using it to measure other than normal forces.

Because, again, it measures a fucking vector, and in order for the measurement to be meaningful, the presuppositions it relies on must hold : normal force (that is, force perpendicular on a defined surface) at rest. 

Stop reading fucking webpages, go read Feynman if you're actually interested in physics.</description>
		<content:encoded><![CDATA[<p>Dude holy god omfg why the fuck would you discuss this problem in terms of... fucking mommentum ?!</p>
<p>You understand it's a problem of acceleration, not of mommentum, why then are you in the wrong branch of the tree (appart from sub-par education in basic science, such as one would be exposed for instance at MIT, resulting in cluelessness as to what the fuck anything is or how it works).</p>
<p>There's two kinds of tools used in basic mechanics. On one hand the scalar tools : energy (mass * speed squared) ; mommentum / impulse (mass * speed), inertia (mass) etcetera. These are generally useful in conservative approaches. On the other hand the vectorial tools : velocity (distance/time IN A DIRECTION), acceleration (distance / time squared IN A DIRECTION), force etcetera. </p>
<p>As the guy points out : the scale does not measure mass ; it measures... force. Force. </p>
<p>I am aware that you read a number, and on this basis assume the scale to be in the scalar business ; but IT IS NOT. The scale's in the vector business, because of how it's made, which is what decides these things. Not "how it looks", that doesn't matter. How it works, that's what matters. The fact that it's not practical to add the unit of the involved vector space next to the value measured dun change its universally omnipotent omnipresence one whit.</p>
<p>Force (which is a vector) equals mass times acceleration (also a vector), thus therefore anything that changes <em>your acceleration</em> wrt the scale changes your perceived weight. Scales are adjusted to measure ~normal~ force ~at rest~, and so if you hit them they give off results. </p>
<p>Try it yourself : get a weight, place it on the scale. Then get the same weight, and THROW it on the scale. Or drop it on the scale from a height. Stand yourself on the scale, then jump in the air and LAND upon the scale at speed. Then get a spring, fix it vertically, measure how far it extends on its own weight, add an extra weight, measure how far it extends now, then LIFT THE WEIGHT AND LET IT GO, watch the spring go into a series of attenuated oscillations until stopping at the previously measured position. For half the time, the object "appeared heavier", though, didn't it, by the simple measure of having the spring extend below the neutral position.</p>
<p>Now try something else, like say place the scale vertically against the wall, and lie down next to it such that your feet are on the scale. It'll show something other than your weight, because you've violated its constructive expectations like you have before, though technically in a different way : this time, instead of using it other than at rest, you're using it to measure other than normal forces.</p>
<p>Because, again, it measures a fucking vector, and in order for the measurement to be meaningful, the presuppositions it relies on must hold : normal force (that is, force perpendicular on a defined surface) at rest. </p>
<p>Stop reading fucking webpages, go read Feynman if you're actually interested in physics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diana Coman</title>
		<link>http://ztkfg.com/2020/02/search-engines-cannot-be-used-to-answer-questions-about-commonly-misunderstood-concepts/#comment-211</link>
		<dc:creator>Diana Coman</dc:creator>
		<pubDate>Thu, 20 Feb 2020 09:17:22 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=423#comment-211</guid>
		<description>Just how many *more* instances of wasting time do you need in order to STOP searching for "the answer" and start aiming instead to *understand* what the question highlights? Because that's the very role of questions - to highlight something you don't yet understand, as a very first step towards gaining more knowledge, not more answers!

That aside, the title IS tedious and annoying in the extreme, indeed.</description>
		<content:encoded><![CDATA[<p>Just how many *more* instances of wasting time do you need in order to STOP searching for "the answer" and start aiming instead to *understand* what the question highlights? Because that's the very role of questions - to highlight something you don't yet understand, as a very first step towards gaining more knowledge, not more answers!</p>
<p>That aside, the title IS tedious and annoying in the extreme, indeed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
