Perhaps because of the "personal contract" thing? And maybe since the average benifits and pay are much better than the average non-IT job would offer?
Or perhaps all these were true 5-10 years ago, but the bubble has since exploded... And so we *do* need a union.
It's not that trigonmetric functions are hard to learn, it's that they rely on transcendal function like sine/cosine which are calculated numerically (as a taylor power series expansion, for example) thus are only approximations to the true values (an accurate number would require the calculation of an infinite series, which isn't practical in given time/space).
The article clearly states that: "Advanced mathematical knowledge, such as linear algebra, number theory and group theory, is generally not needed." (to use this method)
I think that having a percise, simple (polynomials, rational fractions) alternative to current methods in eucleadian trigonometry, is very welcome.
Wouldn't it be nice to be able to calculate angles and distances without having to use a calculator (for sine/cosine calculations)?
How would this affect the IM market? Would it affect the interoperability between the 2 apps? Would the 2 applications consolidate their user base into a single huge IM user base? Perhaps it's a preemptive strike against google which recently joined the market?
Since reading isn't your strong side and you obviously don't get math, let me help you out here.
Note the last line of the parent's post: "Don't assume that each possibility is equally likely .:)"
Which means, in even simpler terms, that you can't assume that the probability for a specific combination of numbers is 1 / "Number of possible combinations".
I'm giving you credit here by assuming that you know "why" each possibility isn't equally likely... but maybe that's a far stretch when it comes to you.
But most users don't know how to interpret the numbers.
For instance, when they said you speaker system is "1000 Watts" I'm pretty sure they meant the PMPO (Peak Music Power) rating, which means: (According to http://www.epanorama.net/documents/audio/amplifier _power.html) "So called "music power". This power figure tells the power which the amplifier can maximally supply in some conditions. PMPO rating gives the highest measuring value, but this info is quite useless, because there is no exact standard how PMPO power should be measured.
The reason for this power rating was to show the max capability of equipment for recreating strong musical transients like kettle drums and the like. Similar thing (music power rating) was used in the sixties, and I think it assumed a square wave that swung the whole supply range of the output stage. This alone gives them a factor of two over a clean sine wave note. But the ugliest thing they did was to assume that the high power lasted such a short period of time that the power supply caps would hold the voltages steady without any drooping. In the real world, an under powered PS could be hidden by this ruse and the PMPO might be a factor of 10 or more higher than what could be sustained on a nice instrumental performance.
Forget what adverts say about peak power or other "power terms" because they are not standardized and anyway comparable between equipments. Just look for "RMS continuous Power" or other reliable power rating (like DIN power). "
Generally, there isn't any direct mapping between PMPO and RMS (Root Mean Square) since every manufacturer formulates his own PMPO measurements.... Most of the time the RMS value of a speaker is about 10 times lower than the PMPO rating. Which in your case, Means ~100 Watt RMS (This is VERY good for a single channel... but it's kind'a low for a large multi-speaker system).
Regarding Tom's Hardware Guide, I'll have to disagree with you.
I usually find Tom's Reviews very in depth and unbiased. Moreover, I've seen products get bad reviews many a time. Especially check out the roundup articles where he compares many products of the same type (like, 17" LCD monitors), he then usually recommends 1 or 2 products that performed the best. You can verify his reasoning and testing methods trough out the article.
Tom's Hardware Guide has taken a very dramatic role in my hardware purchase decision making in the last few years and it never let me down.
When Tom says some thing's good... you know it's good 99% of the time.
66.72% of the entire population of New Orleans is Black.
So I suppose that I stand corrected.
Regarding our education system, though you have a valid point regarding it being indecent, However, I don't think that what it lacks is "ethnic makeup classes".
PC-to-PC calls were available for ages... some software do this very well. But PC-to-Regular Land Lines and Cellular Phones at extremely competitive international/long-distance rates (at least where I live) is the *real* breakthrough.
So until this project supports such services... Nothing to see here, please move along.
I assume currency is incompatible with equality too...
So how can one be rewarded for his achievements in an anarchistic society?
Are there Laws in such a society? An officer of the law seems unequal with a regular citizen, are they allowed? If not, who's to defend the helpless? who's to stop crime and gangs from forming and enslaving others - thus indirectly defeting individual freedom...?
How many copies of windows out there are pirated copies, in your opinion? I assure you that the numbers exceed by a factor of at least 3, the number of legally purchased copies. (I'm only considering home-users)
Do you think that hurts Microsoft? Hell no. It makes them much stronger. The bigger the market share - the more developers you got working on writing apps for that OS. The more apps - the stronger your hold.
Apple has everything to gain from making their OS a common commodity.
Forget about the "apple experience bundled only with apple branded hardware " - I think apple has peaked itself with that attitude. Time to expand - or die.
But a good design can create a generic API that could keep up with software progress for many years.
Furthermore, solutions like WebServices, and other self describing interfaces, can help create intellegent GUIs capable of displaying only VALID options and dynamically adapt to changes.
That aside, a form of RPC is much more of a robust solution than a script front-end would ever be.
I never said my X server was broken or that I was going to fix it with some GUI "configurator".
The entire point of my discussion was to say that "things" should be "standardized".
The example referred to an X config file. Never said the server was broken, or that something didn't work.
I used it as an example, of HOW one can interpret the IDEA of exposing an API to do changes in a standard way. X is not necessarily the correct place to implement such an approach; however, it was merely used for the sake of an example.
The Idea: Make changes in a standard way via an API or an XML schema or WHATEVER.
But don't have each dev write a new script to parse and make specific changes, as it locks down the ability to update the software being configured without breaking the "configurators"!!!
Whereas an API would bypass this... problem.
Btw, you don't need X working to expose an API. It could/should be a library like... libxconfig.so And apps could link to it. It would have functions like, "SetDefaultScreen(ScreenObject scr)" or whatever.
THIS IS JUST AN EXAMPLE! NOT NESSICERALY A GOOD ONE!
This, btw, does NOT prevent scripts from being used. You can use this exact API from within scripts!
However, It would be preferred that All changes to a program would be made via a common interface, so that Updating the program would transparently update everyone!
Regarding: "And implementing a GUI interface for a script is not a hack; it is a textbook example of the model-view separation principle"
I disagree. It perhaps fits into this description; however it is the poor way of doing it. It's not robust at all!
A good example would be the edonkey2K core and GUI, where they communicate via UNIX sockets or something. Any RPC driven front-end is better than a front-end interpreting text output from a script!
Perhaps you should take the time to thoroughly consider this before bashing the idea and proving that you misunderstood the entire concept.
Obviously, you've never developed software professionally.
Take for instance, app 1, that uses some script to change some configuration file. and app 2, that uses an api to make config changes.
now, let's suppose that the application using the config file, decides to change config file format, or perhaps do a more subtle change, like, "1" is true instead of "true" being true.
now, app 1, would break since it's script is not compatible with the change. however, app 2, would continue to function normally, as the API was updated according to the change.
this way, you centrelize the problem, and transperently update the configuration apps saving trouble for a trillion config-app-devs from updating their scripts.
besides, script front ends have many other issues, not to mention speed... for instance, error reporting.. it's horrendous to guess what went wrong with a script. you usualy get an error message sent to the console which the front end program has no idea how to interpert, so it usualy, just displays it in a message box. An API design, would give the config app a LOT more information on the error and it's cause, thus, letting it suggest solutions.
another problem with script front ends, is that it's not a 1 package deal. i.e. if the app won't work, it could either be, the gui or the script or some other dependency of both.
in an API design, it's either the GUI or a direct dependency for the gui. which makes troubleshooting a heck lot easier.
Slashdot Mirror
Actualy, A union seems like a pretty good idea...
I wonder why there aren't any IT worker unions.
Perhaps because of the "personal contract" thing?
And maybe since the average benifits and pay are much better than the average non-IT job would offer?
Or perhaps all these were true 5-10 years ago, but the bubble has since exploded... And so we *do* need a union.
Or do we?
I could in turn say, that FF users are generally more knowledgeable than IE users.
The fact that they're using some open source browser alternative suggests that they're not you're regular joe sixpack.
(note: I still think IE is less secure than FF but not by your reasoning)
You're wrong.
It's not that trigonmetric functions are hard to learn, it's that they rely on transcendal function like sine/cosine which are calculated numerically (as a taylor power series expansion, for example) thus are only approximations to the true values (an accurate number would require the calculation of an infinite series, which isn't practical in given time/space).
The article clearly states that: "Advanced mathematical knowledge, such as linear algebra, number theory and group
theory, is generally not needed." (to use this method)
I think that having a percise, simple (polynomials, rational fractions) alternative to current methods in eucleadian trigonometry, is very welcome.
Wouldn't it be nice to be able to calculate angles and distances without having to use a calculator (for sine/cosine calculations)?
Why do you think they need a better management?
They're perhaps the most successful software company ever...
This in part, has to be due to very good managerial decisions.
Why not just go Open Source?
How would this affect the IM market?
Would it affect the interoperability between the 2 apps?
Would the 2 applications consolidate their user base into a single huge IM user base?
Perhaps it's a preemptive strike against google which recently joined the market?
This could get interesting.
Hey, look... a Burning bridge!
_ print_LOres.PDF
http://www.sun.com/emrkt/rejected/smile_newspaper
(This is actually an approved ad, though they URL may imply otherwise)
Man, you're pathetic.
:)"
You didn't even read his post, yet you flame him.
Since reading isn't your strong side and you obviously don't get math, let me help you out here.
Note the last line of the parent's post:
"Don't assume that each possibility is equally likely .
Which means, in even simpler terms, that you can't assume that the probability for a specific combination of numbers is 1 / "Number of possible combinations".
I'm giving you credit here by assuming that you know "why" each possibility isn't equally likely... but maybe that's a far stretch when it comes to you.
I hope you learned something.
Actually,
r _power.html)
they usually are true.
But most users don't know how to interpret the numbers.
For instance, when they said you speaker system is "1000 Watts" I'm pretty sure they meant the PMPO (Peak Music Power) rating, which means:
(According to http://www.epanorama.net/documents/audio/amplifie
"So called "music power". This power figure tells the power which the amplifier can maximally supply in some conditions. PMPO rating gives the highest measuring value, but this info is quite useless, because there is no exact standard how PMPO power should be measured.
The reason for this power rating was to show the max capability of equipment for recreating strong musical transients like kettle drums and the like. Similar thing (music power rating) was used in the sixties, and I think it assumed a square wave that swung the whole supply range of the output stage. This alone gives them a factor of two over a clean sine wave note. But the ugliest thing they did was to assume that the high power lasted such a short period of time that the power supply caps would hold the voltages steady without any drooping. In the real world, an under powered PS could be hidden by this ruse and the PMPO might be a factor of 10 or more higher than what could be sustained on a nice instrumental performance.
Forget what adverts say about peak power or other "power terms" because they are not standardized and anyway comparable between equipments. Just look for "RMS continuous Power" or other reliable power rating (like DIN power). "
Generally, there isn't any direct mapping between PMPO and RMS (Root Mean Square) since every manufacturer formulates his own PMPO measurements....
Most of the time the RMS value of a speaker is about 10 times lower than the PMPO rating.
Which in your case, Means ~100 Watt RMS (This is VERY good for a single channel... but it's kind'a low for a large multi-speaker system).
Hope this helps.
Regarding Tom's Hardware Guide, I'll have to disagree with you.
I usually find Tom's Reviews very in depth and unbiased.
Moreover, I've seen products get bad reviews many a time.
Especially check out the roundup articles where he compares many products of the same type (like, 17" LCD monitors), he then usually recommends 1 or 2 products that performed the best. You can verify his reasoning and testing methods trough out the article.
Tom's Hardware Guide has taken a very dramatic role in my hardware purchase decision making in the last few years and it never let me down.
When Tom says some thing's good... you know it's good 99% of the time.
"The adjective smitten has 2 meanings:
Meaning #1: (used in combination) affected by something overwhelming
Synonyms: stricken, struck
Meaning #2: marked by foolish or unreasoning fondness
Synonyms: crazy, dotty, gaga, enamored, infatuated, in love, soft on, taken with"
So I suppose we shouldn't really take this review seriously.
66.72% of the entire population of New Orleans is Black.
So I suppose that I stand corrected.
Regarding our education system, though you have a valid point regarding it being indecent, However, I don't think that what it lacks is "ethnic makeup classes".
Notice how at least 80% of those who were left behind are black people.
In the country I come from, this shows the USA in a very bad light.
It shows off how ugly Capitalism can be when not everyone is given equal opportunities/education.
Unless a government acts responsibly enough and develops the product for the good of humanity...
Though you'd need pretty serious lobbying to get past the corrupt officials.
2.09593 Mj/l
PC-to-PC calls were available for ages... some software do this very well.
But PC-to-Regular Land Lines and Cellular Phones at extremely competitive international/long-distance rates (at least where I live) is the *real* breakthrough.
So until this project supports such services...
Nothing to see here, please move along.
I assume currency is incompatible with equality too...
So how can one be rewarded for his achievements in an anarchistic society?
Are there Laws in such a society?
An officer of the law seems unequal with a regular citizen, are they allowed?
If not, who's to defend the helpless?
who's to stop crime and gangs from forming and enslaving others - thus indirectly defeting individual freedom...?
Justifies the entire cost of the system.
Regarding a well publicized computer espionage case.
It seems, the authors of the spying tool used in this case, were arrested in the UK and are being turned over to Israel for justice.
This raises the same moral question, whether an author of the tool is responsible for the way it's being used.
Should Fire Arms companies be held responsible whenever someone uses their branded rifle to commit a crime?
Market share is everything. Market share = power.
How many copies of windows out there are pirated copies, in your opinion?
I assure you that the numbers exceed by a factor of at least 3, the number of legally purchased copies.
(I'm only considering home-users)
Do you think that hurts Microsoft?
Hell no.
It makes them much stronger.
The bigger the market share - the more developers you got working on writing apps for that OS.
The more apps - the stronger your hold.
Apple has everything to gain from making their OS a common commodity.
Forget about the "apple experience bundled only with apple branded hardware " - I think apple has peaked itself with that attitude.
Time to expand - or die.
Why would anyone use an AdWare WebBrowser, when there are completely free alternatives, like Firefox, without the ads to piss you off?
I wasn't sure why Dido was reviewing linux...
I mean, she sings so well, why the sudden career change?
Ofcourse, API changes are almost inevitable.
But a good design can create a generic API that could keep up with software progress for many years.
Furthermore, solutions like WebServices, and other self describing interfaces, can help create intellegent GUIs capable of displaying only VALID options and dynamically adapt to changes.
That aside, a form of RPC is much more of a robust solution than a script front-end would ever be.
You seem to have completely missed my point.
I never suggested that scripts are a bad thing.
I never said my X server was broken or that I was going to fix it with some GUI "configurator".
The entire point of my discussion was to say that "things" should be "standardized".
The example referred to an X config file.
Never said the server was broken, or that something didn't work.
I used it as an example, of HOW one can interpret the IDEA of exposing an API to do changes in a standard way.
X is not necessarily the correct place to implement such an approach; however, it was merely used for the sake of an example.
The Idea: Make changes in a standard way via an API or an XML schema or WHATEVER.
But don't have each dev write a new script to parse and make specific changes, as it locks down the ability to update the software being configured without breaking the "configurators"!!!
Whereas an API would bypass this... problem.
Btw, you don't need X working to expose an API.
It could/should be a library like... libxconfig.so
And apps could link to it.
It would have functions like, "SetDefaultScreen(ScreenObject scr)" or whatever.
THIS IS JUST AN EXAMPLE! NOT NESSICERALY A GOOD ONE!
This, btw, does NOT prevent scripts from being used.
You can use this exact API from within scripts!
However, It would be preferred that All changes to a program would be made via a common interface, so that Updating the program would transparently update everyone!
Regarding:
"And implementing a GUI interface for a script is not a hack; it is a textbook example of the model-view separation principle"
I disagree. It perhaps fits into this description; however it is the poor way of doing it. It's not robust at all!
A good example would be the edonkey2K core and GUI, where they communicate via UNIX sockets or something.
Any RPC driven front-end is better than a front-end interpreting text output from a script!
Perhaps you should take the time to thoroughly consider this before bashing the idea and proving that you misunderstood the entire concept.
Obviously, you've never developed software professionally.
Take for instance, app 1, that uses some script to change some configuration file.
and app 2, that uses an api to make config changes.
now, let's suppose that the application using the config file, decides to change config file format, or perhaps do a more subtle change, like, "1" is true instead of "true" being true.
now, app 1, would break since it's script is not compatible with the change.
however, app 2, would continue to function normally, as the API was updated according to the change.
this way, you centrelize the problem, and transperently update the configuration apps saving trouble for a trillion config-app-devs from updating their scripts.
besides,
script front ends have many other issues,
not to mention speed...
for instance, error reporting.. it's horrendous to guess what went wrong with a script.
you usualy get an error message sent to the console which the front end program has no idea how to interpert, so it usualy, just displays it in a message box.
An API design, would give the config app a LOT more information on the error and it's cause, thus, letting it suggest solutions.
another problem with script front ends, is that it's not a 1 package deal. i.e. if the app won't work, it could either be, the gui or the script or some other dependency of both.
in an API design, it's either the GUI or a direct dependency for the gui.
which makes troubleshooting a heck lot easier.