1. English is an accidental enabler of hardware keyboards. English is one of the languages which have the least number of "characters". And it has become very popular. But popularity and brevity of characterset are not related much. Software keyboards are giving back the rest of the world their more expressive charactersets. And they are loving it - see higher popularity of Android in areas with non-English speakers.
2. One hardware keyboard design has to be created for every language. At least every characterset. The world is a lot more varied in languages and characterset than Americans realize. I am currently in a country where a currency note has the amount printed in 16 languages. Most languages here have 75 or more unique 'characters', some have hundreds, making hardware keyboards impractical.
3. While US is a country predominantly using English language, and many other languages with Roman character set, US doesn't like Android as much as the rest of the world. Especially Asia. US likes its iPhones. And guess what? iPhones have very popular slideout (or fixed) keyboard cases. For Asia, the home of Android, with dozens of languages with millions of speakers each, hardware keyboards just don't make sense.
Overhead the GP is talking about is probably the operating systems that those 30 virtual machines are running, which is a huge duplication of effort.
Big enough infrastructure probably means that (say) the virtual machines are running web servers - you could run just one big web server on an operating system instead of 30 operating systems AND 30 web servers.
And failover advantages of virtualization don't apply to this because even such big web servers should be run in a cluster - as the assumption of "big enough" infrastructure probably enables.
And power saving by consolidating services and switching off servers in low load periods is not really an argument because during low load periods some of the blades running some web servers could be shut down.
With alternating current, the electrons are not leaving the houses of the people. Except by diffusion of electrons, which would happen even when zero electric power is consumed without airgap.
Effectively you harm yourself by dismissing things that could be beneficial for you
Here, it is not primarily about what is beneficial to oneself. It is like doing something benefits oneself greatly, but harms everyone, including oneself, a little bit.
This is the case of file paths changing across operating systems over different releases of operating systems. They can change due to some property in the operating system changing value. Or the place to keep that property changing. Or the property name itself changing. Or the process of determining the file path changing in some manner.
The reason for this change is that some one in operating system design team decided to change it, or the packagers of the software being used decided to change locations of files. The minds of these people are NOT deterministic.
You can analyze the whole operating system in your program, but you wouldn't know the location of the exact file you are looking for. This is because name of the file could have changed, or there could be many files of the same name. So even by analyzing the operating system finding file path in unknown environment is NOT deterministic.
There you were the problem for not buying Nexus. Or any other phone after reading reviews and some space to install alternative keyboard / calendar / messaging applications. Free.
And if you claim ignorance, you cannot claim benefit of free market anymore because free market needs informed participants for functioning properly.
No. Niche markets are always full of stupid shit. Slide-out keyboard phones are a niche market. No amount of Stupid Shit Index is going to alter that fundamental reality.
"Pretty" water bottles, with a lot of attention paid to their looks, leak. Braille books have typos.
For non-niche markets, Moto G and Moto E are available, much cheaper than your phone and with zero stupid shit.
I agree that the post is not as stupid as many slashdotters are claiming.
But Android enabling selling of more devices than Apple's is proof that free market is indeed nice - as Android's market is freer than Apple's. ALL of his problems can be solved by good default application replacements. Most of which do not take a lot of resources.
It is just lies and handwaving, "an enormous amount" of "unrelated" software... except, not.
In a relatively small installation of total 2.9 yum remove systemd | grep 'will be erased' | sort | uniq ---> Package ConsoleKit-libs.x86_64 0:0.4.5-7.fc20 will be erased ---> Package ConsoleKit.x86_64 0:0.4.5-7.fc20 will be erased ---> Package GConf2.x86_64 0:3.2.6-7.fc20 will be erased ---> Package ModemManager.x86_64 0:1.1.0-2.git20130913.fc20 will be erased ---> Package NetworkManager-glib.x86_64 1:0.9.9.0-20.git20131003.fc20 will be erased ---> Package NetworkManager-openconnect.x86_64 0:0.9.8.0-2.fc20 will be erased ---> Package NetworkManager-openvpn-gnome.x86_64 1:0.9.9.0-0.1.git20140128.fc20 will be erased ---> Package NetworkManager-openvpn.x86_64 1:0.9.9.0-0.1.git20140128.fc20 will be erased ---> Package NetworkManager.x86_64 1:0.9.9.0-20.git20131003.fc20 will be erased ---> Package PackageKit-glib.x86_64 0:0.8.13-1.fc20 will be erased ---> Package adwaita-gtk2-theme.x86_64 0:3.10.0-2.fc20 will be erased ---> Package adwaita-gtk3-theme.x86_64 0:3.10.0-2.fc20 will be erased ---> Package aic94xx-firmware.noarch 0:30-6.fc20 will be erased ---> Package alsa-firmware.noarch 0:1.0.27-2.fc20 will be erased ---> Package alsa-plugins-pulseaudio.x86_64 0:1.0.27-2.fc20 will be erased ---> Package alsa-tools-firmware.x86_64 0:1.0.27-3.fc20 will be erased ---> Package alsa-utils.x86_64 0:1.0.27.2-3.fc20 will be erased ---> Package anaconda-widgets.x86_64 0:20.25.15-1.fc20 will be erased ---> Package anaconda.x86_64 0:20.25.15-1.fc20 will be erased ---> Package asunder.x86_64 0:2.3-3.fc20 will be erased ---> Package at-spi2-atk.x86_64 0:2.10.2-1.fc20 will be erased ---> Package at-spi2-core.x86_64 0:2.10.2-1.fc20 will be erased ---> Package at.x86_64 0:3.1.13-13.fc20 will be erased ---> Package audit.x86_64 0:2.3.2-1.fc20 will be erased ---> Package avahi.x86_64 0:0.6.31-21.fc20 will be erased ---> Package b43-openfwwf.noarch 0:5.2-10.fc20 will be erased ---> Package biosdevname.x86_64 0:0.5.0-2.fc20 will be erased ---> Package bluez-cups.x86_64 0:5.12-1.fc20 will be erased ---> Package bluez.x86_64 0:5.12-1.fc20 will be erased ---> Package cairo-gobject.x86_64 0:1.13.1-0.1.git337ab1f.fc20 will be erased ---> Package cairo.x86_64 0:1.13.1-0.1.git337ab1f.fc20 will be erased ---> Package cairomm.x86_64 0:1.10.0-7.fc20 will be erased ---> Package chrony.x86_64 0:1.29-1.fc20 will be erased ---> Package clipit.x86_64 0:1.4.2-5.fc20 will be erased ---> Package colord-libs.x86_64 0:1.1.4-1.fc20 will be erased ---> Package colord.x86_64 0:1.1.4-1.fc20 will be erased ---> Package crda.x86_64 0:1.1.3_2013.02.13-4.fc20 will be erased ---> Package cronie-anacron.x86_64 0:1.4.11-4.fc20 will be erased ---> Package cronie.x86_64 0:1.4.11-4.fc20 will be erased ---> Package crontabs.noarch 0:1.11-6.20121102git.fc20 will be erased ---> Package cryptsetup-libs.x86_64 0:1.6.2-1.fc20 will be erased ---> Package cryptsetup-python.x86_64 0:1.6.2-1.fc20 will be erased ---> Package cryptsetup.x86_64 0:1.6.2-1.fc20 will be erased ---> Package cups-filters.x86_64 0:1.0.41-4.fc20 will be erased ---> Package cups-pk-helper.x86_64 0:0.2.5-2.fc20 will be erased ---> Package cups.x86_64 1:1.7.0-4.fc20 will be erased ---> Package dbus-x11.x86_64 1:1.6.12-1.fc20 will be erased ---> Package dbus.x86_64 1:1.6.12-1.fc20 will be erased ---> Package dconf.x86_64 0:0.18.0-2.fc20 will be erased ---> Package device-mapper-event-libs.x86_64 0:1.02.82-3.fc20 will be erased ---> Package device-mapper-event.x86_64 0:1.02.82-3.fc20 will be erased ---> Package device-mapper-libs.x86_64 0:1.02.82-3.fc20 will be erased ---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-55.fc20 will be erased ---> Package device-mapper-
Do you think the post you two replied to was made by someone rather than triggered by cosmic rays and solar flares ? Probably common sense? Same common sense helps people know the real reason for metro UI.
RedHat/Fedora is not better as I personally know. Removing systemd removes an enormous amount of "unrelated" software.
And no, Fedora doesn't have time to create correct dependency mapping. For last three releases, installing vim-enhanced "conflicts" with vim-minimal. Easy solution is to remove vim-minimal. Which also removes "sudo". Those who don't set root password and depend on sudo, now cannot install any thing as root.
For many software in many situations, it is not optional , see http://sporkbox.us/blog/?r=pag... for just one small example. Not sure how X will turn out.
Whereas support for SysV init is naturally optional as I explained earlier.
Nopes, as far as I have seen, it's called ex-Gratia , and very deliberately NOT called compensation. Compensation opens them up to legal risks, ex-gratia doesn't.
I have nothing against people from India, China, Africa, South America, etc... but you will notice that this ruthless drive to keep productivity up while lowering expenses does not extend to top executives. So you and me and the guy down the street and the woman across town take a pay cut or lose our jobs so someone in Indonesia can have a better life, while the person that decided to axe our positions and everyone on the board of directors get a bigger mansion.
Doesn't make sense at all. The guy who sent this email about firing thousands of people, was born in India. So some American was denied the Microsoft CEO job so that this Indian (US citizen now, I think) can get the job. Rules of the game are the same in top management too.
Yes. And that is why a dummy / fake systemd seems to me to be the only realistic solution. It need not have all the features of systemd, but it should be able to call scripts on simple systemd calls. That should be able to fit in with SysV init, or other initialization systems.
The software packages that contain this fake systemd will declare to provide systemd to the software package manager.
You do realize that X is used by non-linux UNIXes?
And you do realize that systemd does not support non-linux?
Why do you think these two together make a good idea?
Look - systemd is fine. But hard dependency of software on systemd is not fine. "Hard" dependency of software on init never created an issue - because it just meant that a shell script was shipped along with the software to start|stop|restart|status the software. Systems using systemd/upstart/SysVInit could use that shell script, or maybe not use that and roll something of their own.
You are right. I haven't looked into it in great detail, but the solution I see is to create a dummy systemd which need not have all the functionality of systemd but just translates simple systemd calls into shell scripts. Then it would fit into SysV init as well as other initialization systems.
While the way Sony is behaving they are unlikely to survive 100 years, but if they do, they are sure to forget to renew after 100 years. Some bean counter will fire the guy responsible for keeping track of those 100 years and that email address will be abandoned.
Right, and everyone doesn't advertise on Superbowl. Seeing Microsoft's failure in mobile devices, a smart MBA might have correctly concluded that Xbox "marketing" didn't help as much as it cost money, company focus, brand dilution etc.
Slashdot Mirror
1. English is an accidental enabler of hardware keyboards. English is one of the languages which have the least number of "characters". And it has become very popular. But popularity and brevity of characterset are not related much.
Software keyboards are giving back the rest of the world their more expressive charactersets. And they are loving it - see higher popularity of Android in areas with non-English speakers.
2. One hardware keyboard design has to be created for every language. At least every characterset. The world is a lot more varied in languages and characterset than Americans realize. I am currently in a country where a currency note has the amount printed in 16 languages. Most languages here have 75 or more unique 'characters', some have hundreds, making hardware keyboards impractical.
3. While US is a country predominantly using English language, and many other languages with Roman character set, US doesn't like Android as much as the rest of the world. Especially Asia. US likes its iPhones. And guess what? iPhones have very popular slideout (or fixed) keyboard cases.
For Asia, the home of Android, with dozens of languages with millions of speakers each, hardware keyboards just don't make sense.
You say "completely wrong", but not provide any argument against any of my statements.
Failover is used, but cluster solved it already, 30 years ago. You make no argument against any statement of mine in this context.
Overhead of multiple operating systems is well known. You make no argument against any statement of mine in this context either.
Power saving is something I added extra, but I don't see any argument from you about it either.
Are you the author of RFC 3514 ?
Overhead the GP is talking about is probably the operating systems that those 30 virtual machines are running, which is a huge duplication of effort.
Big enough infrastructure probably means that (say) the virtual machines are running web servers - you could run just one big web server on an operating system instead of 30 operating systems AND 30 web servers.
And failover advantages of virtualization don't apply to this because even such big web servers should be run in a cluster - as the assumption of "big enough" infrastructure probably enables.
And power saving by consolidating services and switching off servers in low load periods is not really an argument because during low load periods some of the blades running some web servers could be shut down.
With alternating current, the electrons are not leaving the houses of the people. Except by diffusion of electrons, which would happen even when zero electric power is consumed without airgap.
Effectively you harm yourself by dismissing things that could be beneficial for you
Here, it is not primarily about what is beneficial to oneself. It is like doing something benefits oneself greatly, but harms everyone, including oneself, a little bit.
There the benchmark you put out does not hold.
This is the case of file paths changing across operating systems over different releases of operating systems. They can change due to some property in the operating system changing value. Or the place to keep that property changing. Or the property name itself changing. Or the process of determining the file path changing in some manner.
The reason for this change is that some one in operating system design team decided to change it, or the packagers of the software being used decided to change locations of files. The minds of these people are NOT deterministic.
You can analyze the whole operating system in your program, but you wouldn't know the location of the exact file you are looking for. This is because name of the file could have changed, or there could be many files of the same name. So even by analyzing the operating system finding file path in unknown environment is NOT deterministic.
Not an option in the mathematically challenged US of A where explaining "every other", even numbers, odd numbers would take all the allotted time.
There you were the problem for not buying Nexus. Or any other phone after reading reviews and some space to install alternative keyboard / calendar / messaging applications. Free.
And if you claim ignorance, you cannot claim benefit of free market anymore because free market needs informed participants for functioning properly.
No. Niche markets are always full of stupid shit. Slide-out keyboard phones are a niche market. No amount of Stupid Shit Index is going to alter that fundamental reality.
"Pretty" water bottles, with a lot of attention paid to their looks, leak. Braille books have typos.
For non-niche markets, Moto G and Moto E are available, much cheaper than your phone and with zero stupid shit.
Wow!! How stupid can you get?
FYI, moving off to a virtual desktop, moving apps into folders doesn't get you back the storage either.
I agree that the post is not as stupid as many slashdotters are claiming.
But Android enabling selling of more devices than Apple's is proof that free market is indeed nice - as Android's market is freer than Apple's. ALL of his problems can be solved by good default application replacements. Most of which do not take a lot of resources.
1. Download and install firefox
2. Install downloadhelper plugin for firefox
3. Open youtube video
4. Download it
Watch in trillion times better player of your choice - I use mplayer.
It is just lies and handwaving, "an enormous amount" of "unrelated" software... except, not.
In a relatively small installation of total 2.9
yum remove systemd | grep 'will be erased' | sort | uniq
---> Package ConsoleKit-libs.x86_64 0:0.4.5-7.fc20 will be erased
---> Package ConsoleKit.x86_64 0:0.4.5-7.fc20 will be erased
---> Package GConf2.x86_64 0:3.2.6-7.fc20 will be erased
---> Package ModemManager.x86_64 0:1.1.0-2.git20130913.fc20 will be erased
---> Package NetworkManager-glib.x86_64 1:0.9.9.0-20.git20131003.fc20 will be erased
---> Package NetworkManager-openconnect.x86_64 0:0.9.8.0-2.fc20 will be erased
---> Package NetworkManager-openvpn-gnome.x86_64 1:0.9.9.0-0.1.git20140128.fc20 will be erased
---> Package NetworkManager-openvpn.x86_64 1:0.9.9.0-0.1.git20140128.fc20 will be erased
---> Package NetworkManager.x86_64 1:0.9.9.0-20.git20131003.fc20 will be erased
---> Package PackageKit-glib.x86_64 0:0.8.13-1.fc20 will be erased
---> Package adwaita-gtk2-theme.x86_64 0:3.10.0-2.fc20 will be erased
---> Package adwaita-gtk3-theme.x86_64 0:3.10.0-2.fc20 will be erased
---> Package aic94xx-firmware.noarch 0:30-6.fc20 will be erased
---> Package alsa-firmware.noarch 0:1.0.27-2.fc20 will be erased
---> Package alsa-plugins-pulseaudio.x86_64 0:1.0.27-2.fc20 will be erased
---> Package alsa-tools-firmware.x86_64 0:1.0.27-3.fc20 will be erased
---> Package alsa-utils.x86_64 0:1.0.27.2-3.fc20 will be erased
---> Package anaconda-widgets.x86_64 0:20.25.15-1.fc20 will be erased
---> Package anaconda.x86_64 0:20.25.15-1.fc20 will be erased
---> Package asunder.x86_64 0:2.3-3.fc20 will be erased
---> Package at-spi2-atk.x86_64 0:2.10.2-1.fc20 will be erased
---> Package at-spi2-core.x86_64 0:2.10.2-1.fc20 will be erased
---> Package at.x86_64 0:3.1.13-13.fc20 will be erased
---> Package audit.x86_64 0:2.3.2-1.fc20 will be erased
---> Package avahi.x86_64 0:0.6.31-21.fc20 will be erased
---> Package b43-openfwwf.noarch 0:5.2-10.fc20 will be erased
---> Package biosdevname.x86_64 0:0.5.0-2.fc20 will be erased
---> Package bluez-cups.x86_64 0:5.12-1.fc20 will be erased
---> Package bluez.x86_64 0:5.12-1.fc20 will be erased
---> Package cairo-gobject.x86_64 0:1.13.1-0.1.git337ab1f.fc20 will be erased
---> Package cairo.x86_64 0:1.13.1-0.1.git337ab1f.fc20 will be erased
---> Package cairomm.x86_64 0:1.10.0-7.fc20 will be erased
---> Package chrony.x86_64 0:1.29-1.fc20 will be erased
---> Package clipit.x86_64 0:1.4.2-5.fc20 will be erased
---> Package colord-libs.x86_64 0:1.1.4-1.fc20 will be erased
---> Package colord.x86_64 0:1.1.4-1.fc20 will be erased
---> Package crda.x86_64 0:1.1.3_2013.02.13-4.fc20 will be erased
---> Package cronie-anacron.x86_64 0:1.4.11-4.fc20 will be erased
---> Package cronie.x86_64 0:1.4.11-4.fc20 will be erased
---> Package crontabs.noarch 0:1.11-6.20121102git.fc20 will be erased
---> Package cryptsetup-libs.x86_64 0:1.6.2-1.fc20 will be erased
---> Package cryptsetup-python.x86_64 0:1.6.2-1.fc20 will be erased
---> Package cryptsetup.x86_64 0:1.6.2-1.fc20 will be erased
---> Package cups-filters.x86_64 0:1.0.41-4.fc20 will be erased
---> Package cups-pk-helper.x86_64 0:0.2.5-2.fc20 will be erased
---> Package cups.x86_64 1:1.7.0-4.fc20 will be erased
---> Package dbus-x11.x86_64 1:1.6.12-1.fc20 will be erased
---> Package dbus.x86_64 1:1.6.12-1.fc20 will be erased
---> Package dconf.x86_64 0:0.18.0-2.fc20 will be erased
---> Package device-mapper-event-libs.x86_64 0:1.02.82-3.fc20 will be erased
---> Package device-mapper-event.x86_64 0:1.02.82-3.fc20 will be erased
---> Package device-mapper-libs.x86_64 0:1.02.82-3.fc20 will be erased
---> Package device-mapper-multipath-libs.x86_64 0:0.4.9-55.fc20 will be erased
---> Package device-mapper-
Do you think the post you two replied to was made by someone rather than triggered by cosmic rays and solar flares ? Probably common sense? Same common sense helps people know the real reason for metro UI.
RedHat/Fedora is not better as I personally know. Removing systemd removes an enormous amount of "unrelated" software.
And no, Fedora doesn't have time to create correct dependency mapping. For last three releases, installing vim-enhanced "conflicts" with vim-minimal. Easy solution is to remove vim-minimal. Which also removes "sudo". Those who don't set root password and depend on sudo, now cannot install any thing as root.
For many software in many situations, it is not optional , see http://sporkbox.us/blog/?r=pag... for just one small example.
Not sure how X will turn out.
Whereas support for SysV init is naturally optional as I explained earlier.
Nopes, as far as I have seen, it's called ex-Gratia , and very deliberately NOT called compensation. Compensation opens them up to legal risks, ex-gratia doesn't.
I have nothing against people from India, China, Africa, South America, etc... but you will notice that this ruthless drive to keep productivity up while lowering expenses does not extend to top executives. So you and me and the guy down the street and the woman across town take a pay cut or lose our jobs so someone in Indonesia can have a better life, while the person that decided to axe our positions and everyone on the board of directors get a bigger mansion.
Doesn't make sense at all. The guy who sent this email about firing thousands of people, was born in India. So some American was denied the Microsoft CEO job so that this Indian (US citizen now, I think) can get the job. Rules of the game are the same in top management too.
Yes. And that is why a dummy / fake systemd seems to me to be the only realistic solution. It need not have all the features of systemd, but it should be able to call scripts on simple systemd calls. That should be able to fit in with SysV init, or other initialization systems.
The software packages that contain this fake systemd will declare to provide systemd to the software package manager.
You do realize that X is used by non-linux UNIXes?
And you do realize that systemd does not support non-linux?
Why do you think these two together make a good idea?
Look - systemd is fine. But hard dependency of software on systemd is not fine. "Hard" dependency of software on init never created an issue - because it just meant that a shell script was shipped along with the software to start|stop|restart|status the software. Systems using systemd/upstart/SysVInit could use that shell script, or maybe not use that and roll something of their own.
You are right. I haven't looked into it in great detail, but the solution I see is to create a dummy systemd which need not have all the functionality of systemd but just translates simple systemd calls into shell scripts. Then it would fit into SysV init as well as other initialization systems.
Do you think it would work?
While the way Sony is behaving they are unlikely to survive 100 years, but if they do, they are sure to forget to renew after 100 years. Some bean counter will fire the guy responsible for keeping track of those 100 years and that email address will be abandoned.
This guy has nice analysis, an experiment with 2 restaurants, historical and psychological perspective http://jayporter.com/dispatche...
Right, and everyone doesn't advertise on Superbowl. Seeing Microsoft's failure in mobile devices, a smart MBA might have correctly concluded that Xbox "marketing" didn't help as much as it cost money, company focus, brand dilution etc.