Quantcast
Channel: Planet Apache
Viewing all 9364 articles
Browse latest View live

Ben Hyde: Insurance Deductables

$
0
0

My father was wrong.  I learned at my father’s knee that it is wise to self insure for the little things and buy insurance for the big things.  Thus it is clever and thrifty to buy insurance policies with large deductibles.   It is a little odd to notice that poor people should buy more comprehensive, and hence expensive insurance.  Large economic actors can afford to self insure more than smaller ones; so for example a Billionaire may minimal car insurance – since if he can casually afford to replace the car – but he will carry a substantial personal liability policy since replace his wealth would be harder.   Firms often self insure and some even gin up their own employee health insurance systems.

This advice turns out to be wrong, for most of us.  There are three reasons.  The simple reason: people buy high deductible policies not because they can afford to cover the cost of small loses, but because they don’t have a clue what they are buying.   Secondly the marketing of these things is entirely a pure confusopoly; buyers haven’t got a chance.  But the third reasons is interesting.

Insurance has plenty of adverse selection and agency problems.  Nominally a benefit of self insuring is that your less like to engage in some risky behaviors since you will personally bear the cost.  On the other had you remove any incentive for the insurance company to bring it’s scale advantages to into the equation; e.g. the insurance company is likely to work for systemic improvements that reduce risk.

So there is an argument to be made that my father’s advice might be wrong.  I noticed this because I have a few medical bills on next to me.  My health insurance includes a deductible.  What I notice about these bills is that I am not getting the prices the insurance company negotiated with the providers.  I am paying full price!  Note that agency is not all bad; since agency creates a locus for skill.  In this case I have lost access to both of these.  Having taken the choice to self insure for the amount of the deductible I now have the option to simulate the skills of the insurance company – i.e. I can call these providers and attempt to negotiate a discount … or not.

So this is another interesting story about middlemen.  There are three actors in this story; the service providers, the insurance company, and the service consumers.  I’m am fascinated to notice a new move in the game that can takes place during the negotiation between the insurance company and the providers.  In exchange for a reduction in prices the insurance company assures the providers that it will sell more high deductible policies.  That’s great for the providers since they can then charge those consumers the list price.  To fulfill the promises made during this negotiation the middleman may have to set goals to assure he sells enough of the high deductible policies.

That shapes the market in very perverse ways.  The small jobs become the high profit work.  My father’s advise become obsolete.  How weird is it that purchasing high deductible policies is a form of free riding – since as long as the insurance company price control feedback is working effectively you get the prices and quality provided by that loop without paying for it.

This is all marvelously and distressingly perverse.  Since poor and innocent people tend to mistakenly purchase high deductible policies (do to regulatory failure enabling market failure) this process shifts costs onto poor people.  I also think this explains why the last car I bought had a bumper design that was prone to failure who’s repair was just bellow the typical deductible.  The dealers presumably like that.   The usual feedback loop thru the insurance company that would fix it wasn’t just broken – somebody removed it.


Tony Stevenson: Just been to the physio…

$
0
0

I went to see a physio tonight after suffering with arm and shoulder pain for the past 5/6 weeks after being knocked off my bicycle at about 25mph when a pedestrian stepped out in front of me..

Looks like I will be missing badminton for at least one more month, which is a shame as i will likely miss the start of the season now.

No exertion of the arm either, means chaining my cycling position. Which is good as that will coincide with me wanting to get my new bicycle..

Bah humbug!

Tony Stevenson: Apachecon NA 2010 – Register now

$
0
0

Registration for this years Apachecon is now open, you can visit the site here and click on the register for the conference icon

Whilst your three why not take a look at the conference schedule and see which talks and meet ups you want to go to. You can even download the schedule as an ics file and import it unto your favourite calendar.

Go sign up now!

Justin Mason: Links for 2010-08-12

$
0
0

Jay D. McHugh: Did you miss me...

$
0
0
I had these grand plans for this blog and I think that those big plans kept me from keeping active here.

I thought that I needed to have something big and important to say before I said anything.

I am going to try to get over that.

Small things can be important too.

Jay D. McHugh: Big snakes and programming...

$
0
0
I have started trying to learn Python again.

This time, I am using the book "Hello! Python" by Anthony Briggs.

I am only a few chapters in so far, but it is an easy read.  It is going fairly slowly for me, but that is because its audience is beginning programmers.  And, it seems like it would be great for new programmers (or hobbyists) getting started with Python.

