Blog Tools
Edit your Blog
Build a Blog
View Profile
« July 2007 »
S M T W T F S
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 31
You are not logged in. Log in
Entries by Topic
All topics  «
Apple Fritters
Calamity
Chinadotcom and VCSY
DD to da RR
Endorsements
Facebook
GLOSSARY
Gurgle
HP and VCSY
Integroty
Microsoft and VCSY
Nobody Can Be That Stupid
Notable Opinions
Off the Wall Speculation
Panama
Pervasive Computing
Reference
SaaS
SOA
The DISCLAIMER
The Sneaky Runarounds
TIMELINE
VCSY
VCSY / Baseline
VCSY / Bashed
VCSY / Infotech
VCSY / MLE (Emily)
VCSY / NOW Solutions
VCSY - A Laughing Place #2
Tuesday, 17 July 2007
One foot on the platform, the other on the plane.
Mood:  celebratory
Now Playing: Muckmuck's Vacation - Caveman rediscovers roots in under-developed countries.
Topic: Microsoft and VCSY

And this is so important I thought I should post it in two places at once.

Will Microsoft be reverse engineering 521?

Is this a test rocket or a cannonball?

It's my opinion this is not doable without stepping on 521 claims. I am open to debate anyone who says they think Microsoft is doing it differently.

http://blogs.zdnet.com/microsoft/?p=582
July 17th, 2007
Microsoft offering Office 2007 for rent on a monthly basis
Posted by Mary Jo Foley @ 12:11 pm

Looks like Microsoft’s intial pilots of pay-as-you-go pricing for Office were successful.

Microsoft has expanded its Office rental trial in South Africa to include Office 2007. Microsoft will make Office 2007 available for 199 rand ($28.54) for a three-month subscription, according to a Reuters report. First-time users willg et an extra three months for free, Reuters said. (Thanks to Bink.nu for the link to the Reuters story.)

Microsoft has been testing pay-as-you-go schemes for Office 2003 in several developing countries, including South Africa, company officials said earlier this year. At that time, Microsoft officials said the Office rental trials were also in full-swing in Mexico and Romania. Back in January, Microsoft was planning to decide “in the next couple of months” whether to extend the program to include Office 2007.

I’ve asked Microsoft whether it plans to extend this program and offer Office 2007 on a subscription basis in other countries. Stay tuned.

Meanwhile, would you be interested in renting Office — or any other Microsoft app — on a monthly basis? Why or why not?


Posted by Portuno Diamo at 4:14 PM EDT
Post Comment | Permalink
The Neverending Story
Mood:  happy
Now Playing: Etched in Stone - Moses drops hammer on mountainview
Topic: Microsoft and VCSY

Some folks think I have no life. Of course I do. This is it. What would I do if I didn't have this hobby? Maybe finish my model airplane.

157635

Oh Microsoft virtualization is good enough to bea

yo-eleven  

17 Jul 2007 3:46 PM EDT

157634

Folks are free to comment anywhere. I am thus NOT

yo-eleven  

17 Jul 2007 3:42 PM EDT

157633

Dear RB Moderator - I apologize for the number of

yo-eleven  

17 Jul 2007 3:40 PM EDT

157632

Ouch.

yo-eleven  

17 Jul 2007 3:37 PM EDT

157631

"In some ways, though, the online world is l

yo-eleven  

17 Jul 2007 3:36 PM EDT

157630

I'm laying in a record for you to explain to the

yo-eleven  

17 Jul 2007 3:32 PM EDT

157629

"...a performance nonetheless that put the o

yo-eleven  

17 Jul 2007 3:30 PM EDT

157628

yoyo, You're pumpin' a dry well.

nicheslapper  

17 Jul 2007 3:27 PM EDT

157627

Ballmer "...lectured with little humor and m

yo-eleven  

17 Jul 2007 3:24 PM EDT

157626

Before we launch off into any technical explanati

yo-eleven  

17 Jul 2007 3:23 PM EDT

157625

And here's a list of dates and events to give the

yo-eleven  

17 Jul 2007 3:09 PM EDT

157624

correction 721= 521 aka Patent 7,076,521

yo-eleven  

17 Jul 2007 3:00 PM EDT

157623

Problem? Yes. MSFT does not have free access to 7

yo-eleven  

17 Jul 2007 2:57 PM EDT

 


Posted by Portuno Diamo at 3:52 PM EDT
Updated: Tuesday, 17 July 2007 4:02 PM EDT
Post Comment | Permalink
Monday, 16 July 2007
Rock and Roll Cooty Goo
Mood:  incredulous
Now Playing: Knock About the Block - Auto damage & auto repair (instructional)
Topic: Calamity

For those of you who don't get out much, here's a little slice of Raging Bull for your edification. It's not often you get service like this. It's like being there without having to go there.

 

 Post new message  | Refresh list

 Msg. # 

Subject

Posted by   

Date   

190567

admist = admits. sorry. pesky typos mean somethin

yo-eleven  

16 Jul 2007 2:21 AM EDT

190566

Besides, neepaddie, don't you want Microsoft get

yo-eleven  

16 Jul 2007 2:20 AM EDT

190565

irule: Where did you go? Come out to play, pretty

RapidRobert2  

16 Jul 2007 2:17 AM EDT

190564

