I understand that a time interval is not a good representation for a time event, but again, what about gpp? are you talking about the Gnu Precompiler right?
They must build a partnership with Oracle (and support their database) in order to be seriously considered in enterprises and (finally) get some profits. BTW I don't like Oracle at all, it's just my opinion collected from some real companies that currently pay for RedHat and Suse support.
Of course, everything takes some time, but when something takes too much time, then there is a problem. Of course "too much time" is a subjective matter.
> the developer can check for dynamic library versions during the configuration
Yes, the developer could do a lot of things, but (IMO) the autotools are too difficult to master and use, so the configurations are largely suboptimal. Again, you can point to developer laziness but I believe it's more a conception/requirements/design problem with the tooling.
Ok, I exaggerated with the time... but only assuming that your build will be successful on the first execution (in my experience this is rarely the case.) So you end re-executing configure (with other options or after altering the system in some way). That way it's not uncommon to dedicate several hours for the build, with a lot of that time consumed in the configure executions.
> What autoconf does is check for a representative function in the library
Yes, I understand the reason. The problem is that a lot of projects try dozens of such standard functions apparently with the (false) hope of running on every legendary Unix, so it really takes time. The problem is aggravated when at the end of the process your build fails so you must rerun configure with some correcting option: The same tests usually are reexecuted.. I read there is a cache to avoid it but apparently most autoconf developers just ignore how to leverage it, or doesn't work at all.
"For example, if the ASP.Net application stores sensitive information, such as passwords or database connection strings, in the ViewState object this data could be compromised. The ViewState object is encrypted and sent to the client in a hidden form variable, so it is a possible target of this attack.
If the ASP.Net application is using ASP.Net 3.5 SP1 or above, the attacker could use this encryption vulnerability to request the contents of an arbitrary file within the ASP.Net application. The public disclosure demonstrated using this technique to retrieve the contents of web.config. Any file in the ASP.Net application which the worker process has access to will be returned to the attacker. "
> Care to point out what new problems autotools creates?
Builds that take half an hour just to "configure", checking for the existence of things like strcpy(), but anyway fail at compile or link time because a missing symbol in an upgraded dynamic library?
> How does this compare with young people's enjoyment of negative vs. positive storeis about old people?
Please refer to TFA's postscript: the scientists indeed tried to collect such data, but the damn youths were not able to read any substancial story (positive or negative): they only read tweets.
> Nobody at the time actually believed they were getting a colorful cartoon instead of a lo-res 160x240 blocky game.
Exactly. If the box actually displayed a real screenshot, most people just could not get an idea about the game subject (TFA proves this point.)
I also remember the best looking games for the C64 (for example Law and Order) taking several minutes to load the bitmaps... and more minutes every time you go forward or back the level/scene (at last the first years before the fast loaders.)
Well, not every environment can use Doxygen/Javadoc/whatever. My main client uses mostly COBOL and AFIK they are not interested in buying more software from IBM (I suspect IBM can provide the corresponding tools.) So they just use their good old MS Word with their own templates. I also saw several programmers using Excel (after trying to print at once all the html pages as generated by doxygen)... Maybe I don't get your point.
> 1. The iPhone and iPad notwithstanding, Flash is beginning to show up on other mobile device platforms. > 2. Flash is used for more than just video delivery on the Web. > 3. Adobe provides strong tools and support for designers and developers. > 4. Flash's content protection/DRM appeals to content producers. > 5. Flash remains popular with online advertisers. > 6. HTML 5 still has video codec patent issues to work out.
It would be nice, very nice, if/. editors could take the time to write down that kind of "powered abstract" in order to avoid the remorseful feeling of discussing without reading TFA. Maybe the (few) readers can help with a firehose-powered-wiki?
Think this way: do you prefer testing or writing documentation? at least for me, good tests are an excellent way for users of your code to learn how to use it, so they will not annoy you for comprehensive documentation. What's better, another dummy method or another title+table+paragraph in Word? This works at least for testing library code.
> Of course, Google in using Java in the first place for android, is debatable, still
Until today it was strange for me the Apple's use of an obscure language like Objective-C. The "Cocoa" library portability issue could be just a nice disguise.
Slashdot Mirror
No, it's a car without retro.
Ok... LOL
I understand that a time interval is not a good representation for a time event, but again, what about gpp? are you talking about the Gnu Precompiler right?
Please could you explain why you mention gpp? I can't understand your post at all.
It's 1286686800.
#include stdio.h
#include time.h
main() { struct tm t; t.tm_sec = 0; t.tm_min = 0; t.tm_hour = 0; t.tm_mon = 10 - 1; t.tm_mday = 10; t.tm_year = 2010 - 1900;
printf("%d\n", (int)mktime(&t));
}
> It is impossible to over-recommend learning C if you're interested in programming at all.
But please, for the love of god, avoid developing your applications with C.
They must build a partnership with Oracle (and support their database) in order to be seriously considered in enterprises and (finally) get some profits. BTW I don't like Oracle at all, it's just my opinion collected from some real companies that currently pay for RedHat and Suse support.
> All configuration systems will take some time.
Of course, everything takes some time, but when something takes too much time, then there is a problem. Of course "too much time" is a subjective matter.
> the developer can check for dynamic library versions during the configuration
Yes, the developer could do a lot of things, but (IMO) the autotools are too difficult to master and use, so the configurations are largely suboptimal. Again, you can point to developer laziness but I believe it's more a conception/requirements/design problem with the tooling.
Ok, I exaggerated with the time... but only assuming that your build will be successful on the first execution (in my experience this is rarely the case.) So you end re-executing configure (with other options or after altering the system in some way). That way it's not uncommon to dedicate several hours for the build, with a lot of that time consumed in the configure executions.
> What autoconf does is check for a representative function in the library
Yes, I understand the reason. The problem is that a lot of projects try dozens of such standard functions apparently with the (false) hope of running on every legendary Unix, so it really takes time. The problem is aggravated when at the end of the process your build fails so you must rerun configure with some correcting option: The same tests usually are reexecuted.. I read there is a cache to avoid it but apparently most autoconf developers just ignore how to leverage it, or doesn't work at all.
I really don't understand why some random client can access such information, even after breaking any encryption mechanism.
From http://blogs.technet.com/b/srd/archive/2010/09/17/understanding-the-asp-net-vulnerability.aspx
"For example, if the ASP.Net application stores sensitive information, such as passwords or database connection strings, in the ViewState object this data could be compromised. The ViewState object is encrypted and sent to the client in a hidden form variable, so it is a possible target of this attack.
If the ASP.Net application is using ASP.Net 3.5 SP1 or above, the attacker could use this encryption vulnerability to request the contents of an arbitrary file within the ASP.Net application. The public disclosure demonstrated using this technique to retrieve the contents of web.config. Any file in the ASP.Net application which the worker process has access to will be returned to the attacker. "
> Care to point out what new problems autotools creates?
Builds that take half an hour just to "configure", checking for the existence of things like strcpy(), but anyway fail at compile or link time because a missing symbol in an upgraded dynamic library?
Thank you Adobe! you saved my machine!
Yeah, I also use Oracle on Ubuntu since a long time ago (I remember copying the files from a Red Hat installation.)
But seriously, no company will use, less pay for it.
I know many companies that would install and buy Ubuntu server support if Oracle could run on it.
The old guy thinks along the same line:
http://www.pcmag.com/article2/0,2817,2367331,00.asp
> How does this compare with young people's enjoyment of negative vs. positive storeis about old people?
Please refer to TFA's postscript: the scientists indeed tried to collect such data, but the damn youths were not able to read any substancial story (positive or negative): they only read tweets.
After all, MySql is why slashdot is so relia~ `} v* m& + ' ,
--
Civilization = writing + taxes + booze + hookers
short answer: the cheapest hosting providers didn't forget it yet.
> Nobody at the time actually believed they were getting a colorful cartoon instead of a lo-res 160x240 blocky game.
Exactly. If the box actually displayed a real screenshot, most people just could not get an idea about the game subject (TFA proves this point.)
I also remember the best looking games for the C64 (for example Law and Order) taking several minutes to load the bitmaps... and more minutes every time you go forward or back the level/scene (at last the first years before the fast loaders.)
> And I have no doubt that quite a few delusional audiophiles have shelled out $499 (plus shipping) for the AKDL1.
If thousands of people happily pay about $300 to get a "faster" and "more secure" operating system for their PC...
Well, not every environment can use Doxygen/Javadoc/whatever. My main client uses mostly COBOL and AFIK they are not interested in buying more software from IBM (I suspect IBM can provide the corresponding tools.) So they just use their good old MS Word with their own templates. I also saw several programmers using Excel (after trying to print at once all the html pages as generated by doxygen)... Maybe I don't get your point.
> 1. The iPhone and iPad notwithstanding, Flash is beginning to show up on other mobile device platforms.
> 2. Flash is used for more than just video delivery on the Web.
> 3. Adobe provides strong tools and support for designers and developers.
> 4. Flash's content protection/DRM appeals to content producers.
> 5. Flash remains popular with online advertisers.
> 6. HTML 5 still has video codec patent issues to work out.
It would be nice, very nice, if /. editors could take the time to write down that kind of "powered abstract" in order to avoid the remorseful feeling of discussing without reading TFA. Maybe the (few) readers can help with a firehose-powered-wiki?
Think this way: do you prefer testing or writing documentation? at least for me, good tests are an excellent way for users of your code to learn how to use it, so they will not annoy you for comprehensive documentation. What's better, another dummy method or another title+table+paragraph in Word? This works at least for testing library code.
> Of course, Google in using Java in the first place for android, is debatable, still
Until today it was strange for me the Apple's use of an obscure language like Objective-C. The "Cocoa" library portability issue could be just a nice disguise.