The book is still in its 'early access' phase, so it is only available online as a PDF.  But, you can order it as a 'real' book too and get a copy in digital form to start on while you are waiting.

Andrew Savory: Oracle vs. Google

$
0
0

This is 'fun':

"Oracle filed a complaint in federal court in California, alleging the infringement of seven patents and copyrights by Google's Android mobile operating system software."

http://www.marketwatch.com/story/oracle-sues-google-for-patent-infringement-2010-08-12

"Android (including without limitation the Dalvik VM and the Android software development kit) and devices that operate Android infringe one or more claims of each of United States Patents Nos. 6,125,447; 6,192,476; 5,966,702; 7,426,720; RE38,104; 6,910,205; and 6,061,520."

http://news.cnet.com/8301-30684_3-20013546-265.html

One of the most interesting things about Google's Android was the way in which they leveraged Java for the developer whilst NOT paying Sun royalties for the Java runtime (JRE) shipping on mobiles. They did this by compiling Java source code down to their 'Dalvik' virtual machine, which is responsible for running the code on mobile phones. By using Dalvik and not the JRE, the theory was that there could be no claim by Sun for per-unit royalties.

(For the definitive explanation on how this works, see Stefano's Dalvik: how Google routed around Sun's IP-based licensing restrictions on Java ME.)

Sun was bought by Oracle earlier this year. Since then, a significant number of key people have left Sun/Oracle, including for example James Gosling, 'the father of java'; Tim Bray, a very visible spokesperson and early inventor of XML, who now lives at Google; and Simon Phipps, who was chief open source officer of Sun and facilitated the release of many of Sun's core products under open source licenses.

There's also been much commentary on how Oracle are throwing out a lot of open source projects, which have since been picked up by new companies (e.g. ForgeRock, which also recruited Simon Phipps). Most recently, it became apparent that the next version of Solaris (Sun's UNIX operating system) is being developed behind closed doors, with only the expectation of some open source dumps after Solaris 11 is released. The open source community is routing round this, with the Illumos project kicking off to provide life to what's left of this Linux-competing has-been platform.

My predictions:

  • There will be a lot of noise about the patent risks of Android over the coming months, and a lot of pronounced wariness about adopting it, but it will not dent Android's momentum in the marketplace nor actual adoption rates. This freight train ain't stopping for anyone.
  • Oracle will lose (there's a reason why Sun didn't strike at the time). Oracle will irrevocably harm their 'governance' of the Java platform in the process (companies that opt for patent warfare over innovation are not viewed kindly).
  • When Oracle fail, this may even herald a new era of Java on mobile, as multiple Dalvik-like alternatives spring up - or clean room open source JREs spring up even during the suit.

It's also great news for MeeGo (and marginally LiMo), as it underlines my comment the other day: operators have a vested interest in a degree of open source mobile platform fragmentation, and an Android monoculture is just as dangerous to them as an iPhone monoculture. Practically speaking, don't expect this to result in showers of operator cash on the other open source platforms, though. The operators are more likely to spend that money on expensive risk-assessment exercises with their lawyers ;-)

Update 09:29: Miguel's Initial Thoughts on Oracle vs Google Patent Lawsuit has some great context on this, including Sun shopping around 'the rights to a lawsuit', which makes a fair degree of sense. Maybe that's why Sun didn't sue, rather than the reputational aspects or relative likelihood of failure. I guess we'll have to see how this one plays out.

Update 13:03: Carlo's Oracle/Google: the patents and the implications is a pretty thorough review of the situation, too.

Claus Ibsen: Camel in Action - Is a bestseller

$
0
0
Manning recently published their bestsellers and Camel in Action made into the top 15.

Top 15 books year to date at manning.com based on combined ebook and pbook sales

  1. Spring in Action, Third Edition
  2. jQuery in Action, Second Edition
  3. Secrets of the JavaScript Ninja
  4. Lucene in Action, Second Edition
  5. Ext JS in Action
  6. C# in Depth, Second Edition
  7. The Joy of Clojure
  8. iPhone and iPad in Action
  9. iText in Action, Second Edition
  10. Camel in Action
  11. Clojure in Action
  12. ActiveMQ in Action
  13. Groovy in Action, Second Edition
  14. The Art of Unit Testing
  15. SQL Server MVP Deep Dives