Another basher doing the 'FRANTIC PANIC' DANCE of

RapidRobert2  

16 Jul 2007 2:17 AM EDT

190563

last = lost. sorry. damn typos. eom

yo-eleven  

16 Jul 2007 2:14 AM EDT

190562

OH! irule, techlaw, lawtech, teklaw..or whatever

RapidRobert2  

16 Jul 2007 2:13 AM EDT

190561

OH! irule, techlaw, lawtech, teklaw..or whatever

RapidRobert2  

16 Jul 2007 2:13 AM EDT

190560

neepadder - Wade's a genius for having secured th

yo-eleven  

16 Jul 2007 2:12 AM EDT

190559

Because 'some' lawyer only got a 'few thousand' b

RapidRobert2  

16 Jul 2007 2:08 AM EDT

190558

A wantabe lawyer who will never make the bar sugg

RapidRobert2  

16 Jul 2007 2:06 AM EDT

190557

niche - did you know that's exactly the same lang

yo-eleven  

16 Jul 2007 2:03 AM EDT

190556

irule - If they are basing their position on comm

yo-eleven  

16 Jul 2007 1:56 AM EDT

190555

Yo...

nicheslapper  

16 Jul 2007 1:50 AM EDT

190554

irule - why would it be impossible for MSFT and V

yo-eleven  

16 Jul 2007 1:32 AM EDT

190553

Will one of you learned pumpers...

irule  

16 Jul 2007 1:26 AM EDT

190552

Load..

nicheslapper  

16 Jul 2007 1:20 AM EDT


Posted by Portuno Diamo at 2:42 AM EDT
Updated: Monday, 16 July 2007 3:17 AM EDT
Post Comment | Permalink
Tickle me Elbow.
Mood:  energetic
Topic: Pervasive Computing

An interesting bit of reference knowledge:

An Overview: Where Things Stand in IBM, Novell, and Red Hat
Sunday, July 15 2007 @ 10:01 AM EDT

I thought it would be useful, judging from some recent confusion in the media, to highlight the latest goings on in all the ongoing cases in the SCO saga all on one page, so everyone can follow the bouncing ball. That will mean some slight repetition for some of us, but it also will make it easier for those who don't follow the SCO saga as intently as we do to grasp the current picture.

The very latest is that the court has signed [PDF] the stipulated adjustments the parties proposed to the pre-trial schedule in Novell, there was a SCO status report [PDF] filed in Red Hat and here's Red Hat's latest [PDF], and there was a goofed up filing in IBM, where SCO filed its memorandum in opposition to Novell's evidentiary objections (2nd objections; Novell reply to SCO) in the IBM docket by mistake, and IBM has asked for a 30-day extension of various pretrial scheduled items. But now, let's look at the overview to see how they all interrelate, and I'll also try to give you a picture of what trial preparation in Novell is probably like right about now.

You can read the rest at Groklaw.

http://www.groklaw.net/article.php?story=20070715072440971


Posted by Portuno Diamo at 12:14 AM EDT
Post Comment | Permalink
Sunday, 15 July 2007
Once Upon a Coma...
Mood:  hug me
Now Playing: Who Pawned the Peon? - Lost art found in art-dealer's basement
Topic: SaaS

How popular would 'Emily' be right now if Emily had been allowed to operate out in public unmolested like the giant companies do? You know... what would Emily have been known as today? Would she be as popular and necessary to the next information revolution as, say, AJAX?

I think Emily can be shown to have had a much greater potential for a much more rapid adoption rate than AJAX has shown. AJAX has been developed in public since March 2005. Emily was selling products in 2001. The fact AJAX has taken so long and still has a long way to go to become a robust platform for critical real time distributed use decries the 'obvious' tag for VCSy technology.

http://ajax.sys-con.com/read/400297.htm

Delivering Web 2.0 User Interfaces Using AJAX
The user experience is absolutely central to the Web 2.0 model

By any reckoning, the Internet and the World Wide Web have remade the way we do business. The ascendance of the Web-based enterprise has come to be seen as inevitable. But anyone who takes a hard look at the serious limitations of first-generation Web applications is likely to have a renewed sense of wonder at the spread of their adoption thus far. Users experimented with e-mail, instant messaging, and search engines and turned them into real communication, collaboration, and information-gathering tools. Those same business users endured their fitful interactions with static HTML pages and moved applications to the Web anyway because of the substantial savings promised by the shift. 

Now their patience is about to be rewarded. Emerging from a decade of groundwork is Web 2.0, which offers dramatic gains in productivity for individual workers and whole enterprises. Web 2.0 applications are distributed collaborative tools available on-demand from any browser anywhere. And those tools are constructed to be at least as intuitive and easy-to-use as any application loaded on a desktop.

Web 2.0 is based on many technologies - most prominent among them being Web Services, Asynchronous JavaScript and XML (AJAX), Cascading Style Sheets (CSS), and Really Simple (Web) Syndication (RSS) - and the list will continue to grow. Of these, AJAX has attracted the most attention recently because it's the technology that most effectively fills the gap between the user experience of Web and desktop applications.

