The "One Laptop Per Child" project has a great device ready to ship, but there's no Java on there. Let's think about working together to put Java on OLPC!
We reported earlier that
JSR 291
has been submitted for final ballot via the JCP. However, the website has been unavailable due to 'look and feel'* issues
for more than a week
. You can bet that
Sun has already voted 'no'
-- what do you reckon the site will be down until after the deadline for voting on JSR291 has passed? And do you reckon that this is a co-incidence, conspiracy or just a cock-up?
* PS This is why look-and-feel issues are to be avoided. Use a native widget set instead
** PPS A few people have written in expressing doubt (or even flaming me) for even mentioning this as a possibility. For the humerously-challenged
it was meant as a joke
. I don't seriously believe that there's any relation between the JCP site being down and any JSRs that are undergoing current approval; in any case, given a choice of {co-incidence,conspiracy***,cock-up} then it's always the former or, as in this case, the latter. I shall put signs up to warn the unwary in the future.
*** Unless you live in a trailer park. In that case, they really *are* out to get you.
Re: JCP.org down; co-incidence, conspiracy or cock-up?
It's going a bit far to suggest this might be a conspiracy. There are plenty of other activities at the JCP at the moment that are being held up by the website problems.
Well, as someone not associated with any of the JSR's, app servers, or IDE's I get to add my opinion without any strings attached (although I do support Alex's trend of not pussy-footing around issues)...
> The changes at jcp.org are not look and feel based,
> but a fundamental reworking of the underlying guts of
> the site.
Fundamental reworking? How about they try a fundamental reworking of their project management skills? How can you possibly take down such an important website with such a screw up? What happened to test migrations and site backups?
>
> Unfortunately, this is a classic IT project running
> late and repeatedly slipping deadlines.
Why would they undertake site changes if the project is running late? If the project was mismanaged or under estimated, why wouldn't they approach the upgrade with extreme caution and have an easy back out plan?
> I expect this
> to take a while longer to fix.
So much for an intelligent, comprehensive, cohesive migration plan...
>
> Any link to JSR 291 is just FUD.
Yeah, and it sounds like any link to proper planning is badly mistaken.
This is absolute CRAP. Someone with the proper authority and information should layout a detailed explanation of their version of How To Take Down Your Website During a Migration 101 (or Poor Planning + Poor Execution = Egg on the Face for an entree + Humble Pie for dessert)
>
> Stephen Colebourne
> Co-spec lead JSR-310, Date and Time API
Re: JCP.org down; co-incidence, conspiracy or cock-up?
You honestly think that JSR-291 is relevant or important enough for anyone to give that much of a shit? This is an idiotic entry and you should be ashamed of yourself for even suggesting it. If anything, it reflects terribly on the proponents of JSR-291, who have been banging their wardrums and making idiotic proclamations throughout.
You're hurting your cause by saying this sort of crap, and encouraging people like me to view you all as a bunch of religious fruitcakes.
Re: JCP.org down; co-incidence, conspiracy or cock-up?
Hani, can you at least read the thread before releasing your stream of bile? No, Alex does not honestly think that the JCP was shutdown just to kill JSR 291, as he clearly said.
Shame on him? No, shame on the incompetents who let this happen to the JCP. Doesn't send a great message about using Java for enterprise websites, does it? I'm sure that the LAMP and Rails communities are pissing themselves laughing over this. Assuming of course that JCP.org does run on Java; it would send an even worse message if not.
As for the religious fruitcake thing, well, every technology has some people who get a bit religious about it. At least Alex knows his God exists, and has done since 1999
JCP.org down; co-incidence, conspiracy or cock-up?
At 5:37 AM on Mar 26, 2007, Alex Blewitt
wrote:
* PS This is why look-and-feel issues are to be avoided. Use a native widget set instead
** PPS A few people have written in expressing doubt (or even flaming me) for even mentioning this as a possibility. For the humerously-challenged it was meant as a joke . I don't seriously believe that there's any relation between the JCP site being down and any JSRs that are undergoing current approval; in any case, given a choice of {co-incidence,conspiracy***,cock-up} then it's always the former or, as in this case, the latter. I shall put signs up to warn the unwary in the future.
*** Unless you live in a trailer park. In that case, they really *are* out to get you.
13 replies so far (
Post your own)
Re: JCP.org down; co-incidence, conspiracy or cock-up?
It's going a bit far to suggest this might be a conspiracy. There are plenty of other activities at the JCP at the moment that are being held up by the website problems.So my vote is for "cock-up".
Re: JCP.org down; co-incidence, conspiracy or cock-up?
So am I to understand it that Gosling was the second gunman on the grassy knoll?Re: JCP.org down; co-incidence, conspiracy or cock-up?
I wonder. Is a Gosling gun a smaller relative of the Gatling gun?Alex.
Not look and feel
The changes at jcp.org are not look and feel based, but a fundamental reworking of the underlying guts of the site.Unfortunately, this is a classic IT project running late and repeatedly slipping deadlines. I expect this to take a while longer to fix.
Any link to JSR 291 is just FUD.
Stephen Colebourne
Co-spec lead JSR-310, Date and Time API
Re: JCP.org down; co-incidence, conspiracy or cock-up?
Actually, Napoleon Bonaparte said this better:"Never ascribe to malice that which is adequately explained by incompetence."
Re: Not look and feel
More like TIC (Tongue In Cheek) than FUD, but one wonders why the old system can't be left as-is until the new system is up and running.Alex.
Re: Not look and feel
Well, as someone not associated with any of the JSR's, app servers, or IDE's I get to add my opinion without any strings attached (although I do support Alex's trend of not pussy-footing around issues)...> The changes at jcp.org are not look and feel based,
> but a fundamental reworking of the underlying guts of
> the site.
Fundamental reworking? How about they try a fundamental reworking of their project management skills? How can you possibly take down such an important website with such a screw up? What happened to test migrations and site backups?
>
> Unfortunately, this is a classic IT project running
> late and repeatedly slipping deadlines.
Why would they undertake site changes if the project is running late? If the project was mismanaged or under estimated, why wouldn't they approach the upgrade with extreme caution and have an easy back out plan?
> I expect this
> to take a while longer to fix.
So much for an intelligent, comprehensive, cohesive migration plan...
>
> Any link to JSR 291 is just FUD.
Yeah, and it sounds like any link to proper planning is badly mistaken.
This is absolute CRAP. Someone with the proper authority and information should layout a detailed explanation of their version of How To Take Down Your Website During a Migration 101 (or Poor Planning + Poor Execution = Egg on the Face for an entree + Humble Pie for dessert)
>
> Stephen Colebourne
> Co-spec lead JSR-310, Date and Time API
Re: JCP.org down; co-incidence, conspiracy or cock-up?
You honestly think that JSR-291 is relevant or important enough for anyone to give that much of a shit? This is an idiotic entry and you should be ashamed of yourself for even suggesting it. If anything, it reflects terribly on the proponents of JSR-291, who have been banging their wardrums and making idiotic proclamations throughout.You're hurting your cause by saying this sort of crap, and encouraging people like me to view you all as a bunch of religious fruitcakes.
Re: JCP.org down; co-incidence, conspiracy or cock-up?
This was a tongue in cheek post for those people with a sense of humour. Sorry that you're not one of them.Alex.
Re: JCP.org down; co-incidence, conspiracy or cock-up?
Hani, can you at least read the thread before releasing your stream of bile? No, Alex does not honestly think that the JCP was shutdown just to kill JSR 291, as he clearly said.Shame on him? No, shame on the incompetents who let this happen to the JCP. Doesn't send a great message about using Java for enterprise websites, does it? I'm sure that the LAMP and Rails communities are pissing themselves laughing over this. Assuming of course that JCP.org does run on Java; it would send an even worse message if not.
As for the religious fruitcake thing, well, every technology has some people who get a bit religious about it. At least Alex knows his God exists, and has done since 1999
Re: JCP.org down; co-incidence, conspiracy or cock-up?
You guys crack me upRe: JCP.org down; co-incidence, conspiracy or cock-up?
sometimes it's more fun for me to come in late to conversations. the mix of sarcasm, bile and rebuke always finishes my day off right.Re: JCP.org down; co-incidence, conspiracy or cock-up?
> Actually, Napoleon Bonaparte said this better:>
> "Never ascribe to malice that which is adequately
> explained by incompetence."
Very true.