This is fantastic news for the Camel community, showing there is a great interest in Camel. In fact it may seems like there are more demand for Camel than some of the other integration frameworks which have books as well. For example neither Mule in Action, nor Spring Integration in Action is listed as bestseller.

To celebrate this Manning is giving a 40% promoting discount. Through August 18, we invite you to enjoy any of these Manning bestsellers for 40% off the regular price. Just enter bestseller40 in the Promotional Code box when you check out at manning.com.

You can find the announcement from Manning here.

Steve Loughran: How to win friends and influence people: oracle sues google

$
0
0

The first thing I see on the Planet Apache feed is the news that Oracle are suing Google over Dalvik and, implictly, Apache Harmony

This is really going to cause fun in the open source world. I can see a fork coming on. Can you trust Oracle not to add features to Java just because they have patents on it?

Google Android must be wonderful and terrible for the Java team. Wonderful, because it finally supported the Java language on mobile phones on a platform that was actually good, finally built an application ecosystem. This was the reason why when Sun open sourced Java, they made sure the mobile version was GPL, so anyone embedding it in a phone would be motivated to pay $ for the real thing. Even if it was $0.15 a phone, at scale, that becomes profit. Which is why Sun wouldn't give Apache the test kit for the Harmony Runtime unless the ASF said "not to be used in mobile/embedded devices" (as if they could), and it's hence why Java 7 development has stalled (trouble in the Java oversight group). What development does go on uses the term "JDK 7" to get around the stalemate. Did all that posturing help Sun get Java into phones? Nope.

Android ships with Dalvik, which is not quite Java, according to Stefano, and I believe him.

However, there are patent issues, and had Sun given the ASF access to the TCK -as I believe they were obliged to do- those would have gone away, as compliant implementations get rights to those patents when they pass the tests. But by keeping the TCK, Harmony couldn't pass the tests, could it?

The other funny is that if you look at the complaint, you see at the top the names "BOIES, SCHILLER & FLEXNER". If I am not mistaken, they are the lawyers behind SCO's copyright lawsuit against IBM and Novell about Linux being based on Unix. Well, that was successful wasn't it? I consider, as I type this on my home laptop running Ubuntu 10.4 as every physical computer I use at work also does, from the desktop to the datacentre. It was such a good idea it created a whole web site Groklaw.

Looking forward to this. It could be entertaining.

Robert Burrell Donkin: An Update

Andrew Savory: Blogging elsewhere

$
0
0

Here's a quick summary of the articles I've had posted over on the LiMo Foundation blog. This is in some small part an apology for being so quiet here. I'll try to keep this list up-to-date:

Some other content is well worth reading over there, including:

  • David Kordsmeier's Mobile Java Matters, which is particularly pertinent and prescient right now: "For the LiMo Foundation, for the Apache Foundation, and for our friends at Google, getting Sun's OK to move ahead with the dream of what Java could be is no longer necessary. We have to strike out on our own."
  • Mal Minhas' LiMo publishes the list of open source components in its platform. Publishing a list of components is not ground-shaking or innovative, but serves as a useful point of comparison / information on what goes into a modern Linux mobile stack. Do read the article though, for the discussion of costs driving the software bill of materials. This is why per-unit licensing must not become the de facto norm in mobile platforms.
  • Also by Mal, Analysing the Economics of Open Source. Useful for anyone trying to understand the importance of working with upstream projects.

Enjoy!

Jan Materne: Extend Windows-Search in Windows 7

$
0
0

I wanted to search for a string in Java properties files. I knew that there was one entry – somewhere deep in the codebase … But the search from Win7 didnt find it.

Sounds familiar? So read further …

I remembered that the search works only on particular files (doc, ppt …) and my properties files are not in that list. :-(
So I wanted to tune the search:

Open the system configuration via the start menu and type „search“ into the search field. You should find the „index options“ somewhere.

Press the „Advanced“ button (translated from the German „Erweitert“) and swith to the second „file types“ tab.

Here you can add additional file types by their suffix and specify their index option (only file information, file content).


Reindexing needs time …. but I hope after this I will be able to find my file ;)


Justin Mason: Links for 2010-08-13

Bryan Pendleton: Trinity Alps backpacking

$
0
0
Herewith, a short report on a delightful 5 day backpacking trip to the Trinity Alps.

The Trinity Alps Wilderness Area is a large protected wilderness located inside the Shasta Trinity National Forest in far northern California. It is one of the largest wilderness areas in California, and also one of the least visited.