And the user experience is absolutely central to the Web 2.0 model. Web 2.0 applications must possess a set of user interface components that are as compelling and responsive as a desktop-based environment. Developers can no longer be satisfied to offer discontinuity in user experience, because widely distributed, frequently mobile users won't be able to tolerate it and do their jobs well. The improved user experience will include, but must extend beyond, the most common productivity tools, such as word processing applications and e-mail. Web 2.0 and AJAX-based applications represent an opportunity to fully realize the Web's potential to make users smarter and more productive, and that opportunity extends to the most sophisticated back-end and analytic applications.

How We Got Here: Evolutionary Steps to Web 2.0
As any significant technology evolves toward maturity, attention shifts from the technology itself to the work that the technology enables. That shift is clearly manifest in Web 2.0, the third major phase of the Web's evolution, which can be summarized like this:

  • Web 1.0 - Content delivery and communication. This early stage changed the dissemination of information via two innovations, HTML pages and e-mail.
  • Web 1.5 - Content personalization and multi-level communication. Search and personalization made the spread of information more efficient, while chat rooms and instant messaging expanded communication in real-time.
  • Web 2.0 - Authoring and collaboration. This current stage is not about the dissemination of information, it's about productivity - accomplishing work-related tasks in a virtual space with tools and applications that are available anywhere, at any time, and can be shared collaboratively.
In the past, Web applications' lack of responsiveness and dearth of controls offset most of their advantages as thin-client tools. In contrast, desktop developers have historically taken advantage of two capabilities of Windows that make applications more intuitive and user-friendly than their Web counterparts: richness and responsiveness. When a complex and robust set of UI components is combined as they have been on the desktop, they make the user interface natural, informative, and intuitive to use. And when the application and the user interface quickly adapt to user actions, they create an uninterrupted interaction. Windows applications don't stop to reload, forcing users to move through tasks in stops and starts - or causing them to lose the thread of the business process entirely.

The user experience gap between Windows and the Web has been due to the limitations of the early Web client/server model, with the Web server as the platform for all processing logic and the browser as the client handling nothing more than the data display. In this architecture, users interact with HTML and each of their actions triggers a request to the server, which in turn triggers the generation of a new page.

The incessant reloading of the page severely limits the user experience for a couple reasons. First, flipping from page to page can disorient the user as the allocation of tasks on different page views causes loss of context. On top of that, reloading the page causes a disjointed and rigid interactive flow. The user has to wait for the next page to initiate a new interaction or change the workflow, or be bounced back to the previous page to alter information in a field. Think of the online shopper on a retail site who can't order three shirts instead of two without returning to page one, and then extend the problem to business users struggling with enterprise applications throughout their workday.

The difficulties of the interaction are compounded as the complexity of applications and user options increases. For example, imagine the user experience of writing a document in an application created in Web client/server mode. For each paragraph, the user must open a dialog, enter the text in the input box, and wait for the changes to be applied to the document when the page is refreshed. And then all the steps must be repeated for every edit or format change. The frustrated user needs plenty of patience and training to work with the tool.

Enter AJAX
By contrast, AJAX combines technologies such as asynchronous JavaScript, the Document Object Model, XMLhttpRequest, XHTML, and CSS so the user can incrementally update any element of an application that resides in the browser. The user never leaves the application - never loses context or suffers interrupted workflow - because no action triggers the reloading of a full page.

This seemingly small change has a profound effect on the user's experience. Transferring more of the interaction to the client side not only improves the workflow, it also allows the addition of enriching UI components, which put AJAX-based Web applications on a par with desktop applications for usability. There are, it should be noted, alternatives to AJAX - Adobe's Flash technology also provides a means to develop rich clients and DHTML allows one to partially upload components on an HTML page without reloading the entire page. But AJAX's combination of cross-browser compatibility, zero footprint, and ability to provide interactive complexity to the user gives it a leg up on the competitive technologies.

The improved interactivity of Web 2.0 applications is driving even more applications off the desktop, since the lower total cost of ownership now comes without the offsetting negatives of cumbersome user experience. These transitional Web 2.0 applications enabled by AJAX have been productivity tools, such as word processing and e-mail applications, calendars and spreadsheets. Examples are Google's recently released Writely and Google Spreadsheets; competitive word processors like Zoho Writer, Abe Writeboard, and ajaxWrite; Num Sum spreadsheet functionality; and 30 boxes, a Web-based calendar. Web-based desktops are also emerging, like the one available at www.desktoptwo.com.

Their lower TCO comes from centralizing most of the software in a single location on the server, with only a browser installed on desktops throughout the organization. This lowers installation and maintenance costs, provides for incremental upgrades to existing applications, creates user administration savings, and offers enterprise-wide control over document backup and archiving, as well as compliance and security. The Web 2.0 model makes applications instantly available to users, eliminating desktop installations. And it's a model that can be extended to applications across the enterprise.

For example, as sophisticated analytics and business intelligence information are pushed further out into the enterprise, it is essential that applications deliver the information smoothly, clearly, and in an uninterrupted context. AJAX provides the foundation for user interfaces based on reusable components, each of which enables a set of UI functions that can be manipulated individually for or by the user. The flexibility inherent in AJAX-enabled applications translates into quick, easy rollouts of new functionality as user needs change, as well as the ability to customize the interface for users based on their roles and specific needs. Improving the user experience translates into a parallel improvement in the user's ability to apply high-level information to the decision-making process, which is, after all, the goal of business intelligence.

