Agreed. Heapsort may not be the fastest in all cases but it is much faster than quicksort in the worst case. I use a heapsort algorithm whenever I am faced with a lot of random items to sort.

There are several reasons that may compel you to design an ASIC. If the algorithm can't run in real-time on the proposed hardware. Reduced hardware requirements of various resources (ram, clock-speed, etc.). Just don't do it because it sounds like a good idea.

I've created dozens of ASICs over my career and there are things you need to consider before doing it.
* Choosing the technology. You want to pick a process that meets your needs (with an engineering margin) at the lowest cost.
* Will the algorithm change over time needing a hardware change?
* Are you prepared to fix your design if it doesn't work the first iteration? There are a significant number of things that can go wrong.
* Do you have ample knowledge of how to test for processing defects so you don't end up shipping broken parts? Testing for defects is different than testing for functionality. You'll also have to learn the needs of the test equipment to design test patterns (test periods, clock cycles, strobes, etc.).
* Is your algorithm amenable to conversion? A direct translation may require resources that don't make sense (take up too much real estate or require components that don't mix well with the chosen technology).

I remember a project, I think called MOSIS, created for Universities. It allows your design to be placed along side of others on the same wafer/cookie to share the expense for low volume projects.

I wouldn't discourage looking into the process, but I expect that you will find it an eye-opening experience.

Thank you, right on the nose. Using equalization can fix some frequency response issues at the expense of adding phase shifts which ultimately destroy the impulse response. The KEFs are nowhere near audiophile quality so I'm not impressed.

Absolutely captivated me. From then on I was a fan. She will be missed.

This is really a lame-brain position. As a long time developer I have two mottos:
* If it isn't tested, it doesn't work.
* A developer make assumptions all the time.

I can guarantee that, if I was responsible for QA on my own code, things would be broken in subtle ways.

Many years ago I did QA consulting for AT&T. We set up a system where the human factors engineering group would document an application in a specification. One copy went to the developers and one copy went to the QA personnel. The QA staff designed a test plan from this spec and then implemented it against the product sent from the developers. I can't tell you how many things the developers missed because of assumptions they made that were caught by the test plans.

This is the reason I picked up a Blackberry Android device. If nothing else, Blackberry has been true to their word about keeping their phones secure. I ran the vulnerability checker and it claims that my Priv is properly patched (at least by the first week of September when the last monthly patches came).

WebOS was a blank sheet of paper new design. It was well thought out and things worked seamlessly, albeit a bit slow as they never got the chance to optimize the javascript engine. I'm still using a WebOS phone daily thanks to the dedicated work of the homebrew community to keep apps running. Every time I have to grit my teeth and use Android or iOS I have a "if only" moment. Damn you Leo!

I couldn't have stated it any clearer. Net neutrality is not the only thing that will suffer under the new head. He's already put the kibosh on work to get carriers to push available security patches to our phones in a timely manner.

However, Trump continues to use a Pew report and twist it's results. Even after Pew publicly stated that their data in the report does not support his claims, he continues to spew the same rhetoric. It's an impressive embrace of Orwellian tactics.

There are over 300 million people in the US. http://www.worldometers.info/w...

There is a nominal point of unemployment that is healthy. If it were 0% then there can be no economic growth. The inflationary pressures happen when it approaches 0% and employers are forced to increase wages to hire from the available pool. http://www.economicshelp.org/b...

This was in reply to meta-monkey that insinuated that he was only talking about black males. This was the racist remark that I was de-bunking.

Examples?

Oh my! So it's OK to fib as long as you're repeating it? Why is it still repeated? He also claims things are supported by research even after being de-bunked. You should join his team, you'll fit right in.

Correction... There are approximately 8 million people in NYC so that is over twice their population.

Note that the data includes all citizens age 16 and older. To find the right number for unemployment, we must remove students, retirees, handicapped, etc. from this pool. Any policies to do with unemployment directly on this data is meaningless and misleading. If you wanted to significantly reduce the 37.3% you would have to put all retirees and students to work. Between 37.3% and 42% proposed by Trump is 18 Million people! That's almost twice the population of NYC.