One can think of the Mona Lisa in this application as the "environment," and "fitness" of a picture candidate is defined, as in nature itself, as the picture "best" suited to the environment. For digital pictures, "best" is then determined by minimal per-pixel RGB mismatches.
The lifeform is the DNA/polygon sequence that is tested against its environment.
So this is quite Darwinian in that the lifeform evolves to fit its environment. This application could, I think, be applied to any picture to approximate it.
One time a buddy and I were walking, carrying our loaves of bread.
My Apple BreadPro slipped out of its bag (it ripped open) and hit the pavement. It only suffered a slightly crushed corner, but did leave some crumbs on the ground.
My buddy's bag also ripped open at the exact same time (weird, huh), and his DellBread WheatMaster 1400XL landed on its corner, but the damage was devastating. He lost both heels, and some of the slices were all over the ground.
He bought apple bread after that, which just seems to hold together better. They have a unibody, unsliced construction ya know.
1.x: First release from either a new company, or of a new product. If the former, it's probably innovative if a bit quirky (wait for 3.0). If the latter, check for a "Home" qualifier, or look for the "Pro" moniker, then decide and wait for version 3.
2.x: It's amazing the feedback they've received through "anonymous, not personally identifiable" network connections. They've been really busy fixing bugs and adding enhancements. Unfortunately, they don't fix the bugs and functional issues that you've noticed.
3.x: Now we're getting somewhere. Many bugs are fixed, usability is improved, and memory footprint is still reasonable. Backup this version, this is the version you are looking for. Stock splits, investors take note.
4.x: Version 4.x is usually released far longer after the previous release than any other release. That's because Version 3 was such a kickass product, that everybody who wanted it has it, and sales have now dropped. But what a cash cow Version 3 was. Version 4 introduces the rental license, with mandatory bi-yearly upgrade deactivation with NannyAlert(tm). Stock has a mild bump up to 42% of what it was a year ago, then drops back to 35%.
5.x: Hmm, sales continue to plummet, so/obviously/ it's from piracy. Version 5 introduces per-machine CPU serial number locking (or a USB dongle), a new EZ-to-Yoose one-window interface, and a Registry Cleaner, "for Security". Walmart begins selling it. Fry's begins offering rebates.
6.x: You must be writing antivirus, portable document, checkbook-balancing, or tax prep software. Start looking at newer vendors or other products, because those offerings will be closer to Version 3 functionality.
14.x: Autodesk called, they want their CAD system back.
200x: For software companies, a year-based version number is the proverbial White Flag of Surrender. It's an acknowledgment that their development process is so encumbered by well, Process, their quality control so numbed by despondent QA testers, and innovation positively hindered by burnout and irrelevance, that any hope of a release more often than the vernal equinox is out of the question.
201x: First OS X release. In a Cider wrapper.
--------
On a serious note to the OP, I do see version numbers >5 as "has been". History has shown that innovation is long gone, and major releases contain minor enhancements ("Now supporting CSV and XML formats!") Why not exhibit some courage and make it not 1.0, but 1.0! and make a statement? Innovation takes courage. Deception is not innovation.
If I saw a new product, especially with a 6.x version number, I really would wonder where it's been. "It must have not sold very much before, I wonder if it's still crap?"
I, too, have been working on three apps, and have put them on hold.
The seemingly arbitrary blocking/rejection of certain apps makes me wonder just what their criteria is. For some, such as the net tethering application, it is obvious (direct competition/avoidance of AT&T's minutes plans). But for other apps, what is the criteria?
It is starting to look like the iphone app market is closing, because if Apple is declaring certain apps to be "duplicate functionality", then how can competition have a role?
The developers who were first to the store have all the advantage right now. I.e., timing, not functionality or merit, is key. Apple should clarify exactly what they are doing, which policies they are employing to make this determination.
Maybe I'll just write some "flashlight" apps -- those always get accepted./rolls eyes
The Windows program TopoFusion (www.topofusion.com) will merge photos with GPS logs, and place them on a map. As you said, make sure the camera is synced to GPS time.
I've used TopoFusion for a few years and have been pretty happy with it (primarily used for cycling logs and making rough maps of trails).
The shorter handles are for thigh or knee control, hence the curved sides.
I wonder how that would feel. I mean, doesn't the Segway turn by the rider rotating one of the grips? As a cyclist, I think that would feel extremely odd, but I've not tried it.
But I suppose with leg control it may feel a little more natural leaning into a turn a bit.
I don't have any idea about the licensing in this case, but using code with an unclear license opens your business up to a lot of unwanted attention and possible legal action. Thats not a good thing even if you don't want ethical crusaders working for you.
That's just it, using code with unclear permissions is just a bad idea IMO. It takes such a small effort to ask permission, and if not granted, not too much time to rewrite the 200 lines from the original example.
I've been in a similar situation. I used to do a *lot* of Mac OS hacking from about 1990-1994, and shared my code on Usenet, got it published on CD-ROM collections, etc. Most of the comments I received was just banter from other developers, some great code improvements, etc. A few years later, probably 97 or so, I received a frantic email from a company that used some of my custom UI control code in a just-about-released commercial product. On the one hand, since they admitted this, I had them by the short hairs -- if I wanted to. My intention in sharing the code, however, was to just share the code. I told them to use it if they wanted, I provided it as-is without support, and I require a copy of their product, which I did receive a couple months later.
My point is, code snippets posted in developer forums are intended to demonstrate an idea, and I believe the expectation is for others to use the code. (Especially if someone asks how to do something and another posts code to do so.) But at the same time, it's usually fairly easy to confirm with the author the intention, and to get explicit permission. What if that 200 lines of code was 2000 lines of fairly complicated computation? You should probably give the author *some* compensation since the code was so useful or shortened your development time.
I disagree. While GCC is the current cornerstone to much free software, if it didn't exist you can rest assured that another compiler would fulfill the role. Hackers always create the tools they need, and the incredible variety of supported architectures and platforms in GCC/Binutils proves this out.
The high cost of tool chains does not mean they didn't exist. The tools to create a free compiler were always there.
If there wasn't GCC, there's LCC. If no GAS there's NASM. If no bison there's yacc and byacc. etc. (I'm not making any claims as to the comparability/compatibility of these various tools; they have had different amounts of effort put into each.)
Boost's threading library is nicely done. One aspect of Boost I like are the various lock types. scoped_lock is great for placing in a code block and having it cleaned up properly: func() {
blah;
blah;
{
scoped_lock theLock(m);
blah2;
blah2;
} }
In some test code I needed time delays. Boost's types for measuring time are clumsy, but as I remember that is one area they are working to fix.
Vista: Atrocious licensing extortion, no definite technical benefit, and a glitzy UI. Five years and a rewrite for what? I'd hate to have been working on any part of that (hmm,/me remembering the article about the developer who worked on the shutdown option for a year...).
This is still America, you fascist! That means that we still have the right not to vote, and bitch loudly and incessantly about whatever it is that bugs us, without one iota of a sense of responsibility to help the situation. Now biggee size my four-layer burger, and shove it into the back of my SUV, I have a baptist convention to attend.
I kid, I kid. I think... ----
Some spots in Texas, e.g. Dallas, have reported problems with electronic machines during early voting last week. The machines kept flipping various votes to the Republican candidate. No final word on it from election officials, other than a "your fingernail was in the wrong place" type of response.
FWIW, I voted with a #2 pencil on paper ballots today.
Slashdot Mirror
I'm a lazy remixer. I love gapless playback while on shuffle mode.
One can think of the Mona Lisa in this application as the "environment," and "fitness" of a picture candidate is defined, as in nature itself, as the picture "best" suited to the environment. For digital pictures, "best" is then determined by minimal per-pixel RGB mismatches.
The lifeform is the DNA/polygon sequence that is tested against its environment.
So this is quite Darwinian in that the lifeform evolves to fit its environment. This application could, I think, be applied to any picture to approximate it.
We could power entire metropolises with my mother in law.
This is totally false. An AC doesn't deserve the time for a more complete reponse than "admin" perms != "root".
One time a buddy and I were walking, carrying our loaves of bread.
My Apple BreadPro slipped out of its bag (it ripped open) and hit the pavement. It only suffered a slightly crushed corner, but did leave some crumbs on the ground.
My buddy's bag also ripped open at the exact same time (weird, huh), and his DellBread WheatMaster 1400XL landed on its corner, but the damage was devastating. He lost both heels, and some of the slices were all over the ground.
He bought apple bread after that, which just seems to hold together better. They have a unibody, unsliced construction ya know.
Software Version Number Guide
1.x: First release from either a new company, or of a new product. If the former, it's probably innovative if a bit quirky (wait for 3.0). If the latter, check for a "Home" qualifier, or look for the "Pro" moniker, then decide and wait for version 3.
2.x: It's amazing the feedback they've received through "anonymous, not personally identifiable" network connections. They've been really busy fixing bugs and adding enhancements. Unfortunately, they don't fix the bugs and functional issues that you've noticed.
3.x: Now we're getting somewhere. Many bugs are fixed, usability is improved, and memory footprint is still reasonable. Backup this version, this is the version you are looking for. Stock splits, investors take note.
4.x: Version 4.x is usually released far longer after the previous release than any other release. That's because Version 3 was such a kickass product, that everybody who wanted it has it, and sales have now dropped. But what a cash cow Version 3 was. Version 4 introduces the rental license, with mandatory bi-yearly upgrade deactivation with NannyAlert(tm). Stock has a mild bump up to 42% of what it was a year ago, then drops back to 35%.
5.x: Hmm, sales continue to plummet, so /obviously/ it's from piracy. Version 5 introduces per-machine CPU serial number locking (or a USB dongle), a new EZ-to-Yoose one-window interface, and a Registry Cleaner, "for Security". Walmart begins selling it. Fry's begins offering rebates.
6.x: You must be writing antivirus, portable document, checkbook-balancing, or tax prep software. Start looking at newer vendors or other products, because those offerings will be closer to Version 3 functionality.
14.x: Autodesk called, they want their CAD system back.
200x: For software companies, a year-based version number is the proverbial White Flag of Surrender. It's an acknowledgment that their development process is so encumbered by well, Process, their quality control so numbed by despondent QA testers, and innovation positively hindered by burnout and irrelevance, that any hope of a release more often than the vernal equinox is out of the question.
201x: First OS X release. In a Cider wrapper.
--------
On a serious note to the OP, I do see version numbers >5 as "has been". History has shown that innovation is long gone, and major releases contain minor enhancements ("Now supporting CSV and XML formats!") Why not exhibit some courage and make it not 1.0, but 1.0! and make a statement? Innovation takes courage. Deception is not innovation.
If I saw a new product, especially with a 6.x version number, I really would wonder where it's been. "It must have not sold very much before, I wonder if it's still crap?"
I, too, have been working on three apps, and have put them on hold.
The seemingly arbitrary blocking/rejection of certain apps makes me wonder just what their criteria is. For some, such as the net tethering application, it is obvious (direct competition/avoidance of AT&T's minutes plans). But for other apps, what is the criteria?
It is starting to look like the iphone app market is closing, because if Apple is declaring certain apps to be "duplicate functionality", then how can competition have a role?
The developers who were first to the store have all the advantage right now. I.e., timing, not functionality or merit, is key. Apple should clarify exactly what they are doing, which policies they are employing to make this determination.
Maybe I'll just write some "flashlight" apps -- those always get accepted. /rolls eyes
OS X + 1 = OS XI
I can't wait for it to rival Rocky or the Super Bowl.
The Windows program TopoFusion (www.topofusion.com) will merge photos with GPS logs, and place them on a map. As you said, make sure the camera is synced to GPS time.
I've used TopoFusion for a few years and have been pretty happy with it (primarily used for cycling logs and making rough maps of trails).
The shorter handles are for thigh or knee control, hence the curved sides.
I wonder how that would feel. I mean, doesn't the Segway turn by the rider rotating one of the grips? As a cyclist, I think that would feel extremely odd, but I've not tried it.
But I suppose with leg control it may feel a little more natural leaning into a turn a bit.
But with an IM client you don't need a text plan, so this cost is irrelevant. And the data plan is unlimited.
Somebody cast magic missile.
Ha!
Anybody know the reason for this?
Ah, nice quote!
Hmm, surely there's been at least one useful post and one accurate summary before.
Therefore, I mod this +1, Plausible.
That's just it, using code with unclear permissions is just a bad idea IMO. It takes such a small effort to ask permission, and if not granted, not too much time to rewrite the 200 lines from the original example.
I've been in a similar situation. I used to do a *lot* of Mac OS hacking from about 1990-1994, and shared my code on Usenet, got it published on CD-ROM collections, etc. Most of the comments I received was just banter from other developers, some great code improvements, etc. A few years later, probably 97 or so, I received a frantic email from a company that used some of my custom UI control code in a just-about-released commercial product. On the one hand, since they admitted this, I had them by the short hairs -- if I wanted to. My intention in sharing the code, however, was to just share the code. I told them to use it if they wanted, I provided it as-is without support, and I require a copy of their product, which I did receive a couple months later.
My point is, code snippets posted in developer forums are intended to demonstrate an idea, and I believe the expectation is for others to use the code. (Especially if someone asks how to do something and another posts code to do so.) But at the same time, it's usually fairly easy to confirm with the author the intention, and to get explicit permission. What if that 200 lines of code was 2000 lines of fairly complicated computation? You should probably give the author *some* compensation since the code was so useful or shortened your development time.
Ooh-la-la!
Ooooooh-laaaa-laaa
SimCity, SimAnt and SimLife were time sinks that were worth it.
Hmmm, that gives an idea.
H2 - will it blend?
I disagree. While GCC is the current cornerstone to much free software, if it didn't exist you can rest assured that another compiler would fulfill the role. Hackers always create the tools they need, and the incredible variety of supported architectures and platforms in GCC/Binutils proves this out.
The high cost of tool chains does not mean they didn't exist. The tools to create a free compiler were always there.
If there wasn't GCC, there's LCC. If no GAS there's NASM. If no bison there's yacc and byacc. etc. (I'm not making any claims as to the comparability/compatibility of these various tools; they have had different amounts of effort put into each.)
Boost's threading library is nicely done. One aspect of Boost I like are the various lock types. scoped_lock is great for placing in a code block and having it cleaned up properly:
func()
{
blah;
blah;
{
scoped_lock theLock(m);
blah2;
blah2;
}
}
In some test code I needed time delays. Boost's types for measuring time are clumsy, but as I remember that is one area they are working to fix.
Vista: Atrocious licensing extortion, no definite technical benefit, and a glitzy UI. Five years and a rewrite for what? I'd hate to have been working on any part of that (hmm, /me remembering the article about the developer who worked on the shutdown option for a year...).
I'm waiting for aiglx/compix/etc because I want jiggly windows on my PS3.
Maybe that would get us the bump to Web 2.1. ...RC 0
Seriously, good initiative.
This is still America, you fascist! That means that we still have the right not to vote, and bitch loudly and incessantly about whatever it is that bugs us, without one iota of a sense of responsibility to help the situation. Now biggee size my four-layer burger, and shove it into the back of my SUV, I have a baptist convention to attend.
I kid, I kid. I think...
----
Some spots in Texas, e.g. Dallas, have reported problems with electronic machines during early voting last week. The machines kept flipping various votes to the Republican candidate. No final word on it from election officials, other than a "your fingernail was in the wrong place" type of response.
FWIW, I voted with a #2 pencil on paper ballots today.
Corrected:
thank you Dr. Pedantic and the previous posters who, it is blatantly obvious, are all members of the Anal-Retentive Guild
Oh yes, I'm very serious.