You mention that such a thread was discussed ~20 years ago, and such information is so old that it's aging off the web. Considering that I was a toddler ~20 years ago, I could not have understood it then, I think. So why not start a new thread now to replace the threads aging away?
Why SQL? Edit: Joking aside, I had read the information on REST. I did give it more than a few minutes' thought prior to posting. But I still did not quite understand its prevalence today; perhaps that speaks to my inability to comprehend or analyze information. Regardless, I decided to post on HN in the hopes that someone would help me out - I wasn't arguing for, nor against, REST. Could you suggest another forum where to post? What else should I do when I've read the available information and still don't "get it"?
All the C derivatives are getting closer to one-another. How different are Typescript, C-sharp, and Java? When JavaScript adds gradual typing, interface, etc. won't all these languages be nearly the same? The runtimes will differ but the language features and syntax will be almost the same.
What I failed to say when suggesting a POST only API was that the various access methods could be encoded in the body of the request. Also I didn’t understand that REST isn’t tied to HTTP’s methods - but rather HTTP is itself a REST implementation... from what I understand. Thank you for that.
I have an idea. Why don't we give up on a strictly declarative format/solution? What if, associated with each possible API call, was a pseudocode or generalcode representation of the code executed to validate the request?
Is reading code snippets that difficult? For a short validation program, a machine could certainly infer if a type would be accepted (just run the validation).
I know that a declarative format seems like the right choice, given validation in mainstream programming languages is expressed declaratively via the type system, but these standards, to me, often seem to only translate awkwardly an implicit validation program into a very verbose declaration.
Damn. I was just in one like two weeks ago looking for a laser tag system. The prominent NERF gun display right by the entrance was glorious. NERF has progressed significantly and has also developed a new kind of spherical ammo in case you were wondering. I'll have to buy a few while they're on clearance.
Would you say that working out those problems has given you a solid fluency in math, in that you spend little to no time now on approaching a new problem? I want to develop a strong intuitional base in math, and from what I've read solving problems is the way to go.
I'm going to try that forming that habit. I think that there definitely is a "snowball" effect to productivity, in that easing yourself into work by starting with the small things is more effective than starting on something big right away.
I think there's a great analogy for why he cares so little about his intelligence: do you think Michael Jordan sat around admiring his build, his height, etc? In a competitive environment, it's best to accept that some of your abilities are fixed, so you can focus on training what can be bettered.
I think the key mechanic that makes games like Minecraft fun is simply the creative element. Once players are given the opportunity to not only experience a dynamic world, but also shape it, that's when they feel that it's truly not static. Otherwise, the "procedurally generated" aspect is just eye-candy, as the reddit post mentioned.
As a relatively young programmer, I feel that I'm just now exiting this stage of over-abstraction and pursuing a "perfect" design. Perhaps it does plague many older programmers, but to me super object oriented programming was a sort of programming puberty. In high school, I would sit down to write a Java program and figure that I would have to construct this grand architecture where each class reused absolutely no code and fit perfectly in an abstraction hierarchy. Of course, I would quickly lose focus of business logic and write a gazillion SomethingSomethingRepresentation classes and get nowhere. It really hit me when I realized I had a file named Null.java :)