Just wanted to add that I've been using Flex 4 in production for more than 6 months now, and there is absolutely no reason I would ever go back to Flex 3. My first project with 4 was to convert a Flex 3 app to Flex 4, and while the transition wasn't easy, it was quite smooth. In addition, I got the chance to replace all the old buttons with nice vector button skins, which reduced file size, and I picked up a massive performance increase just by switching to spark.
Re:Run with more threads than processors
on
Clean Code
·
· Score: 1
He's not saying that you should debug concurrency with more threads than processors. What he is saying is that you should first work out issues not related to concurrency in threaded code, and then fix the concurrency issues using whatever method you deem correct.
I agree with the parent. I started programming in Perl, solving little 30 minute problems from a local programming competition. Things like processing an input file for interesting data, writing algorithms for interesting math rules, and even implementing a game or two. The best thing a budding programmer can do is learn how to program. Whatever language they end up doing their programming in shouldn't matter, because once you know how to program, switching languages is easy. Personally, I would recommend Python as the best starting language because it's highly object-oriented, but if you know C/C++ teaching Perl might be easier.
True, but WiFi service also allows customized mapping (MITs campus), the possibility of easy traffic data when phones start to have WiFi, and many other things that are impossible without the ability to determine location.
Slashdot Mirror
Just wanted to add that I've been using Flex 4 in production for more than 6 months now, and there is absolutely no reason I would ever go back to Flex 3. My first project with 4 was to convert a Flex 3 app to Flex 4, and while the transition wasn't easy, it was quite smooth. In addition, I got the chance to replace all the old buttons with nice vector button skins, which reduced file size, and I picked up a massive performance increase just by switching to spark.
He's not saying that you should debug concurrency with more threads than processors. What he is saying is that you should first work out issues not related to concurrency in threaded code, and then fix the concurrency issues using whatever method you deem correct.
I agree with the parent. I started programming in Perl, solving little 30 minute problems from a local programming competition. Things like processing an input file for interesting data, writing algorithms for interesting math rules, and even implementing a game or two. The best thing a budding programmer can do is learn how to program. Whatever language they end up doing their programming in shouldn't matter, because once you know how to program, switching languages is easy. Personally, I would recommend Python as the best starting language because it's highly object-oriented, but if you know C/C++ teaching Perl might be easier.
True, but WiFi service also allows customized mapping (MITs campus), the possibility of easy traffic data when phones start to have WiFi, and many other things that are impossible without the ability to determine location.