My most annoying test was writing a grammar and recursive descent parser for a set of complex regular expressions on paper.
That professor was simultaneously the best and worst teacher I have ever had. He was a total hard ass, but if you managed to pass his classes, you really ended up learning.
I don't know, there are parts of Alaska, Canada and the Continental Northwest where having a rifle that can switch to full auto might be a better alternative to carrying a second higher caliber gun for bear defense.
I know what you mean. My girlfriend has looked like a 14 year old for the last 12 years. We get odd looks all the time. I can't buy alcohol if they see her in line with me at the store. I'm not really complaining.
For live video streaming, you only need to buffer enough to cover the latency between peers and the time needed to stitch the video stream back together. That is at most a couple minutes / several 10's of megs.
"Is H264 incumbered by any patents not held by the MPEG-LA?" Probably.
The protection that H264 has is that any outside entity filing an h264 patent lawsuit is going to have to defend themselves against MPEGLA's patent portfolio.
VP8 has exactly the same protection from Googles patent portfolio.
The difference between the two is that Google offers a free forever license, where MPEGLA can start charging any amount at any time and that there are no H264 cameras that are legally licensed for commercial or for profit work. Every professional videographer using H264 is in violation of the MPEGLA license.
This looks like almost exactly the same functionality that we were developing. Though we used a java applet for P2P that recombined the signals into a stream that would run on almost any player: flash, quicktime, silverlight media player, embedded windows media player, and many more. We even had a setup that would detect other clients on the local network and they would all source from the same feed, allowing any number of local clients at no additional external bandwidth usage.
We were in the final stages of testing early in 2009, I jumped ship when paychecks started coming in late and a few months before the venture capitalists pulled the plug for good.
It is even funnier when you understand that like pigs, dogs are considered an unclean animal by most Muslims. Any Iraqi killed by "friendly fire" in such an attack would be damned.
Some are oppression fighters (fighting for oppression), the rest see the US as occupying their home and strike at US anywhere. Bin Laden is a little bit of both, he became offended when the Saudi leadership invited the US in during the first gulf war and he also wishes to impose a global Caliphate where a select group of islamic clerics impose anything they say as absolute law and all non-muslims are exterminated.
People generally use the same or similar usernames and passwords for most of their online identities. If you you know someone in particular uses facebook.com, hotmail.com, kittenwar.com and randombank.com you can use facebook and kittenwar as attack vectors against their email and banks. Alone, history sniffing does not present a huge threat. But it can dramatically increase someones vulnerability to identity theft.
Because they are the only ones who have laws that allow them to prosecute people with open wifi as contributing to copyright infringment.
Re:Asynchronous and self modifying code.
on
Programming Clojure
·
· Score: 4, Informative
You are mistaking how you use certain functional programming languages for what functional programming is.
There is no requirement that a functional language allow self modifying code, only that it is expressed as the composition of functions, is stateless and avoids mutable data.
Re:Asynchronous and self modifying code.
on
Programming Clojure
·
· Score: 4, Informative
2: functional programming and self modifying code have nothing to do with one another. functional programming transforms a set of inputs into a set of outputs without reference to any external state. It is a purely mathematical expression. Functional programming languages can be used to write self modifying code, but so can can most languages.
1: if you understand what you are doing, asynchronous programming is easy. All you have to do is prevent screwing up the shared state between threads. Since functional languages have no state to share, you can avoid 99% of the pitfalls of dealing with threading.
I deal with threading every single day. Problems occur when the problem is intractable (and then nothing can help it split), the solution is poorly designed (to much shared state), the language is poorly documented/designed (ambiguous thread safety, inability to be thread safe) or the developer just does not know what they are doing.
Functional programming is good at threading because it eliminates shared state completely. The question is no longer "can I split this, what do I have to rewrite from scratch, and will it be worth it?", but rather "will splitting this be worth the overhead of creating, context switching and synchronizing the threads?"
Abstracting multi-threading to make the syntax easier for inexperience developers is a mistake unless you can also fundamentally prevent most of the issues that make multi-threading a pain in the ass as well. Adding real closures to more traditional languages like c++, java, c# etc would go a long way towards making multi-threading easier to deal with because the vast majority of problematic code in relation to multi-threading will produce a compile error if used within a real closure.
The difference is that the first job is a lot easier to get with a BA than with an AT/AA. After that, the only thing that matters is your experience, skill and how you present yourself.
The market for programmers is there, but it is extremely frugal. I've had two companies die under me in the 2 years and now I am waiting on confirmation that my project is going to be renewed to find out if I need to find a new job. But in each case, I was able to secure a new job in two weeks or less.
You forgot that you also need to know xml and apache configuration settings, plus make if you want to make it into an easily deployable package, and etc...
And that is exactly why I wanted xhtml2 instead of html5. It has a real framework for web applications between xforms and xml events. It is almost exactly what I would have done for my perfect web application format. The only thing I would add would be the ability to send a model from one page to the next without transmitting the data to the server.
That just means that at least 5% of IE users and 50% of ie6 users would rather use something else to browse the web, but are forced to use IE due to the policies of their workplace.
Slashdot Mirror
My most annoying test was writing a grammar and recursive descent parser for a set of complex regular expressions on paper.
That professor was simultaneously the best and worst teacher I have ever had. He was a total hard ass, but if you managed to pass his classes, you really ended up learning.
I don't know, there are parts of Alaska, Canada and the Continental Northwest where having a rifle that can switch to full auto might be a better alternative to carrying a second higher caliber gun for bear defense.
I know what you mean.
My girlfriend has looked like a 14 year old for the last 12 years.
We get odd looks all the time.
I can't buy alcohol if they see her in line with me at the store.
I'm not really complaining.
Just put it in vibrate mode, you wouldn't want to get interrupted, or maybe you would?
You are not thinking strait, those are practical medical applications.
This things first real application in humans? A weight loss supplement for the fabulously wealthy.
Only if you want to save to the hard drive.
For live video streaming, you only need to buffer enough to cover the latency between peers and the time needed to stitch the video stream back together. That is at most a couple minutes / several 10's of megs.
2prophets1cup?
That is why we were going the applet route, no install needed for most systems.
"Is H264 incumbered by any patents not held by the MPEG-LA?" Probably.
The protection that H264 has is that any outside entity filing an h264 patent lawsuit is going to have to defend themselves against MPEGLA's patent portfolio.
VP8 has exactly the same protection from Googles patent portfolio.
The difference between the two is that Google offers a free forever license, where MPEGLA can start charging any amount at any time and that there are no H264 cameras that are legally licensed for commercial or for profit work. Every professional videographer using H264 is in violation of the MPEGLA license.
Well. Damn.
This looks like almost exactly the same functionality that we were developing. Though we used a java applet for P2P that recombined the signals into a stream that would run on almost any player: flash, quicktime, silverlight media player, embedded windows media player, and many more. We even had a setup that would detect other clients on the local network and they would all source from the same feed, allowing any number of local clients at no additional external bandwidth usage.
We were in the final stages of testing early in 2009, I jumped ship when paychecks started coming in late and a few months before the venture capitalists pulled the plug for good.
It is even funnier when you understand that like pigs, dogs are considered an unclean animal by most Muslims. Any Iraqi killed by "friendly fire" in such an attack would be damned.
Some are oppression fighters (fighting for oppression), the rest see the US as occupying their home and strike at US anywhere. Bin Laden is a little bit of both, he became offended when the Saudi leadership invited the US in during the first gulf war and he also wishes to impose a global Caliphate where a select group of islamic clerics impose anything they say as absolute law and all non-muslims are exterminated.
People generally use the same or similar usernames and passwords for most of their online identities. If you you know someone in particular uses facebook.com, hotmail.com, kittenwar.com and randombank.com you can use facebook and kittenwar as attack vectors against their email and banks. Alone, history sniffing does not present a huge threat. But it can dramatically increase someones vulnerability to identity theft.
Because they are the only ones who have laws that allow them to prosecute people with open wifi as contributing to copyright infringment.
You are mistaking how you use certain functional programming languages for what functional programming is.
There is no requirement that a functional language allow self modifying code, only that it is expressed as the composition of functions, is stateless and avoids mutable data.
2: functional programming and self modifying code have nothing to do with one another. functional programming transforms a set of inputs into a set of outputs without reference to any external state. It is a purely mathematical expression. Functional programming languages can be used to write self modifying code, but so can can most languages.
1: if you understand what you are doing, asynchronous programming is easy. All you have to do is prevent screwing up the shared state between threads. Since functional languages have no state to share, you can avoid 99% of the pitfalls of dealing with threading.
I deal with threading every single day. Problems occur when the problem is intractable (and then nothing can help it split), the solution is poorly designed (to much shared state), the language is poorly documented/designed (ambiguous thread safety, inability to be thread safe) or the developer just does not know what they are doing.
Functional programming is good at threading because it eliminates shared state completely. The question is no longer "can I split this, what do I have to rewrite from scratch, and will it be worth it?", but rather "will splitting this be worth the overhead of creating, context switching and synchronizing the threads?"
Abstracting multi-threading to make the syntax easier for inexperience developers is a mistake unless you can also fundamentally prevent most of the issues that make multi-threading a pain in the ass as well. Adding real closures to more traditional languages like c++, java, c# etc would go a long way towards making multi-threading easier to deal with because the vast majority of problematic code in relation to multi-threading will produce a compile error if used within a real closure.
[Citation needed]
There is case law upholding the right of the consumer to copy for personal use.
copying isn't even actionable here.
Nor is receiving a copy.
Only when distributing a copy are you infringing.
I've seen a perfectly bug free computational device. It is called an abacus.
The difference is that the first job is a lot easier to get with a BA than with an AT/AA. After that, the only thing that matters is your experience, skill and how you present yourself.
The market for programmers is there, but it is extremely frugal. I've had two companies die under me in the 2 years and now I am waiting on confirmation that my project is going to be renewed to find out if I need to find a new job. But in each case, I was able to secure a new job in two weeks or less.
You forgot that you also need to know xml and apache configuration settings, plus make if you want to make it into an easily deployable package, and etc...
And that is exactly why I wanted xhtml2 instead of html5. It has a real framework for web applications between xforms and xml events. It is almost exactly what I would have done for my perfect web application format. The only thing I would add would be the ability to send a model from one page to the next without transmitting the data to the server.
Everything is copyrighted as soon as it is distributed, automatically without any other action required.
That just means that at least 5% of IE users and 50% of ie6 users would rather use something else to browse the web, but are forced to use IE due to the policies of their workplace.
The circumvention clause of the DMCA is criminal as well.
http://www.law.cornell.edu/uscode/html/uscode17/usc_sec_17_00001201----000-.html
http://www.law.cornell.edu/uscode/uscode17/usc_sec_17_00001204----000-.html