Mr. Softy has a historical addiction to ugliness.
They "need" to pile up a lot of "sobriety" to reduce the tarnish on the image. The philanthropy of the Bill and Melinda Gates Foundation amounts to little in the technical community.
One little binge of historical practices will knock them off the wagon.
Mr. Softy wasn't addicted to coca^H^H^H^Hmonopolistic practices; he just liked the way they smelled.
I dunno. My theory is that it's really all an iceberg, where the waterline is at the interface level.
Typically, we want to manage things in a declarative sort of way, with a high waterline, and have the code fret about the annoying details.
Then, suddenly, things no worky-worky, or we need to improve time/space/features of the code. Now we want that waterline lower, exposing more of our iceberg, so we can do some imperative sorts of things with it.
While not a GUI, I've been recently living this iceberg metaphor in a MS environment. Consider:
Public Sub asdf() Dim x As ADOX.Catalog Dim c As ADODB.Command Set x = New ADOX.Catalog x.ActiveConnection = CurrentProject.Connection Set c = x.Procedures("your_query").Command End Sub
Duplicating this code in C-shrap or C-pee-pee is a non-trivial undertaking.
As for Eclipse...I fell short of being thrilled back around 3.0.
Dare I say, as an emacsor to a viman, that the old "rivalry" between the two shall continue, long past the eventual demise of Java, XML, and the Next Bloated Idea (NBI) has come to roost.:)
I'd like to use C++ STL containers (I understand them, the knowledge is broadly usable) against managed code to do some custom indexing against MS Word.doc files.
Various data are kept in an.mdb to support the task.
While I'm making steading progress (already prototyped the thing in VBA, it was just too slow and threw some obscure error that may have been memory-related at about the 4-hour point), I must express
dismay at what an obfuscated object model MS Word presents
admiration for the VBA enviornment for creating such a silk purse out of this sow's ear.
So, in addition to tidying the operating system (or at least producing well documented test cases showing WTF), we could also expect to see gradual creation of wrapper classes that would un-bork a lot of this ugliness. I'm envisioniong http://ms_office_space.sourceforge.net, or something, as an umbrella project for libraries that are as 'easy' to use as VBA, but are in a language we can use without negative impact to our self-esteem.
That will be enough wishful thinking for now, Chris; back to work.
Also, what is meant by "reading" bears exploration. Do you mean a Mark 1 eyeball, or another piece of software?
Quite a variety of stuff in the My Documents "folder" (we really do want to relate these digital artifacts to everyday office ones, do we not?).
DRM has all the pleasure of any externally imposed regime.
When someone wanted to dupe my "Strange Beautiful Music" by Satriani, I said, "Nah, we have to keep Joe in guitars."
DRM is about artists putting out quality stuff, the market appreciating the stuff, and the Right Thing occuring.
Anything else is your standard technological solution to a social problem, i.e. <Dr. Evil gesture>failure</Dr. Evil gesture>.
Will the register-based VM of Parrot trump the plethora of stack-based environments in circulation, e.g. Mono?
Or, will MS port its Office suite to C#, relase Linux binaries, and enjoy a jolly chuckle?
You can't write documentation without asserting something about the reader.
Does "no clue" imply that this is the first time they've ever tried coding something?
In this case, you want to write something gentle. The python tutorial is one notable example of what to do there.
However, if you're talking boost, the 100-level stuff isn't going to win applause.
One thing I haven't seen yet in this thread is the task-oriented, or 'cookbook' approach, that serves at least two distinct purposes:
quick-n-dirty steps for the initiated
nice feature overview, to highlight functionality you may not yet be using.
Another thing unmentioned in the thread in indices. For documentation of size, the better the indices, the more useful.
Under the heading of conflicts of interest, one wonders about the correlation between
shares of MSFT in the portfolios of government decision makers, and
selection of Microsoft products to support new projects.
No real cures for this hypothetical problem that wouldn't be far worse than the disease, alas...
Not true. Major Major Major Major got promoted far more quickly than 10 years; no copy of Catch-22 handy to verify the exact number of years. Offtopic, but hey.
Dunno. History is a fairly reliable critic. If the daytime soaps you equate with Shakespeare are still in circulation in 100 years, as Bill S. will presumably be, then you may be right.
1. Researchers have integriddy. Intuhgrity. Inta--that thing where they pursue truth. They develop a hypothesis, test it, and report the results, unvarnished.
2. ????
3. Profit!
Dunno. I hasn't been starin' at too many horses of late. But we doesn't wanna explore yo' puhsonal b'iness... :)
Och, the deliverable is the piece above the waterline. Who but a naval architect can calculate the size of the iceberg?
Mr. Softy has a historical addiction to ugliness.
They "need" to pile up a lot of "sobriety" to reduce the tarnish on the image. The philanthropy of the Bill and Melinda Gates Foundation amounts to little in the technical community.
One little binge of historical practices will knock them off the wagon.
Mr. Softy wasn't addicted to coca^H^H^H^Hmonopolistic practices; he just liked the way they smelled.
The Ion desktop icons still didn't make it. Oh, wait...
Typically, we want to manage things in a declarative sort of way, with a high waterline, and have the code fret about the annoying details.
Then, suddenly, things no worky-worky, or we need to improve time/space/features of the code. Now we want that waterline lower, exposing more of our iceberg, so we can do some imperative sorts of things with it.
While not a GUI, I've been recently living this iceberg metaphor in a MS environment. Consider:
Duplicating this code in C-shrap or C-pee-pee is a non-trivial undertaking.
As for Eclipse...I fell short of being thrilled back around 3.0.
Dare I say, as an emacsor to a viman, that the old "rivalry" between the two shall continue, long past the eventual demise of Java, XML, and the Next Bloated Idea (NBI) has come to roost.
Various data are kept in an
dismay at what an obfuscated object model MS Word presents
admiration for the VBA enviornment for creating such a silk purse out of this sow's ear.
So, in addition to tidying the operating system (or at least producing well documented test cases showing WTF), we could also expect to see gradual creation of wrapper classes that would un-bork a lot of this ugliness. I'm envisioniong http://ms_office_space.sourceforge.net, or something, as an umbrella project for libraries that are as 'easy' to use as VBA, but are in a language we can use without negative impact to our self-esteem.
That will be enough wishful thinking for now, Chris; back to work.
Also, what is meant by "reading" bears exploration.
Do you mean a Mark 1 eyeball, or another piece of software?
Quite a variety of stuff in the My Documents "folder" (we really do want to relate these digital artifacts to everyday office ones, do we not?).
The Onion totally lost cool points with the subscription thing.
Capitalists.
If a male sheep is a ram,
and a wild horse is an ass,
Why is a ram in the ass a goose?
The question is all the more compelling during tax season.
You must be new here:
1. Bang head against wall, repeatedly.
2. ????
3. Profit!
DRM has all the pleasure of any externally imposed regime.
When someone wanted to dupe my "Strange Beautiful Music" by Satriani, I said, "Nah, we have to keep Joe in guitars."
DRM is about artists putting out quality stuff, the market appreciating the stuff, and the Right Thing occuring.
Anything else is your standard technological solution to a social problem, i.e. <Dr. Evil gesture>failure</Dr. Evil gesture>.
Will the register-based VM of Parrot trump the plethora of stack-based environments in circulation, e.g. Mono?
Or, will MS port its Office suite to C#, relase Linux binaries, and enjoy a jolly chuckle?
Consider the boost libraries http://boost.org/.
You get tokenizer, regex, and a parser library (spirit), in sorted by increasing caliber.
It's all about the right tool for the job.
Does "no clue" imply that this is the first time they've ever tried coding something?
In this case, you want to write something gentle. The python tutorial is one notable example of what to do there.
However, if you're talking boost, the 100-level stuff isn't going to win applause.
One thing I haven't seen yet in this thread is the task-oriented, or 'cookbook' approach, that serves at least two distinct purposes:
quick-n-dirty steps for the initiated
nice feature overview, to highlight functionality you may not yet be using.
Another thing unmentioned in the thread in indices. For documentation of size, the better the indices, the more useful.
shares of MSFT in the portfolios of government decision makers, and
selection of Microsoft products to support new projects.
No real cures for this hypothetical problem that wouldn't be far worse than the disease, alas...
Not to be confused with an AK47.
Not true. Major Major Major Major got promoted far more quickly than 10 years; no copy of Catch-22 handy to verify the exact number of years. Offtopic, but hey.
Dunno. History is a fairly reliable critic. If the daytime soaps you equate with Shakespeare are still in circulation in 100 years, as Bill S. will presumably be, then you may be right.
Repeat until true.
We can make it rounder! Rational pi!
1. Researchers have integriddy. Intuhgrity. Inta--that thing where they pursue truth. They develop a hypothesis, test it, and report the results, unvarnished.
2. ????
3. Profit!
Perhaps version control, as a software category, breeds Truly Lame Arrogance.
Go, Subversion!
Thanks, man. /.ed was severe, but surely you have pulled us back from the knife edge of the cusp of the precipice. ;)
The threat of Google getting
+10 Informative post of the day.
Domo.