Organizations were moving applications to the Web even before the emergence of Web 2.0 and AJAX-based tools because cost savings were so attractive that they trumped the limitations of first-generation Web applications. Now, with Web 2.0 applications that provide a user experience equal to that of desktop applications, that trend is going to build momentum rapidly.

For several years, enthusiasts have predicted that the impact of the Internet and the Web will rival that of the Industrial Revolution. Driven by the same need to use resources more effectively and increase productivity as that earlier transformation, Web 2.0 could make those predictions come true. But instead of centralizing workers and machines in factories, Web 2.0 will liberate a distributed, mobile workforce by offering consistent access to applications and information anywhere in the complex world of the global enterprise.


Posted by Portuno Diamo at 3:07 PM EDT
Updated: Sunday, 15 July 2007 3:37 PM EDT
Post Comment | Permalink
What I did on my summer vacation.
Mood:  chillin'
Now Playing: (Making Stew in the Pew) Church bus trip runs over speedbump. ()
Topic: Microsoft and VCSY

I know you fine as frog fur folks won't be trudging through the muck and mire of the Raging Bull VCSY message board so I thought a few posts to give you the flavor of recent events might be useful to your study and edification.

Don't mind the mustard stains and the way it all looks. It's all bad potato salad.

My field trip on the tour bus on Friday the 13th. (not that I'm supersuspicious or anything)

 

Me, I gotta go and start the thing talking about the rapture compared to VCSY and all...

189982

soon. now you know why people waiting for Jesus t

yo-eleven  

13 Jul 2007  
1:13 PM EDT

Brother abuckwilldo was testifying. 'I once was...'

189983

i was at $6 dollars now at .05

abuckwilldo  

13 Jul 2007  
1:15 PM EDT

Heh heh heh. The old adversary thought he had him with that one.

189984

How is that 'good news'?

tepe  

13 Jul 2007  
1:22 PM EDT

Everybody was getting impatient, like.

189985

RR can Microsoft wait until 11:59 pm and file it

Sliver_Fox  

13 Jul 2007  
1:33 PM EDT

Getting into theological discussions and all...

189986

Gee, Port I never thought of or put Mr. Wade and

dorty  

13 Jul 2007  
1:36 PM EDT

Like how you can't take it with you but we would like to have a little to rub on us before we go...

189987

yo, All the money in the world can't buy eternal

waitin-on-news  

13 Jul 2007  
1:40 PM EDT

And then there are those who can skip the Sunday school lesson, they want to hear the band...

189988

Let me know when the Trumpet sounds

pbalsamo  

13 Jul 2007  
1:42 PM EDT

The mood was rather nasty. A salty sea dog heckled from the amen section...

189998

"The one downside to being a VCSY shareholde

seabeemike  

13 Jul 2007 

And we all said 'Amen'...

189999

seabee cares. he really cares. eom

yo-eleven  

13 Jul 2007  
2:59 PM EDT

To that.

190000

Really

Sliver_Fox  

13 Jul 2007  
3:07 PM EDT

And the odometer rolled over a bit and then WHAM...

190007

From the yahoo message board

stargate94  

13 Jul 2007  
3:26 PM EDT

We thought we rolled over a log in the road...

190008

So is VCSY not going to win. It seems like the m

longandstrong1  

13 Jul 2007  
3:28 PM EDT

So one of the 'long and strong' mechanic guys took a look under the bus and pronounced us doomed.

190011

Now im scared of the, next day, next week, next m

longandstrong1  

13 Jul 2007  
3:35 PM EDT

Happy Bob got out the dealership papers from the glove compartment and found the table of contents...

190012

Well, I don't know if it will help but you could

RapidRobert2  

13 Jul 2007  
3:37 PM EDT

And then one of the deacons reminded the mechanic this bus charter was non-refundable. You either ride or you get off and don't complain.

190013

longandstrong, Who promised what?

4sirius2  

13 Jul 2007  
3:37 PM EDT

Of course, it wasn't a log. It was an unexpectedly thick rolled up newspaper.

190019

How come no one is happy we did it

stargate94  

13 Jul 2007  
3:45 PM EDT

Nobody believed what the headline on the newspaper said so it didn't get unrolled...

190023

stargate - the posts on the Yahoo messageboard ar

yo-eleven  

13 Jul 2007  
3:59 PM EDT

Then, Happy Bob read the 'terms and conditions for return of damaged bus' in fine print...

190027

Well, MSFT just filed a response with the court.

RapidRobert2  

13 Jul 2007  
4:28 PM EDT

And he had to take a poop in the woods. He took some reading material with him.

190033

MSFT says the patent is invalid and they will sho

RapidRobert2  

13 Jul 2007  
4:39 PM EDT

Was it the potato salad? The chicken and cucumbers Sister Shirley made? Was it the roach in the pickle jar?

190040

Any guesses on Monday's action? Is it telling tha

kalineaz  

13 Jul 2007  
4:53 PM EDT

Happy Bob came back and said he needed some time and privacy. 'Hand me that newspaper roll.' he says.

190044

Will respond later, have to leave now...eom

RapidRobert2  

13 Jul 2007  
4:59 PM EDT

We all wondered how many others at the Social would be 'chucking the chicken', as it were.

190048

My take--I can't imagine there will be much dumpi

kalineaz  

13 Jul 2007  
5:07 PM EDT

Sister Inez said she had a cousin went crazy from bad potato salad. We all was feeling a little dizzy by then.

190050

8 yr's and waiting,we may all go insane.lol

abuckwilldo  

13 Jul 2007  
5:13 PM EDT

Latchmouth Leroy said we could probably all go on disability if we ate out of the pickle jar.

190051

Sure hoped they were willing to work with us. Now

4th_and_9  

13 Jul 2007  
5:14 PM EDT

Some was already planning for the future.

190054

Yo, you think google will be our new friend?

benjaamin  

13 Jul 2007  
5:24 PM EDT

Some figured the day was shot and they needed one.

190055

The Sun will set in the West and rise in East jus

KRBJR  

13 Jul 2007  
5:25 PM EDT

And then up jumped the devil.

190056

Born July 12, 2007. Wonder who else writes "

tepe  

13 Jul 2007  
5:26 PM EDT

He started getting down in to where he be's...

190057

Even if they ARE working out the final details of

tepe  

13 Jul 2007  
5:29 PM EDT

Accusing and abusing.

190059

I TOLD YOU!!!! You were so darn sure that there

tepe  

13 Jul 2007  
5:35 PM EDT

Denying the promises.

190060

There is NO IBM DEAL EITHER! That was all hype j

tepe  

13 Jul 2007  
5:38 PM EDT

Smiling faces.

190061

Kalineaz, I generally agree with you, but I think

tepe  

13 Jul 2007  
5:40 PM EDT

Lying to the races, y'all.

190066

Dan, I said my concern was that MSFT would challe

tepe  

13 Jul 2007  
5:52 PM EDT

Teaching false doctrine!

190078

The Pumper's Handbook

tepe  

13 Jul 2007  
6:31 PM EDT

Mocking righteous judgment!

190080

You're right, the jury is still out. But the ver

tepe  

13 Jul 2007  
6:36 PM EDT

Spreading doubt.

190081

I doubt more than a dozen people were watching...

tepe  

13 Jul 2007  
6:38 PM EDT

Making a damn fool of hisself and The Story isn't over. That was just on Friday.

By Sunday morning people was having to pray through all over again.

190412

I think we all ought to

LV_GaryD  

15 Jul 2007  
12:35 AM EDT

Sorry the journal looks so funky. Bumpy road and squiggly lines. Because there's just not enough space or time, looks like y'all going to have to visit the pages in between yourself to find out what turned everybody from tried and tribulated to shouts of getting the victory... and a few laughs to boot.


Posted by Portuno Diamo at 12:38 AM EDT
Updated: Sunday, 15 July 2007 3:23 PM EDT
Post Comment | View Comments (2) | Permalink
Saturday, 14 July 2007
Is this thing on?
Mood:  accident prone
Now Playing: THUMP THUMP THUMP Testes 123... bvweeeeeeeep
Topic: Microsoft and VCSY

News as of Friday evening July 13, 2007 is that Microsoft intends to prove the SiteFlash patent not valid per technical interpretation of the application process.

Yes, we have no furter news and frankly I think you're being a little foreward to ask.

I will be found at this spot from time to time as time goes by. Next time bring cigarettes and candy.

It's still the same old story. A fight for love and glory. A case of dew or dye. 

And, while you're limericking and delineating, I'll give you some background muzak.

http://ragingbull.quote.com/mboard/boards.cgi?board=VCSY&read=190338
 
http://ragingbull.quote.com/mboard/boards.cgi?board=VCSY&read=190330
 
http://ragingbull.quote.com/mboard/boards.cgi?board=VCSY&read=190370
 
http://ragingbull.quote.com/mboard/boards.cgi?board=VCSY&read=190394

UPDATE

http://ragingbull.quote.com/mboard/boards.cgi?board=MSFT&read=154750

http://ragingbull.quote.com/mboard/boards.cgi?board=MSFT&read=154738

http://ragingbull.quote.com/mboard/viewreplies.cgi?board=MSFT&reply=154732

http://ragingbull.quote.com/mboard/boards.cgi?board=MSFT&read=154585

http://ragingbull.quote.com/mboard/boards.cgi?board=MSFT&read=154584


Posted by Portuno Diamo at 11:13 PM EDT
Updated: Wednesday, 18 July 2007 2:17 PM EDT
Post Comment | View Comments (1) | Permalink
Tuesday, 29 May 2007
Excuse me, are these seats taken?
Mood:  irritated
Now Playing: 'Gang aWay' Family arrives just in time to board last boat off the island. (Travel / Adventure)
Topic: Integroty

This is utterly laughable and disgusting all at the same time. And you nitwits sit there with a thumb up the pie like Little Jack.

One would think Microsoft would have some sort of accountability with their own public and shareholders, but, I guess when you're that big, you can do as you pretty damn well please.

I DOOOOO wonder what is headed Microsoft's way.

By: Texas_Star
29 May 2007, 03:27 PM EDT
Msg. 186224 of 186227 

MSFT "Insider Selling" accelerating fast!

Some notes:

1. Bill Gates has SOLD roughly 20,000,000 shares THIS month.

2. BACH ROBERT J has SOLD roughly 20% of his shares THIS month.

3. Over 40,000,000 shares SOLD by insiders in last 6 months.

4. ZERO shares purchased by insiders in last 6 months.

5. VCSY filed a lawsuit against MSFT just last month.


http://finance.yahoo.com/q/it?s=MSFT

Hmmmmmm! Very interesting I'd say!

Tex*

IMO


Posted by Portuno Diamo at 3:52 PM EDT
Updated: Tuesday, 29 May 2007 3:52 PM EDT
Post Comment | View Comments (3) | Permalink
IBM wants to know. LOL
Mood:  hug me
Now Playing: 'Making Tools' Stone age tribe hammered by robots. (Fossils / Freebies)
Topic: Pervasive Computing

Question:

IBM (actually an O'Reilly Editor is asking) wants to know: "What are all you 'XML Programmers' using for tools? Rocks tied to sticks?"

XML and Java technology: Low-level or high-level XML APIs?

How much control do you want over your XML?

Brett D. McLaughlin, Sr. (brett@newInstance.com), Author and Editor, O'Reilly Media, Inc.
29 May 2007

Not many years ago, the options for working with XML were limited essentially to SAX, DOM, or a home-brewed API. With hundreds of different developer-friendly APIs today, though, have developers lost some of their ability to manipulate XML?

Here's the deal: I'm looking to stir the pot a bit. This is obviously not a tip that is overflowing with working code, because I wonder who really does use working XML code these days, and what API (or APIs) they use. Is it true that hundreds, thousands, tens of thousands of you out there still plug away with SAX and DOM, comfortable writing your startProcessingInstruction() method, or have data binding and helper APIs completely taken over? I'm curious, as is much of the developerWorks editorial staff.

And arguably more importantly, do you believe you still have the control and power over your XML? I pose this question particularly to programmers who have worked with XML since the early days when SAX was your only option for speedy XML reading, and DOM was the only choice if you wanted to deal with an XML document in object form. Do you find yourself working at a higher level, and are you OK with that? Or have we all become Turbo Pascal programmers while only a select few guys are popping the stack over on their ASM terminals? Please, get involved in this discussion—hop on over to the forum and start posting, and let's see what everyone thinks. XML programmers: declawed or not?

I would like to know a few answers as well, like, how do all you developers feel watching Java take on XML while .Net sits in the closet?


Posted by Portuno Diamo at 3:28 PM EDT
Updated: Tuesday, 29 May 2007 3:39 PM EDT
Post Comment | Permalink
Forget the bipolar bears, it's the icebergs that will get us.
Mood:  a-ok
Now Playing: 'North to Santa Barbara' World situation heats up for eskimos in the sun light.
Topic: The Sneaky Runarounds

SOME CLARITY FOR YOUR WATER?

The following dated fragments come from the Timeline Vershtinken (see sidebar) which is a compendium of only a few interesting coincidental datings clustered around Microsoft, their efforts toward a web-based client which never materialized, and VCSY intellectual property awards.

August 18, 2004 VCSY SiteFlash Patent allowance
(date approximated by subtracting example 104 day span on Enabler patent allowance/granted cycle)
[see March 28, 2006]

August 27, 2004 Longhorn rewrite announced. Winfs out of Longhorn

November 11, 2004 Ballmer throws chair during meeting with Lucovsky

November 18, 2004 Ballmer accuses Linux of violating >258 patents

November 30, 2004 VCSY SiteFlash Patent granted

The marginalization of those developers who know what Longhorn was about (as opposed to “journalists” who write what they're told and don't bother looking into details) and what Microsoft intended Longhorn and all the other lost qualities that were to make up Vista, has begun.

 

 

May 25, 2007

Longhorn Reloaded: Nostalgia Run Amok
Filed under: Windows Vista
Posted by Randall Kennedy on May 25, 2007 08:28 AM

excerpted:

...for some people the memories are so compelling that they simply don't know how to "let go." Take the case of the "Longhorn Reloaded" project. These poor souls are so tortured by Microsoft's decision to abandon portions of the original Windows "Longhorn" vision that they've taken it upon themselves to "complete" Microsoft's work by delivering a rogue version of the Windows OS they believe "Longhorn" could have become.

...Why? Why resurrect the unfinished code base of a BETA OS (LHR, as they call it, is based on the WinHEC 2004 pre-release build 4074) that Microsoft shelved over 3 years ago?

...folks... believe that Microsoft abandoned the "Longhorn" effort prematurely and that the product they delivered last year - Windows Vista - is a mere shadow of the original vision.

More at URL

 

Hmmm. Clever but not correct. It follows the Microsoft issued line of 2004 which has been shown to be self-serving and deflective.

Just to even the playing field, I thought I might take this opportunity to put a few surveyor spikes down so we can take at least a couple benchmarks to get a lay of the land, so to speak.

NECESSARY BACKGROUND

The first [1] is "What's Next" Should Be "What's Now" from February 2004 by Joe Wilcox, then a writer for Jupiter Research.

The next [2] regards “Longhorn Reloaded” from 2004. Longhorn reloaded is a curious phrase that happens to coincide with development of the cut versions of Microsoft Longhorn by outside developers over a recent seven (you read right 7) month period, achieving what Microsoft has not been able to accomplish in many years with very much money.

The next [3] is a Raging Bull VCSY Message Board post by myself (as Ajax203) writing at the time as Ajax203. My various usernames were necessary as numerous anti-VCSY posters infested the board and would goad others into arguments in order to have those posters removed by Raging Bull for violating Terms Of Service (TOS) conditions not connected with the discussion at hand. It's been guerilla posting on VCSY Raging Bull for seven (you read right 7) years with many of the original anti-VCSY people like DC-Steve and recy43 no longer operational under those names at least.

Why am I telling you this? Well, first, if you are a veteran of the posting wars, this is a set of triangulation markers so we can refresh our understanding as to what has taken place over the years.

If you are a newbie and don't know (probably don't really care except somebody shoved some info in your face and you're now curious) you've got a very long way to go before you will understand very much about what you're looking at. Lots of luck. You're going to need it. BUT, it may be some of the most valuable investigation and due diligence you will likely ever do.

yers truly - portuno

To Wit:

 

[1]

February 25, 2004
By Joe Wilcox
"What's Next" Should Be "What's Now"

Once again, Microsoft is on the "What’s Next" trail instead of "What’s Now." Longhorn evangelism videos, here, show the next-generation Windows capabilities applied to healthcare and real estate; ...

...I see Microsoft as spending too much time talking about Longhorn when it’s Windows XP that matters right now. Two weeks ago, I blogged on the failure of Windows XP evangelism, after taking a cue from colleague Michael Gartenberg (here and here). Yesterday, I blogged about Microsoft’s stance on security, which, related to Longhorn evangelism, is about how new products will solve existing problems.

The "future products will solve your existing problems" message is well worn out by Microsoft.

 

 

More at URL

[2]

March 03, 2004
By Joe Wilcox
Longhorn Reloaded

About two months ago, I started warning folks to watch for a major Windows Longhorn retrenchment in early 2004. I had expected Microsoft to seriously rethink its larger Longhorn strategy and make changes potentially as colossal as .Net. Around the beginning of the millennium, Microsoft made .Net into a "bet the company" strategy, but later backed away from its boldest ambitions: Moving into the subscription content and Web services market. Microsoft execs also have talked about betting the company on Longhorn.

I would consider last week’s Windows XP Reloaded announcement the first step in the Longhorn retrenchment process.

Longhorn is Microsoft’s boldest Windows upgrade plan since the company abandoned Cairo about a decade ago. The products share many similar design goals. But Longhorn’s delivery schedule--I’ve been saying no sooner than 2006--has been looking increasingly difficult to meet. As I blogged last week, Microsoft has too many pieces to put into place to realistically meet 2006; similarly, I see the colossal number of changes coming in Windows XP Service Pack 2 as giving businesses plenty of behavioral and software changes to contend with. SP2 could further slow Windows XP upgrades.

Already, slow upgrades have plagued Windows XP. As I blogged before (here, here and here), Microsoft hasn’t effectively evangelized Windows XP. That’s not a good situation, considering the growing hype around Linux. I would consider any company using older Windows versions--that’s one in five large businesses running version 95 somewhere--as candidates for Linux experimentation.

How much or how little a threat Linux poses to Windows is a topic for an upcoming report. Whether Linux is or is not a threat is immaterial; Microsoft clearly perceives a threat. In the latter 1990s, I doubted that Netscape could steal Microsoft’s operating system crown, but Microsoft saw enough of a threat to set off the so-called browser wars.

With Linux a perceived threat now in the backdrop of slow Windows XP conversions, Microsoft has plenty of good reasons to turn up the hype around its current OS and turn down the volume on Longhorn. Microsoft also has to be concerned too much Longhorn hype could further stall Windows XP upgrades. Worse, Longhorn will usher in so many changes, many businesses might further stall upgrades.

If the company looks seriously at the failure of Windows XP evangelism, the perceived Linux threat and Longhorn’s ambitious design goals, strategy retrenchment is a sensible approach.

Some news reports already are talking about XP Reloaded leading to a delay in Longhorn’s delivery. But, I see that as having been an inevitable outcome for some time. I would look for Microsoft to either push out Longhorn’s release or deliver a less ambitious upgrade within the original schedule. At least, those are two options I would recommend the company consider.

Posted by Joe Wilcox at March 03, 2004 09:53 AM

 

 

 

 

[3]

By: ajax203
04 Jun 2006, 06:09 PM EDT
Msg. 160258 of 186163

[a] excerpted:

One thing to think about. Tim Bray made his SOA BS comment public in his blog here:
http://www.tbray.org/ongoing/When/200x/2006/04/17/SOA-or-not
The End of SOA
Updated: 2006/04/18

(content is a rant by Tim Bray of Sun Microsystems regarding SOA as “vendor bull****” in Tim's words. I am simply passing his views to you.)

[b] excerpted:

from http://ragingbull.lycos.com/mboard/boards.cgi?board=VCSY&read=160235
March 29, 2006
Vertical Computer Systems, Inc. Receives a Notice of Allowance From The U.S. Patent & Trademark Office For a Patent Application Covering Various Aspects Of The XML Enabler Agent ...

 

 

More at URL

 

Mary Jo Foley appears to be following the Longhorn Reloaded activity in more than one place. Apparently there are a number of “nostalgic” developers out there who feel they were jilted by Microsoft's erasure of Longhorn history.

 

 

May 29th, 2007
There’s more than one way to reload Longhorn
Posted by Mary Jo Foley @ 4:37 am

The folks over at Joejoe.org aren’t the only ones with “Longhorn” nostalgia.

Enthusiasts over at the AeroXperience.org site also are looking to bring back Longhorn, a k a, the precursor to the Windows Vista release that Microsoft launched in January 2007.

The Joejoe.org Longhorn Reloaded team is looking to ressurect and retrofit a 2004 pre-release version of Windows so that it can be used as an alternative to Windows Vista.

The AeroXP “Vista Customization Square”/Retrophase team is looking to bring the existing Vista Aero interface to a pre-Longhorn-Reset version of Windows.

Incubating in our very forums is a project called ‘Retrophase.’ Think the reverse of ‘Longhorn Reloaded.’ Instead of bringing Windows Vista capabilities to the rotting Longhorn 4074 platform, the community is bringing Longhorn goodness to the shiny new Windows Vista platform,” blogged AeroXP member Rafael Rivera.

The Longhorn Reloaded effort kicked off in earnest last October; Retrophase started in June 2006. Last week, the Longhorn Reloaded team announced it had achieved Milestone 1 along its internally-set release timetable.

The existence of both of these projects raises a number of questions:

  • Once Microsoft “abandons” a code base, is it fair game for developers to use that code base to build a new product/technology? (I doubt Microsoft considers the Longhorn client code to be “abandonware,” as one member of Joejoe.org suggested, but this is still an interesting point to ponder….)

  • If Microsoft doesn’t “release” code — under some kind of open/quasi-open-source license as a platform atop which developers are encouraged to tinker — as was the case with, say, Visual FoxPro (the basis for Sedna/SednaX) –can the code still be used in that way?

  • Would Microsoft be open to the “community” keeping a discontinued/older code base alive? (The Visual FoxPro folks are requesting an answer on this very issue right now, with their call for Microsoft to release the FoxPro source code so that the community can keep continue to update it.)

 

What is “intellectual property” children? Is it work done? Or ideas acquired and kept locked up?

Or is it something intangible like “ownership”. It appears, no matter which way Microsoft turns on this question, the wolves have the buffaloes surrounded and are now nipping at those hooved feet to bring the big boys down.

 

 

 

UPDATE
I suspect this Longhorn Reloaded issue will blow into quite a firestorm before long. It's better to be informed than ignorant and anyone who believes what was told them in 2004 should take a re-read to make sure they weren't the unwitting victim and participant in an old-school flim-flam.

January 23rd, 2007
Rewriting Vista history
Posted by Mary Jo Foley @ 12:08 pm

What would have happened, on that fateful day of August 27, 2004, if Microsoft officials had said: "You know what? We messed up with Longhorn. And we're starting over."

Instead, as Microsoft historians know, Microsoft decided to cast its decision to gut the next version of Windows client as a "reset."

"We didn't do much — just took out WinFS, the Windows File System. Oh yeah — and back-port some of the stuff that was supposed to be exclusive to Longhorn to Windows XP. Other than that, it's full-steam ahead."

As Microsoft enthusiast Robert McLaws on Windows-Now.com notes, the Longhorn reset was really more of a do-over.

The Longhorn we first heard about as early as 2002 is not the Vista that Microsoft will launch next week on January 29. Fewer of the application-programming interfaces at its core are "managed," as opposed to "native," than Microsoft originally had hoped/expected. The integrated search is less capable and game-changing than the one Microsoft initially touted. In short, the product formerly code-named Longhorn is more evolutionary than revolutionary.

Like McLaws, I am not criticizing Microsoft for changing its course. I agree with him that the big mistake was not coming clean and admitting that Longhorn, as originally outlined, wasn't going to work. The stuff we saw at the Professional Developers Conference in 2003, which was Longhorn's first coming out party, looked snazzy. But Microsoft couldn't pull it off.

Being upfront about Longhorn — and, as McLaws also suggests — changing the code-name (Windows "Shorthorn," anyone?) to indicate it was not the same product could have changed the historical course and public perception of Windows Vista.

What if:

* the Vista development clock began ticking in August 2004, instead of August 2001? Microsoft could have claimed that Vista took just over two years (instead of five) to develop.

* Microsoft could have tabled WinFS sooner (and stopped spending countless cycles to get it to work well enough to make the centerpiece of Longhorn). The Softies could have sent WinFS to the SQL Server graveyard in 2004 instead of 2006.

* Microsoft could have dedicated some of its Windows development hands to Windows XP Service Pack (SP) 3 at an earlier point in time, thereby releasing the next XP service pack in 2005 or 2006, not in 2008.

Who knows … Microsoft might even have managed to get Vista out in time for the holiday 2006 buying season if the company had just been up front in 2004 that it was going to release a relatively minor, yet more stable, Windows upgrade two years on the heels of Windows XP SP2. (As Windows chief Jim Allchin himself has said,  XP SP2 really was a new version of Windows, not just a traditional service pack.)

Sure it's a lot of should-have/could-have/would haves. But definitely something worth pondering on the eve of the Vista launch.

Update: McLaws has some comebacks on my what-if Vista-history timeline.

Things you need to ponder: http://vcsy.blogspot.com/2007/05/bits-and-bites.html


Posted by Portuno Diamo at 1:13 PM EDT
Updated: Tuesday, 29 May 2007 3:43 PM EDT
Post Comment | Permalink

Newer | Latest | Older