HN user

ta0967

210 karma
Posts0
Comments141
View on HN
No posts found.

you ignored the silver bullet criticism

i don't think so, i simply refuse to have my arguments framed that way since i'm very well aware of the shortcomings present in what has so far passed for a "RDBMS". i consider velocitypsycho's argument ("Thinking RDBMS is a silver bullet is just as bad as thinking a document database is a silver bullet.") a non-sequitur: the former is a proper superset of the latter, that sentence simply "does not compute".

doubled down on SQL as the silver bullet

where does the post you replied to mention SQL? are you confusing SQL for the relational model?

but we're not talking about silver bullets: we're talking about models which let you derive most information from your data. mathematics says you will get the most bang for your buck from the relational model.

if you like hierarchical databases (data trees), consider that relational database gives you a forest: you can treat any datum as your tree root and bloom from there. with hierarchical, you're tied to a single pre-designated root.

both relational and hierarchical databases let you go from department to employee, only one lets you go from employee to their department without enumeration. what purpose does precluding the latter serve?

like the yesterday's submission of "Why you should never use MongoDB (2013)" (https://news.ycombinator.com/item?id=12290739), this is all just plain sad because totally unnecessary: the failure of hierarchical databases was obvious in 1960s and was the background of Edgar F. Codd's work on the relational model.

unfortunately, this industry is dominated by cocky PFYs (of any age) convinced they don't need to study history of their field and, as a result, don't even recognize they're repeating 50 years old mistakes. sure, SQL has fallen so short of the promise of the relational model it's not even funny, but don't conflate the model with the query language, folks!

HTTPie 0.9.6 10 years ago

the manpage is very explicit about that:

       Use the file name "-" (a single dash) to use stdin instead of a given file.
       Alternately, the file name "." (a single period) may be specified instead of
       "-" to use stdin in non-blocking mode to allow reading server output while
       stdin is being uploaded.

explain the presence of homosexuality in a population when the theory of evolution predicts that any such trait (which leads to much lower genetic fitness) would have disappeared a long time ago

one's homosexuality may improve fitness of one's family: if we're brothers and i'm homosexual, we won't be splitting resources between your and my children, and i'll be an extra "parent" looking after your kids. genetically speaking, that is still a (qualified) success for me.

also, genes don't give a damn about individual's reproduction, and local optima are rampant.

edit: what siblings have said.

HTTPie 0.9.6 10 years ago

do not use -X without having read the manual, it can break redirects and other things.

from the curl(1) manpage:

       -X, --request <command>

              (...)

              Normally you don't need this option. All sorts of GET, HEAD, POST and PUT requests  are  rather
              invoked by using dedicated command line options.

              This  option  only  changes the actual word used in the HTTP request, it does not alter the way
              curl behaves. So for example if you want to make a proper HEAD request, using -X HEAD will  not
              suffice. You need to use the -I, --head option.

              The  method  string you set with -X will be used for all requests, which if you for example use
              -L, --location may cause unintended  side-effects  when  curl  doesn't  change  request  method
              according to the HTTP 30x response codes - and similar.
PUT is indicated by using -T / --upload-file, POST by -d / --data or any --data-foo option (eg. --data-raw). DELETE is the only HTTP method in the parent list that needs -X to be used.

normal conditionals are common in everyday life: "If they don't have a dark roast coffee, get me a medium roast."

"They had dark roast so I got you nothing as requested."

IOW, this program is either incomplete or wrong. Cf. "Get me the darkest roast they have." - ifless, concise, robust.

today. the various BSD systems all come without bash in their default configurations (and it's never in /bin).

this should not be construed as an argument in support of /bin/sh.

yeah, that was really close, wasn't it? just imagine we had all these mature IP protections in place two thousand years ago! so much stuff we could have had by now! imagine no one but the chinese government having access to silk production!? there'd be no nylon made without royalties!

they said "oh, React is one of the better documented frameworks out there"

well, consider the ruby language: it is implementation-defined(!).

i got a Rails job without knowing any of Ruby beforehand (and the other party was aware of this). i made myself comfortable in the office and asked: so where's the Ruby manual? they said, "ruby-doc.org". "that's just the API docs, where's the language reference?" i asked. "there's none. maybe you could use the Bison grammar from the MRI source..." "???"

i've read you comment, and it looks to me like this is a fair rephrasing. can you offer better alternatives where i mischaracterize your position?

* you are allowed to drive under the influence of alcohol and endager other people's lives * you are allowed to kill another as long as they weren't 100% obviously harmless * stealing food is worse than threatening or terminating others' lives

my impression has been that node.js reached the top of its hip curve a few years ago, same with golang. not that they're disused, they're just not obsessive-compulsive topics. this is mostly based on what i (don't) see and hear at work and here.

again, based on what i see on hn, github is actually falling out of favor (we'll see if they can reverse the trend [sic] with the newly released features; the search removal inspires little confidence).

twitter has been around for too long to be trending upwards, it's like facebook. the populace split into users and abstinents has ossified. it's even more pronounced with linkedin which has been around much longer.

i have no idea what's supposed to be trending in programming instead though. recently it's felt to me like a plateau of sorts.