Many mutually conflicting models can be created to describe the same properties of the same system.
We have no way of ever finding the "truth".
386 karma · joined April 29, 2014
Many mutually conflicting models can be created to describe the same properties of the same system.
We have no way of ever finding the "truth".
If I go to a restaurant and order a meal, and the waiter decides that's a good opportunity to invite his friends to eat from my plate, I'd find this a good opportunity to walk out without paying a dime.
There's a certain kind of people who like to buy into simple formulas for health, success and so on. There are more of them than it's comfortable to admit.
The ad is worded to appeal to them, because after all Soylent is a business, and which business would ignore the large segment of the market that'll be buying your product regularly, every single day?
For those who are more balanced thinkers, Soylent remains an interesting option when you need to have a meal on the go. Better than fast food.
A side reminded, just like with vitamin pills, you should be skeptical of some of the claims made about Soylent's ingredients. Say, just because a product has calcium in some form doesn't mean your body can assimilate it in that form.
Contracts aren't written and signed just so you can sue each other. Contracts are written and signed as an evidence for both sides about what both sides agreed at the time, because no one's memory is that good. Contracts are written so when the proverbial s--t hits the fan, both sides are aware of what happens and are fine with the consequences.
And in all of those cases it pays to use the correct, specific, unambiguous language to express the intent of both sides. Expressing intent isn't easy. You can't go back and fix a contract easily the way you can say "Oh no, I mean X, not Y" in a casual conversation.
Lots of people, resources and time are about to be spent fulfilling a contract. A lot of problems will occur on the way to it being fulfilled.
If you think it's an option to take contracts lightly and you think it's an option to just trust fate & the goodwill of people you didn't know yesterday to sacrifice themselves in order to save your money, time, property and business, it's a sign you've not been burned enough times to learn to think otherwise.
Remember, that when stress gets high, and both sides paint themselves in a corner, even the most moral, loyal and honest of people may find themselves bending their morality, loyalty and honesty in order to survive in an impossible situation.
And now just think about this for a second - a bee explosion. Is this really a better problem to have, seriously?
My scientific opinion is that some problems are just not meant to be solved. Instead, we should look into quadcopter beebots.
If you don't cannibalize yourself from time to time, someone else will eat you. Fact of life.
Or in simpler words. Stop bitching, and port that library to Python 3.
Also, it hits me as some awful mutation to be using your "external protocol" (voices) for internal communication.
Is the claim they were literally hearing voices? Can't be right.
First you'd constantly be getting startled or confused whether someone in your head said something, or someone outside your head said something.
Second there's an inherent lag in converting speech to information and back, when the brain is interconnected well enough with much more efficient ways of communicating internally.
Speech is also highly inaccurate. Same sentence can have multiple meanings. Imagine the hilarious misunderstandings between you and your internal voice.
Which brings another point. How do you answer back? Do you speak out loud, or does the mind have a dedicated "internal speaker" for you to say things into?
Another awkward redundant apparatus.
If they check out, we use the stories to extrapolate reality, i.e. build models that predict where reality will go based on our stories.
There are three things to keep in mind:
1) There are infinite stories that may be equally good at describing the same reality. It's best to pick the simplest one that has a set of benefits we need, because why make our life hard, right?
2) If we can't measure how a story matches reality, the story is useless. Say, how on Earth would we measure if people had voices in their minds 3000 years ago? We can't. Therefore the story can't be verified.
3) One should be very careful not to confuse the stories with the reality it models. A story is a story. A model is a model. A math formula is a math formula.
Reality is neither a story, a model, or a math formula. So when it comes to explaining the true nature of things, such as what the heck conscience is, and how it comes to be, science comes short. Because it always has been, and it always will be, just making up stories. But that doesn't make science any less useful, of course.
It seems like W3C are trying to please everyone. Hence the result.
Chances are not only all people are conscious and introspective, but most animals are to some degree (it's not an on/off switch, it's an emergent property, the sum of all your reasoning skills).
As for bicameralism, it's just a demonstration of the lengths at which our wrong assumptions can reach when the subject we're creating conjecture about (ancient people) are no longer around, or otherwise unable to explain themselves.
There are plenty of people in the modern day, which claim to have heard the voice of god (or the devil, or aliens, or what have you), which might be a mental disturbance, or quite often is a simple confusion (a dream taken for reality, and so on).
It's just how the mind works to this present day. Sometimes we misinterpret input and make up reasons.
Heck, the theory of bicameralism seems like an example of making up reasons.
Now write this in SQLAlchemy without strings, without concatenation, and let's see which provides you with more clarity.
In the latter case it's also unclear when your queries run in a transaction, which isolation level the transaction is, heck, in many ORM you barely know when the server gets called at all (it's usually not when you expect it's called), nor you have any guarantees about the order in which your updates are fed to the server.
You also have no control to supply direct SQL when you need to as you have no direct access to the connection, or the ORM relies on caching where direct access would cause inconsistent data.
The difference between an ORM, and a simple query generator under your control seems like a subtle detail, but as the wise ones said, the devil's always in the details.
No standard is perfect, but the worst standard is no standard.
Make up your fucking mind already.
Committees only work to codify existing de-facto standards as official standards.
Look at any of the big standards we're using and you'll discover their origins are often a small team or even a single person.
It's funny that SPDY was considered a good thing for the most part, until it tried to become a standard, and everyone had their chance to complain about it.
It's a well-known caveat. Experts would rather focus on the flaws of the alternatives in order to "disprove" their viability, rather than try & find solutions for said flaws.
This solar panel technology may not have all the benefits of traditional roads, but it has benefits which traditional roads don't. It's not possible to really know which set of pros/cons is better for us today, before the technology is tested and iterated upon, to weed out the inevitable issues that will pop up.
Any new technology in the history of humanity has failed the "thought exercise" experiments of those deemed experts at the time. Cars, computers, airplanes, heck, even computer mice were called "impossible" at some point.
CSV is bullshit, it's not good for anything except scenarios where you control both the export process, and the parser (so you know what delimiter is used and so on).
This means a programmer has to tell apart two types of recursion based on how a compiler optimizes them. It's possible to learn, but this qualifies as a "leaky abstraction".
It's far better to use loops when you want to loop, and recursion when you want to recurse, and if the compiler happens to use TCO, so be it. But don't rely on TCO.
Instead, we see here whole algorithms which depend on TCO to work without filling up the stack. It's a path towards more obscure code, not more succinct code.
If your language religiously omits loops, it's understandable why you'd need to emulate loops this way, but the alternative solution is: have loops in the language.
This leaves us with continuations, which is a great hack, but again, a hack, for languages which don't implement fibers/coroutines/generators natively (see Python generators, see C# await/async, etc.).
This is not the path we have to go down to. Layering hacks upon hacks, so we can implement other hacks on top of it.
If we need loops, have a language with loops. If we need coroutines, the language should implement coroutines.
Keep in mind we use said "proofs" to justify how we treat animals used for food, experiments, hunting them for sport, and so on.
http://www.eecs.harvard.edu/~kalyans/research/snapshots/supp...
Other info that gets damaged during NameCheap transfers may include company name, phone and fax.
I reported it to them. More than a year ago. We've spoken about this. Look how much of a fuck they've given.
It was not long time ago we'd claim that for our peers, based on silly traits like skin color.
By the way, I wonder where's the "proof" that humans experience emotions. I demand someone prove it to me.
It'll be the "60s" maybe for a few months, at the most.
Development is accelerating, and it'll never slow down.
Aren't you a little bit too excited about quantum computing. I'm quite sure that when it becomes practical we'll be able to catch up quickly in terms of programming it.
Doing a CS course in a programming model that has zero application today is not different in terms of sanity that teaching a programming model that stopped being useful years ago.
We do this. I do this. We like to decide "how cool it'd be..." and do something. There's nothing bad in that, as long as we don't start coming up with invented reasons for its reasons to be.
When asked to quickly name a tool, most people say "hammer". When asked to quickly name a site application, most people think "blog". The focus on blogs inadvertently tells you that these authors were scratching their own itch of making the generator itself, and focused on the first application they could think of, and not responding to real needs. I remember when the coolest thing was for everyone to make their own web framework, everyone focused on making frameworks where blogs were easy to set up and demo. Notice a pattern?
In the end though, all sites need a machine to be put on, a server to serve them, and the arbitrary goal of pre-generating basic things like header and footer includes externally has little real value to offer when it comes to business needs ("business" used in a wide sense, as in people's real reason to have a site in the first place).
Any non-static site can maintain a static cache when performance is needed, and any non-static site can be as simple (and therefore as secure, by function of its complexity alone) as you need it. Maybe your non-static site "engine" can just do basic includes and support a contact form, and nothing else. It's easy to secure this, and you draw the line. But there's no need to ever cross that specific line where your site is 100% static. You have nothing to gain from it.