Awww, cute kitten! Our cat lacks front claws (we could tell when he was a kitten that he wasn't learning that retracting them was a good thing), but he's made up for it with his teeth and back claws. I'm the only one who plays with him "rough", but I make sure he gets his energy out. Most days, I come away from our rumble with scratches up my arms (from him being on his back, defending himself with back claws) and puncture wounds in at least one hand, but nothing too evil. He does this one-eyed-twitch when he's thinking of attacking something, and snorts when angry (rather than hissing). Saying "no" around him tends to set him off, even if not directed at him. But he's the sweetest kitten in the mornings and evenings when he's tired -- preferring to be held for hours (only by his mommy, naturally.)
I was always afraid that not being around other cats (even as a kitten, he and his sister were dropped off at the vet 2 days after birth) was going to stunt his ability to deal with them when he did finally meet them. A friend of ours came over with her cat, dropped him off, and she and my girlfriend went on a week-long trip to utah. The cats got along okay, and the style of play was pretty much what I had taught ours -- except Dmitri still has his front claws. The look of abject terror on Indy's face was terrific. He hates playing with us "rough" if we cover our hands or arms with anything. If you wear gloves for the fight, he'll just attack your wrist instead, or your elbow.
He never wakes me up though. He sleeps on our legs as he sees fit, but he only wakes up my girlfriend (including, one morning, sticking his paw in a glass of water she'd kept on the nightstand, and flicking it all over her face as a wake-up call. Most mornings he just invades her pillow and purrs in her ear.) Once she's up and gone to work, he comes back to sleep on me, and doesn't budge when I get up.
Ours is part-maine-coon... he loves water. He's pretty good about his bath (once every week or two -- the long fur catches stuff, and ew). Once you get him in the bathtub, he gives up. He'll try to wander off while you're not looking, but nothing terrible -- no claws or screaming. The worst part is "wringing him out" (tail, paws) and wrapping him up in a towel for a few minutes. We're "in trouble" with him for a few hours after that. When we still had CRT monitors, he would try to sit on those to warm up and dry off. Now he tries to sit on our laptops to do the same. He apparently determined that "technology" gives him warm, fuzzy feelings. (Sadly, ours was the runt of his litter, only 13 pounds at age 3. His sister was bigger than him already when they were kittens.)
Working from home (as a guy) is just about as bad for your image. My mate works in a "real" job (IT manager for the county), so she pokes fun at me for being the one staying home. I get to watch the cat, change the laundry, accept packages arriving (for her)... and yeah, pretty much everyone around me asks if I work. Apparently to work, you not only have to have income from it, you also have to have an office away from home. (I fully respect "homemakers" for the work they do, particularly if there are lots of kids at home... but then, I vacuum and do the dishes, and wouldn't have it any other way. If one of us weren't employed, we'd still split the chores.)
"When your house is on fire, it's not the time to talk about remodeling."
You're right. While the house is on fire, you should be thinking "hey, once they're done removing this wreck from the plot of land, what should we build in its place?" If nothing else, you should probably think to build a house that won't so easily set itself on fire. Besides, in our current political climate, everything's always on fire (it keeps people interested/scared;) if we keep putting off design issues until better days, we'll never get there. (No, I don't program XP-style, and yes, I do like replacing software from scratch -- even my own.)
As everyone else is pointing out, you can just include the criterion in the result set, and do your parameterization that way.
Indeed: we use Firebird (the db server,) and for cases where you're doing param'ed views, it works just as well (speed-wise) to pull from the view with extra search criteria attached -- the optimizer sees the whole thing as one statement and optimizes it accordingly. It runs just as fast, and it doesn't restrict you to the parameters you thought of initially when creating the function. Firebird does support procedures returning datasets, and you can use them in an sql query, but they're a little odd (to me) in that they're expected to return results for a bit of everything, and you join against them for the more specific result you care about... basically, you're expected to create (as I understand it) a dynamic view, join against it, and it'll figure out how to make just enough happen to answer your query. Did I mention I don't use that feature much at all?
It would be nice if all symbols (set-valued procedures, functions, views, tables, anything) could be used completely interchangeably, but current products tend to disallow that kind of thing (sadly).
... actually, that's not always been the position (vague) of the FSF. it's been -also- said that dynamically linking with a library is the -same- thing as statically linking, thus making it subject to the same rules. sure, it's debated, and sure, it's never been tested in court. but it's not as clear as you would like it to be.
if you want your stuff to be usable, make the client libraries LGPL. period.
If Zend continues to shy away from MySQL and completely joins forces with Sun, MySQL may soon no longer be part of the picture, and cheap, fast development may no longer be possible for PHP developers in the same capacity as it is today.
Maybe you don't realize this, but PHP supports quite a range of database products. The fact that it seemed to favor MySQL over the rest didn't really help anything; it just made more people use a product they wouldn't necessarily have chosen on its own merits alone, and directed more programming/bug-fixing toward that one product. Postgresql or Firebird, SAP or Oracle... you have plenty of choices, and fast development doesn't depend on MySQL. In fact there are problem domains where MySQL slows down development because of lacking features. It's something to consider. Unless PHP drops all support for database operations, it'll remain useful for these kinds of applications. There's no reason to give up hope!
And as to MySQL, remember it's not as free as the rest. Like Qt and MySQL (Trolltech and MySQL AB) are both using dual-licensing to make their products "free" for some use, but not for others. MySQL's client libraries are GPL rather than LGPL, which makes using them for corporate projects less... legal. It makes sense for a language like PHP to distance itself from such projects -- not eliminate support, just appear less entangled. It cleans everything up, and leaves us with obvious choices to be made.
... and I have never, ever used PHP's ability to embed PHP code inside of HTML. I'm a C coder at heart, so I still use 'echo' and whatnot for those few cases where there's actual output; most of my code however is algorithm-oriented, with a little bit of output here and there... because of this, I have trouble seeing PHP as anything but yet another interpreted language like perl, except with slightly different syntax and different built-in functionality and libraries. and I have used PHP as glue between programs, particularly between my own C++ programs and existing utilities provided alongside the OS...
What a language is good for is determined by a few things: a) what it can express (access to libraries, etc.) b) what it can express quickly
PHP has access to libraries for doing all sorts of random work, just like perl or C. And the speed with which it can express a given task varies at least partially (mostly?) based on your familiarity with the language. I've coded in PHP more than perl -- it's been months since I've touched perl, so I likely don't want to spend half an hour re-learning parts of it when I need a script written. I coded in C++ just a few minutes ago (and most of every day), so I may still prefer that to PHP even for some small script-like tasks, unless I just know I don't want to deal with input/output stuff, formatting, etc. How "good" a language is (in general) is rarely a factor, nor is "what the language was meant for" -- things change, evolve... eh.
... how 'bout we require patent holders to very obviously be seeking to do something useful with their patents, immediately? you don't get to sit on it, you don't get to hold it and wait for someone else to get the idea... and you absolutely don't get to claim patent rights if someone else invents the same thing without your help (though it'd be hard to prove they didn't see your patent application, even if you don't document elsewhere.) regardless, patent holders should be required to obviously be trying to find buyers from day 1, or be building their own solution (not vaporware) based on the patent. the whole point is to give you a little extra time (advantage) to get your shit together before the competition comes in, -not- to give you a nice legal monopoly to sit on. besides, if companies are already innovating... do we need patents? the point was incentives -- if they're going to create new algorithms and machines because there's a market for them (if there's no market within a few years of an invention, the patent is just an expense to you)... then we don't need patents at all. (reminder: incentives of this sort are created out of the clear blue sky, and should be just as easy to repeal.)
... and also note that mysql wants to charge you a fee if you use it in your business (if it ever makes a difference in your revenue) regardless of whether or not you want support.
postgresql and firebird are both free for personal -and- corporate use, as I recall. they're both slower for the sorts of things mysql users usually want (retrieve by id, grab entire slice of the db to post-process in app code), but both enforce constraints, have stored procedures, good transaction handling (a comment above says postgres is getting savepoints, firebird already has savepoints; postgres is also from the looks of it getting nested transactions which firebird isn't), etc... and you are free to make non-gpl apps with support for these databases (and even include a copy of the db installer too) even in corporate settings. I suppose the mysql-killer would be a featureless version of either of these db's -- faster, less sane, but still free...
Citizen's arrest? Something about holding the person until the soonest possible moment you can hand him/her over to actual cops... but there are also annoying rules about what you can/can't do to them in order to hold them. Eh.
As to prank calls, well, that's also an issue of intent. If you don't seem to find the matter terribly funny (cops will likely take their sweet time leaving, such that the prank won't be funny anyway), I doubt they'll charge you unless they're just having a really bad night.
And as to the issue at hand... they want money for public performances. What can I say? It's an entirely pragmatic, economic issue. Anything dealing with copyright is about -trying- to make sure movie studios (and artists in general) feel it's worth their time to make stuff. It never had anything to do with what was idealy correct, on any level.
I could define a private party as "my door will be open, bring drinks, we'll be showin movie A at X time." My idea of privacy isn't everyone else's (I'm actually not fond of large groups of people) -- if they want to restrict public performances, they should probably put a warning on movies that reads/says "not to be shown to more than N people at a time."
Or consider a business showing a movie to all employees -- it's not open to the public, it's a well-known, planned list of guests... but it could be a huge number of people. They'd probably like to get money from that too, but... will they?
We can confirm that. Our app has been recording every message box it pops up for about a year. User, timestamp, question, response, and how long it took them to decide. We check it every once in a while to see if old bugs have popped up again (users never tell us themselves), or to see if something's just plain annoying (warnings about possibly bad data, when it actually legitimately happens all the time.) An extreme majority of message boxes are dismissed within 1 second -- and we're usually at least somewhat verbose (symptom, likely cause, probably solution, politeness, etc.)... there's no way they're actually reading them. We've considered adding a feature to make it impossible to respond to a message box under a certain time limit (based, say, on the length of the message and standard reading speed.)
It's been useful though -- we've had users claim they don't remember doing something, claim the app "just messed up" and never asked them. We have the message box log to confirm they did, in fact, answer "yes" to all seven warning boxes that appeared. Maybe clicking [ok] so many times, so quickly, actually somehow erased their memory. It's research-worthy. (Yes, the other possibility is that someone was using their computer while they were in the bathroom. Eh. If so, it's their own damn fault for not locking the console/gui/whatever.)
I think the idea was that ISPs should not refuse to open ports to you unless they know for sure something fishy is going on (at which point their terms of service will likely be getting you kicked off.) The idea is to have it off by default to make normal home users less useful to spammers releasing spam-relay-virii. You should (as I read the grandparent's description) have the option of running your own home email server if you like. It'd be something to ask for when you get the service set up, or something you'd get a note about before anything changed. "Just call us if you need this" -- nothing special. Sure, there are ISPs that aren't that nice, and would use this as an excuse to do worse things, without recourse. But for the "nice" ISPs out there, this would just be a "if you know to ask, you can have it" thing, that could prevent a lot of spam and make it less useful to have virii floating around. (Make sure it's listed somewhere obvious, with an easy way to get it enabled.)
The same would be true, I would imagine, of other ports the ISP thinks are often "on" uselessly, leaving security holes open. They shouldn't even ask for a reason -- it should be enough to get a request from a customer.
You're right. I should tell my users, starting today, that they can't tell me what's wrong with my app until they have a working patch for it. That's progress. (And it makes my life easier, ne?)
He's an academic (of sorts -- Pascal is the more... irritating of three, the other two being Date and Darwen): his purpose is to sit there and tell us how things -should- be, and let us do what we're good at, which is making things happen. Yes, it's annoying, but we -could- try being humble for a minute and realizing this is a cry for help. He sees stuff as sucking, he wants it to be better, and he's not a coder. We're coders, and too lazy to go looking for problems to solve. Seems like the two kinda go together, eh?
The Third Manifesto book (Date / Darwen) actually proposes a new language, with reasoning behind each feature (and choices of the form "having either A or B would be sufficient, so the implementation can select whichever it likes best".) It's a boring book, and I'm not fond of their interest in trying to define an OO basis of their own (I don't think it's flexible enough, nor better-defined than current OO languages), but the rest is there.
Technically, it's not a relational-database concern. Relation variables (tables) aren't sorted, order doesn't matter. Any time your query asks the output to be sorted, it's asking for something extra that isn't appropriate for relations, but -is- appropriate for list/vector/array/what-have-you.
Yes, it's more efficiently done server-side. But a relational database server could, academically, be a full-blown RDBMS and not have any sorting abilities whatsoever.
It's a good thing the Bible doesn't talk about sex. At all. Song of Solomon, anyone? Heck, how many instances of "... A knew B..." can you find in the Bible? How many instances of violence? Women and children being murdered because God said so (yes, that -does- happen)? Or even better -- God deciding, after drowning everyone (minus a few,) that maybe that wouldn't be such a good thing to do in the future? Nor is it uncommon in the Bible to find references to men having multiple wives (particularly kings), without this being a 'bad thing' (tm). Women having sex with their own father so as to bear him children so he can have heirs... people receiving offers for anal sex... yup, the Bible is devoid of any such stuff.
And assuming that the whole "covering himself with a leaf" thing was the result of sin, and the discovery of good and evil... wouldn't unashamed public nakedness (and acceptance thereof) be a return to the "better, good ol' days" of pre-sin innocence?
Do you think most people would put up with the in-between "cheaper, but not free" step? Seems like they'd have to jump from gamer money to ad money, or people might feel they're not getting a good enough deal in the transition period.
What I fail to understand though is how advertising does -anything- anymore. Too much of it. Targetted ads don't help me either -- if I want something, I generally already know I want it, and will do my own searching for the best product and price. If I don't, telling me about it doesn't help either -- I just don't care.
Perhaps part of what the grandparent is trying to point out is that a lot of the/.-related culture revolves around LAMP. That's fine as long as that's actually the best tool for the job -- but people get stuck on things, and if never exposed to other tools won't recognize the better tool when they see it.
So really, it's not so much that we need more Firebird/Postgresql in books because they're better, it's to make sure that the audience gets a bit of everything. MySQL might be seen as a "teaching database", but you don't see programming books exclusively explaining things in terms of Pascal code, assuming you can translate to other languages if you know them. I think it'd be useful for the writing community to make an effort to marry random-seeming technologies together, if nothing else to demonstrate that none of the technologies are weak or narrowly-applicable. I doubt we'll see that though.
Someone else pointed out that web apps rarely need the full integrity and concurrency support of a more featureful database server. Is it that attitude that gives web apps the "toy" reputation they have?
On another note -- unlike most programming languages, MySQL is a commercial operation and the quantity of books focusing on using MySQL probably has something to do with its commercial success. Free advertising? (Must I remind people that unlike MySQL, Firebird and Postgresql are both free-even-in-commercial-circumstances? The same would apply to all linux GUI books focusing on Qt rather than other visual toolkits.)
Nono. You want the competitors to be left standing, with products winning and losing -- you want them to have a reason to try again with a new product, and want them to be around to do so. (Must fail only enough for them to try something different, but not fail so much they give up, or fail by so little they just don't care.)
Also, we need to remember there are issues related to C++ (the language) and C++ compilers, vs. Java (the language) and Java compilers/virtual machines. Is the Java language itself faster than C++?
Here, the issue you brought up of identifying things that will not be true (formally) makes sense. That's thanks to the language. With JIT, Java now compiles for the platform it's on. That's overhead -- imagine all your apps requiring users to have GCC installed so it can compile them as you go, for the target platform. But you can also get platform-specific optimizations (not just compiling for the common denominator), and the run-time optimizations (if done correctly) seem useful too.
Cross-platform compatibility, at this point, is more of an issue of writing good code, and shipping compilers for all platforms. Last I heard there were more platforms with a C/C++ compiler than with Java compilers/virtual machines. But most code isn't written to be cross-platform (people get lazy, or have a schedule.)
Seems now the difference is mostly going to be in the delivery part, not the coding part. Both have standard libraries, both can be optimized, they're similar anyway... It's then all about weighing costs: start-up time (I don't want to fire up a JVM when I run "ls") and run time (I don't need run-time optimization when there isn't much in the way of loops that can be optimized.)
... and that they might have something to gain from it. Most big news outlets are owned by companies that also make/sell movies, music, or other media covered under copyright law that would be worth protecting overseas (your nightly news really doesn't matter in that respect.) Now, it's quite possible that because it's not an inconvenience to them, it simply didn't interest them (and they figured you wouldn't care either.) If this were very much not in their own best interest, they could easily blow it into a "big deal" everyone would suddenly mildly care about (as much as anybody seems to care about anything these days -- oh, wait, has that been true for all of history? Oh.)
Borland C++ Builder 5 has this feature too, though we only recently started using it (and yes, we still use BCB5, too cheap to upgrade.) We didn't get it when it was new, about three and a half years ago. A quick googling shows Builder 5 was release in march of 2000.
... that would be why OSS is partially volunteer work. you agree to do it knowing this can happen to you, and that you're okay with it. if you're not, don't take the risk.
the rest of the world operates around "we want this, we'll pay you to do it." around here, we seem to assume that "i want this, you'll pay me to do it" is going to work. it's not, except if, by sheer luck, you happen to want to do something, and get paid to do it, that someone else is willing to pay for already. and then they're using you again.
we're happy to see stuff released as OSS. the more, the better. just don't take the risk if it's not worth it to you, personally. the programmer is the one liable here, it's up to each programmer to decide how much value there is in a particular project/feature.
Slashdot Mirror
Awww, cute kitten! Our cat lacks front claws (we could tell when he was a kitten that he wasn't learning that retracting them was a good thing), but he's made up for it with his teeth and back claws. I'm the only one who plays with him "rough", but I make sure he gets his energy out. Most days, I come away from our rumble with scratches up my arms (from him being on his back, defending himself with back claws) and puncture wounds in at least one hand, but nothing too evil. He does this one-eyed-twitch when he's thinking of attacking something, and snorts when angry (rather than hissing). Saying "no" around him tends to set him off, even if not directed at him. But he's the sweetest kitten in the mornings and evenings when he's tired -- preferring to be held for hours (only by his mommy, naturally.)
I was always afraid that not being around other cats (even as a kitten, he and his sister were dropped off at the vet 2 days after birth) was going to stunt his ability to deal with them when he did finally meet them. A friend of ours came over with her cat, dropped him off, and she and my girlfriend went on a week-long trip to utah. The cats got along okay, and the style of play was pretty much what I had taught ours -- except Dmitri still has his front claws. The look of abject terror on Indy's face was terrific. He hates playing with us "rough" if we cover our hands or arms with anything. If you wear gloves for the fight, he'll just attack your wrist instead, or your elbow.
He never wakes me up though. He sleeps on our legs as he sees fit, but he only wakes up my girlfriend (including, one morning, sticking his paw in a glass of water she'd kept on the nightstand, and flicking it all over her face as a wake-up call. Most mornings he just invades her pillow and purrs in her ear.) Once she's up and gone to work, he comes back to sleep on me, and doesn't budge when I get up.
Ours is part-maine-coon ... he loves water. He's pretty good about his bath (once every week or two -- the long fur catches stuff, and ew). Once you get him in the bathtub, he gives up. He'll try to wander off while you're not looking, but nothing terrible -- no claws or screaming. The worst part is "wringing him out" (tail, paws) and wrapping him up in a towel for a few minutes. We're "in trouble" with him for a few hours after that. When we still had CRT monitors, he would try to sit on those to warm up and dry off. Now he tries to sit on our laptops to do the same. He apparently determined that "technology" gives him warm, fuzzy feelings. (Sadly, ours was the runt of his litter, only 13 pounds at age 3. His sister was bigger than him already when they were kittens.)
Working from home (as a guy) is just about as bad for your image. My mate works in a "real" job (IT manager for the county), so she pokes fun at me for being the one staying home. I get to watch the cat, change the laundry, accept packages arriving (for her) ... and yeah, pretty much everyone around me asks if I work. Apparently to work, you not only have to have income from it, you also have to have an office away from home. (I fully respect "homemakers" for the work they do, particularly if there are lots of kids at home ... but then, I vacuum and do the dishes, and wouldn't have it any other way. If one of us weren't employed, we'd still split the chores.)
I, for one, welcome our new (glow-in-the-dark) cockroach overlords? (or rather, successors?)
"When your house is on fire, it's not the time to talk about remodeling."
You're right. While the house is on fire, you should be thinking "hey, once they're done removing this wreck from the plot of land, what should we build in its place?" If nothing else, you should probably think to build a house that won't so easily set itself on fire. Besides, in our current political climate, everything's always on fire (it keeps people interested/scared;) if we keep putting off design issues until better days, we'll never get there. (No, I don't program XP-style, and yes, I do like replacing software from scratch -- even my own.)
Just let it burn.
As everyone else is pointing out, you can just include the criterion in the result set, and do your parameterization that way.
... basically, you're expected to create (as I understand it) a dynamic view, join against it, and it'll figure out how to make just enough happen to answer your query. Did I mention I don't use that feature much at all?
Indeed: we use Firebird (the db server,) and for cases where you're doing param'ed views, it works just as well (speed-wise) to pull from the view with extra search criteria attached -- the optimizer sees the whole thing as one statement and optimizes it accordingly. It runs just as fast, and it doesn't restrict you to the parameters you thought of initially when creating the function. Firebird does support procedures returning datasets, and you can use them in an sql query, but they're a little odd (to me) in that they're expected to return results for a bit of everything, and you join against them for the more specific result you care about
It would be nice if all symbols (set-valued procedures, functions, views, tables, anything) could be used completely interchangeably, but current products tend to disallow that kind of thing (sadly).
... actually, that's not always been the position (vague) of the FSF. it's been -also- said that dynamically linking with a library is the -same- thing as statically linking, thus making it subject to the same rules. sure, it's debated, and sure, it's never been tested in court. but it's not as clear as you would like it to be.
if you want your stuff to be usable, make the client libraries LGPL. period.
If Zend continues to shy away from MySQL and completely joins forces with Sun, MySQL may soon no longer be part of the picture, and cheap, fast development may no longer be possible for PHP developers in the same capacity as it is today.
... you have plenty of choices, and fast development doesn't depend on MySQL. In fact there are problem domains where MySQL slows down development because of lacking features. It's something to consider. Unless PHP drops all support for database operations, it'll remain useful for these kinds of applications. There's no reason to give up hope!
... legal. It makes sense for a language like PHP to distance itself from such projects -- not eliminate support, just appear less entangled. It cleans everything up, and leaves us with obvious choices to be made.
Maybe you don't realize this, but PHP supports quite a range of database products. The fact that it seemed to favor MySQL over the rest didn't really help anything; it just made more people use a product they wouldn't necessarily have chosen on its own merits alone, and directed more programming/bug-fixing toward that one product. Postgresql or Firebird, SAP or Oracle
And as to MySQL, remember it's not as free as the rest. Like Qt and MySQL (Trolltech and MySQL AB) are both using dual-licensing to make their products "free" for some use, but not for others. MySQL's client libraries are GPL rather than LGPL, which makes using them for corporate projects less
... and I have never, ever used PHP's ability to embed PHP code inside of HTML. I'm a C coder at heart, so I still use 'echo' and whatnot for those few cases where there's actual output; most of my code however is algorithm-oriented, with a little bit of output here and there ... because of this, I have trouble seeing PHP as anything but yet another interpreted language like perl, except with slightly different syntax and different built-in functionality and libraries. and I have used PHP as glue between programs, particularly between my own C++ programs and existing utilities provided alongside the OS ...
... eh.
What a language is good for is determined by a few things:
a) what it can express (access to libraries, etc.)
b) what it can express quickly
PHP has access to libraries for doing all sorts of random work, just like perl or C. And the speed with which it can express a given task varies at least partially (mostly?) based on your familiarity with the language. I've coded in PHP more than perl -- it's been months since I've touched perl, so I likely don't want to spend half an hour re-learning parts of it when I need a script written. I coded in C++ just a few minutes ago (and most of every day), so I may still prefer that to PHP even for some small script-like tasks, unless I just know I don't want to deal with input/output stuff, formatting, etc. How "good" a language is (in general) is rarely a factor, nor is "what the language was meant for" -- things change, evolve
... how 'bout we require patent holders to very obviously be seeking to do something useful with their patents, immediately? you don't get to sit on it, you don't get to hold it and wait for someone else to get the idea ... and you absolutely don't get to claim patent rights if someone else invents the same thing without your help (though it'd be hard to prove they didn't see your patent application, even if you don't document elsewhere.) regardless, patent holders should be required to obviously be trying to find buyers from day 1, or be building their own solution (not vaporware) based on the patent. the whole point is to give you a little extra time (advantage) to get your shit together before the competition comes in, -not- to give you a nice legal monopoly to sit on. besides, if companies are already innovating ... do we need patents? the point was incentives -- if they're going to create new algorithms and machines because there's a market for them (if there's no market within a few years of an invention, the patent is just an expense to you) ... then we don't need patents at all. (reminder: incentives of this sort are created out of the clear blue sky, and should be just as easy to repeal.)
... and also note that mysql wants to charge you a fee if you use it in your business (if it ever makes a difference in your revenue) regardless of whether or not you want support.
... and you are free to make non-gpl apps with support for these databases (and even include a copy of the db installer too) even in corporate settings. I suppose the mysql-killer would be a featureless version of either of these db's -- faster, less sane, but still free ...
postgresql and firebird are both free for personal -and- corporate use, as I recall. they're both slower for the sorts of things mysql users usually want (retrieve by id, grab entire slice of the db to post-process in app code), but both enforce constraints, have stored procedures, good transaction handling (a comment above says postgres is getting savepoints, firebird already has savepoints; postgres is also from the looks of it getting nested transactions which firebird isn't), etc
Citizen's arrest? Something about holding the person until the soonest possible moment you can hand him/her over to actual cops ... but there are also annoying rules about what you can/can't do to them in order to hold them. Eh.
... they want money for public performances. What can I say? It's an entirely pragmatic, economic issue. Anything dealing with copyright is about -trying- to make sure movie studios (and artists in general) feel it's worth their time to make stuff. It never had anything to do with what was idealy correct, on any level.
... but it could be a huge number of people. They'd probably like to get money from that too, but ... will they?
As to prank calls, well, that's also an issue of intent. If you don't seem to find the matter terribly funny (cops will likely take their sweet time leaving, such that the prank won't be funny anyway), I doubt they'll charge you unless they're just having a really bad night.
And as to the issue at hand
I could define a private party as "my door will be open, bring drinks, we'll be showin movie A at X time." My idea of privacy isn't everyone else's (I'm actually not fond of large groups of people) -- if they want to restrict public performances, they should probably put a warning on movies that reads/says "not to be shown to more than N people at a time."
Or consider a business showing a movie to all employees -- it's not open to the public, it's a well-known, planned list of guests
We can confirm that. Our app has been recording every message box it pops up for about a year. User, timestamp, question, response, and how long it took them to decide. We check it every once in a while to see if old bugs have popped up again (users never tell us themselves), or to see if something's just plain annoying (warnings about possibly bad data, when it actually legitimately happens all the time.) An extreme majority of message boxes are dismissed within 1 second -- and we're usually at least somewhat verbose (symptom, likely cause, probably solution, politeness, etc.) ... there's no way they're actually reading them. We've considered adding a feature to make it impossible to respond to a message box under a certain time limit (based, say, on the length of the message and standard reading speed.)
It's been useful though -- we've had users claim they don't remember doing something, claim the app "just messed up" and never asked them. We have the message box log to confirm they did, in fact, answer "yes" to all seven warning boxes that appeared. Maybe clicking [ok] so many times, so quickly, actually somehow erased their memory. It's research-worthy. (Yes, the other possibility is that someone was using their computer while they were in the bathroom. Eh. If so, it's their own damn fault for not locking the console/gui/whatever.)
I think the idea was that ISPs should not refuse to open ports to you unless they know for sure something fishy is going on (at which point their terms of service will likely be getting you kicked off.) The idea is to have it off by default to make normal home users less useful to spammers releasing spam-relay-virii. You should (as I read the grandparent's description) have the option of running your own home email server if you like. It'd be something to ask for when you get the service set up, or something you'd get a note about before anything changed. "Just call us if you need this" -- nothing special. Sure, there are ISPs that aren't that nice, and would use this as an excuse to do worse things, without recourse. But for the "nice" ISPs out there, this would just be a "if you know to ask, you can have it" thing, that could prevent a lot of spam and make it less useful to have virii floating around. (Make sure it's listed somewhere obvious, with an easy way to get it enabled.)
The same would be true, I would imagine, of other ports the ISP thinks are often "on" uselessly, leaving security holes open. They shouldn't even ask for a reason -- it should be enough to get a request from a customer.
You're right. I should tell my users, starting today, that they can't tell me what's wrong with my app until they have a working patch for it. That's progress. (And it makes my life easier, ne?)
... irritating of three, the other two being Date and Darwen): his purpose is to sit there and tell us how things -should- be, and let us do what we're good at, which is making things happen. Yes, it's annoying, but we -could- try being humble for a minute and realizing this is a cry for help. He sees stuff as sucking, he wants it to be better, and he's not a coder. We're coders, and too lazy to go looking for problems to solve. Seems like the two kinda go together, eh?
He's an academic (of sorts -- Pascal is the more
The Third Manifesto book (Date / Darwen) actually proposes a new language, with reasoning behind each feature (and choices of the form "having either A or B would be sufficient, so the implementation can select whichever it likes best".) It's a boring book, and I'm not fond of their interest in trying to define an OO basis of their own (I don't think it's flexible enough, nor better-defined than current OO languages), but the rest is there.
Technically, it's not a relational-database concern. Relation variables (tables) aren't sorted, order doesn't matter. Any time your query asks the output to be sorted, it's asking for something extra that isn't appropriate for relations, but -is- appropriate for list/vector/array/what-have-you.
Yes, it's more efficiently done server-side. But a relational database server could, academically, be a full-blown RDBMS and not have any sorting abilities whatsoever.
It's a good thing the Bible doesn't talk about sex. At all. Song of Solomon, anyone? Heck, how many instances of "... A knew B ..." can you find in the Bible? How many instances of violence? Women and children being murdered because God said so (yes, that -does- happen)? Or even better -- God deciding, after drowning everyone (minus a few,) that maybe that wouldn't be such a good thing to do in the future? Nor is it uncommon in the Bible to find references to men having multiple wives (particularly kings), without this being a 'bad thing' (tm). Women having sex with their own father so as to bear him children so he can have heirs ... people receiving offers for anal sex ... yup, the Bible is devoid of any such stuff.
... wouldn't unashamed public nakedness (and acceptance thereof) be a return to the "better, good ol' days" of pre-sin innocence?
And assuming that the whole "covering himself with a leaf" thing was the result of sin, and the discovery of good and evil
Do you think most people would put up with the in-between "cheaper, but not free" step? Seems like they'd have to jump from gamer money to ad money, or people might feel they're not getting a good enough deal in the transition period.
What I fail to understand though is how advertising does -anything- anymore. Too much of it. Targetted ads don't help me either -- if I want something, I generally already know I want it, and will do my own searching for the best product and price. If I don't, telling me about it doesn't help either -- I just don't care.
Perhaps part of what the grandparent is trying to point out is that a lot of the /.-related culture revolves around LAMP. That's fine as long as that's actually the best tool for the job -- but people get stuck on things, and if never exposed to other tools won't recognize the better tool when they see it.
So really, it's not so much that we need more Firebird/Postgresql in books because they're better, it's to make sure that the audience gets a bit of everything. MySQL might be seen as a "teaching database", but you don't see programming books exclusively explaining things in terms of Pascal code, assuming you can translate to other languages if you know them. I think it'd be useful for the writing community to make an effort to marry random-seeming technologies together, if nothing else to demonstrate that none of the technologies are weak or narrowly-applicable. I doubt we'll see that though.
Someone else pointed out that web apps rarely need the full integrity and concurrency support of a more featureful database server. Is it that attitude that gives web apps the "toy" reputation they have?
On another note -- unlike most programming languages, MySQL is a commercial operation and the quantity of books focusing on using MySQL probably has something to do with its commercial success. Free advertising? (Must I remind people that unlike MySQL, Firebird and Postgresql are both free-even-in-commercial-circumstances? The same would apply to all linux GUI books focusing on Qt rather than other visual toolkits.)
Nono. You want the competitors to be left standing, with products winning and losing -- you want them to have a reason to try again with a new product, and want them to be around to do so. (Must fail only enough for them to try something different, but not fail so much they give up, or fail by so little they just don't care.)
Also, we need to remember there are issues related to C++ (the language) and C++ compilers, vs. Java (the language) and Java compilers/virtual machines. Is the Java language itself faster than C++?
... It's then all about weighing costs: start-up time (I don't want to fire up a JVM when I run "ls") and run time (I don't need run-time optimization when there isn't much in the way of loops that can be optimized.)
Here, the issue you brought up of identifying things that will not be true (formally) makes sense. That's thanks to the language. With JIT, Java now compiles for the platform it's on. That's overhead -- imagine all your apps requiring users to have GCC installed so it can compile them as you go, for the target platform. But you can also get platform-specific optimizations (not just compiling for the common denominator), and the run-time optimizations (if done correctly) seem useful too.
Cross-platform compatibility, at this point, is more of an issue of writing good code, and shipping compilers for all platforms. Last I heard there were more platforms with a C/C++ compiler than with Java compilers/virtual machines. But most code isn't written to be cross-platform (people get lazy, or have a schedule.)
Seems now the difference is mostly going to be in the delivery part, not the coding part. Both have standard libraries, both can be optimized, they're similar anyway
so for an N-way SMP, combining this with a fork() bomb might work out nicely?
... and that they might have something to gain from it. Most big news outlets are owned by companies that also make/sell movies, music, or other media covered under copyright law that would be worth protecting overseas (your nightly news really doesn't matter in that respect.) Now, it's quite possible that because it's not an inconvenience to them, it simply didn't interest them (and they figured you wouldn't care either.) If this were very much not in their own best interest, they could easily blow it into a "big deal" everyone would suddenly mildly care about (as much as anybody seems to care about anything these days -- oh, wait, has that been true for all of history? Oh.)
Borland C++ Builder 5 has this feature too, though we only recently started using it (and yes, we still use BCB5, too cheap to upgrade.) We didn't get it when it was new, about three and a half years ago. A quick googling shows Builder 5 was release in march of 2000.
... that would be why OSS is partially volunteer work. you agree to do it knowing this can happen to you, and that you're okay with it. if you're not, don't take the risk.
the rest of the world operates around "we want this, we'll pay you to do it." around here, we seem to assume that "i want this, you'll pay me to do it" is going to work. it's not, except if, by sheer luck, you happen to want to do something, and get paid to do it, that someone else is willing to pay for already. and then they're using you again.
we're happy to see stuff released as OSS. the more, the better. just don't take the risk if it's not worth it to you, personally. the programmer is the one liable here, it's up to each programmer to decide how much value there is in a particular project/feature.