Don't you think though, with a "forever" house, waiting a few years for bigger, faster internet would be worth it?

I think it's inevitable.

http://news.slashdot.org/story...

But still seriously cool. Between this, the entire linux kernel, and DOOM, there is a lot of neat code online to analyze.

Reading code is to coding as reading books is to writing. Essential.

You're right, I've been thinking this for a long time. If we do it right, we will eliminate drunk driving and killed-by-sms. Wouldn't that be nice.

As far as my rights, I'm just fine giving up manually navigating LA traffic... I can't imagine anything better.

Let's hope what it takes is: Really good automated vehicles.

I think this is one technology that we don't really want typical google-style beta testing (think gmail) with. Let's wait for things to mature a bit before they go mainstream.

You made some good points, but I think the unix compatibility fueled a lot of developer interest in the early days. Developing on OS X was a joy compared with windows. You have tons of useful built-in tools, plus the ability to port over tools common to the GNU Linux/FreeBSD environment.

If an OS is easy to develop on, it can't hurt.

I agree though, most end users do not care and never would know the difference.

At the beginning and end of the linked video showing the demo of the Apple-1, there is some lovely ASCII art shown on the Apple-1 monitor.

Are these artworks hidden in the rom somewhere? Anyone got a link?

I was wondering the same thing too.

I have a decent 8-core xeon at work as my workstation. When I have intense computations to run, I do it on one of our clusters. The idea that someone would do intense calculations on a phone is pretty ridiculous. You've outlined a few good examples, but like you said, most of that is done with dedicated hardware, and seemingly instantly.

The only app that needs to be fast, and I mean really fast, is the app switcher and the Phone app. And they are pretty light on the computation anyway.

Besides gamers, who cares if it takes a few more milliseconds to launch a web browser or process an image?

Seeing as all these phones are pretty decent, from my point of view, I just want the greatest battery life.

I don't see why nobody is taking the middle road here.

Why not strip out all the non-init.d stuff from systemd for now (I understand there's a light fork that does this already), add plaintext logging (easy), and see how things go (testing).

This is linux, and debian at that. We shouldn't have to deal with extremely beta ideas that change so many paradigms all at once. If they can do what I've outlined here, then we should give it a shot (not on production servers yet of course). If it catches on, then over the years we can debate how much to delegate to systemd and how much to do another way.

For one, I can see no disadvantage in keeping a plaintext log around. Sure, takes a little more space, but most systems are not that space-limited these days. Seems like it would be handy...

For that, you'll have to talk to Motorola and the FCC.

Most p25 traffic isn't encrypted anyway. There is no need and some definite disadvantages to p25 as well. And there are cryptographic weaknesses.

Apple's leverage of open source encryption concepts will always be a few years more advanced, if not decades more, than embedded p25-compliant radios.

"...that person will be immediately isolated..."

Unless of course, they need some soup.

http://www.dailymail.co.uk/new...
http://www.nydailynews.com/new...
http://www.georgianewsday.com/...

A complete blur on both sides. Since the light is extremely convergent, it won't make any sense to the eye.

These are the same optics in a telescope, by the way. If you were to look inside a telescope without the eyepiece, you'd get the idea right away of how it would look to be in the middle of this "new" idea.

Ok, but how important is it to keep passwords secure to a textbook website or an iPad? Maybe if someone steels Johnny's textbook password then the teacher can just go in a reset it?

Let's keep things in perspective here, these are not banking passwords or social security numbers. These passwords are only used to identify individuals for the purpose of individualizing the presentation of information. Nothing of value, especially to an identity thief (and especially to a fellow 6-year-old student) can be lost.

It's not in the linked article, but here is the interesting part of the new rules: creators have to refund remaining money, and have to post status updates.

Read it here:
If a creator is unable to complete their project and fulfill rewards, theyâ(TM)ve failed to live up to the basic obligations of this agreement. To right this, they must make every reasonable effort to find another way of bringing the project to the best possible conclusion for backers. A creator in this position has only remedied the situation and met their obligations to backers if:

they post an update that explains what work has been done, how funds were used, and what prevents them from finishing the project as planned;
they work diligently and in good faith to bring the project to the best possible conclusion in a timeframe thatâ(TM)s communicated to backers;
theyâ(TM)re able to demonstrate that theyâ(TM)ve used funds appropriately and made every reasonable effort to complete the project as promised;
theyâ(TM)ve been honest, and have made no material misrepresentations in their communication to backers; and
they offer to return any remaining funds to backers who have not received their reward (in proportion to the amounts pledged), or else explain how those funds will be used to complete the project in some alternate form.

All those users that don't directly interact with init scripts might suddenly find that they need to when systemd causes things to break that used to just work.

This is a big deal to more than just admins.