Unfortunately, it's always the merchants who take the largest risk in accepting credit card payments.
Not so anymore. At least not in the UK. There are schemes in place that will move the vast majority of fraud liability on to the card issuers. It will mean a few more hoops for e-commerce transactions (specifically the entering of a password by the card holder) but I can tell you that there is a LOT of interest in this scheme.
Re:How many of us could actually mount a defense?
on
The Basics of EULAs
·
· Score: 3, Informative
A judge threw it out, fined Mattel a large amount and made them pay the guy's full legal fees.
Which is all fine and dandy if you can get your lawyers to work for free until the judgement. Otherwise Mattel didnt pay the legal fees they just gave him back what he had already paid. This, of course, relies on you having the money to mount a defence and take the risk of waving goodbye to it if you lose.
Surely bloggers that are willing to accept payment from a candidate would support that candidate and say 'good things' about them anyway.
I may not be from the US, but if I were I would certainly not be a Bush supporter and it would take a very large sum of money for me to publicly support Bush, far more than the value of my 'blogged opinions'.
It doesnt sound very well thought out to me.
Re:And let's not forget who is funding a lot of th
on
New and Improved SETI
·
· Score: 1
That assumes that the exploring of the vast expanse of practically nothing couldn't lead to anything that could help the masses.
I totally agree.
'It is unlikely that an alien race broadcasted the answer to earth's problems at the exact moment so that it reached us in the timeframe we are able to receive it (between the invention of the radio telescope and the extinction of humanity, which is likely a very short timespan on the glactic scale)'
This just seems like a fairly safe assumption to me.
Re:And let's not forget who is funding a lot of th
on
New and Improved SETI
·
· Score: 3, Insightful
Boo, hiss, where are the groups of objectors now?
Well me for one...
True, SETI is a 'sexy' project for geeks and sci-fi fanboys but how practical is it?
Even if this thing detects 'something' there will still be a large number of sceptics. The broadcasting 'E.T.s' had better be damn specific in their message so that it is clear to everyone on the planet that it was not naturally occuring. Otherwise it just an expensive way to piss off the religous fundementalists (and we have seen first hand what happens then!).
Also given the potential distances involved, a two-way conversion would be problematic at best.
Essentially, the best-case seems to be "We found a blip that could be something, but even if it was, it was broacast a few million years ago". Worst-case is that Mr Allen may as well wipe his backside with the banknotes.
In summary, we can all put our storm trooper costumes away. Darth Vader isnt coming to recruit anytime soon.
Personally, I feel that making sure everyone in the world has at least the basic... "Food, Water and Shelter" requirements of life would be a good first step for investment. We can explore the intriquing and unimaginable vast expanse of pratically nothing, later.
I did a quick google on the "JDO with Hibernate" think and couldnt find such a project. It was a vague recollection, perhaps I am mistaken. Although, there is talk about JBoss using hibernate to implement their CMP. Perhaps it was that...
I will definately take a second look at JDO. Seems that much has been happening their and so im probably a shade out of date.
I guess it boils down to the fact that on all of my recent projects, hibernate has handled the ORM and I have never really had cause to complain. If it aint broke, dont fix it, and designing to keep technology neutral covers my ass for when the next silver-bullet comes flying by.
Having said this, I have a project that is just starting and we are at the 'verticle slice' stage of development. Perhaps I will try converting our hibernate persistance layer to using a JDO implementation. It would be interesting to make the comparison without changing the other tools (velocity & spring at this point). I just may do this...
Perhaps I should have said defacto, free for commercial use, ORM mapping tool. Clearly this (slightly more restrictive) category doesnt currently include toplink (to my knowledge, the download on Oracle's site provides a version of TopLink that is licensed only for prototype development).
I guess the debate between JDO and Hibernate isnt really comparing apples to apples. JDO is a specification and Hibernate is a concrete API. I am vaguely aware of reading about somebody using Hibernate to implement the JDO spec (JBoss perhaps).
What is interesting is that Sun are actively pushing two persistance specs. JDO and the ever popular, entity beans. My money was on entity beans disappearing from the radar but with the new EJB work, inversion of control, Java 5 attributes etc, it sounds like EJB (including entities) are still alive and kicking at Sun.
So what criteria do you choose to decide on JDO vs Entities? Sun is telling us that both are enterprise ready, transactional, persistance storage access tools.
I am not aware of Hibernate's potential to scale, or the benefits that JDO provides for scalability but I will say that I rarely choose a library based on its ability to scale. With a clear set of interfaces that define the DAO's and a set of unit tests, changing between Hibernate and JDO probably wouldnt be much of a problem.
I generally find that even with a spec like JDO, a team still ends up specializing on the selected implementation. You are still 'buying into a product'. I remember looking at CORBA ORB products thinking "This is about 20% CORBA standard and 80% '...or why not try it OUR way' add-ons". Perhaps its not quite as bad in JDO implementations, but the potential is always there.
So pick a JDO implementation or pick Hibernate. Architect to abstract the choice from the rest of the system wite unit-tests to the interfaces and I guess it doesnt matter. Just comes down to preference (and usually the question "What am I/the team already familier with").
It is a shame that you see an arrogance in the Hibernate team. I have never seen this, but definatly have from JBoss. Now that hibernate is a JBoss project I truely hope the attitude transfer surgery wasnt part of the deal!
[i]you should definitely use JDO, not Hibernate. JDO is a standard[/i]
Im not sure I entirely agree with you here. JDO is a nice interface (certainly better than working with JDBC directly) but it is a persistance library designed to be all things to everyone. For instance, it should (in theory) support object databases and relational databases transparently.
Hibernate, on the other hand, is fast becoming the defacto ORM tool. It deals purely with relational databases and does so very well IMO. It may not be a documented standard, but I always put more weight behind tools that have been largely accepted by the community, whether documented or not. Hibernate passes this test.
I tend to lean towards hibernate with one, open implementation (no subtle differences of opinion regarding the 'spec' that you get with JDO), and I dont really see a large jump in uptake of object databases in the near future.
Then I type in how I think it is spelled and click the 'did you mean' link. Infact... it is not uncommon for me to use google as a spellchecker when I am unsure of the spelling of a word.
Bah! No way would they use unproven, unreliable machines that provide absolutely no audit trail for something as important and the gnome board of directors election!
Someone should start a blog that keeps the community up-to-date on the latest news from the technology world.
News on games, programming, evil corps attempting to charge licenses for popular open source operating system kernels, and when there isnt much news to reports, it could just present the older news again....
Hell, the format for an Apache password file is [user]:[crypted password], so the password file really doesn't do you much good
Actually, it does you a lot of good if you are into cracking.htaccess security. Just because that password is hashed doesnt mean it cant be bruteforced (which I admit can take some time), and I will wager than 90% of passwords on any site you have worked on where the user gets to choose their password can be cracked with a fairly simple wordlist.
A 'hacker' (using the term loosly) that want their porn for themselves only needs to get one of those passwords, and even someone planning to share will only need a few.
Other than that glaring inaccuracy, a very interesting post:o)
Slashdot Mirror
This critique doesnt happen to co-incide with the release of "Microsoft US high school 2005" does it?
Unfortunately, it's always the merchants who take the largest risk in accepting credit card payments.
Not so anymore. At least not in the UK. There are schemes in place that will move the vast majority of fraud liability on to the card issuers. It will mean a few more hoops for e-commerce transactions (specifically the entering of a password by the card holder) but I can tell you that there is a LOT of interest in this scheme.
Yeah, cos if the sun explodes.....
scientists have come up to a solution as to where all the matter in the universe actually is.
In the middle somewhere?
...and a little paper slip that you have to mail to the head office to get a 40% rebate on your limo to the award ceremony.
Our server hosting site is verisign??
Wow... live and learn.
A judge threw it out, fined Mattel a large amount and made them pay the guy's full legal fees.
Which is all fine and dandy if you can get your lawyers to work for free until the judgement. Otherwise Mattel didnt pay the legal fees they just gave him back what he had already paid. This, of course, relies on you having the money to mount a defence and take the risk of waving goodbye to it if you lose.
Surely bloggers that are willing to accept payment from a candidate would support that candidate and say 'good things' about them anyway.
I may not be from the US, but if I were I would certainly not be a Bush supporter and it would take a very large sum of money for me to publicly support Bush, far more than the value of my 'blogged opinions'.
It doesnt sound very well thought out to me.
That assumes that the exploring of the vast expanse of practically nothing couldn't lead to anything that could help the masses.
I totally agree.
'It is unlikely that an alien race broadcasted the answer to earth's problems at the exact moment so that it reached us in the timeframe we are able to receive it (between the invention of the radio telescope and the extinction of humanity, which is likely a very short timespan on the glactic scale)'
This just seems like a fairly safe assumption to me.
Boo, hiss, where are the groups of objectors now?
Well me for one...
True, SETI is a 'sexy' project for geeks and sci-fi fanboys but how practical is it?
Even if this thing detects 'something' there will still be a large number of sceptics. The broadcasting 'E.T.s' had better be damn specific in their message so that it is clear to everyone on the planet that it was not naturally occuring. Otherwise it just an expensive way to piss off the religous fundementalists (and we have seen first hand what happens then!).
Also given the potential distances involved, a two-way conversion would be problematic at best.
Essentially, the best-case seems to be "We found a blip that could be something, but even if it was, it was broacast a few million years ago". Worst-case is that Mr Allen may as well wipe his backside with the banknotes.
In summary, we can all put our storm trooper costumes away. Darth Vader isnt coming to recruit anytime soon.
Personally, I feel that making sure everyone in the world has at least the basic... "Food, Water and Shelter" requirements of life would be a good first step for investment. We can explore the intriquing and unimaginable vast expanse of pratically nothing, later.
I did a quick google on the "JDO with Hibernate" think and couldnt find such a project. It was a vague recollection, perhaps I am mistaken. Although, there is talk about JBoss using hibernate to implement their CMP. Perhaps it was that...
I will definately take a second look at JDO. Seems that much has been happening their and so im probably a shade out of date.
I guess it boils down to the fact that on all of my recent projects, hibernate has handled the ORM and I have never really had cause to complain. If it aint broke, dont fix it, and designing to keep technology neutral covers my ass for when the next silver-bullet comes flying by.
Having said this, I have a project that is just starting and we are at the 'verticle slice' stage of development. Perhaps I will try converting our hibernate persistance layer to using a JDO implementation. It would be interesting to make the comparison without changing the other tools (velocity & spring at this point). I just may do this...
BTW... Merry Xmas (Or politically correct alternative)
Perhaps I should have said defacto, free for commercial use, ORM mapping tool. Clearly this (slightly more restrictive) category doesnt currently include toplink (to my knowledge, the download on Oracle's site provides a version of TopLink that is licensed only for prototype development).
I guess the debate between JDO and Hibernate isnt really comparing apples to apples. JDO is a specification and Hibernate is a concrete API. I am vaguely aware of reading about somebody using Hibernate to implement the JDO spec (JBoss perhaps).
What is interesting is that Sun are actively pushing two persistance specs. JDO and the ever popular, entity beans. My money was on entity beans disappearing from the radar but with the new EJB work, inversion of control, Java 5 attributes etc, it sounds like EJB (including entities) are still alive and kicking at Sun.
So what criteria do you choose to decide on JDO vs Entities? Sun is telling us that both are enterprise ready, transactional, persistance storage access tools.
I am not aware of Hibernate's potential to scale, or the benefits that JDO provides for scalability but I will say that I rarely choose a library based on its ability to scale. With a clear set of interfaces that define the DAO's and a set of unit tests, changing between Hibernate and JDO probably wouldnt be much of a problem.
I generally find that even with a spec like JDO, a team still ends up specializing on the selected implementation. You are still 'buying into a product'. I remember looking at CORBA ORB products thinking "This is about 20% CORBA standard and 80% '...or why not try it OUR way' add-ons". Perhaps its not quite as bad in JDO implementations, but the potential is always there.
So pick a JDO implementation or pick Hibernate. Architect to abstract the choice from the rest of the system wite unit-tests to the interfaces and I guess it doesnt matter. Just comes down to preference (and usually the question "What am I/the team already familier with").
It is a shame that you see an arrogance in the Hibernate team. I have never seen this, but definatly have from JBoss. Now that hibernate is a JBoss project I truely hope the attitude transfer surgery wasnt part of the deal!
[i]you should definitely use JDO, not Hibernate. JDO is a standard[/i]
Im not sure I entirely agree with you here. JDO is a nice interface (certainly better than working with JDBC directly) but it is a persistance library designed to be all things to everyone. For instance, it should (in theory) support object databases and relational databases transparently.
Hibernate, on the other hand, is fast becoming the defacto ORM tool. It deals purely with relational databases and does so very well IMO. It may not be a documented standard, but I always put more weight behind tools that have been largely accepted by the community, whether documented or not. Hibernate passes this test.
I tend to lean towards hibernate with one, open implementation (no subtle differences of opinion regarding the 'spec' that you get with JDO), and I dont really see a large jump in uptake of object databases in the near future.
Then I type in how I think it is spelled and click the 'did you mean' link. Infact... it is not uncommon for me to use google as a spellchecker when I am unsure of the spelling of a word.
Bah! No way would they use unproven, unreliable machines that provide absolutely no audit trail for something as important and the gnome board of directors election!
Someone should start a blog that keeps the community up-to-date on the latest news from the technology world.
News on games, programming, evil corps attempting to charge licenses for popular open source operating system kernels, and when there isnt much news to reports, it could just present the older news again....
Now.... what to call such a blog...
Now... where have I heard that before???
In Soviet Russia new slashdot memes attempt to make YOU!!!
Using a reconfigured phaser?
Hell, the format for an Apache password file is [user]:[crypted password], so the password file really doesn't do you much good
.htaccess security. Just because that password is hashed doesnt mean it cant be bruteforced (which I admit can take some time), and I will wager than 90% of passwords on any site you have worked on where the user gets to choose their password can be cracked with a fairly simple wordlist.
:o)
Actually, it does you a lot of good if you are into cracking
A 'hacker' (using the term loosly) that want their porn for themselves only needs to get one of those passwords, and even someone planning to share will only need a few.
Other than that glaring inaccuracy, a very interesting post
Tell me, would you take a week to evaluate existing frameworks?
I should hope so, I have spent the better part of my Java career evaluating existing frameworks, and indeed, some of it writing them.
If you include porn sites....
[i]it seems that a hole has recently been found in the proof[/i]
He forgot to carry the 1
Or buying Diebold shares!
So, can I take my tin-foil hat off now?