I have ran and finished on Linux several WIndows only games, using Wine. Wine can be very useful, but in my experience, you lose a big amount of time just testing different wine versions and playing with configuration (Windows version, DLL overrides, runtimes, etc.).
So, even if it is only something like PlayOnLinux on steroids, managing different Wine versions and with scripts automating its usage, it could be good if Valve uses a decent amount of its resources to testing. This could avoid the end users to waste lots of time.
BUT, after writing this, I do now think this will be the case. Something like DOSBox, SCUMMVM and that kind of wrappers seem more feasible.
I'm assuming we are talking about home routers (no enterprise grade stuff here). If you have the required knowledge, buy a router supported by OpenWRT. Install this distro and keep it properly managed (keep security updates up-to-date, create a sane configuration, etc.).
My experience running it on VirtualBox, is NO. The last version I tested was 0.4.2 IIRC. Excepting pendrives, keyboards and mouse, no USB device I tested worked, even pretty simple ones like USB to RS232 converters. Most applications crash unexpectedly, and getting pretty simple hardware configured, like the sound card, can lead to lots of crashes and even BSOD easily.
I appreciate the great effort that ReactOS team is doing, but nowadays, if you need to run Windows software, you have pretty much better chance to get it working with GNU/Linux+Wine, that in ReactOS.
Try running Android with 128 MiB and you'll be glad if it ever boots. I have an Android tablet with a Tegra 2 CPU (dual core 1.2 GHz) and 512 MiB RAM Running Cyanogenmod 10.1 (Android 4.2.2 IIRC) and it runs painfully slow. Of course I don't think iOS would be able to run properly with these specs.
FFOS does a great job squeezing poor hardware, but it cannot do miracles.
FFOS is a good mobile OS. I have tried version 2.0 in a ZTE Open and although this is also a crappy phone (single core CPU, 256 MiB RAM), it is not as crappy as the Cloud FS. The keyboard works well, and the OS runs rock solid (no hangs, decent speed). The only problems with this phone are the crappy camera (slightly better than the one in the Cloud FX) and the poor multitasking due to the low RAM amount.
If you install FFOS e.g. on a Nexus device, you will find it performs great and it has no multitasking problems. I like FFOS and I've been considering switching from Android to FFOS, the only things I'm missing right now is a good SSH client that works "offline" (e.g. not connecting to a web page through the Internet) and a swype-like keyboard.
About these extremely low spec smartphones, I think something like the almost dead Symbian would make a lot more sense. I owned a Nokia 5800 some time ago, with the same amount of RAM (128 MiB) and a weaker CPU, and it performed pretty decent. 128 MiB is just too low for a full featured mobile OS like FFOS.
Everybody knows Stradivarius violins only sound better when the one who listens to it knows the violin is a Stradivarius. The same goes for french wine that tastes better only if you know where it comes from, etc.
I want to buy an ARM Chromebook since it was announced, but as today, I still have not one, and maybe I'll never have it. Why? Because I live in Spain, and ARM Chromebooks still have not been released here:(. I don't know why Google punish spaniards not launching it here, but I also don't know how they pretend to have big sales if they do not launch it everywhere and make big advertising campaigns.
It can be a good idea if it is used as a complementary system, used ONLY for a few selected packages, like for example non free ones. Non free packages have the problem that sometimes they become a real pain to get working, when the libraries they depend on get outdated, and are not available in the repositories of the distro you are using.
As Ubuntu continues moving away from the free software ecosystem, I think this is hardly a surprising move.
Another reason to ditch away closed source in favor of open alternatives. Maybe $10.000 would be a good start to pay a coder to release an entirely open source one.
Just call rms to release all its fury.
Jokes aside, I suppose you can request help from the Free Software Foundation: http://www.fsf.org/
Clear GPL violations, even this relatively small ones, should not be tolerated.
Comparing it with the RPi, this one has more memory, a faster processor, a lot of GPIO pins, etc. But the lack of an Ethernet port, an HDMI output, an internal and an internal flash makes it less attractive for me.
I really don't get the point about coding on a tablet. Why bother doing it when it will always be easier to do it in a "traditional" computer.
Sure you can create contents using a tablet, but tablets are designed for content consumption, not for content creation.
I have ran and finished on Linux several WIndows only games, using Wine. Wine can be very useful, but in my experience, you lose a big amount of time just testing different wine versions and playing with configuration (Windows version, DLL overrides, runtimes, etc.).
So, even if it is only something like PlayOnLinux on steroids, managing different Wine versions and with scripts automating its usage, it could be good if Valve uses a decent amount of its resources to testing. This could avoid the end users to waste lots of time.
BUT, after writing this, I do now think this will be the case. Something like DOSBox, SCUMMVM and that kind of wrappers seem more feasible.
I'm assuming we are talking about home routers (no enterprise grade stuff here). If you have the required knowledge, buy a router supported by OpenWRT. Install this distro and keep it properly managed (keep security updates up-to-date, create a sane configuration, etc.).
Otherwise you are screwed.
The fact that a *private* corporation is (supposedly) trying to fix the patent system, means that it is extremely broken.
... to read the article T_T
A friend of mine likes to say: "If you want to do something robust, code it in Ada. If you want to do something quick, code it in Python".
My experience running it on VirtualBox, is NO. The last version I tested was 0.4.2 IIRC. Excepting pendrives, keyboards and mouse, no USB device I tested worked, even pretty simple ones like USB to RS232 converters. Most applications crash unexpectedly, and getting pretty simple hardware configured, like the sound card, can lead to lots of crashes and even BSOD easily. I appreciate the great effort that ReactOS team is doing, but nowadays, if you need to run Windows software, you have pretty much better chance to get it working with GNU/Linux+Wine, that in ReactOS.
Security by obscurity. How could that go wrong?
I'm not updating my Nexus 4 because I need Xposed framework, and it doesn't work with ART Java VM (the only one available on Lollipop).
Weren't adenosine receptors blocked by caffeine?
Try running Android with 128 MiB and you'll be glad if it ever boots. I have an Android tablet with a Tegra 2 CPU (dual core 1.2 GHz) and 512 MiB RAM Running Cyanogenmod 10.1 (Android 4.2.2 IIRC) and it runs painfully slow. Of course I don't think iOS would be able to run properly with these specs. FFOS does a great job squeezing poor hardware, but it cannot do miracles.
FFOS is a good mobile OS. I have tried version 2.0 in a ZTE Open and although this is also a crappy phone (single core CPU, 256 MiB RAM), it is not as crappy as the Cloud FS. The keyboard works well, and the OS runs rock solid (no hangs, decent speed). The only problems with this phone are the crappy camera (slightly better than the one in the Cloud FX) and the poor multitasking due to the low RAM amount. If you install FFOS e.g. on a Nexus device, you will find it performs great and it has no multitasking problems. I like FFOS and I've been considering switching from Android to FFOS, the only things I'm missing right now is a good SSH client that works "offline" (e.g. not connecting to a web page through the Internet) and a swype-like keyboard. About these extremely low spec smartphones, I think something like the almost dead Symbian would make a lot more sense. I owned a Nokia 5800 some time ago, with the same amount of RAM (128 MiB) and a weaker CPU, and it performed pretty decent. 128 MiB is just too low for a full featured mobile OS like FFOS.
Everybody knows Stradivarius violins only sound better when the one who listens to it knows the violin is a Stradivarius. The same goes for french wine that tastes better only if you know where it comes from, etc.
Please someone upload an ultra slow motion video of the process!!!
I want to buy an ARM Chromebook since it was announced, but as today, I still have not one, and maybe I'll never have it. Why? Because I live in Spain, and ARM Chromebooks still have not been released here :(. I don't know why Google punish spaniards not launching it here, but I also don't know how they pretend to have big sales if they do not launch it everywhere and make big advertising campaigns.
It can be a good idea if it is used as a complementary system, used ONLY for a few selected packages, like for example non free ones. Non free packages have the problem that sometimes they become a real pain to get working, when the libraries they depend on get outdated, and are not available in the repositories of the distro you are using. As Ubuntu continues moving away from the free software ecosystem, I think this is hardly a surprising move.
Another reason to ditch away closed source in favor of open alternatives. Maybe $10.000 would be a good start to pay a coder to release an entirely open source one.
Just call rms to release all its fury. Jokes aside, I suppose you can request help from the Free Software Foundation: http://www.fsf.org/ Clear GPL violations, even this relatively small ones, should not be tolerated.
Comparing it with the RPi, this one has more memory, a faster processor, a lot of GPIO pins, etc. But the lack of an Ethernet port, an HDMI output, an internal and an internal flash makes it less attractive for me.
I really don't get the point about coding on a tablet. Why bother doing it when it will always be easier to do it in a "traditional" computer. Sure you can create contents using a tablet, but tablets are designed for content consumption, not for content creation.