I guess you haven't been to your local record store in a while (neither have I, for that matter). But I do know they happen to have a large collection of Classical CDs covering probably everything you know about classical music and then some for the paltry sum of less then $5. The quality of many of these recordings is not bad, but not at the level of a top notch symphony like the Pops.
If the average adult lifespan is about 75 years, then 50 years is most if not all of that adult lifespan. Does that sound limited given the initial 14 years plus the possibility of an additional 14 years as spec'd in the Constitution?
you are definitely being unreasonable. While I don't agree at all with the *AA's stances on copyright, I don't agree with no copyright. I do believe the founders of the US Constitution had it right when they stated that copyright should be for a limited time. 50+ years is not limited for most adult life spans.
If there was no copyright law nobody would sell VHS/DVD/BluRay because it would be impossible to make money from them.
and that's why we have the hords and hords of CDs with that noise known as classical music on them, or DVDs based off of ancient fables and stories because no one could possibly make money off of public domain works... (hint - the DVD reference is directly aimed at Disney...)
With Spring, it really depends upon what you're working with, not that it excuses the existence of Spring, but that's a different story.
Core: Dependency Injection (the initial biggie and raison d'etre) - if you're only using this for testing, why would you inject test code in your production code? (yes, pun intended). Otherwise, see above statement about 5 lines of code in most cases for a hard compiled factory, or possibly as few as 10 for a reflection based factory. Either way, Spring's use in this category is usually abused to allow for things like circular dependencies - really bad idea.
DAO: Haven't really used this directly, although it's been inflicted on me via a third party app. Spring transactions get rather abrupt comments from Hibernate folks in hibernate forums. If you want a nice migraine, try debugging why a particular transaction is broken when you change 1 minor operation, like, say, add a field to an object.
ORM: all third party stuff, why not use them directly? Unless you just enjoy writing more XML.
AOP: A poor man's dynamic proxy approach to AOP. This can have some interesting side effects if you actually expect a specific object.
JEE: heard the EJB part was good, but I avoid EJBs like the plague.
WEB: Spring MVC - who uses this? Seriously. I've never seen it in an enterprise environment. It's sort of like Struts 2, it might be nice, but it's MIA.
But you should definitely learn about these technologies, because knowing them will allow you to make better decisions.
This is a facet of copyright they need to fix. If you publish something, then take it out of print, you lose your copyright. Charging usurious fees for a print should also be considered "out of print" (like more than 30% of the initial run's street price, not MSRP:)
And yes, this would directly remove most Disney works from copyrighted status, as this is their ploy to create artificial scarcity and increase demand for their products.
I agree with you - pretty much anytime you're looking at a long running project you're better off not using frameworks that have cut corners in areas to "make it easier for developers". Frameworks like Hibernate are especially guilty of this, since those pesky DBs are just too hard for those poor little devs to learn how to interface with using the standard library (JDBC - which, btw, still morphs but usually keeps backwards compatibility)
I personally find hibernate to be fine for simple POC's or very simplistic apps that have a definite EOL. Anything else, don't use these persistence frameworks because they'll wind up costing you more time in maintenance than having written a specific layer for your system in the first place. I've seen several projects where the Hibernate/JDO persistence layer code ran into the tens of thousands of LOCs, because the DB no longer matched the simplistic object table layout these frameworks assume. And even when you're looking to use simple tables, linking multiple commits in a transaction winds up being more difficult than it needs to be, especially if that transaction is "handled" by Spring:
Spring - that's another one. Spring has a special place in my heart, as I see it as the Darth Vader of frameworks corrupting otherwise workable architectures everywhere. After more than 5 years of having to deal with it, I've concluded that if I can remove Spring from any project I'm working on, I will. It will save me significant time in the future. It's a poor substitute for real AOP. It masquerades as this wonderful factory (5 lines of compile time checked code without Spring, a min of 2 lines of runtime checked code with 9 lines of xml with Spring) that can inject all sorts of nastiness into your system and requires runtime debugging to figure out why the heck you don't have the object you thought you had, from the service you wound up actually not calling, 6 layers deep.
Now, with all that said, sometimes you have to work with these systems, because there's no business case for removing them. It appears the OP has finally gotten to the point where there is a business case for revisiting his persistence layer, and if he's designed the access to Hibernate correctly on the edge of his application, it won't be too bad to remove Hibernate and install his own layer. If he's used the Hibernate calls throughout his code, he may wish to first migrate everything behind an internal API, and then start migrating code.
You're either the worst type of admin (and it certainly sounds like it with your ham-fisted policy statement) or your business has no real negative impact from your policy, in which case it's ok.
In the presented case, it sounds like there is significant disk I/O. Adding an encryption layer to disk I/O that's not hardware driven is going to slow down disk access, possibly significantly. The type of modeling discussed generally uses huge amounts of resources and can strain all current systems to near breaking points. I used to do similar work modeling large structures, and even the Crays and Convexes I used would take many hours to run highly optimized code that reduced memory requirements as much as possible. Output was measured in GBs, even compressed.
An encryption layer on a fully utilized machine would have significantly slowed down processing, as Disk I/O was already a bottle neck.
Those would be the lazy bad admins and, unfortunately, are usually the only ones left after a period of time as the better ones all get better jobs/pay as soon as they can.
A good IT staffer knows their network and the various ways they can implement the policy's goals. (Note, policy should be abstract things like keep bad guys out of network, not specific things like install single Firewall Brand A and cut all other connections between network and internet.) They would also know how to accommodate changing needs.
Guitar Hero has no controller advantages as it relies on an add in controller.
Mario Kart is quite a bit of fun with the wheel. It seems to work just fine on control once you get the hang of it, like any other control. I haven't even tried any of the other controls.
Games like Rayman's Ravin Rabbids (1, 2, and soon to be released TV Party) are more along the lines of what I'm talking about. They're interesting and far different from the fare offered on other platforms. They're also all "group" games, because at least half the fun is watching other people play. If that isn't your bag, then the Wii probably isn't for you.
And I'd also say that you're off in your claims of 1:1 motion requirements. It may not be a requirement, but that's more a game programming issue than anything else. Rabbids 2 definitely has different effects based on motion, with wrist flicks resulting in much smaller motion than large sweeps in some of the games. Others do not differentiate between the two. Wii Sports also has various games that appear to have motion sensitivities, although perhaps not to an exact 1:1 relationship.
Wii Ski with the Fit is another interesting game with a whole different approach.
From your games list, I'd say your interests may not be best served by the Wii. Or maybe they might, if you look beyond those games. (And no, I don't remember anything about Star Wars fans in relationship to the Wii. Actually, are there any left?)
And what is that reason? Better games? Not really. More powerful? Not really. Better online support? Definetly not. Interesting control scheme? Sure, I'll give it that.
Yes, to all of the above, for the apparent majority of people that are interested in buying consoles, with the exception of the statement "more powerful".
Apparently the Wii is powerful enough for what it needs to do. Yes, the other two can render 4 times the detail and at higher frame-rates. Neither is important for the casual gamer. They aren't going to "study" the 1st person shooter of the moment to be able to take advantage of either of those facets.
Better games: this is entirely subjective. I'd state they're a lot more fun, but that's still merely my (and millions more) opinion.
Online support is adequate.
The controllers and their abilities and effects on game play are what separates the Wii from the others, and PCs too. The XBox 360 and PS3 are basically PCs, and pretty much now just average PCs, if they're even that good. (Which is why they suck, btw)
There were plenty of things around all the way back to at least the early 80s.
The DMCA was primarily crafted in response to the DVD CSS breakage and the inherent flaws of all DRM which were well understood and documented and the fear that movies would suffer the same fate as music as the internet continued to evolve.
I'll second that. The Wii and the games for it have proven to be a ton of fun. Try Rayman Raving Rabbids (1, 2, and the soon to be released TV Party). The physical antics of the players as they try to control their on screen characters are hilarious, which is why hardcore gamers probably don't like the Wii, they're always playing solo and never get to watch the actions of others while they're playing, because they might miss that 1 bonus framerate they paid $500 to get.
And I'll buy the Nintendo Wii if it's either $100 flat or $150 with a free game.
I guess you'll buy one when the next generation comes out, if you can find one. There's a reason the Wii's outselling all other consoles combined, despite its lower graphics capability, but it appears you may never find out unless you visit a friend with one.
You have yet to provide any evidence of "gestapo methodologies."
"papers please" or any variation there of is gestapo, or perhaps you need a refresher in 1939-1945 German and Communist Russia police tactics?
The more hurdles you put in place, the harder it is for the smuggling to go on.
I strongly suggest you immigrate to your nearest police state.
Do you believe George's favorite pipe stuffing should be enjoyable by his descendants? You do realize why hemp was outlawed, right? Had nothing to do with drugs and everything to do with two guys named DuPont and Hearst fearing their fortunes would be depleted by the new fiber extraction process.
The post alluded to discussed using a set of single large disks to back up RAID arrays in rotation. That would come in under his budget, and provide all the backups requirements he needs.
Slashdot Mirror
I guess you haven't been to your local record store in a while (neither have I, for that matter). But I do know they happen to have a large collection of Classical CDs covering probably everything you know about classical music and then some for the paltry sum of less then $5. The quality of many of these recordings is not bad, but not at the level of a top notch symphony like the Pops.
.
.
.
The list just goes on and on.
Whether you like them or think they're sappy POSes is irrelevant, they make tons of money off of these, and they're all public domain stories.
If the average adult lifespan is about 75 years, then 50 years is most if not all of that adult lifespan. Does that sound limited given the initial 14 years plus the possibility of an additional 14 years as spec'd in the Constitution?
you are definitely being unreasonable. While I don't agree at all with the *AA's stances on copyright, I don't agree with no copyright. I do believe the founders of the US Constitution had it right when they stated that copyright should be for a limited time. 50+ years is not limited for most adult life spans.
If there was no copyright law nobody would sell VHS/DVD/BluRay because it would be impossible to make money from them.
and that's why we have the hords and hords of CDs with that noise known as classical music on them, or DVDs based off of ancient fables and stories because no one could possibly make money off of public domain works... (hint - the DVD reference is directly aimed at Disney...)
I read it as a console MMO a la MUD...
Forgot to add a reasonable timeline.... say 1-2 years after going into print.
With Spring, it really depends upon what you're working with, not that it excuses the existence of Spring, but that's a different story.
Core: Dependency Injection (the initial biggie and raison d'etre) - if you're only using this for testing, why would you inject test code in your production code? (yes, pun intended). Otherwise, see above statement about 5 lines of code in most cases for a hard compiled factory, or possibly as few as 10 for a reflection based factory. Either way, Spring's use in this category is usually abused to allow for things like circular dependencies - really bad idea.
DAO: Haven't really used this directly, although it's been inflicted on me via a third party app. Spring transactions get rather abrupt comments from Hibernate folks in hibernate forums. If you want a nice migraine, try debugging why a particular transaction is broken when you change 1 minor operation, like, say, add a field to an object.
ORM: all third party stuff, why not use them directly? Unless you just enjoy writing more XML.
AOP: A poor man's dynamic proxy approach to AOP. This can have some interesting side effects if you actually expect a specific object.
JEE: heard the EJB part was good, but I avoid EJBs like the plague.
WEB: Spring MVC - who uses this? Seriously. I've never seen it in an enterprise environment. It's sort of like Struts 2, it might be nice, but it's MIA.
But you should definitely learn about these technologies, because knowing them will allow you to make better decisions.
NONE of the DOS-based Windows (1,2,3,95,98/me) were stable. They were kludges sitting on top of an ancient DOS, trying to be a Mac-like environment.
Wait, are you talking about MS Windows or X Windows?
You must be new here.
This is a facet of copyright they need to fix. If you publish something, then take it out of print, you lose your copyright. Charging usurious fees for a print should also be considered "out of print" (like more than 30% of the initial run's street price, not MSRP:)
And yes, this would directly remove most Disney works from copyrighted status, as this is their ploy to create artificial scarcity and increase demand for their products.
I agree with you - pretty much anytime you're looking at a long running project you're better off not using frameworks that have cut corners in areas to "make it easier for developers". Frameworks like Hibernate are especially guilty of this, since those pesky DBs are just too hard for those poor little devs to learn how to interface with using the standard library (JDBC - which, btw, still morphs but usually keeps backwards compatibility)
I personally find hibernate to be fine for simple POC's or very simplistic apps that have a definite EOL. Anything else, don't use these persistence frameworks because they'll wind up costing you more time in maintenance than having written a specific layer for your system in the first place. I've seen several projects where the Hibernate/JDO persistence layer code ran into the tens of thousands of LOCs, because the DB no longer matched the simplistic object table layout these frameworks assume. And even when you're looking to use simple tables, linking multiple commits in a transaction winds up being more difficult than it needs to be, especially if that transaction is "handled" by Spring:
Spring - that's another one. Spring has a special place in my heart, as I see it as the Darth Vader of frameworks corrupting otherwise workable architectures everywhere. After more than 5 years of having to deal with it, I've concluded that if I can remove Spring from any project I'm working on, I will. It will save me significant time in the future. It's a poor substitute for real AOP. It masquerades as this wonderful factory (5 lines of compile time checked code without Spring, a min of 2 lines of runtime checked code with 9 lines of xml with Spring) that can inject all sorts of nastiness into your system and requires runtime debugging to figure out why the heck you don't have the object you thought you had, from the service you wound up actually not calling, 6 layers deep.
Now, with all that said, sometimes you have to work with these systems, because there's no business case for removing them. It appears the OP has finally gotten to the point where there is a business case for revisiting his persistence layer, and if he's designed the access to Hibernate correctly on the edge of his application, it won't be too bad to remove Hibernate and install his own layer. If he's used the Hibernate calls throughout his code, he may wish to first migrate everything behind an internal API, and then start migrating code.
You're either the worst type of admin (and it certainly sounds like it with your ham-fisted policy statement) or your business has no real negative impact from your policy, in which case it's ok.
In the presented case, it sounds like there is significant disk I/O. Adding an encryption layer to disk I/O that's not hardware driven is going to slow down disk access, possibly significantly. The type of modeling discussed generally uses huge amounts of resources and can strain all current systems to near breaking points. I used to do similar work modeling large structures, and even the Crays and Convexes I used would take many hours to run highly optimized code that reduced memory requirements as much as possible. Output was measured in GBs, even compressed.
An encryption layer on a fully utilized machine would have significantly slowed down processing, as Disk I/O was already a bottle neck.
Those would be the lazy bad admins and, unfortunately, are usually the only ones left after a period of time as the better ones all get better jobs/pay as soon as they can.
A good IT staffer knows their network and the various ways they can implement the policy's goals. (Note, policy should be abstract things like keep bad guys out of network, not specific things like install single Firewall Brand A and cut all other connections between network and internet.) They would also know how to accommodate changing needs.
Guitar Hero has no controller advantages as it relies on an add in controller.
Mario Kart is quite a bit of fun with the wheel. It seems to work just fine on control once you get the hang of it, like any other control. I haven't even tried any of the other controls.
Games like Rayman's Ravin Rabbids (1, 2, and soon to be released TV Party) are more along the lines of what I'm talking about. They're interesting and far different from the fare offered on other platforms. They're also all "group" games, because at least half the fun is watching other people play. If that isn't your bag, then the Wii probably isn't for you.
And I'd also say that you're off in your claims of 1:1 motion requirements. It may not be a requirement, but that's more a game programming issue than anything else. Rabbids 2 definitely has different effects based on motion, with wrist flicks resulting in much smaller motion than large sweeps in some of the games. Others do not differentiate between the two. Wii Sports also has various games that appear to have motion sensitivities, although perhaps not to an exact 1:1 relationship.
Wii Ski with the Fit is another interesting game with a whole different approach.
From your games list, I'd say your interests may not be best served by the Wii. Or maybe they might, if you look beyond those games. (And no, I don't remember anything about Star Wars fans in relationship to the Wii. Actually, are there any left?)
And what is that reason? Better games? Not really. More powerful? Not really. Better online support? Definetly not. Interesting control scheme? Sure, I'll give it that.
Yes, to all of the above, for the apparent majority of people that are interested in buying consoles, with the exception of the statement "more powerful".
Apparently the Wii is powerful enough for what it needs to do. Yes, the other two can render 4 times the detail and at higher frame-rates. Neither is important for the casual gamer. They aren't going to "study" the 1st person shooter of the moment to be able to take advantage of either of those facets.
Better games: this is entirely subjective. I'd state they're a lot more fun, but that's still merely my (and millions more) opinion.
Online support is adequate.
The controllers and their abilities and effects on game play are what separates the Wii from the others, and PCs too. The XBox 360 and PS3 are basically PCs, and pretty much now just average PCs, if they're even that good. (Which is why they suck, btw)
There were plenty of things around all the way back to at least the early 80s.
The DMCA was primarily crafted in response to the DVD CSS breakage and the inherent flaws of all DRM which were well understood and documented and the fear that movies would suffer the same fate as music as the internet continued to evolve.
Only because they havent' played Mario Kart in WFC... oh wait, that's Wii only....
I'll second that. The Wii and the games for it have proven to be a ton of fun. Try Rayman Raving Rabbids (1, 2, and the soon to be released TV Party). The physical antics of the players as they try to control their on screen characters are hilarious, which is why hardcore gamers probably don't like the Wii, they're always playing solo and never get to watch the actions of others while they're playing, because they might miss that 1 bonus framerate they paid $500 to get.
Heh, try Sega Genesis (32X CD!!!!)
Now that was definitely not successful.
And I'll buy the Nintendo Wii if it's either $100 flat or $150 with a free game.
I guess you'll buy one when the next generation comes out, if you can find one. There's a reason the Wii's outselling all other consoles combined, despite its lower graphics capability, but it appears you may never find out unless you visit a friend with one.
So would that be the original "The Tick" cartoon, or that failed mainstream TV series?
I wonder, do servers whimper?
You have yet to provide any evidence of "gestapo methodologies."
"papers please" or any variation there of is gestapo, or perhaps you need a refresher in 1939-1945 German and Communist Russia police tactics?
The more hurdles you put in place, the harder it is for the smuggling to go on.
I strongly suggest you immigrate to your nearest police state.
Do you believe George's favorite pipe stuffing should be enjoyable by his descendants? You do realize why hemp was outlawed, right? Had nothing to do with drugs and everything to do with two guys named DuPont and Hearst fearing their fortunes would be depleted by the new fiber extraction process.
I'll nominate your post for the first use of this new mod category...
The post alluded to discussed using a set of single large disks to back up RAID arrays in rotation. That would come in under his budget, and provide all the backups requirements he needs.