One of the good guys? By trying to put questionable licenses into GPL'd products? By promoting a vendor who is known by the motto 'embrace, extend, extinguish'?? How is promoting this vendor and sleeping with them beneficial to the community? Everytime Microsoft makes a decent gesture, they screw it up by doing something anti-competitive o ruin the gesture of good faith with the open source community. And Novell saying 'no no, I swear they have changed' while we watch the beatings go on is just an embarassment to Novell.
So if Novell refuses to believe they are in an abusive relationship, I think everyone is already making the correct decision... ignore them until they acknowledge the problem.
Novell here is the victim of Microsoft harassment, and the reason they are acting they way that they do is precisely out of sheer survival and based on their history.
If they are victim, then they are victim of 'battered wife syndrome'. They love the deal too much to leave but hate the abuse that gets heaped onto them. They were warned before entering into this relationship how abusive it was and yet they still went in and are still in it. I think it's time for an intervention and moving Novell to a safe house for it's own safety so that we can once and for all break Microsoft's hold over it and De Icaza.
Obviously you cannot separate your passionate love for Steve Ballmers trouser snake from the need for good engineering. Should 40% be acceptable for detecting parachute defects? How about life raft defects? Is this a severe comparison? Well when healthcare systems and life support systems and financial systems and even a INTERNATIONAL SPACE STATION run on their software, you'd think 99.9% would be the only goal they would be happy with and anything short of that would be unacceptable.
Instead, they send a message to their staff that 40% if a perfectly acceptable goal. Shoot for 40% everyone, thats where we set the bar.
That's why everyone is making fun. Not at their goal, but at their acceptance of it as acceptable. Pathetic.
See now thats not an intern... that is a motivated person looking to kick someone else out who is less motivated. That's not an intern, thats a shark disguised as an intern. Good for you shark. Many happy meals for you.
Your an intern. Expect to be treated like my little brother after having lost a bet. I will make you do the most menial of tasks that I don't want to do and give you table scraps and you will be thankful for the experience of being able to write it on your resume that you were my personal slave for 6 months and this company because it actually looks like experience when it was nothing but humiliation and torture. Welcome the day you get your first intern with a guilty pleasure.
I couldn't agree more. It's when you deconstruct the concept of what something is and how it relates to the world around it that you truly understand that object and what it's purpose is. You also understand how to IMPROVE it's role; because while some thought they understood the role and purpose, the misunderstood the relationship to it's surrounding environment and by repurposing it or shifting it, you can improve it's performance. Understanding relationships has taught me so much about how to TRULY program and not just string lines of code together just to get something done.
Is it? what isn't an object and what doesn't inherit from something else? All ideas are derivatives and all objects are derivatives and inherited.
Your wallet is an object owned by you for storage of a variable called money. Your boss has a relationship to you as your superior and the location you work is merely a branch of the parent company (even if branch instance is only 1). etc etc
Data Modelling can show you how all real life situations can be turned into objects and relationships and can be very useful practice in development as well as database administration and planning.
Understanding how to model real life objects into a database taught me alot about what an object truly is. It also taught me alot about relationships between entities, parent and child and 'many to many' relationships. I made leaps and bounds in development just by understanding data modeling.
Use it all the time. Never once has it supplied the source code for me. And maybe Windows should check dependencies; then they wouldn't have so many crappy and broken apps.
The poster compared it to apt-get. Apt get allows for updates and upgrading as well as checking for dependencies. I repeat... how is an app store like a repository???
Inflate your statistics because they will usually be correct if they do not have onsite support. If they farm it out to offsite support, they may not be available and when they become available, the staff has to get to the site (travel time) and then they have to get up to speed on that particular vendors setup (which takes twice as long as someone who is already familiar). Whatever the time is for you to get something taken care of, it will be 4-8 times as bad without you there. So here is a good calc:
Number of machines (if 1 machine=1 person) x 5.5(average of above factor) x (number of hours spent fixing problem) x (average employee wage).
So if you spent 4 hrs, fixing a machine that caused 20 employees to be unproductive (or potentially avoided unproductivity), take 80 times their average wage (we'll say $15), TIMES 5.5. $6600 was just saved on that one task.
My customers tend to be editorial types who want a simple API to access the data AND they want it to scale but they don't know jack squat about DBs and honestly they shouldn't have to.
You're customers want a database driven application but their development staff doesn't want to have to know anything about databases? That my friend is a recipe for disaster. If you honestly believe that the maintainer of a database driven app doesn't need to know anything about databases, you are very very naive.
...Which is exactly what we do with our ORM mapping.
with overkill. Loading too much data, improper query caching, allowing methods access to data that they probaby should not have access to. Your query is custom built for the method to increase speed, limit datasets and secure data for the method calling it. ORM bypasses all of this in one way or another adding overhead, allowing access to data when it should not be allowed to the function and other bad practices as well as the overhead of have to access a relationship to access the relationship; dept of redundancy dept. calling.
I've seen an ORM based solution for creating search indexes of basically the entire music catalog of all the major labels in the united states
Yawn... try a 10 terabyte searchable customer database actively being updated with hundreds of customer records per second for a telecom. And that doesn't even count the reads!!! And thats JUST the customer database. When I worked at Amazon, puttin book data into the database is just as similar as that music database. It's not too hard to make that searchabl with orm as the datasets are HIGHLY repeatable. But when you are talking about nonrepeating datasets... ORM cannot scale.
Well ideally, it shouldn't have to import at all; instead it should create a library by 'linking' to those files in those directories. Unfortunately, this can slow down search and shuffle functions since it has to search the file system for those files and if the directory structure is corrupted in anyway (yes yes, thats mostly a Windows issue), its even more problematic. Having them all in one place simplifies it and forcing the user to use the applications file system makes it a bit more inconvenient for them to switch to another application.
Thats a very good argument for non-database people to use databases. But not a very good argument for using ORM for scalable projects. Because if you need a project to scale, you will NEED to understand databases and have custom built queries and query caching in place. Building these into a separate database layer easily makes it so the DBA can make these changes separate from the application.
While ORM may simplify in some respects, it also overcomplicates the process and makes queries take longer or return too much data thus increasing the load on a database. A truly database driven application that is intended to scale to any level beyond an entry level market would not use ORM. I use OOP in just about everything I do but the OOP model is overkill when applied to the database model which is why it drastically slows the process in comparison to a separate database layer in your application.
And while you preserve the relationship, you expose methods to data that they shouldn't have access to or you load excessive data; if you are wishing your methods to only have access to limited data sets to preserve data security or to limit data being loaded, ORM is not your answer. The database preserves your relationships, why do you need to preserve the relationships between objects containing that data??
It's not the codec that they support, it's the codecs that the developer develops in that Microsoft has not RELEASED or the APIS that have not been released to Mac or Linux. Silverlight developers can write silverlight apps to hook into DirectX and other windows specifix apis and codecs that Macs and Linux cannot makes use of. Flash does not do this but hooks into applications that then will make use of them; this makes Flash more open than Silverlight and more friendly to cross platform devlopment.
For all Microsoft's talk, this is just another bait and switch routine; bait developers with Silverlight and then switch consumers and developers of Silverlight to IIS,.NET and other Microsoft platforms.
ORM has it's own problems for database run applications. It adds alot of overhead to the amount of data you have to load when you could be customizing your queries to each method that has to call the database and just have the class instantiate a DB object instead. Is this a little more work? Yes. Is this more scalable? Definitely. Is this 'messier'? Depends. I abstract the sql into a separate database layer so it isn't even included in the functions; that way the DBA can mess with the database queries as much as he wants (as long as he is communicating his changes to the developers) and the developers don't have to see all those queries in their code.
ORM is a solution only if you are fanatic about turning EVERYTHING into an object but a true engineer knows that one tool does not fit all paradigms. And ORM is such a case where objects tend to fall short; good in the short run but the more you try to scale your application up, the more ORM becomes a problem and you end up falling back on hand coding your queries.
Thats also a reason not to use it if getting media STREAMED (as well as streaming video as you pointed out). At any time that media can rely upon proprietary apis or codecs and can switch at the whim of the developers. This is never the case with Flash. Flash will not require WMV or DirectX to view your media; it can TIE to additional programs that will require them but it will not require it itself which Silverlight can and will.
Cross platform compatibility should rank high. When apple laptop sales are over 40% on campuses and over 33% in the overall market, you are guaranteed that apple will be in your business. Linux is ALREADY in your business if you have sys admins or developers. Silverlight relies on Microsoft products that are not available to these platforms. Your mac will not be able to play alot of data that Slverlight uses. You are at the mercy of a company that is not releasing all their codecs, apis that Silverlight uses.
Slashdot Mirror
One of the good guys? By trying to put questionable licenses into GPL'd products? By promoting a vendor who is known by the motto 'embrace, extend, extinguish'?? How is promoting this vendor and sleeping with them beneficial to the community? Everytime Microsoft makes a decent gesture, they screw it up by doing something anti-competitive o ruin the gesture of good faith with the open source community. And Novell saying 'no no, I swear they have changed' while we watch the beatings go on is just an embarassment to Novell.
So if Novell refuses to believe they are in an abusive relationship, I think everyone is already making the correct decision... ignore them until they acknowledge the problem.
If they are victim, then they are victim of 'battered wife syndrome'. They love the deal too much to leave but hate the abuse that gets heaped onto them. They were warned before entering into this relationship how abusive it was and yet they still went in and are still in it. I think it's time for an intervention and moving Novell to a safe house for it's own safety so that we can once and for all break Microsoft's hold over it and De Icaza.
Hmmm.... my vote is for 'or something'.
Obviously you cannot separate your passionate love for Steve Ballmers trouser snake from the need for good engineering. Should 40% be acceptable for detecting parachute defects? How about life raft defects? Is this a severe comparison? Well when healthcare systems and life support systems and financial systems and even a INTERNATIONAL SPACE STATION run on their software, you'd think 99.9% would be the only goal they would be happy with and anything short of that would be unacceptable.
Instead, they send a message to their staff that 40% if a perfectly acceptable goal. Shoot for 40% everyone, thats where we set the bar.
That's why everyone is making fun. Not at their goal, but at their acceptance of it as acceptable. Pathetic.
See now thats not an intern... that is a motivated person looking to kick someone else out who is less motivated. That's not an intern, thats a shark disguised as an intern. Good for you shark. Many happy meals for you.
got news for you peon... intern == tiny penis. Pray I dont whip you out and wave you around in the ladies rest room
Your an intern. Expect to be treated like my little brother after having lost a bet. I will make you do the most menial of tasks that I don't want to do and give you table scraps and you will be thankful for the experience of being able to write it on your resume that you were my personal slave for 6 months and this company because it actually looks like experience when it was nothing but humiliation and torture. Welcome the day you get your first intern with a guilty pleasure.
Trying to speak about logic and science with religious zealots is like trying to wash the shit off a turd.
That would explain alot. PI is required by many Al Gore Rhythyms that Microsoft has yet to master
LOLZ> You are talking about a Microsoft app store and expecting bug free, spywarefree software??? Can I live in your fantasy world?
I couldn't agree more. It's when you deconstruct the concept of what something is and how it relates to the world around it that you truly understand that object and what it's purpose is. You also understand how to IMPROVE it's role; because while some thought they understood the role and purpose, the misunderstood the relationship to it's surrounding environment and by repurposing it or shifting it, you can improve it's performance. Understanding relationships has taught me so much about how to TRULY program and not just string lines of code together just to get something done.
Is it? what isn't an object and what doesn't inherit from something else? All ideas are derivatives and all objects are derivatives and inherited.
Your wallet is an object owned by you for storage of a variable called money. Your boss has a relationship to you as your superior and the location you work is merely a branch of the parent company (even if branch instance is only 1). etc etc Data Modelling can show you how all real life situations can be turned into objects and relationships and can be very useful practice in development as well as database administration and planning.
Understanding how to model real life objects into a database taught me alot about what an object truly is. It also taught me alot about relationships between entities, parent and child and 'many to many' relationships. I made leaps and bounds in development just by understanding data modeling.
Use it all the time. Never once has it supplied the source code for me. And maybe Windows should check dependencies; then they wouldn't have so many crappy and broken apps.
The poster compared it to apt-get. Apt get allows for updates and upgrading as well as checking for dependencies. I repeat... how is an app store like a repository???
Um... how is an app store the same thing as an app repository?? You are comparing apples to microwave ovens.
Inflate your statistics because they will usually be correct if they do not have onsite support. If they farm it out to offsite support, they may not be available and when they become available, the staff has to get to the site (travel time) and then they have to get up to speed on that particular vendors setup (which takes twice as long as someone who is already familiar). Whatever the time is for you to get something taken care of, it will be 4-8 times as bad without you there. So here is a good calc:
Number of machines (if 1 machine=1 person) x 5.5(average of above factor) x (number of hours spent fixing problem) x (average employee wage).
So if you spent 4 hrs, fixing a machine that caused 20 employees to be unproductive (or potentially avoided unproductivity), take 80 times their average wage (we'll say $15), TIMES 5.5. $6600 was just saved on that one task.
You're customers want a database driven application but their development staff doesn't want to have to know anything about databases? That my friend is a recipe for disaster. If you honestly believe that the maintainer of a database driven app doesn't need to know anything about databases, you are very very naive.
with overkill. Loading too much data, improper query caching, allowing methods access to data that they probaby should not have access to. Your query is custom built for the method to increase speed, limit datasets and secure data for the method calling it. ORM bypasses all of this in one way or another adding overhead, allowing access to data when it should not be allowed to the function and other bad practices as well as the overhead of have to access a relationship to access the relationship; dept of redundancy dept. calling.
Yawn... try a 10 terabyte searchable customer database actively being updated with hundreds of customer records per second for a telecom. And that doesn't even count the reads!!! And thats JUST the customer database. When I worked at Amazon, puttin book data into the database is just as similar as that music database. It's not too hard to make that searchabl with orm as the datasets are HIGHLY repeatable. But when you are talking about nonrepeating datasets... ORM cannot scale.
Well dont know what to tell you my friend. The 90's have come and gone. Let me know when you want to step into our century.
Well ideally, it shouldn't have to import at all; instead it should create a library by 'linking' to those files in those directories. Unfortunately, this can slow down search and shuffle functions since it has to search the file system for those files and if the directory structure is corrupted in anyway (yes yes, thats mostly a Windows issue), its even more problematic. Having them all in one place simplifies it and forcing the user to use the applications file system makes it a bit more inconvenient for them to switch to another application.
Thats a very good argument for non-database people to use databases. But not a very good argument for using ORM for scalable projects. Because if you need a project to scale, you will NEED to understand databases and have custom built queries and query caching in place. Building these into a separate database layer easily makes it so the DBA can make these changes separate from the application.
While ORM may simplify in some respects, it also overcomplicates the process and makes queries take longer or return too much data thus increasing the load on a database. A truly database driven application that is intended to scale to any level beyond an entry level market would not use ORM. I use OOP in just about everything I do but the OOP model is overkill when applied to the database model which is why it drastically slows the process in comparison to a separate database layer in your application.
And while you preserve the relationship, you expose methods to data that they shouldn't have access to or you load excessive data; if you are wishing your methods to only have access to limited data sets to preserve data security or to limit data being loaded, ORM is not your answer. The database preserves your relationships, why do you need to preserve the relationships between objects containing that data??
It's not the codec that they support, it's the codecs that the developer develops in that Microsoft has not RELEASED or the APIS that have not been released to Mac or Linux. Silverlight developers can write silverlight apps to hook into DirectX and other windows specifix apis and codecs that Macs and Linux cannot makes use of. Flash does not do this but hooks into applications that then will make use of them; this makes Flash more open than Silverlight and more friendly to cross platform devlopment.
.NET and other Microsoft platforms.
For all Microsoft's talk, this is just another bait and switch routine; bait developers with Silverlight and then switch consumers and developers of Silverlight to IIS,
ORM has it's own problems for database run applications. It adds alot of overhead to the amount of data you have to load when you could be customizing your queries to each method that has to call the database and just have the class instantiate a DB object instead. Is this a little more work? Yes. Is this more scalable? Definitely. Is this 'messier'? Depends. I abstract the sql into a separate database layer so it isn't even included in the functions; that way the DBA can mess with the database queries as much as he wants (as long as he is communicating his changes to the developers) and the developers don't have to see all those queries in their code.
ORM is a solution only if you are fanatic about turning EVERYTHING into an object but a true engineer knows that one tool does not fit all paradigms. And ORM is such a case where objects tend to fall short; good in the short run but the more you try to scale your application up, the more ORM becomes a problem and you end up falling back on hand coding your queries.
Thats also a reason not to use it if getting media STREAMED (as well as streaming video as you pointed out). At any time that media can rely upon proprietary apis or codecs and can switch at the whim of the developers. This is never the case with Flash. Flash will not require WMV or DirectX to view your media; it can TIE to additional programs that will require them but it will not require it itself which Silverlight can and will.
Cross platform compatibility should rank high. When apple laptop sales are over 40% on campuses and over 33% in the overall market, you are guaranteed that apple will be in your business. Linux is ALREADY in your business if you have sys admins or developers. Silverlight relies on Microsoft products that are not available to these platforms. Your mac will not be able to play alot of data that Slverlight uses. You are at the mercy of a company that is not releasing all their codecs, apis that Silverlight uses.
Flash on the otherhand is much more open.