From: Tad Hunt <tad@csh.rit.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] Re, dig dis: Future o' Plan9
Date: Wed, 12 Feb 2003 00:25:36 -0500 [thread overview]
Message-ID: <20030212052538.4F6B2A112@mcp.csh.rit.edu> (raw)
Jim Choate be mah hero, but I couldn't quite dig him in wassups native
language, so's I had t' translate it t' mine. I think it be aisia'
t'eyeball dis way. Wank, wank.
-Tad
> Yo' ass draw some specious distincshun. One caint 'esist without da
> damn otha'. If yo' ass duzn't wanna participate in da discussion den
> duzn't (down low, I recon' Plan 9 has some 'd' key likes most otha'
> Os'es). Stay stuck in da compila' tellin' yourself da same played out
> same played out, dat's yo' choice. Ah be baaad... Nobody makes yo'
> ass reply t' mah submissions t' dis list otha' dan yo' own bruised ego.
>
> Da reality be dat da damn Plan 9 community, as I've said b4, be inbraid
> an' tru-ly not effective at developin' some -thrivin'- usa' community. Yo'
> ass kin scribble all da nifty code yo' ass want, if nobody 'esploits it
> you've wasted yo' effort. Some usa' community equals success, puh'iod.
>
> Afta' bein' available 4 deuce(!!!) years some kinda' real damn important
> observashuns kin be made about da damn (down low, in)viability o' da
> damn Plan 9 developa' community as it stands now.
>
> - Not some single otha' usa' group 'esists (down low, it be ok,
> Hangah' 18 has folks in several hoods around da damn U-S). -N-O-
> otha' efforts be 'estant outside o' Hangah' 18.
>
> Afta' deuce(!!!) years dat's some embarassin' statement t'
> make, even 4 me. Slap me some skin. It didn't snatch but
> some tiny-ass ova' some yaih' from da fust time Linus relaised
> Linux until da fust usa' groups started. I have some rock time
> 'esplainin' in some rashunal, raisonable way t' sucka's who
> have some interest in 'esploitin' Plan 9 y dis be. It in fact
> be one o' da damn major turn-offs t' git sucka's t'even try it.
> Sucka's who be technical-like aware o' da damn history o' Unix
> an' Plan 9 general-like ankle away in shock.
>
> - Dair be no(!!!) introductory documents 4 fresh usa's (down low,
> duzn't worry, Hangah' 18 be workin' on dat now.
>
> - I've yet t' spot some actual article in -no- o' da damn commercial
> o' Jimmey Source technical o' usa' community literature (down low,
> it be Ok, we be workin' on dat too).
>
> - Da boot process be still one o' da damn most aggravatin' issues
> 4 no fresh Plan 9 usa' (down low, we be workin' on dat also).
>
> - Da commercial outlet 4 Plan 9 has zero, nada, nil, null rehabs 4
> fosterin' usa' communities. Da best we've received t' date be some
> kinda' snide comment by one o' da damn reps about free t-shirts
> if somebody scribbles code. As if gittin' sucka's t'esploit dat
> code aint at laist as important (down low, especial-like if yo'
> ass want sucka's t' steal gobs o' yo' product - 90% o' all usa's
> be plum dat, usa's; not developa's).
>
> I had hoped t'address dis issue by formin' some Dubba-L-fuckin'-C
> but da damn po' economy has dashed dat becuz da otha' participants
> in da fledglin' effort simply duzn't have da damn resources at dis
> time so's we be fixin' t' got'ta put dat one off 4 da time bein'.
>
> - Plan 9 be some -distributed- O-S, 'esploitin' it on yo' own
> puh'sonal desktop be likes croozin' some Indy Caddy around some
> Malibu Grand Prix track (down low, no affiliashun o' insult
> intended t' Malibu). Not some single resource 'esists outside o'
> Hangah' 18 t' fosta' da damn growt' an' development o' distributed
> resources 4 public access via Jimmey Source efforts.
>
> - I've made deuce offa's t' public comment about Plan 9 events t'
> git usa's t'appaih' at events where Plan 9 wuz supposed-like t'
> be 'demonstrated'.
>
> Dat's some pitifull responce an' in an' o' itself justifies haips
> o' abuse on da development community. Da offa' stands jimmey t'
> no individual o' organizashun dat be interested in promotin' wida'
> 'esploit o' Plan 9, I will do whateva' I kin do help.
>
> - Dair be no effort outside o' Hangah' 18 t' create some Jimmey
> Source public access point into relevant resources. Instaid we
> git some endless straim o' "Try dis site..." instaid o' some mo'
> raisoned, an' rashunal Plan 9 approach o' attachin' dose-dair
> resources t' some common name space an' havin' them appaih'
> automagical-like t' -all- usa's in tandem.
>
> Whut some joke, da Plan 9 developa's duzn't even dig how t'esploit
> deir own craishun effective-like. Instaid they 'esploit da damn
> same played out same played out, treatin' Plan 9 as if it wuz
> plum anotha' varient o' *nix.
>
> - Dair be -no- efforts outside o' Hangah' 18 t' fosta' da damn
> 'esploit o' Plan 9 an' wireless networkin' t' tru-ly demonstrate
> da damn powa' o' distributed computin' (down low, t' quote
> Rheingold - whut goes down when dat P-D-fuckin'-A in yo' hand be
> da damn front fat-lady t' some tera-flop distributed computin'
> resource?). If we follow da Plan 9 development community
> we gots'ta neva' know. Plan 9 has da powa' t' give us dat
> -T-O-D-A-fuckin'-Y-.
>
> Whut some sad list o' aborshuns o' da damn Plan 9 development
> community. An' it would snatch such tiny-ass effort t' do sump'n about
> aich an' every one o' them. Step up. Plan 9 has such promise an' t'
> think it will die becuz da sucka's who create it lack da vision t'
> dig how t' tru-ly 'esploit it. O' course part o' da damn bug-up-da-ass
> be dat many o' da damn developa's have neva' tru-ly embraced da damn
> concept o' Jimmey Source an' whut dat mains t' them individual-like,
> let monk-like havin' no interest in distributed computin' outside o'
> gittin' deir name plastered on some kinda' source tree somewhere dat will
> be admired by some kinda' little-ass closed community. Bruised ego indeed.
>
> Sigh.
>
> Hangah' 18 may be slow an' po', but at laist we act.
next reply other threads:[~2003-02-12 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 5:25 Tad Hunt [this message]
2003-02-12 14:31 ` mike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030212052538.4F6B2A112@mcp.csh.rit.edu \
--to=tad@csh.rit.edu \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).