I see. The N810 is the model with the GPS. I have an N800 and a bluetooth GPS, which works but can be a pain. Hopefully Nokia listened to complaints and put a decent GPS in the N900.
On the one hand CPU is an acronym for a specific item and to use it as a reference to an entire system is unacceptable even from a layman's point of view. It is unavoidably confusing in nearly every context.
And the terms you chose to criticize:
* video/still camera
* gps
* phone
Those are not ambiguous, confusing or misused in describing the N900's functions, especially in the context of this article.
Jokes aside, this is an example of the poor terminology used in the computer systems field. Storage is memory so that's OK, but can be confused depending on its context. I think the relevant difference is persistent vs. volatile memory; so maybe we should use terms such as P-MEM AND V-MEM. It's about time we came up with some proper terms. I'm tired of hearing things like "Just plug the jump drive into the front of the CPU."
BTW, I paid $400 for my N800 when it came out and would pay between $600-$800 for this since it's also a good still/video camera, gps and phone.
* You can watch a movie on this phone. The screen on these things (I have an n800) is stunning at 800 x 480. I and some of my relatives have enjoyed full length movies on my n800 and I keep my personal video collection (dv converted to mpeg4) on it.
* word-work? Never heard that term, but I'll assume you're talking about messaging (I hope your not talking about word processing). Many people are quite efficient on each of the various keyboard input setups and this has two of them; touchscreen and pop-out keyboard, so you probably just need practice.
* In case you missed the article the camera is very nice. Carl Zeiss; 5.2 MP. More than enough for "happy snaps".
* Maemo is a very active community (http://www.maemo.org) with lots of great software. So what is it that you want your phone to do? More than likely there is an application to do it.
We (the geeks) have been clamoring for an open platform phone and now it appears we're getting it. I admit that I get excited at the thought of being able to ssh into my phone, run scripts and write programs in Python/GTK and configure pretty much any and every aspect of the device. If you don't, you're probably not a geek and this whole thing will be lost on you.
I think computer jargon needs some improvement. What do you call the computer system, sans monitor? Box? Tower? I don't blame users for being confused. They probably call it CPU or hard drive because they expect a technical term to apply, yet none does. And what about hard disk? How's that going to fly when we're using flash drives? It's not actually a disk.
We need some better terminology. Maybe pmem (persistent memory) instead of hard drive.
Maybe. Depends on the software. Think of some software that's 7 years old.
MS Office 2002/XP or whatever it's called?
Windows XP
Oracle 9i
OS X Panther
Can you imagine these being freely redistributable? Like I said, the period depends on the software. The developer needs enough time to profit and then move on.
This sounds similar to what I want to do. I wrote about it a few months ago here.
free to view
free to modify
free to redistribute AFTER some time period
There's some more to it (see link), but the idea is to have the effect of a reasonable copyright period. Say 7 years. I'm working on some software now that I want to release under this license within 6 months. I would be very interested in discussing this further.
This approach to virtualization Operating System-Level Virtualization is sorely lacking in the Linux Kernel. I know you can patch with VServer and OpenVZ, but the more I use it the more I believe it should be built in. It has almost 0% overhead and facilitates many peoples needs for virtualization in which they often use more resource costly and complex virtualization techniques.
If the kernel version doesn't matter to you, Jails/Vserver/etc. may be a good fit. No hardware emulation, disk images, etc. BTW, Debian includes Vserver and OpenVZ patched kernels. Ubuntu does not. Don't know about others.
Also, the number of cells just determines the voltage, not the capacity. Size matters. So I don't think comparing 2 cells to 3 cells means much. So no, it's not clear that the HP is using only 50% more power.
My n800 with an ARM at 400 mhz runs a full browser, plays mpeg4 (dsp) video and doesn't burn my lap (or hands). So I imagine a laptop with a much larger battery than my n800 and a faster, but still power efficient processer (cortex-A8) would run nicely and last a very long time (10 hours +).
I'm aiming to release software within 6 months with a license that meets these criteria, but I don't know of one. If you have any interest in a license that meets these goals, I'd like to hear from you.
-Reduce the American standard of living via increased immigration to correct the high cost of labor?
-Increase the global standard of living via offshoring to correct their low cost of labor?
-Cause stagnation via protectionist policies, then wait for other nations to pass us by on their way to a higher standard of livin and eocnomic vitality?
A form of protectionism. We should require that our labor standards be upheld regardless of location. Otherwise, the only way to compete is to drop our labor standards. Consider that.
Get a hand cut off. You're fired because you are now useless.
40 hour work week. Probably more like 100+.
Sick days. Na. Suck it up.
Oh yea. Your children will need to work too.
We can't hold one standard here and another one somewhere else. Example: My dad works on an oil rig and said they couldn't use it anymore because it didn't meet safety and environmental standards. One of the issues was there were no catalytic converters on the generators. So they were going to sell it to someone in another country. That way, someone else can get hurt and pollute their air (oh wait).
Certainly there are details that would be hard to work out, but if we took a general stance that our standards had to be upheld when off-shoring, I think that would be sustainable.
There are two big advantages to libre software in business:
1. You can customize the software. 2. You're not dependent on the vendor. You can hire a third party to maintain the software.
Number two is posed to create a flourishing technology economy. Say you've got some great accounting software from small vendor X and vendor X goes out of business. You can hire any third party to add new features or fix problems. Or if vendor X ignores your bug reports, you can hire vendor Y to fix the bug. The libre checkbox could be very attractive to businesses.
So now to the big worry-- how are developers going to make money? I'm not sure.
Of course they can make money through support and services, but I still think there is room for the ISV. The two options often discussed are polarized. On the one hand you've got closed sourced proprietary that heavily restricts freedoms, but allows for direct profit and on the other you have Open Source software (as defined by OSD) that gives its users freedom and makes the software really theirs. I think everyone here knows the benefits of Open Source so I won't go into it, but I think there exists a potential that lies between these two extremes.
First, consider the some negative points for each ideology.
Close Source Proprietary:
User is unable to view and/or modify the source code. If something is broken or requires customization, s/he is reliant on the vendor.
If the vendor goes out of business, it's likely that the software becomes lost. If the software was valuable, that value is lost entirely.
Open Source:
Small markets are often unserved or under-served. For a small market for which an ISV could make a decent profit at $50 per license, there's often not enough developers willing to put in the time and effort to serve it or serve it properly.
Often, open source software is not polished. It's usually functional, but not pretty or very user friendly.
So how about a solution that addresses these short comings? Consider open source (user gets the source code) software with limited time redistribution restrictions. The user can examine and modify the software or hire someone to modify it for them and the software license reverts to an OSD style license after a set period of time; say 5-7 years to allow for redistribution. I think this addresses all 4 negative points posted above and is both good for the end user and the market.
I'm working on some software now with the hopes of releasing under a license such as this. I haven't found such a license so I sure would like to hear from someone knowledgeable on the subject.
I'd bet a large part of that is uncompressed attachments and probably Word and/or Excel. Also, from Windows users I tend to get bitmaps as screenshots.
Your fsck at boot problem was probably due to the default ext3 config 180 days or whatever. That's configurable and certainly not a reason to switch from ext3. The first time you encountered this, you should have reconfigured it.
One point to consider. Price theory says the cost ~= marginal cost for mass market items, which in software, I equate to the likes of MS Windows and Office. This still leaves room for ROI in software development. I think that while the software is scarce (not well known or widely distributed), there is room for decent profits per copy, but as it moves towards mass market, that profit margin should go down until it's nearly or completely free.
That's exactly what biodiesel solves. Why is this comment insightful? Biodiesel uses existing infrastructure and with a productive feedstock will "rival that of petroleum in terms of quantity, price, availability and reliability". The largest shortcoming at the moment is a productive feedstock, which algae may be.
Copyright: Sharman Networks Ltd does not condone activities and actions that breach the rights of copyright owners. As a Kazaa user you have agreed to abide by the End User License Agreement and it is your responsibility to obey all laws governing copyright in each country.
Slashdot Mirror
I see. The N810 is the model with the GPS. I have an N800 and a bluetooth GPS, which works but can be a pain. Hopefully Nokia listened to complaints and put a decent GPS in the N900.
Would you care to elaborate?
On the one hand CPU is an acronym for a specific item and to use it as a reference to an entire system is unacceptable even from a layman's point of view. It is unavoidably confusing in nearly every context.
And the terms you chose to criticize:
* video/still camera
* gps
* phone
Those are not ambiguous, confusing or misused in describing the N900's functions, especially in the context of this article.
Guess you missed that episode of IT Crowd.
Jokes aside, this is an example of the poor terminology used in the computer systems field. Storage is memory so that's OK, but can be confused depending on its context. I think the relevant difference is persistent vs. volatile memory; so maybe we should use terms such as P-MEM AND V-MEM. It's about time we came up with some proper terms. I'm tired of hearing things like "Just plug the jump drive into the front of the CPU."
BTW, I paid $400 for my N800 when it came out and would pay between $600-$800 for this since it's also a good still/video camera, gps and phone.
* You can watch a movie on this phone. The screen on these things (I have an n800) is stunning at 800 x 480. I and some of my relatives have enjoyed full length movies on my n800 and I keep my personal video collection (dv converted to mpeg4) on it.
* word-work? Never heard that term, but I'll assume you're talking about messaging (I hope your not talking about word processing). Many people are quite efficient on each of the various keyboard input setups and this has two of them; touchscreen and pop-out keyboard, so you probably just need practice.
* In case you missed the article the camera is very nice. Carl Zeiss; 5.2 MP. More than enough for "happy snaps".
* Maemo is a very active community (http://www.maemo.org) with lots of great software. So what is it that you want your phone to do? More than likely there is an application to do it.
We (the geeks) have been clamoring for an open platform phone and now it appears we're getting it. I admit that I get excited at the thought of being able to ssh into my phone, run scripts and write programs in Python/GTK and configure pretty much any and every aspect of the device. If you don't, you're probably not a geek and this whole thing will be lost on you.
I think computer jargon needs some improvement. What do you call the computer system, sans monitor? Box? Tower? I don't blame users for being confused. They probably call it CPU or hard drive because they expect a technical term to apply, yet none does. And what about hard disk? How's that going to fly when we're using flash drives? It's not actually a disk.
We need some better terminology. Maybe pmem (persistent memory) instead of hard drive.
Maybe. Depends on the software. Think of some software that's 7 years old.
Can you imagine these being freely redistributable? Like I said, the period depends on the software. The developer needs enough time to profit and then move on.
This sounds similar to what I want to do. I wrote about it a few months ago here.
There's some more to it (see link), but the idea is to have the effect of a reasonable copyright period. Say 7 years. I'm working on some software now that I want to release under this license within 6 months. I would be very interested in discussing this further.
This approach to virtualization Operating System-Level Virtualization is sorely lacking in the Linux Kernel. I know you can patch with VServer and OpenVZ, but the more I use it the more I believe it should be built in. It has almost 0% overhead and facilitates many peoples needs for virtualization in which they often use more resource costly and complex virtualization techniques.
If the kernel version doesn't matter to you, Jails/Vserver/etc. may be a good fit. No hardware emulation, disk images, etc. BTW, Debian includes Vserver and OpenVZ patched kernels. Ubuntu does not. Don't know about others.
Let's throw the display out:
Beagle Board: Max power consumption @ 2W
http://www.h-online.com/news/TI-launches-the-open-source-Beagle-Board-for-Lb75--/111204
Atom with Chipset: TDP @ 11W
http://en.wikipedia.org/wiki/Silverthorne_(CPU)
Also, the number of cells just determines the voltage, not the capacity. Size matters. So I don't think comparing 2 cells to 3 cells means much. So no, it's not clear that the HP is using only 50% more power.
My n800 with an ARM at 400 mhz runs a full browser, plays mpeg4 (dsp) video and doesn't burn my lap (or hands). So I imagine a laptop with a much larger battery than my n800 and a faster, but still power efficient processer (cortex-A8) would run nicely and last a very long time (10 hours +).
And it burns > 10 watts. You missed the point. ARM can run under 1 watt.
Combine good parts from both. Why so polar?
Freedom + Economic Incentive
If I got your attention, you can read more here.
I'm aiming to release software within 6 months with a license that meets these criteria, but I don't know of one. If you have any interest in a license that meets these goals, I'd like to hear from you.
A form of protectionism. We should require that our labor standards be upheld regardless of location. Otherwise, the only way to compete is to drop our labor standards. Consider that.
We can't hold one standard here and another one somewhere else. Example: My dad works on an oil rig and said they couldn't use it anymore because it didn't meet safety and environmental standards. One of the issues was there were no catalytic converters on the generators. So they were going to sell it to someone in another country. That way, someone else can get hurt and pollute their air (oh wait).
Certainly there are details that would be hard to work out, but if we took a general stance that our standards had to be upheld when off-shoring, I think that would be sustainable.
--Randall
I'll be scouring this thread because I think libre/non-gratis software has a future. I put some thoughts down here:
http://tnr.cc/the_software_license.html
There are two big advantages to libre software in business:
1. You can customize the software.
2. You're not dependent on the vendor. You can hire a third party to maintain the software.
Number two is posed to create a flourishing technology economy. Say you've got some great accounting software from small vendor X and vendor X goes out of business. You can hire any third party to add new features or fix problems. Or if vendor X ignores your bug reports, you can hire vendor Y to fix the bug. The libre checkbox could be very attractive to businesses.
My first guess is that you've probably got some electrical problem. I switched to CFL about 5 years ago and haven't had the problems you have.
I agree. See this comment.
I think there is room for a solution that grants freedom to the user, direct monetary reward to the developer and is economically sound.
So now to the big worry-- how are developers going to make money? I'm not sure.
Of course they can make money through support and services, but I still think there is room for the ISV. The two options often discussed are polarized. On the one hand you've got closed sourced proprietary that heavily restricts freedoms, but allows for direct profit and on the other you have Open Source software (as defined by OSD) that gives its users freedom and makes the software really theirs. I think everyone here knows the benefits of Open Source so I won't go into it, but I think there exists a potential that lies between these two extremes.
First, consider the some negative points for each ideology.
Close Source Proprietary:
Open Source:
So how about a solution that addresses these short comings? Consider open source (user gets the source code) software with limited time redistribution restrictions. The user can examine and modify the software or hire someone to modify it for them and the software license reverts to an OSD style license after a set period of time; say 5-7 years to allow for redistribution. I think this addresses all 4 negative points posted above and is both good for the end user and the market.
I'm working on some software now with the hopes of releasing under a license such as this. I haven't found such a license so I sure would like to hear from someone knowledgeable on the subject.
I'd bet a large part of that is uncompressed attachments and probably Word and/or Excel. Also, from Windows users I tend to get bitmaps as screenshots.
I bet it only works on Windows machines.
Your fsck at boot problem was probably due to the default ext3 config 180 days or whatever. That's configurable and certainly not a reason to switch from ext3. The first time you encountered this, you should have reconfigured it.
# Please !
# All those braces give me a headache.
if something:
stuff()
else:
other stuff
So you bought an eeepc for $300 then spent another $200 for Windows XP?
One point to consider. Price theory says the cost ~= marginal cost for mass market items, which in software, I equate to the likes of MS Windows and Office. This still leaves room for ROI in software development. I think that while the software is scarce (not well known or widely distributed), there is room for decent profits per copy, but as it moves towards mass market, that profit margin should go down until it's nearly or completely free.
>Wake me when someone solves *that* one.
That's exactly what biodiesel solves. Why is this comment insightful? Biodiesel uses existing infrastructure and with a productive feedstock will "rival that of petroleum in terms of quantity, price, availability and reliability". The largest shortcoming at the moment is a productive feedstock, which algae may be.
So this is exactly what you say it isn't.
Randall
Scarecrow. Duh.
From the front page of the Kazaa website:
Copyright: Sharman Networks Ltd does not condone activities and actions that breach the rights of copyright owners. As a Kazaa user
you have agreed to abide by the End User License Agreement and it is your responsibility to obey all laws governing copyright in each country.
Enough said.
Randall