victory gin in the bathtub, the ol' pair of two-eyes a swimmin'. yeah 2003 was when the hubbub died down, the world had begun its dimmin'.
these days, tubed in and happy, my two-eyes plays only the best tunes. true, reception's a bit crappy, but can't recall different in many moons...
ahh, a news update -- how exciting! the war may be close to ending, says the voice. i smile warmly to two-eyes, inviting patriotic appearance to shield my secret choice.
the white speck of dust, my betrayer; there is no place to keep thoughts but inside. julia, oh lost julia, sadness in layers, a musty regret salty w/ the passing tide.
how to learn to live w/ slashdot (or any other) bias:
consider yourself the HERO PROTAGONIST in that old videogame
(frogger was it called?).
that's all there is to it. as you meander across the fiber-bourne road-
and waterways that is the internet, you realize there is quite a bit of
flotsam and jetsam (not to mention bad analogies but work w/ me here...), some
biased in this direction, some biased in that direction, sometimes at a
constant rate, sometimes spiking quickly and w/o warning. but no worries, you
carry your consciosness from one log to another, from one piece of clear
pavement to the next, your powerful jumping keeping you alive through the
tumult.
alternatively, you are the bird that craps wisdom on the frogs surviving
so, below. oop ack!
you can't just hope people will think for themselves, you have to actively
(1) think for yourself; (2) understand your thought process; (3) show those
interested how you do (1) and (2), hopefully in way that takes root.
obviously, those who are not interested are beyond reach for the moment, but
if you do it right, you'll get to them w/ network effects eventually. if you
do it wrong, however, there will be long periods of fruitless debate and
cultism, activities which can be enjoyable in their own right, at least until
you realize your time is limited.
in a similar critical vein, i would say openness is a prerequisite for
integrity, not the other way around. that is, if a system (or group of
people) has openness, whether or not there is integrity can be judged by the
observer rather than being a quality that must be blindly accepted on faith.
you do not regard it highly probably because you haven't asked the
question: "who owns the government" and listened to real answers (not theory).
just follow the money, o querilous one.
yes, students should learn all the facts of life, including the dangerous
ones. ideally, they should also learn some ethics to discern the proper time
to apply what they learned. any teacher operating otherwise is basically
irresponsible (and should go back to school for remedial pedagogy classes!).
at some point web-browsing through (x)emacs is going to basically involve
a subprocess using gecko, so even if aol zonks the mozilla contributors, they
can still further their art by hacking on emacs. (this presumes they don't
mind working w/ emacs programmers.)
this explains the design of the hudson (mass.) chip design building of hp (was
compaq was dec), i was told a few years back. the raised entrance/miniplaza
is to prevent vehicles entering the building, whether accidentally or w/
malicious intent. "so what's new, in hl02?"
hehe, you answer your own question. hate of usloth is not blind in a
vacuum; usloth encourages both blindness and so-called "trust". when that
trust is ultimately betrayed (as it always is), it is no surprise the result
is blind hate. duh.
better to have informed hate, because at least there is a root cause that
can be examined and the hate eventually channelled into productive action
(like fixing the root cause), presuming the hate is not so off-putting to the
recipient. w/ free software, there is much passionate (anti-)advocacy but at
the end of the day, code is there to use, improve, and pass around. informed
hate as found in the free software community is not so bad, and can even be
ludicrously
entertaining even when unproductive.
anyway, as for the other two combinations, blind love and informed love,
the former leads to betrayal (see above) and the latter has its own dangers
but is still much preferable to the grinding drag that is having to deal w/
any kind of hate. but in all cases, those who deal keep it real.
that point is (quite obvious when you think about it) when usloth actually
does lose to linux. that point is when all their efforts amount to
pouring money (and any remnants of goodwill from their locked-in userbase)
down the drain. that point is pretty much w/in the next half year or so.
of course, there will be localized dingleberries here and there (e.g.,
united states government) but most of the world will wise up pretty fast.
besides, greenspan already read the tarot: a "growth economy" based on
"intellectual property" coercion is the bigger bubble that makes stuff like
dot-bomb small in comparison. hopefully the bubble will seep instead of pop,
but all these extra squeezing by elected bribe collectors don't help the
situation much.
you have a point (approaches congruent w/ mathematical rigor would help
improve the software development process) although your presentation draws
flames. next time, try to synthesize the half-steps taken by well-meaning but
perhaps less incisive practioners instead of discarding them. for example,
many of the extreme programming practices do indeed aim to close the mapping
gap; you could have actually highlighted those efforts to shore your point.
enough of logos, how about pathos: using the word "sad" raises activation
energy for acceptance of your point. perhaps it is a happy circumstance that
so many people still have in front of them that "a ha!" moment when their
brain flips from prescriptive to descriptive, imperative to functional,
unordered to orderd, global to re-entrant. only when the knowing make fun of
the ignorant can the situation be called "sad".
as for ethos: it is proper to expose this point at this time. no
complaints from me in this respect. good luck next post.
heh, selling licenses to rent proprietary software is indeed an accounting
scandal[1]. it's just taken several decades for most people to realize this.
nothing
seeds resentment
greater than a late realization of mis-applied trust.
[1] don't think so? well if you promise to pay me (too) i promise to lie
to you (too). fair enough? let's start! where do you want to go today?
by separating copy from read, and allowing copy privs but not read privs,
you basically force the requirement of some kind of "copy-file" system call
(instead of allowing it to be done "manually"). system calls can be logged
for accounting purposes, and the resulting copied file can be made also w/o
read privs, the end effect being whoever invokes that copy-file system call
is guaranteed to be opaque to the data.
security is improved because you don't need to audit that program wrt that
data (as much;-). failure of that program (whether by implementation or by
external (virus) factors) has much less chance of compromising that data, and
what chance remains is highly localized.
the interested learn first how to feed their interests. sometimes this
lies inside the educational system but most of the time it doesn't. when it
comes to disciplines like computer science, the only really interesting
educational system is the one you set up for yourself.
how a person does this reveals in what ways they are interested /
interesting. but that's not news, and neither is it solely applicable to
computer science.
on a more pragmatic note: when making small talk, just say "i see code
like those dudes in the matrix". this is not far from the truth; a programmer
sees the machine's point, and a computer scientist sees the machine's point of
view. of course, if you really can't see code like that, don't lie, say
instead (honestly, like the rest of us), "i am a student".
Re:and you don't think the RIAA knows this???
on
RIAA vs The Economy
·
· Score: 1
"snowmen"
yeah but that could also be because they used coke (and whores)
to blow your mind (and otherwise) pre-signing. musicians are
nothing if not easily swaysed by these influences.
well you have a healthy parental attitude, but quite a bit of people who join
loins actually don't think this way. to these people kids are a parent's
badge and if the badge is not so shiny or gets ripped off somehow, no big
deal, either get new ones, or rationalize the discarding of the badge. that
is, the kids are only so cherished as long as they are shiny and reflect the
idealized self-image of the parent.
that is to say, many parents are not more than kids still looking for proper
parents, by way of breadth-first search.
why does any creative choose any field? in a word: riff.
skilled application of what is known to please your own feedback aesthetics in
the guitar world is known as "riffing". it is probably similar to other
fields of creative endeavor.
well one very simple example is the difference between the time when the
starting gun goes off and (1) when the sprinter's reflex starts involuntary
motion of the body; (2) when the sprinter's consciousness detects the sound of
the gun and begins streaming explicit "commands" (run like hell) to the body.
researchers measure (1) w/ a fast camera and (2) w/ electrodes sensitive to
the sections of the brain responsible for voluntary motor control.
anyway, very highly trained sprinters rely more and more on (1) since it is
typically the "shorter neural path" (resulting in faster times, duh) and
suppress the urge to rely on (2) overmuch, in contrast w/ those not so highly
trained (i.e., the rest of us). some argue that this is the subconscious
overriding the conscious, and other such interesting interpretations.
like security, quality is a process. "quality control" is basically checking
for manufacturing defects in physical (tangible) products. quality control in
the software arena (beta testing, i.e., customers) is not really enough. the
loop has to be tighter. enter "quality assurance" which is in its ideal form
the checking of the the production process (how programmers program),
not just throwing it over the wall to some hapless tester who has very little
insight into not only the cause of any perceived software misbehaviors, but
the cause of the mindset that went into the programming of those misbehaviors.
this is nothing new, just listen to any extreme programming advocate 'splain
it to ya.
in any case, usloth knows all this but can't be bothered because they are, as
many people now understand, simply a marketing shell around a captive (in the
sense of bound and gagged) research and development core. but unlike the
makeup of the earth, where the crust is relatively thin, and the mantle (and
core) are relatively thick, usloth marketing is like the gases of jupiter; who
knows what enormous pressures must be exerted on the miniscule core trapped
inside.
if someone were to send a monolith and ignite usloth, perhaps all those nice
minds bribed to remain silent could spark another star, to complement that
which is already burning, i.e., free software.
well, i'm an american (so far -- perhaps that will change in the
future), and above all i know my dishonor was not participating in the
political process of the country for about a decade. in many ways i
focused too much on
freesoftware
as an aid to all of society, and
neglected to DTRT in my phsyical community. i hope in the next few
years to return to balance.
i guess it depends on how serious you mean "serious thought" to be. it takes
lots of psychology and false smiles to do what those leeches at mtv do, and
i'm sure more than one coke mirror is busted in rage when someone screws up,
but overall the thinking that goes into exploitation of the young and mostly
defenseless (albeit frivolous) is probably less serious than the thinking that
goes into the question: what happens when the society eats its young?
i believe these were originally in the minds of those media pioneers (witness
for example the yogi bear cartoon episode where they visit a banana-split
factory and recoil in horror at the organized waste therein), but times change
and here we are, priming for social collapse in one form or another.
victory gin in the bathtub,
the ol' pair of two-eyes a swimmin'.
yeah 2003 was when the hubbub
died down, the world had begun its dimmin'.
these days, tubed in and happy,
my two-eyes plays only the best tunes.
true, reception's a bit crappy,
but can't recall different in many moons...
ahh, a news update -- how exciting!
the war may be close to ending, says the voice.
i smile warmly to two-eyes, inviting
patriotic appearance to shield my secret choice.
the white speck of dust, my betrayer;
there is no place to keep thoughts but inside.
julia, oh lost julia, sadness in layers,
a musty regret salty w/ the passing tide.
how to learn to live w/ slashdot (or any other) bias:
consider yourself the HERO PROTAGONIST in that old videogame (frogger was it called?).
that's all there is to it. as you meander across the fiber-bourne road- and waterways that is the internet, you realize there is quite a bit of flotsam and jetsam (not to mention bad analogies but work w/ me here...), some biased in this direction, some biased in that direction, sometimes at a constant rate, sometimes spiking quickly and w/o warning. but no worries, you carry your consciosness from one log to another, from one piece of clear pavement to the next, your powerful jumping keeping you alive through the tumult.
alternatively, you are the bird that craps wisdom on the frogs surviving so, below. oop ack!
that country exists w/o borders; immigrate today!
you can't just hope people will think for themselves, you have to actively (1) think for yourself; (2) understand your thought process; (3) show those interested how you do (1) and (2), hopefully in way that takes root. obviously, those who are not interested are beyond reach for the moment, but if you do it right, you'll get to them w/ network effects eventually. if you do it wrong, however, there will be long periods of fruitless debate and cultism, activities which can be enjoyable in their own right, at least until you realize your time is limited.
happy societal hacking.
in a similar critical vein, i would say openness is a prerequisite for integrity, not the other way around. that is, if a system (or group of people) has openness, whether or not there is integrity can be judged by the observer rather than being a quality that must be blindly accepted on faith.
"there is a difference ..."
but even a five year old can be coached to scan some docs and type "POKE ADDR, VAL" into a a boot-rom basic prompt.
you do not regard it highly probably because you haven't asked the question: "who owns the government" and listened to real answers (not theory). just follow the money, o querilous one.
yes, students should learn all the facts of life, including the dangerous ones. ideally, they should also learn some ethics to discern the proper time to apply what they learned. any teacher operating otherwise is basically irresponsible (and should go back to school for remedial pedagogy classes!).
at some point web-browsing through (x)emacs is going to basically involve a subprocess using gecko, so even if aol zonks the mozilla contributors, they can still further their art by hacking on emacs. (this presumes they don't mind working w/ emacs programmers.)
this explains the design of the hudson (mass.) chip design building of hp (was compaq was dec), i was told a few years back. the raised entrance/miniplaza is to prevent vehicles entering the building, whether accidentally or w/ malicious intent. "so what's new, in hl02?"
hehe, you answer your own question. hate of usloth is not blind in a vacuum; usloth encourages both blindness and so-called "trust". when that trust is ultimately betrayed (as it always is), it is no surprise the result is blind hate. duh.
better to have informed hate, because at least there is a root cause that can be examined and the hate eventually channelled into productive action (like fixing the root cause), presuming the hate is not so off-putting to the recipient. w/ free software, there is much passionate (anti-)advocacy but at the end of the day, code is there to use, improve, and pass around. informed hate as found in the free software community is not so bad, and can even be ludicrously entertaining even when unproductive.
anyway, as for the other two combinations, blind love and informed love, the former leads to betrayal (see above) and the latter has its own dangers but is still much preferable to the grinding drag that is having to deal w/ any kind of hate. but in all cases, those who deal keep it real.
that point is (quite obvious when you think about it) when usloth actually does lose to linux. that point is when all their efforts amount to pouring money (and any remnants of goodwill from their locked-in userbase) down the drain. that point is pretty much w/in the next half year or so.
of course, there will be localized dingleberries here and there (e.g., united states government) but most of the world will wise up pretty fast.
besides, greenspan already read the tarot: a "growth economy" based on "intellectual property" coercion is the bigger bubble that makes stuff like dot-bomb small in comparison. hopefully the bubble will seep instead of pop, but all these extra squeezing by elected bribe collectors don't help the situation much.
(but make sure you do it legibly. :-)
you have a point (approaches congruent w/ mathematical rigor would help improve the software development process) although your presentation draws flames. next time, try to synthesize the half-steps taken by well-meaning but perhaps less incisive practioners instead of discarding them. for example, many of the extreme programming practices do indeed aim to close the mapping gap; you could have actually highlighted those efforts to shore your point.
enough of logos, how about pathos: using the word "sad" raises activation energy for acceptance of your point. perhaps it is a happy circumstance that so many people still have in front of them that "a ha!" moment when their brain flips from prescriptive to descriptive, imperative to functional, unordered to orderd, global to re-entrant. only when the knowing make fun of the ignorant can the situation be called "sad".
as for ethos: it is proper to expose this point at this time. no complaints from me in this respect. good luck next post.
heh, selling licenses to rent proprietary software is indeed an accounting scandal[1]. it's just taken several decades for most people to realize this. nothing seeds resentment greater than a late realization of mis-applied trust.
[1] don't think so? well if you promise to pay me (too) i promise to lie to you (too). fair enough? let's start! where do you want to go today?
by separating copy from read, and allowing copy privs but not read privs, you basically force the requirement of some kind of "copy-file" system call (instead of allowing it to be done "manually"). system calls can be logged for accounting purposes, and the resulting copied file can be made also w/o read privs, the end effect being whoever invokes that copy-file system call is guaranteed to be opaque to the data.
security is improved because you don't need to audit that program wrt that data (as much ;-). failure of that program (whether by implementation or by
external (virus) factors) has much less chance of compromising that data, and
what chance remains is highly localized.
the interested learn first how to feed their interests. sometimes this lies inside the educational system but most of the time it doesn't. when it comes to disciplines like computer science, the only really interesting educational system is the one you set up for yourself.
how a person does this reveals in what ways they are interested / interesting. but that's not news, and neither is it solely applicable to computer science.
on a more pragmatic note: when making small talk, just say "i see code like those dudes in the matrix". this is not far from the truth; a programmer sees the machine's point, and a computer scientist sees the machine's point of view. of course, if you really can't see code like that, don't lie, say instead (honestly, like the rest of us), "i am a student".
"snowmen"
yeah but that could also be because they used coke (and whores) to blow your mind (and otherwise) pre-signing. musicians are nothing if not easily swaysed by these influences.
oop ack!
that is to say, many parents are not more than kids still looking for proper parents, by way of breadth-first search.
skilled application of what is known to please your own feedback aesthetics in the guitar world is known as "riffing". it is probably similar to other fields of creative endeavor.
anyway, very highly trained sprinters rely more and more on (1) since it is typically the "shorter neural path" (resulting in faster times, duh) and suppress the urge to rely on (2) overmuch, in contrast w/ those not so highly trained (i.e., the rest of us). some argue that this is the subconscious overriding the conscious, and other such interesting interpretations.
this is both the power and the curse of recursion. it's not just enough to "get it", you have to know how to "get out".
this is nothing new, just listen to any extreme programming advocate 'splain it to ya.
in any case, usloth knows all this but can't be bothered because they are, as many people now understand, simply a marketing shell around a captive (in the sense of bound and gagged) research and development core. but unlike the makeup of the earth, where the crust is relatively thin, and the mantle (and core) are relatively thick, usloth marketing is like the gases of jupiter; who knows what enormous pressures must be exerted on the miniscule core trapped inside.
if someone were to send a monolith and ignite usloth, perhaps all those nice minds bribed to remain silent could spark another star, to complement that which is already burning, i.e., free software.
i believe these were originally in the minds of those media pioneers (witness for example the yogi bear cartoon episode where they visit a banana-split factory and recoil in horror at the organized waste therein), but times change and here we are, priming for social collapse in one form or another.