Yeah, which is why I don't think the correct solution is to mount a lawsuit against people making a product that blocks ads, nor is it the right solution to mount a lawsuit against your own customers. I think it's kind of a bad situation that sites are in. Even if they only have good ads that don't take up a bunch of resources and screen real estate and aren't really that obtrusive, they still risk getting blocked because there are a lot of other advertisers that do have intrusive ads that most people don't want to see.

The problem is that using ad block can kind of be compared against messing with your electricity or water meter so you aren't billed for as much. I understand that it's inherently different, because there is no agreement/requirement set up to view the ads in exchange for browsing the website they are on, but that's basically how things are set up. There's only a few ways things could work.

First option. Web site is free to use and there are no ads. Person visiting the site is happy, but the person hosting the site has no way to generate money, other than asking for donations, but that could be considered an ad for the site itself.

Second Option. Only people who pay see the site. This works for the website owner, because they are ensured that everyone pays, but breaks the general way in which most of the internet is used, because you can't send a link to a friend and have them view the content if they haven't paid. Works for sites like Netflix but wouldn't work for something like a blog.There would still be problems with not everybody paying because people would share accounts.

Third Option. Website maker puts up ads on their site to make money for operating the site. If the user blocks the ads then the person operating the site cannot generate any money

Fourth option. The website owner sells actual products at their website and makes money that way. This works if the website is an actual store, as that's what the user came there to do, but very few users, if any, are going to buy something from a website that isn't actually a store. Also, the person operating the website also has to operate a store, which they may have no expertise or interest in doing.

Feel free to come up with some other ways of generating income from a website to recoup the costs of running one. There aren't a lot of good options. I realize that some ads can be over the top and extremely annoying. In that case I just usually leave the site and try not to go there in the future. I don't like blocking ads that are not intrusive, as that undermines the website's ability to make money, and if it's a good website, I want it to remain in operation.

more data than will fit in the device's memory

. I record my bike rides with my GPS. Not once in the last 2 years have I had to remove data off the device because it ran out of space. I think in total there might be a few megabytes worth of data, and it's only that big because they use XML to store the data, which is inherently verbose. There is less data than actual XML. I'm sure that a simple fitness bracelet could store a lifetime's worth of data in under 1 GB.

If home owners could take advantage of using batteries to balance out the peaks in electricity usage, the electricity companies would probably be doing it already. Maybe not in the US, but some power company in some country would be doing it if it was economical. The reason it's not being done is because it's not economical yet. Perhaps someday it would be, and I hope it is soon. As soon as we get battery technology that makes it economical to do so to offset the peak usage rates, renewable forms of electricity and other generation methods like nuclear are a lot more convenient because you don't have to worry so much about variability when the power is generated or (in the case of nuclear) how fast you can ramp them up when more power is needed immediately.

I write web applications in .Net, and as far as I'm concerned, nothing else I've see comes close for large projects. There was a bunch of hype about Ruby, so I tried that. For anything beyond basic CRUD applications, it was quite painful to use. The .Net API has amazing amounts of built in functionality. I can't think of any language that comes close. It amazes me how people write stuff in Java without having a decent "Date" data type. Why should I have to use a third party library to get decent date support?

That's kind of the big legal question. I remember that Nintendo went after a bunch of "watch me play" people on YouTube. The music in the background is often owned by a third party and licensed for use in the game. And I know that Youtube often takes down videos (video games and others) based on copyrighted songs being in the background.

Exactly. The only situation where the homeowner would want to optimize for the highest use time of day is if the power company was paying them an increased rate for power fed into the grid during that time period. and at that point, it might make more sense for the home owner to store all the power generated in batteries and only send power back to the grid when they are getting the best price.

Where I live there's a 5 cent difference between the cheapest and most expensive parts of the day. I wonder how cheap/efficient batteries would have to get before it would make sense to just charge the batteries at night, and use them during the day so I never have to pay the higher rate.

Obviously the panels should be motorized so that they are always facing the most optimal direction. A system that moves the panels shouldn't add that much to the cost and will probably pay for itself very quickly with the extra energy collected.

I have a Surface 2 (not Pro), and even I like that better than the iPad in just about every respect, save for the number of apps available. The entire device is done very well. I think if on the next iteration they could get a more affordable x86 tablet then they could really start to take some business away from Apple and the other tablet manufacturers. Get rid of the digitizer and go with a plain old touch screen, use a low power Atom processor, and include the keyboard in the box, and I'm sure that most people who really stopped to think about it would easily choose a Surface over an iPad or Android tablet, which is extremely limited, and would be just as expensive.

Why not just have a mechanical trigger? squeeze the grip at the end you're holding it on, and a mechanical finger is moved to press the camera button on the screen. Should be pretty easy to build different ones that automatically line up for popular phone types, or make an adjustable one that can handle a variety of phones.

Based on life expectancy, I can probably assume that I will live another 50 years, barring anything catastrophic. 50 years ago, computers took up entire rooms, and the thought of having computer at each and every desk was kind of a dream. Now it's a reality. With how much has changed in the past 50 years, I'm not going to pretend that I know what technology will bring in the next 50, but it would seem to me that quite a few jobs are going to disappear, and I don't really see a lot of low qualification jobs opening up.

It increases income for the corporation, and the fewer people who are left working there. It won't free people to work in more productive jobs, because they simply don't have the skills to do anything more productive. If they had the skills, they would already be working those jobs because they pay better. People aren't working in an Amazon warehouse because they enjoy it and the pay is good. They do it because they aren't qualified to do work that is more fulfilling (financially and personally). Getting robots to do their jobs won't suddenly make them qualified to do more complicated jobs. And it seems to me that the are a lot of people that, even given the opportunity to acquire new skills, are incapable for one reason or another of getting the skills necessary for a better job.

Automation can minimize labor costs but it cannot eliminate them because it is not economical to automate all jobs even when it is technologically possible to do so.

The only thing stopping that is that it's still too expensive to build machines to do certain jobs. But that won't last forever. Eventually, with the progress of technology, it will become very economical to replace workers with machines. Some jobs may require a robot that requires 20 years to pay itself off, that probably isn't worth it for a lot of businesses. Some jobs will pay off the machine in 2 or 3 years. At that point, as far as the company is concerned, it's economically irresponsible to not get the robot to do the job. As the cost of the machines come down, that machine that used to take 20 years to pay off, will only take 10, or 5, and eventually it will be cheap enough. The only jobs left will be thinking/creative jobs (unless there is some major advancement in AI), and jobs that people actually want to talk to a person for. As annoyed as people get with customer support personnel, they would be infinitely more annoyed at a machine who was reading off the same script.

Sure he would save an hour, and he would probably also burn a lot more gas. Engines are optimized to get maximum efficiency at certain speeds. Even if you optimized them for higher speeds, there's still the problem of air resistance which goes up as a function of the cube of the speed.

That's pretty much the problem with Linux on any machine. If you buy the machine specifically for running Linux, there are plenty of options that will run without problems. However if you pick a random machine at the store, odds are there will be some part of the hardware that has less than optimal drivers.