3,223 karma · joined January 31, 2010
Quote I like:
"Make game of that which makes as much of thee" -- Omar Khayaam
If the universe will die, and that establishes that anything which occurs within it has no meaning, perhaps meaning becomes entirely worthless as a concept. It distinguishes nothing. It becomes identical with mere existence.
I really don't see how YouTube could be seen as anything but anticompetitive in many of its practices. Primarily, the fact that they have used and continue to use revenue driven by search from Google to maintain the tremendous infrastructure necessary to run YouTube. This means that anyone who wishes to compete with YouTube needs to be able to find investors (or pay themselves, but the number of people or organizations that could do that can be counted on one hand) willing to foot the bill to build billion-dollar infrastructure and then expect to run it at a profound loss, burning hundreds of millions of dollars a year for potentially a decade or more. Google is probably making some money on YouTube now, but they ran it at a mountainous loss for years and years for no reason other than suppressing the possibility of competition being developed. There also other smaller things, like the US government deciding to host all of their video content on YouTube without even considering following the legally-required bidding process - because there was no realistic competitor. That's pretty telling.
Sure there have been catastrophic failures like Knight Capital, but those, at leas the ones I am aware of, all boil down to the system having flaws. I have yet to see a system which worked and followed the logic the designers intended, but which is accidentally (or purposely?) exploited by other automated systems doing the same. Shouldn't the complexity of these systems make such a thing almost inevitable and common?
Normally, the "interoperability" defense is used to protect instances of circumventing copyright protection mechanisms, not for copying itself. For instance, that was the defense in the case where Lexmark brought a DMCA claim against a third party ink cartridge manufacturer, claiming that by making their ink work, they circumvented protection mechanisms Lexmark claimed existed to protect their copyrighted firmware code in their ink carts. The court didn't buy it, Lexmark lost, it was established that you can do that kind of circumvention. But this copying of the word list... it's different in a couple fundamental ways, and I don't know if there has been a case that has dealt with this sort of thing.
In any case, thanks for your contributions with a tool that is obviously so useful to so many. I almost never use macOS, but I do own a 2015 MBP from some development I needed it for in the past. Next time I boot it up, you can be sure I will be installing iTerm2. (I might actually have it and just not remember, but I don't think so, I never invested too much into the platform.)
The likelihood a company like Google is reading your emails directly and trying to scoop your business on a product idea or something like that is slim. The likelihood they are profiling your communications in aggregate and producing derivative information like "how many companies in the space are considering hiring" or "do the employees at this company talk about Chipotle" and using that for advertising or data products is, I would guess, pretty high.
This is obviously incorrect. If an AI system of superhuman mental capabilities is installed on a system with no network connection and no physical interfaces, we can completely control the harm is might create. It would be unable to directly act, of course, requiring humans to authorize and carry out whatever plan it devises. But failing to do this should be prosecuted and treated no differently from if a person or company built a tank and then permitted it to drive over and through people. The biggest difficulty here will be that our legal frameworks have no established way to assign liability and criminal culpability to any system involving software. With no legally-enforceable industry standards (like the electrical code followed by electricians, things like that) any prosecution fails as the company can either claim ignorance of the potential harm their system might cause or simply throw individual employees under the bus, claiming they were not acting on direct orders.
It is true that we can not fully specify the goal, and that is a grave concern. It's partially due to this that AI systems shouldn't be directly connected to the ability to act in the physical world unless their attempted actions go through some sort of 'filtering' first.
A collapse would be the perfect and likely sole opportunity to ditch the mistakes of the past and forge something completely new with the benefit of a "foresight" forged from hindsight.
From the customers perspective, the only real difference when it came to reading the billing information they received was that federal agencies received a bill that said 'federal' and others received a bill that said 'non-federal'. No big deal, right? Well, not to most agencies. But the US government works pretty closely with, and extends government-style permissions to, various native American tribal authorities. Native American tribes... do not like to be considered to be part of the US government. At all.
It's entirely understandable, but we had to make a bunch of modifications because they wanted to retain the ability to run 'federal agency' style transactions, but wanted their bills to say 'non-federal'. It actually caused quite a lot of drama, but most of it was isolated to the political side of the agency (software changes are not free, after all, so they tried to be diplomatic and begged the tribes lodging the complaint to just ignore the word 'federal' on the monthly bills they received, but they would not budge and demanded it be changed ASAP) luckily. As software lead on the project I did get to hear about some of the firestorm secondhand when working with management to figure out exactly how we were going to change things. The 'federal' designation was a boolean in the database, used both by us in the billing system to determined what kind of processing to do (it impacted amount charged too, with federal customers getting a small discount) and the frontend of the system to kick out attempts to use transaction types not supported for non-federal agencies. So they couldn't just flip the bit and make them non-federal or it would cause even more chaos. It's been a long time ago now, but I believe we ended up special-casing it so that the report templates for the non-federal bills were applied in cases where the agencies were on a hard-coded list of 'federal but non-federal' agencies. All over text maybe 2 people even ever saw.
One of the ladies in the video shared a concern that there would only be jobs for high-IQ people who could use a computer. That certainly didn't take into account that computers would become tremendously easier to use, but I do think it hints at a problem. It's easily seen that our societies have been eliminating the middle class and splitting into a much more widely disparate lower and upper classes... but I think it might more be moving such that the 'middle class' is only knowledge workers, particularly those working in software. This movement likely would have been quite abrupt if not for the establishment early on of wage fixing by the largest companies (which they were convicted for), but it seems to have been accelerating the past 10 years. It makes some sense economically (not its magnitude, it should be much larger, but its existence) because software is a productivity multiplier unlike anything in world history, but doesn't it bear out her concerns?
Sure when factories came around, craftspeople could transition to working in restaurants, or as cashiers, or working in the distribution chain, etc, because those were things that could be picked up on the job. While using computers has gotten simpler, building systems fundamentally cannot beyond a certain point. If you're building a system which must track 100 things, you must be capable of dealing with those 100 things. If that's something which is beyond your capacities, then its not just a matter of getting trained.
I don't expect automation to be a large-scale problem as quickly as some do (how long have we been hearing about automated factories and how many do we actually have? A long time and not many. They are hard problems.) but I do think concerns are warranted. Concerns were warranted when factories were developed, and we probably would have benefited from some forethought there too. We still carry many of the social changes that occurred to handle the densely packed urban centers that grew up around factories despite none of their original motivating factors still existing. We will most likely see changes on that scale, and strife to match if we just let things happen.
Science isn't just a matter of what people believe. It often gets considered when governments create policy. Bad science can kill millions. I've run into many 'bugs' in the algorithm descriptions published in computer science and mathematics papers, I shudder to think what the code backing nontechnical research is like.
This was awhile ago, up until 2001, so things may have changed but I strongly doubt they have changed very significantly given that even then they were using an NCR mainframe which was literally the very last operational one of its kind (the owner of the 2nd to last one gave us theirs for free when they replaced it with a PC, so we got a DR site!). Their policy was to never change anything that cost a penny if it still functioned. When I left, the bank had been acquired by a larger bank and the plan was to move the smaller banks processing into the larger ones data center. I ran into one of my coworkers 5 or so years later and none of that had happened. Everything was still as it was.
CopyFile([from] 'presentation.md', [to] '/home/presenter')
with the "[from]" and "[to]" parts not being actual tokens that are part of the source file, but annotations that appear to assist the developer. They would appear as little badges, non-editable or selectable, with distinctions in their display to make it clear they are UI elements rather than part of the source code.That's insurance-supported medical care in the US. No one wants to go to the cut-rate bargain-basement doctor. And the majority of patients aren't paying their own medical bills. The insurance company is footing that bill. So when their kid gets sick, they're price-shopping in reverse. They only want the premium level, and offering a good deal actively stops people from using the service.
And that doesn't even get into the price-fixing that insurance companies engage in, entirely legally, because insurance is determined to be "not commerce" and therefore exempt from all antitrust laws. There is definitely a reason why Americas sub-standard care is so expensive - insurance.
That is just an element of consistency. Since the 1980s management 'wisdom' has been centered around the idea that all workers should be fungible, replaceable units of work. Ideas like 'if you are irreplaceable, you are expendable' and the notion that your degree of importance to the functioning of a company is also a measure of how much of a liability you are, etc. They're ideas rooted in the notion that a business should prefer to close its doors rather than do anything which could raise the cost of labor in the market. If an individual becomes important in the functioning of a business, they should be eliminated as swiftly as possible because otherwise they will remain and eventually ask for more money. Since you can never, ever, consider granting that request, you will have to fire them at that point and the damage would be even harder to repair than if you had disposed of them when you first realized their importance. So better to eject them when you first realize it and clean up whatever damage that causes when it is more containable. Perhaps that viewpoint might have had some relevance in industries centered around commodity repetitive physical labor, but I would argue that it is overall destructive in knowledge-based industries. It has been phenomenally successful at suppressing the cost of labor (between 1950 and 1980, the median wage of workers rose 75%, between 1980 and 2010 it rose by only 1%) but it's caused a widespread host of much larger problems that threaten the very foundation of the economy.
I don't know if it is meditation or more my studying of philosophy (both in college and on my own time) that has led to my ability to control my emotions better. I would also say my emotions are ephemeral, but that's really because I understand them better. When they are justified, and helpful, I can nurture them and encourage them and indulge in them just fine. And if they're not, usually I can let them pass. There are exceptions, of course, for deep-seated things that I need more repeated attempts at suppression to change. Emotions are essentially a trained response, after all. Even if you intellectually know they're nonsensical, it has to be retrained.
McDonald's is popular, at least this is what I was told in business courses, because people like familiarity and they know when they get a meal at a McDonald's it's going to be mostly the same everywhere. Uber doesn't really enjoy that. They do enjoy that it is a unified app and service no matter where you are, they have that going for them for a certainty, but they do not have control over their drivers to the level at which McDonald's has control over their franchisees. That's down to the fact their drivers are independent contractors, although it likely couldn't work any other way. It might be moot since the service is the same, getting from point A to B, so the part people want stays the same.
I would almost be inclined to see it as Uber being more valuable for their management of driver reputations than the software they provide, really. They set a standard, and hold drivers somewhat accountable to that standard, which is something that a more 'open' solution would make very difficult or impossible to do.