We drove up from the Bay Area on Saturday afternoon, and spent the night in Weaverville at the Red Hill Cabins. Sunday morning we arose early, picked up sandwiches and coffee at the local Tops market, and headed up California 3 toward the Trinity Alps. At Trinity Center, where Swift Creek enters Trinity Lake (formerly Clair Engle Lake, which is a story all to itself), we left the paved road and drove 8 miles on Forest Service dirt roads up to the Poison Canyon trailhead. Trinity Center is at about 2,500 feet elevation, while the trailhead is at 4,100 feet elevation; the Forest Service road took almost 45 minutes to drive.

When we got to the trailhead, we were a trifle concerned when we noticed that the brand new Toyota 4Runner parked there had been apparently attacked by a bear: there were paw marks on the windows; two fiberglass side panels were torn off the car and lying on the road; and when we looked into the car window, a cooler was sitting open on the back seat. We had no food to leave in the truck, so we carefully moved our overnight bags of spare clothes into the center-front of the truck bed, covered them with a grey blanket, closed the truck up tight, and hoped for the best.

From BryanTrinityAlps2010


The Poison Canyon trail leads upward along the North Fork of Swift Creek, staying close enough to the creek to hear the water, but not close enough to see the creek. The trail is steep: it climbs 1,800 feet in just 2 miles, which is about a 17% average grade. Happily the trail leads mostly through shaded woods and pleasant meadows, so even though it is steep and unrelenting, we took our time and enjoyed the walk. Poison Canyon is apparently named due to a type of grass which grows there, which is indigestible by the livestock. Of course, we backpackers refrained from chewing the plants...

As the trail rises through the canyon, we start to see views of towering Ycatapom Peak, the 7,600 primary landmark of the area.
From BryanTrinityAlps2010


After a long break for lunch, we arrived at Lilypad Lake in mid-afternoon, and spent a few hours selecting the best campsite and setting up camp. As the guide books had predicted, we had the canyon to ourselves, and so we picked a great campsite high on the boulders above the lake, near the feeder stream with its pleasant running water. Firewood is abundant in this area of the Alps, and we had an enjoyable campfire before an early night, as we were all quite tired.

From BryanTrinityAlps2010


Monday morning we headed up the Thumb Rock trail above Lilypad Lake. Again, this trail is very steep, but since we were only carrying light day packs it was much more tolerable, and we made good progress. The trail takes you quickly up 600 feet above the lake, where the views of Mount Shasta are tremendous! We climbed a bit further, past the junction with the Deer Flat trail, to a knoll above Poison Canyon with a spectacular view, at about 7,000 feet of altitude. After lunch, we hiked a bit further, to the crest of the Parker Divide, where we got a 360-degree view of the eastern Trinity Alps, including the Parker Creek canyon, Cub Wallow, and Deer Flat. We split up, with Roger and Rich heading off to climb Thumb Rock's neighbor peak (elev. 7735), while Mike, Deb, and I returned back down the switchbacks to Lilypad Lake for some rest, book reading, and wildlife study.

From BryanTrinityAlps2010


The shooting stars were great on Monday night! I think we were 3 days early for the Perseids, but we still saw lots of meteors.

Tuesday morning dawned cold and grey, with heavy clouds overhead. Tired and a bit discouraged, we cancelled our plans to take the 8 mile (round trip) hike over to Boulder Lake, and instead decided to play campground games: horseshoe golf, poker, and rock skipping were all favorites. Unfortunately Rich didn't get to use his fishing pole; maybe next year!

Wednesday we broke camp and headed back down to the trailhead. Happily, Mr. Bear had decided that there was nothing worth fighting for in the truck, and we sailed back down the dirt road, through Weaverville, back to I-5, and (eventually) made it home to the Bay Area for the conclusion of another great trip.

For more pictures, see my online web album!

Ben Laurie: FreeBSD Capsicum

$
0
0

I mentioned FreeBSD Capsicum in my roundup of capability OSes earlier this year without mentioning that I am involved in the project. Since then we’ve managed to port and sandbox Chromium, using less code than any other Chromium sandbox (100 lines), as well as a number of other applications. Also impressive, I think, is the fact that Robert Watson managed to write this sandbox in just two days, having never seen the Chromium codebase before – this is as much a testament to Robert’s coding skills and the clean Chromium codebase as it is to Capsicum, but nevertheless worth a mention.

