err... If something is opensource, then I assume you accept contributions. Then "intellectual property" isn't truly owned by you, is it?
By the way, the world is constantly changing. Software is more and more commodity, unless you work in particular niches or develop truly complicated stuff, generally applicable to algorithms. Consider also how the software can be used to develop a certain kind of "ecology" in your area. So rather than just developing tools, you become a kind of steward for that area with consultancy, knowledge management etc... This is a perfect match for opensource and with more people into the idea, your business can grow a lot stronger and at a much faster pace. If you don't limit marketing and commercial "application" of the software by others in different countries, then everybody wins. The project gains reputation and this kind of reputation is easily related to the business you may be starting (since you need to show sponsorship).
The difficulty is wearing two quite different hats most of the time. The key here is looking for the right balance!
If either the quality of the source or the quality of the output medium is bad, the other end can't compensate whatsoever. (put garbage in, get garbage out).
This thus means that if the output medium is not very good, the source only needs to be equally good. Improving the quality of the source won't give any substantial benefit in the output. Certainly not when the "speakers" are $0,50 headphones. This is why the sound of MP3's is "acceptable". (add some reverb effect and other DSP's and the sound, to many, quickly sounds "better", when it just has more effect.)
If you play an mp3 on B&W speakers with similar quality amp (say Musical Fidelity or Rotel), I can't imagine no one wouldn't be able to hear the difference. It probably also depends how much you've trained yourself to listen to detail in music.
When people mention "losless quality", but the amount of information is reduced by 90%, there are definitely areas in the sound where this loss is more significant than in others. Someone mentioned hi-hats and guitar solos. I suppose that higher harmonics are probably suffering a lot from the mp3 reduction, which usually don't come out very well in cheaper systems, but still add to the sound overall.
I started Project Dune in 2004 and rewrote a couple of things. It's Java + Hibernate + GWT at the moment. Timesheets are still in development, but the intention is to connect everything off the trouble tickets (issues) that you create in the system.
http://www.sf.net/projects/pdune
G>
Hmmmm... I guess not. There's already a great deal of location-integrated services and location is just another way to group data together. Location is not always relevant. Besides this... Web 3.0 is supposed to be about a web that is machine-parsable. RDF, integration between services, etc. Whereas the business/enterprisey services are based on SOAP, WDSL and what-have-not, RDF is a less formal approach than XML and allows machines to parse the information (content free of markup). Somehow I also feel that RDF is possibly not the best approach, even though advocated through w3c and the likes. It's time someone in their garage comes up with something better;).
By the way, where's the multi-lingual web in this case? Translation of web pages independent of written language and so on... (Google translation can translate it, but it's not indexed in different langs, so cannot be searched).
I also consider that the web of meaning becomes more important. Rather than searching on keywords and how machines operate, I reckon that machines must become more responsible for chewing the text in such a way that we're less burdened by chewing our query to the way the machine can process it. Ever got frustrated finding the exact method for querying Google to find very specific documents that are not often referenced and highly specific to a certain knowledge domain?
Check out the efforts on Natural Language Processing, LSI, LSA and so on. There are some interesting projects and researches on retrieving better semantics (meaning) out of regular documents. The problems are that we don't really know yet how to map meaning into a different representation than huamn-interpreted words (convert language into a map of meaning), besides extracting semantics out of language elements. Where these efforts have been somewhat successful, they prove very difficult to implement without enormous machine resources and unworkable for a search engine that processes a very high volume of queries... oh well... one of these days!
I have it in my appartment. It's great! No nagging, no waiting in the morning, you can go whenever you please, it has another shower too... The previous owner modified it this way to have the extra bathroom for the housekeeper. We never bothered to change it, since the space increase is not exactly worth it (plus structural damage).
The definition of slavery is that you are unable to terminate your labour "relationship" voluntarily...
If you are forced to stay at work for a company due to any pressure and you cannot voluntarily reject, that basically conforms to "neo-slavery".
This kind of slavery in different forms can also be found in the Amazon (numbers going around 80,000 people subject to this new kind of slavery). They do not work under the threat of violence all that often (well, work "under the whip"), but violence is an end-possibility. When they bring the "slaves" from other states to the farm, a month later they are kindly reminded that the bar tab so far plus the trip is actually to be paid for. Hence, the "slaves" are unable to voluntarily terminate their contract and this qualifies as slavery. High penalties exist for these kinds of farms, once discovered.
It's a bit similar in your case. You should be able to counter-sue on the account of slavery perhaps and see what happens, if the worst case arises!:)
I've written my own java profiler/coverage tool using JVMTI, JNI which publishes results on a dynamic webpage (see Patty @ SourceForge ). One of the problems when maintaining statistics on execution and line number coverage if you keep it in the same JVM is that it has a large performance impact to continuously look up the buckets (like many profilers do), the buckets where the statistics are kept.
So one of the things is to bring down this impact by only profiling certain classes, plus sending all the profiling data to a separate computer, which has CPU available to put the data into the stat buckets to be extracted later. (this is the process that is costly to do inside the same process, putting stats into the correct buckets, due to `lookup` code ). I'm using a Tomcat process to gather data for example on a simple text-based protocol.
With ByteCode Engineering (called bytecode instrumentation in this case) rather than AOP, the advantage is that you can reload the class later without the instrumentation. AOP is not that flexible. So the advantage is that without any instrumented classes, if your environment is set up correctly, you can even start profiling in production if you wanted to (I would highly recommend not to though).
The other benefit of native profilers is that you can put this profiler under every JVM, even code that you don't know anything about, and it allows you to profile anything at will without writing specific AOP junctions or other stuff. (let's not assume you only want to profile your own 'known' code?)
JVMTI also allows you to analyze the objects on the heap. If you look into the Sun API, you can see there are various functions to tag objects, which cna be used to filter on specific objects only. I'm using this to make an estimate how many instances of certain objects there are and how much memory they are using.
Sun comes out with their own implementations (JFluid for NetBeans) and jconsole. So the benefit of future projects is that it must be aimed at a specific problem not yet solved. My project on SourceForge has full source code available if you wanted to have a look how it works (C and Java). (GPL / Mozilla, you choose)
Slashdot Mirror
Are you sure your motherboard applies the correct voltage for the memory modules? This can be verified in the BIOS I believe?
err... If something is opensource, then I assume you accept contributions. Then "intellectual property" isn't truly owned by you, is it? By the way, the world is constantly changing. Software is more and more commodity, unless you work in particular niches or develop truly complicated stuff, generally applicable to algorithms. Consider also how the software can be used to develop a certain kind of "ecology" in your area. So rather than just developing tools, you become a kind of steward for that area with consultancy, knowledge management etc... This is a perfect match for opensource and with more people into the idea, your business can grow a lot stronger and at a much faster pace. If you don't limit marketing and commercial "application" of the software by others in different countries, then everybody wins. The project gains reputation and this kind of reputation is easily related to the business you may be starting (since you need to show sponsorship). The difficulty is wearing two quite different hats most of the time. The key here is looking for the right balance!
If either the quality of the source or the quality of the output medium is bad, the other end can't compensate whatsoever. (put garbage in, get garbage out).
This thus means that if the output medium is not very good, the source only needs to be equally good. Improving the quality of the source won't give any substantial benefit in the output. Certainly not when the "speakers" are $0,50 headphones. This is why the sound of MP3's is "acceptable". (add some reverb effect and other DSP's and the sound, to many, quickly sounds "better", when it just has more effect.)
If you play an mp3 on B&W speakers with similar quality amp (say Musical Fidelity or Rotel), I can't imagine no one wouldn't be able to hear the difference. It probably also depends how much you've trained yourself to listen to detail in music.
When people mention "losless quality", but the amount of information is reduced by 90%, there are definitely areas in the sound where this loss is more significant than in others. Someone mentioned hi-hats and guitar solos. I suppose that higher harmonics are probably suffering a lot from the mp3 reduction, which usually don't come out very well in cheaper systems, but still add to the sound overall.
I started Project Dune in 2004 and rewrote a couple of things. It's Java + Hibernate + GWT at the moment. Timesheets are still in development, but the intention is to connect everything off the trouble tickets (issues) that you create in the system. http://www.sf.net/projects/pdune G>
Hmmmm... I guess not. There's already a great deal of location-integrated services and location is just another way to group data together. Location is not always relevant. Besides this... Web 3.0 is supposed to be about a web that is machine-parsable. RDF, integration between services, etc. Whereas the business/enterprisey services are based on SOAP, WDSL and what-have-not, RDF is a less formal approach than XML and allows machines to parse the information (content free of markup). Somehow I also feel that RDF is possibly not the best approach, even though advocated through w3c and the likes. It's time someone in their garage comes up with something better ;).
By the way, where's the multi-lingual web in this case? Translation of web pages independent of written language and so on... (Google translation can translate it, but it's not indexed in different langs, so cannot be searched).
I also consider that the web of meaning becomes more important. Rather than searching on keywords and how machines operate, I reckon that machines must become more responsible for chewing the text in such a way that we're less burdened by chewing our query to the way the machine can process it. Ever got frustrated finding the exact method for querying Google to find very specific documents that are not often referenced and highly specific to a certain knowledge domain?
Check out the efforts on Natural Language Processing, LSI, LSA and so on. There are some interesting projects and researches on retrieving better semantics (meaning) out of regular documents. The problems are that we don't really know yet how to map meaning into a different representation than huamn-interpreted words (convert language into a map of meaning), besides extracting semantics out of language elements. Where these efforts have been somewhat successful, they prove very difficult to implement without enormous machine resources and unworkable for a search engine that processes a very high volume of queries... oh well... one of these days!
"This is the way of big bureaucratic corporations that lack innovation," Lack innovation? ummmm.... oh well, it's slashdot!
Rare risk and overreactions. A great article on human psychology and our "failures" inside our own brain: http://www.schneier.com/crypto-gram-0706.html
I have it in my appartment. It's great! No nagging, no waiting in the morning, you can go whenever you please, it has another shower too... The previous owner modified it this way to have the extra bathroom for the housekeeper. We never bothered to change it, since the space increase is not exactly worth it (plus structural damage).
The definition of slavery is that you are unable to terminate your labour "relationship" voluntarily... If you are forced to stay at work for a company due to any pressure and you cannot voluntarily reject, that basically conforms to "neo-slavery". This kind of slavery in different forms can also be found in the Amazon (numbers going around 80,000 people subject to this new kind of slavery). They do not work under the threat of violence all that often (well, work "under the whip"), but violence is an end-possibility. When they bring the "slaves" from other states to the farm, a month later they are kindly reminded that the bar tab so far plus the trip is actually to be paid for. Hence, the "slaves" are unable to voluntarily terminate their contract and this qualifies as slavery. High penalties exist for these kinds of farms, once discovered. It's a bit similar in your case. You should be able to counter-sue on the account of slavery perhaps and see what happens, if the worst case arises! :)
I've written my own java profiler/coverage tool using JVMTI, JNI which publishes results on a dynamic webpage (see Patty @ SourceForge ). One of the problems when maintaining statistics on execution and line number coverage if you keep it in the same JVM is that it has a large performance impact to continuously look up the buckets (like many profilers do), the buckets where the statistics are kept. So one of the things is to bring down this impact by only profiling certain classes, plus sending all the profiling data to a separate computer, which has CPU available to put the data into the stat buckets to be extracted later. (this is the process that is costly to do inside the same process, putting stats into the correct buckets, due to `lookup` code ). I'm using a Tomcat process to gather data for example on a simple text-based protocol. With ByteCode Engineering (called bytecode instrumentation in this case) rather than AOP, the advantage is that you can reload the class later without the instrumentation. AOP is not that flexible. So the advantage is that without any instrumented classes, if your environment is set up correctly, you can even start profiling in production if you wanted to (I would highly recommend not to though). The other benefit of native profilers is that you can put this profiler under every JVM, even code that you don't know anything about, and it allows you to profile anything at will without writing specific AOP junctions or other stuff. (let's not assume you only want to profile your own 'known' code?) JVMTI also allows you to analyze the objects on the heap. If you look into the Sun API, you can see there are various functions to tag objects, which cna be used to filter on specific objects only. I'm using this to make an estimate how many instances of certain objects there are and how much memory they are using. Sun comes out with their own implementations (JFluid for NetBeans) and jconsole. So the benefit of future projects is that it must be aimed at a specific problem not yet solved. My project on SourceForge has full source code available if you wanted to have a look how it works (C and Java). (GPL / Mozilla, you choose)