This is completely asinine. Schools provide two forms of education. The first is teaching kids science, math, art, PE and that type of stuff. The second is helping to teach them how to function in society.

Having public schools forces people have to associate with people they don't agree with. While in school this seems fucking bonkers to the children, but what they learn from this is invaluable in real life. Letting parents choose schools based on what they align to will only exacerbate the existing Trump vs world shit that is currently happening.

But at the same time the 32 bit libraries won't be loaded. Thus overall reduced ram usage for the device. Not necessarily per application.

I firmly believe that the Apple Watch rumor at the time was market research*. Let someone else spend the resources to see if there is an actual market. Phone screens kept getting bigger and bigger, so moving to something as small as a watch face for a screen was iffy.

With Apples established tie in as a fashion accessory they weren't worried about being first to market in this segment. If the market was legitimate they just had to release something and it would fly off the shelf. And that's pretty much what happened.

* Apples history of secrecy for new product lines is what let me to this conclusion. At the level of concept the people who would have known about the possibility of a watch would have been so small that the leak had to be deliberate -- as market research.

But if they did that it would be harder to classify their Ireland operation as a separate entity. With separate domain names in each region/country they give the illusion that they are different entities even though everyone knows realistically they are not.

HTML is not programming. It's markup. It's using Word to write a document. HTML is just data. It's frequently the result of programming.

HTML + CSS -- a bit fuzzy. It depends on the features you use. You can actually *do* something with this.

HTML + Javascript -- Programming. Well the Javascript aspect is programming, but the two are almost always intermingled.

The primary difference you can use to separate them is: Does the result of my work execute. Yes -- programming. No -- Data.

I think people are mistakenly equating being on the latest release with being "up to date".

As long as the version you are on is still getting security updates you are on the latest version of your release line. This is all we need, and what we need to push vendors to support. If your hardware is good enough to support the latest release, you should be pushing your vendor for an update, but it's not wholly necessary.

Mentioning the age does nothing for the story. It's completely irrelevant data.

I am sanity.

I'm saying that the "rarely" is the problem. Until that is solved you have to:

a) Own a separate car that is rarely used just to go out for those rare events.
b) Rent a car to go out into the boonies. This may or may not be feasible to do on a whim.
c) Don't go.

"a" is a huge financial hurdle. "b" has limitations on spontaneity. "c" represents a freedom I'm not wiling to give up.

Everyone that keeps saying that the autonomous cars are just around the corner all live in big cities. To get to the point they work without a steering wheel (aka manual mode) these companies have to solve for rural driving. Until the cars can reliably drive up a back woods, rocky, single lane mountain road they are worthless.

Think of going camping. Are you going to be able to take your family camping in your autonomous minivan? What about going for a tour of scenic back roads in Montana, Alaska, Wyoming, the Dakotas.

Last, how are these cars going to navigate through a rural dirt road with 2 feet of fresh snow on it.

These are all problems the people in the big cities are going to have to live with. They may only live with it a very very small percentage of the time, but it's a major hurdle to overcome.

You are so close replace the computer with a magnet and you got yourself a list

Two nics would allow for many network related functions to be performed by the RaspberryPI. Currently the single nic is quite limiting if you have ~30+ MBit of bandwidth to your home.

Based on my experience at a fortune 100 company with a heavy interest in Java. Don't use Java. Use PHP or LUA as a cgi. Your sysadmins who have to keep your application up will thank you.

• Do not use java. To make it work rigth you have to go against everything the community says you should do.
• Do not use NFS
• For file storage use something like MogileFS. It is not likely the best, but it's a proper example of what you will want
• If you use a database you MUST understand and use the relational aspects of things. If you use the database as just a key:value store I will personally beat the ever living shit out of you.
• Use loose coupling and sharding of your data. Multiple databases on multiple replicated servers is happy. Isolate each aspect of your product into separate databases.
• On a related note it's likely that only accounts need to be replicated between databases. It's not hard and will allow you to scale very large
• If you use memcached do not store individual bits of data. Store complete rendered data only
• Use cgi. Mod_* and Java are a bitch to debug. Php and lua work well for this. If you have something that is multi-tenant multi-version this applies even more.
• Do not use web session affinity.
• Do not use full text search in a database
• Do not use stored procedures
• Do not use large frameworks. If you must use a framework use small ones dedicated to a small subset of functionality. No framework you use should use a database.

Our interviews for sysadmins always ask what editor people use on their Linux boxes. People always think it's a funny joke due to the vi/emacs war, but it is actually a serious question and there is only two wrong answers: nano and pico. If you answer nano or pico you will not get hired.

It actually shows that you do not know the system as well as you are claiming. nano/pico will silently corrupt files on you.

Try it for yourself. Create a file with long lines in vi/emacs. Have a bunch of words on the long line. Now open that file in pico/nano and put a single space at the beginning of the long line and save the file.

If you go in with emacs/vi you will now notice an extra carriage return that you did not put in. If I ever catch a sysadmin using nano on a system file it is cause for termination.

Except for varmint shooters (I'm one). That's all for the kill. Gophers/Prairie dogs exploding in a ball of red mist is just amazing.

They make really heavy guns shooting small caliber bullets out of medium cartidges (.204 Ruger/.17 Fireball) for two things: Target (read paper) and Varmint (dead sploded things). The heavy guns let you see the target in scope as it blows up. Without the combination of lighter cartridge and heavy gun the recoil would not allow you to see the action.

The design of the varmint bullets is such that you have a bullet spinning at a couple hundred thousand RPMs that is highly frangible. This is what makes the things go *poof*. There is far more varmint type bullets from commercial manufacturers than there are target bullets in these calibers. That's what people want, and for good reason: it's fun.

Down south some of these critters actually get big enough to be a source of food. Where I live (up north) that's not the case. They are tiny little critters that just annoy ranchers and farmers. The annoyance is in the form of broken legs on cows/horses and crop damage. My fun actually helps things, but I do it for the fun, not out of helping a fellow human down the road.