Anyway, at USENIX Security this week, we won Best Student Paper. A PC member described the paper to me as “excellent” and “very important”. Robert has also blogged about it rather more eloquently than I can manage at this time in the morning.

You can read the paper, too, if you want.

Even more exciting, FreeBSD 9 will include the Capsicum capability framework, allowing the peaceful coexistence of capability and POSIX programs. Although this has been attempted before, as far as I am aware all previous versions have put a POSIX emulation layer on top of a capability system, rather than grafting capabilities onto POSIX. Since Capsicum is highly efficient and FreeBSD is a perfectly sound and portable system (and my server OS of choice), this opens up the possibility of a gradual migration to capabilities, something that has been problem up to now.

Robert and I (and a host of others) are continuing our research into practical capability systems, Robert at Cambridge and me at Google. Work is also in progress to port Capsicum to Linux.


Jan Materne: Another Admin job Hudson: ensure that there are not too many old builds …

$
0
0

Especially if you have a large number of jobs and they are running more often, you’ll come to a point, where your disk is full of old builds.

Hudson provides a configuration parameter for that: „discard old builds“. This will delete old builds according to the specified number of days or number of builds.

For Apache I wrote a script which ensures, that all jobs have „discard“ setting and that existing values are not higher than a defined maximum value.

/** Default-Setting for the "number of old builds" */
numberOfOldBuilds  = 10

/** Maximum of "number of days" */
maxDaysOfOldBuilds = 14

/** Should we override existing values? */
overrideExistingValues = true

/** Closures for setting default 'max number' */
setMaxNum = { job ->
   job.logRotator = new hudson.tasks.LogRotator(-1, numberOfOldBuilds)
}

/** Closures for setting default 'max number' */
setMaxDays = { job ->
 job.logRotator = new hudson.tasks.LogRotator(maxDaysOfOldBuilds, -1)
}

// ----- Do the work. -----

// Access to the Hudson Singleton
hudsonInstance = hudson.model.Hudson.instance

// Retrieve all active Jobs
allItems = hudsonInstance.items
activeJobs = allItems.findAll{job -> job.isBuildable()}

// Table header
col1 = "Old".center(10)
col2 = "New".center(10)
col3 = "Job".center(50)
col4 = "Action".center(14)
header = "$col1 | $col2 | $col3 | $col4"
line = header.replaceAll("[^|]", "-").replaceAll("\\|", "+")
title = "Set 'Discard old builds'".center(line.size())

println title
println line
println header
println line

// Do work and create the result table
activeJobs.each { job ->

 // Does the job have a discard setting?
 discardActive = job.logRotator != null

 // Enforce the settings
 action   = ""
 newValue = ""
 oldValue = ""
 if (!discardActive) {
 // No discard settings, so set the default
 setMaxNum.call(job)
 action   = "established"
 newValue = "$numberOfOldBuilds jobs"
 } else {
 // What are the current settings?
 oldDays = job.logRotator.daysToKeep
 oldNums    = job.logRotator.numToKeep

 if (oldNums > 0) {
 // We have a set value for 'numbers'
 if (oldNums > numberOfOldBuilds && overrideExistingValues) {
 // value is too large so set a new one
 setMaxNum.call(job)
 action   = "updated"
 newValue = "$numberOfOldBuilds jobs"
 oldValue = "$oldNums jobs"
 } else {
 // Correct value or we arent allowed to override.
 oldValue = "$oldNums jobs"
 }
 } else {
 // we have a value for 'days'
 if (oldDays > maxDaysOfOldBuilds && overrideExistingValues) {
 // value is too large so set a new one
 setMaxDays.call(job)
 action   = "updated"
 newValue = "$maxDaysOfOldBuilds days"
 oldValue = "$oldDays days"
 } else {
 // Correct value or we aren't allowed to override.
 oldValue = "$oldDays days"
 }
 }
 }

 // String preparation for table output
 oldValue = oldValue.padLeft(10)
 newValue = newValue.padLeft(10)
 jobname  = job.name.padRight(50)

 // Table output
 println "$oldValue | $newValue | $jobname | $action"
}
println line

// Meaningful output on the Groovy console
// (the console will output the result of the last statement)
printout = "Number of Jobs: $activeJobs.size"

In the first section I define the „constants“ (line 001-008). After that I define two closures which update a given Hudson job (line 010-018).
The basic structure is the one I used in earlier scripts
The work here is in lines 053-088. But that’s pretty easy: check the given values and eventually set new values using the pre defined closures.
New is the last line: I dont use a >x = „“< instruction for suppressing the output. I use a more meaningful message: the number of jobs.


