8,592 karma · joined March 30, 2014
I don't see this as being entirely a bad thing. While nurses and other caregivers can be an important source of human contact for the sick and elderly, caring and being cared for by another person can be an emotionally and physically fraught and draining process. If we can build automated systems that allow baseline physical and hygienic needs to be met, even for the frailest and sickest people, I think that had to be good for the mental health of both those needing care, as it will reduce their sense of being a burden, and on the caregivers themselves, as they will be able to focus on the most important quality-of-life issues instead of being stuck on a treadmill of providing basic care.
It is possible to build these systems using OO, by reifying the network of functions and the data into objects. But all you are really doing is reinventing functional programming with a layer of OO cruft on top of it, and it is always going to be easier to build the equivalent system in a language that lets the functions and the data structures be unencumbered.
For programming tasks that actually are best conceptualised as objects, OO works quite well. These usually involve the provisioning of some largely static virtual environment, such as a UI, game world, or inversion of control container. Here, objects are long-lived, genuinely independent, and interact in well-defined ways via actions and events, usually swapping only small pieces of state.
My guess is that the advent of GUIs and sophisticated games in the 80s and 90s pushed programmers to be more interested in this latter type of problem, and this was reflected in the languages that evolved. Then the advent of the internet and machine learning in the 2000s and 2010s revived interest in data processing and data flow, and so language design began to shift back.
I suspect in 100 years, if humans are still doing any programming, all popular languages will be mixed-paradigm, and the question of OO vs functional will simply be a blend decided by needs of the problem at hand, rather than the kind of dogmatic arguments of this era, which will be viewed through a historical lens as rather quaint and silly.
Now consider the sheer volume of trash — paper, plastic, foil, fumes, food, etc. — many individuals and organisations throw out every day. It essentially defies comprehension, but it's a lot. So much that's we've created an incredible reverse supply-chain to get it all out of sight and out of mind as quickly as possible, with the result that we rarely stop to think just how much crap we're all generating.
Set against this, people throwing out a tiny electronic item, even an item containing some nasty toxic stuff inside it, is a very small problem. Smartphones are novel and make for a high-profile target, but the real problem is the more mundane avalanche of detritus that accompanies modern civilisation.
Amy believes the backfire effect is real, whereas Ben believes it is fake. Amy reads an article saying the backfire effect has been disproven, then passes her new opinion on to Ben. What will be Ben's revised opinion of the backfire effect be if 1) the backfire effect actually exists, 2) the backfire effect doesn't exist.
I'll bet that over time the technology will improve and require less intensive management, and for every patient who ends up in an unpleasant twilight between life and death, there's going to be one whose short-term survival inspires doctors to find a way to get them off ECMO. Long-term survival and recovery rates will improve as the years and decades go by, and eventually technology like this will be a regular and uncontroversial part of medicine. Doctors will look back on these early days like we look back on early surgery: as the hardest part of a learning curve that eventually pays off handsomely.
Why is you acting like a slow, biological package manager for small bits of code better than using a real package manager for the same purpose?
Its message seemed to be that, yes, you have virtually no chance of success, but accepting that fact means you have no chance of success. To have a chance, you have to willingly accept a degree of self-delusion, and have a support system of fellow wannabes who'll back up this self-delusion, as you back up theirs.
Since they cannot judge theories scientifically, and they cannot judge them based on how well they're presented, they can only fall back on social consensus and instinctive sense of weirdness. "Trust the academy", would seem to be the more accurate shorthand.
Yes, if all you care about are able-bodied Western users consuming content on standard devices, then you can get away with just baking your style / layout into the markup like your someone hacking away back in the 90s. The moment you need to move beyond that, you'll start to introduce methods for abstracting style and layout that, eventually, will lead you to reinventing something pretty similar to CSS.
The thought of some dev buying this thing just to stare at xcode all day is kinda hilarious.
In the case of these business functions, the standard and correct approach is to outsource them to a 3rd-party service provider. You do this with accountancy, legal representation, facilities, office management, recruitment, etc. If you try to bring all these things in-house from the get-go you'll never get around to building a product, and it's financially and logistically sensible to do it with IT as well. This calculation may change over time as your business grows, but if you can't comprehend that the correct strategy for a fledgling business may not be the same as an established one, then you're simply not suited to run a business in the first place.
Of course, in every case, you're taking a calculated risk by relying on a service provider: They may go bust, they may be incompetent or malicious, they might ramp up their prices. Your job as the manager of a company is to accept and manage these risks as best you can. Risks cannot be eliminated, only managed, and attempting to do is a fool's errand. If things do go wrong, you'll always have people lining up to tell you how you could have avoided this problem, usually it's by making a decision that can be justified with the benefit of hindsight. You should ignore these people. The only question is: did you make the correct decision at the time, based on the facts to hand?
To me, Angular is what HTML and the DOM would look like if they had been designed from the beginning for application development:
- Custom elements backed by controller classes. - Data-binding and event-binding syntax baked into HTML - Component style encapsulation, on by default.
React seems far more like a project created by people who dislike front-end development: As I recall the genesis of the project was to replace traditional DOM mutation with a more PHP-esque approach of updating state and re-rendering everything, just as you would do on the back-end.
That's good, because these aren't the reasons the HTML standard is changed, and to claim they are is absurd.
HTML may have had its origins in SGML, but it has long, long since grown past beyond those origins to become the web platform. Like any other non-dead software platform, it is undergoes a process of refinement and enhancement, not for reasons of "job security" or "Webkit dominance", but to provide additional functionality to allow more and better software to be build with of it, and to remain competitive with other software platforms.
You, and a large constituency of Hacker News commenters along with you, may utterly loathe the web platform. You may wish the web had evolved along entirely different lines, remaining a simple system for server hypertext documents. But the fact is, it didn't, and to act as if that the global development ecosystem that relies on the web platform doesn't exist is ridiculous.
I don't see what is so oxymoronic about this? Just because a consensus has been reached doesn't mean that consensus must be immutable.
Just because the process of standardisation in some technical domains has tended to use versioned documents doesn't mean that such an approach is fundamental to standardisation.
Secondly, most criminal justice systems reward early confession with reduced sentences and plea bargaining. In such systems, presenting a suspect with fabricated evidence—which is what a "positive" lie detection report is—seems just as likely to induce a false confession as a real one.
If we allowed cops to plant evidence and falsify statements, we could probably get a lot more confessions. If we eliminated the "innocent" verdict at trial, or reintroduced trial by ordeal, we could do the same. But we don't do this because these are fundamentally unjust, and so is allowing law enforcement to claim they know people are guilty due to magic.
More concerning is the fact that so many large law enforcement institutions continue to use these systems even after the fact of their ineffectiveness has been established beyond a reasonable doubt. If such institutions cannot weigh and respond to evidence correctly as it relates to their own investigatory methods, why should we have any faith in their ability to handle evidence correctly in the course of those investigations themselves?
And yet, via Github, the community has reinvented the centralised model of software development. For any project, there is a single instance that is the "blessed" version, by virtue of having the most stars or collaborators, or owning the associated package name. 99% of forks are nothing more than a place where you create a feature branch that you intend to PR to the blessed project.
I hope that, one day, somebody invents a git-based project ecosystem that solves the problem of decentralised project management. I don't know exactly what this would look like, but I think it would need to embed the idea of community and contributor consensus and democracy at a fundamental level, separating the concept of the project and project ownership from any individual fork.
Yes, but only because the heart of the modernist movement has been an attempt to deny, belittle and mock the idea that the instinctive aesthetic reaction of the majority to their creations is important or valid. If you think their constructions are ugly, that's not their problem, it's your problem. Firstly, you're too stupid, conservative and narrow-minded to perceive its genius, and secondly, in fact, you actually do like it, or eventually you will, if you just shut up and wait long enough.
It's as if avant-garde jazz advocates were put in charge every radio station and music streaming service on Earth, and given free rein to remorselessly enforce their taste on the whole population, with any dissenter being shouted down and told that, when they eventually forget what all other music sounded like, they'll come to love atonal jazz noise.
In such a situation, the fightback would have to begin with people being told it's OK to trust their own instinct and hate the music that's been forced upon them. Likewise, the fightback against overweening modernism has to begin by bursting the elitist bubble of faux-intellectual obfuscation that modernists have created around architecture. It has to begin by telling people that they have as much right to judge the aesthetics of huge changes to the places they live and work as anybody else, and that if they think the changes are ugly, then that's valid, without any "but..." unfolding into a lecture about how daring and original the latest edifice being foisted upon them actually is.