Jochen Wiedmann: Bad news for Oracle

$
0
0
I think this is bad news for Oracle: Groklaw will cover the Oracle-Google litigation on Java patents allegedly violated by Android's Dalvik JVM.

Well deserved. If big companies believe that software patents are a good thing, then only because there is a balance between 'em. Assuming that Oracle is not by itself violating one patent or the other is ridiculous. Now Oracle has annihilated this balance. Just at the same time when they announced to drop OpenSolaris. I think they'll soon learn that Google is not the only opponent they have acquired. A pinprick (Bugzilla's main developer requests dropping Oracle support as a consequence of the patent litigation.) is only a pinprick, but we'll see how many of them will follow.

If I were a Google lawyer, I'd definitely follow Groklaw in the months and possibly years to come: Groklaw's much more than a pinprick.

Isabel Drost: Scrumtisch August Berlin

$
0
0

Just seen it - the next Scrumtisch Berlin has been scheduled for 25th August 2010 at 18:30 Uhr. So far, no official talk has been scheduled, so please expect two topics on Scrum and its application to be selected for discussion according to Marion’s agile topic selection algorithm.

Please talk to Marion Eickmann if you would like to attend the next meetup.

Bryan Pendleton: Help me understand this Oracle/Google lawsuit

$
0
0
I'm confused about the ideas behind the Oracle-Google lawsuit announced last week. The facts are clear enough: Oracle sued Google in the US District Court for the Northern District of California, for infringing on copyrights and patents related to Java, saying that:

Android (including without limitation the Dalvik VM and the Android software development kit) and devices that operate Android infringe one or more claims of each of United States Patents Nos. 6,125,447; 6,192,476; 5,966,702; 7,426,720; RE38,104; 6,910,205; and 6,061,520.


What's considerably less clear is what Oracle is really mad about, and what they want Google to do. In the software industry, patent law is a clumsy tool, and when it is exhibited in this fashion, as this Forbes blog suggests, it usually indicates that something else is going on behind the scenes.

As Bruce Perens points out, the Java Language Specification includes a broad patent grant. Is Oracle claiming that Google violated that grant?

Or, as suggested by this ComputerWorld analysis, is Oracle claiming that Google, who have hired many prominent engineers from the original Sun Java team, could not possibly have followed true "clean-room" techniques when building their Dalvik/Android system?

Or, as Bruce Perens notes in a follow-up article, is the debate about whether Google's version of Java is really compliant to the Java standards and specifications, and, if not, whether that means they cannot call their implementation "Java", similar to the objections that Sun had over Microsoft's not-quite-the-same version of Java years ago?

Or, as suggested by this article, is Oracle trying to save whatever is left of Java Micro Edition, which had achieved a moderate amount of success in the cell phone market, but which is now being crushed by Android's runaway adoption? And, as this article speculates, will this just play into the hands of Microsoft and their lagging, but technically very advanced, .NET mobile platform?

It's all very confusing.

When Android first came out, I was excited by the possibility of an open Java-based mobile computing platform, and I downloaded the Android development tools and tried to write some applications. But I was quite shocked to see that Derby, which is one of the most portable, highest-quality Java applications in existence anywhere, would not run on the Android platform:

  • Derby's use of common Java APIs, such as javax.naming, ran afoul of Android's selective inclusion of the JDK API set

  • Derby's on-the-fly generation of Java byte code, for execution of query plans, ran afoul of Android's custom Dalvik VM, which doesn't interpret standard Java byte code, but rather requires that Java byte code be re-compiled into Dalvik code.


After those discoveries, I gave up in disgust, so there may be more such obstacles lurking. But those incompatibilities were large and severe, and I can see that Sun/Oracle would be upset by them. It brings back memories of the Sun-Microsoft fights over Java last century, when Microsoft similarly produced their own not-quite-the-same version of Java, and Sun fought bitterly to force Microsoft to abandon that technology.

What will happen here? Does it make sense to you? If you have any ideas to share, or pointers to clear and well-written analysis, please let me know!

Sam Ruby: Empty Nest

$
0
0

Melyssa Allen: Meredith College will welcome new students during Move-In Day this Saturday, Aug. 14.  The College expects approximately 375 students.

One of those is our daughter.

Viewing all 9364 articles
Browse latest View live




Latest Images