People like you only want to filter out as much contributions as possible. Too much filtering is the biggest problem for Wikipedia: it make every contribution a difficult task. Filtering must be only used to avoid abuse, not to reject contribution you don't like because it don't fit an excessively restrictive policy.
Wikipedia must evolve to retain as much contribution as possible, even from expert, even with self-referencing. Instead of filtering out, it must keep and classify the contributions.
By deleting information, moderator have to redo the same again and again each time an user express a viewpoint that don't match the current policy. By keeping alternative viewpoint, others users can see that it already have been expressed and can contribute to either add more information to it or to change his classification. The moderators work will be lighter, and the contributors will be more happy to add new work.
We are human, and this fact is critically important because human don't simply manipulate facts as a computer do, human interpret facts using his own personality. Since Wikipedia is for human (as now), it must evolve to manage the human interpretation instead of regress into an useless factual only system.
For new embedded design I now use Qooxdoo, so the application work with any computers, tablets, or smartphone with any OS as long as it has a decent web browser. The usual setup is to use lighttpd web server for the statics Qooxdoo files and a FastCGI service for the JSON command parser. This allow remote operations and since the Qooxdoo part is static, this lower the load of the system to the minimum.
Best of all, the user don't have to install anything to use the application: It just have to enter the URL of the system.
I can't count how many time a page with some hard to find information has been deleted simply because someone just have no clue about the fact that that information is hard to find. The usual excuse is that there is not enough reference to verify the information. Hell, this is precisely why this information is hard to find !!!
Basically Wikipedia is now a sandbox for frustrated asshole that only show there ego by destroying others contributions. Every contribution must be retained: aside of complete joke or manipulation, people express there new viewpoint about a fact and this is important.
There is now way in expressing a unique viewpoint about a fact. The only solution is to retain all viewpoint and to classify them.
I should have used the Gnome libraries dependencies instead of GTK+ to compare to the Qt complete library.
The GPL license was a showstopper for non-open projects that don't wants to use a commercial license. The LGPL changed that important nuance.
The difference in the language is certainly a massive concern in case of a direct merge, but I don't think there is any features of one of the project that cannot be implemented in the language used by the other project. This is still a hug amount of work...
A other even more ideal dream, C and C++ should also merge. Each new standard tend to share the best feature of the other, but this process is depressingly slow, and the C++ name mangling fiasco that make each compilers incompatible is still not even in the radar of the foreseeable next C++ standards.
GTK+ was outrageously superior to anything out there about 5 years ago and today it's a declining community without clear goals and without strong support from developers that need this kind of library. I don't fully understand all the details that make this happened, but I clearly remember that about 2 or 3 years ago, something changed radically when Nokia changed the Qt license and when the Gnome leaders started to act against there own community with the suicidal Gnome 3 project.
There nothing to hope when a few peoples take the power to deny the criticisms from a large part of there community. The community simple change to get away from the toxic. That's the strong power of the open source, and it's a shame that leaders from leading open source project don't understand that simple rule.
In a ideal world GTK+ and QT should have merged there most valuable features in a new neutral project as soon as QT was fully open source. Real developers don't car about the name of the project as long as the quality and the community are driving the project up to the edge of there expectations.
You can find how to service the battery at the end of the manual, page 272. Basically in involve the back cover, 6 screws and 2 connectors. It's not that difficult but certainly most of users will be afraid to do this alone. But I think that the biggest problem will be to buy the battery part at a fair price 3 or 4 years from now.
Like for the standard USB power adapter, a standard range of phone batteries could be an advantage in the long term for the end users.
FPGA allow a lot of fun design, but there are still more expensive and complex to understand than a simple Arduino kit and IDE. Many FPGA need multiple power rails, external bitstream memory and external oscillator. Not really as fun as a small highly integrated small uC. But I hope that those two technologies will collides and bring the fun of FPGA flexibility to the uC world. There is more and more experiments on that matter from more and more manufacturers, but none are actually as open and as simple as the Arduino fans are expecting.
The most basic microcontrollers like the attiny4x or attiny8x, witch are easily supported on the Arduino IDE, allow to program design that perfectly fit your "full color on a string of individually addressable leds" and "Power, Ground and data. And even that went from needing two data wires to just one." goals.
I just shipped boards to a client that need to control a string of 20 lasers from just a single strobe signal of a camera with the capability to modulate the strobe signal to modulate additional datas without disturbing the laser synchronization. The datas allow to detect each individual board connected on a hierarchical tree (there have 1 input port and 2 outputs ports each), assign a individual address to each of them, end then to control detail of each 4 lasers outputs per board as well as an optional tricolors LEDs on each boards. All of this with only a attiny84 on each boards, and all programmed on the Arduino IDE.
If the more powerful boards in questions would get a easy Arduino IDE and a simple Arduino API, would that change your mind ? I don't know the future, but I really hope that the Linux will adopt the Arduino library for basic I/O programming that fit a lot of simple applications.
Have you ever programmer a AM3xxx I/O ? Just read the appropriate user manual to figure out how complex this can be. And last time I checked you have to statically do the multiplexer configuration in the C board file and have to change the definition header file too because only the internal signals defined for the evaluation board are defined, witch is only maybe something like 1/4 of the possibilities of the multiplexer. There is no way to even like a simple GPIO name to the corresponding multiplexed configuration to output that GPIO on a pin, all is manual and really non trivial. For the record I have wrote a code to automatically multiplex a GPIO when you open the corresponding/sys file and a can tell you that this is just a nightmare.
And maintaining a custom kernel module is a consuming task in the long term because of the non-stable API nature of the Linux kernel. Not that I want a stable API, but it's just stupid to have to many peoples doing there own private small kernel driver when probably most of them would have been very happy with a Adruino API on Linux.
And you are luck to even have 3.3V in your design. I have worked on a AM3xxx design where we have to use 1.8V because most of the peripherals components where 1.8V. I did't have a noise problem, but the AM3XXX have so complex I/O programming model that some tasks are now handled by a external CPLD, to prevent lost of knowledge in case we change the processor in the futures, witch is about to be the case after 3 or 4 years. A standard and easy library like the Arduino provides would have been very welcome on that design.
The AM3359 I/O capabilities easily outperform the ATmega32u4, so why not use the CONFIG_PREEMPT_RT patch and porting the Arduino libraries directly on the AM3359 ? The response is probably the time to do this work, but I hope that the Adruino API will be in the future directly integrated into the Linux kernel, this would make the basic I/O programming far more standard and easy than it is today. Setup a basic PWM output or an analog input is still too hard on Linux compared to an Arduino.
Yes Arduino is about making things easy and the hug success of the project prove that it fit this goal very well. Now there is no reason to not bring this feature to more powerful platforms. Actually, this is still not as easy to code basic hardware interaction on Linux. There is no a standard and simple API to do on Linux what you can actually do on a Adruino. There is project like Comedi, but there are not focused on SoC. There is almost a different IO API for every SoC on Linux, even it there is ongoing work to fix that for the most basics operations. And maintaining a specific Linux driver is a resource consuming task on the long term because of the non-stable API nature of Linux.
Think of a future when you can program a hardware focused Linux real-time application as easily as today with the Arduino IDE but on a more powerful chip where you can for example use a full database and a webserver to allow your user to interact with your device datas by using a nice Qooxdoo application from remote computers, phones and tablets. Ok I am biased, as a already do this kind of design since many years now, and the clients are really happy with it.
I do embedded systems since early 1990 and while I have see some machines running DOS at this time, I never see for at least the full last decade a new design based on DOS-like OS. And a simple Linux driver allow direct access to the hardware on any platform probably even more easily as you can do on a DOS-like OS because Linux provides already a lot of services to make drivers as simple as possible, witch is really not the case of a DOS-like where you basically have to write everything by yourself. Now if you really want the simplest way to program hardware, then the Arduino libraries is exactly with you want already.
The AM3359 is a far more flexible chip than the BCM2835 of the Raspberry Pi, just look at his datasheet: http://www.ti.com/lit/ds/symlink/am3359.pdf. And at USD 23, the AM3359 is a very good deal.
* Run faster than the Intel solution: An Atom core yield the same code execution speed as an Cortex-A8 core at the same frequency, so 1GHz A8 will easily catch on a 0.4GHz ia32). * Cheaper and simpler to design on a custom board: just look at the chip package and at the PCB routing... * Simpler power supply design, again just look at the schematics and at the PCB. * HDMI output. * More I/O, and all are integrated directly into the two CPUs, not using peripheral chips with low bandwidth. * Already supported by larges communities, for the two processors.
Intel is just trying to enter a new market with a big buzz, but there actual solution still far away from the concurrent solutions. There just don't understand that in the embedded market nobody is bounded to the ia32 instructions set. Integration is the key and there Quark X1000 don't bring anything new on the table.
Very true. This is why there is more and more discussion in Switzerland to change the army role. While the majority of the population is afraid of not having a traditional army (we voted on that exact subject just a week ago) there is a raising concern about his efficiency against more modern threads, like government/commercial data theft and manipulation, or terrorism.
Even the French military power will not be able to kill millions of peoples. The end result of an invasion will be a massive exodus into the other foreign countries, a strong guerrilla into the Alpe and a big international reaction that will certainly not be in the advantage of the invader, nor in the short term, not in the long term. Think just a second how the EU would allow a such aggression from one of his member.
Yes, Geneva is probably easy to invade from the military point of view, and this will not be enough to affect the rest of the Switzerland. But this will cause a major international problem for the invader because there is a lot of international institutions in Geneva, and there will have to react to assert there credibility. Almost half of peoples living in Geneva are not Swiss to give a other view of the picture.
Until the credibility of paying the debts rate is lost. History have show that this kind of event blast disruptively fast and the most unexpected moment.
While this somewhat was true on the last century, this in not the case anymore. In fact the "federal vacation" (about 2 weeks per years of obligatory military exercise) is now perceived by the companies as a hug vast of there employees time.
Actually most Swiss jails are overcharged due to a decade of criminal activity increase. Recent scandals have forced most of them to be very restrictive, to the point that blur the lines of international laws in that matter.
Slashdot Mirror
Have you tried the new one ? I think it's a big advance in the usability of Wikipedia.
People like you only want to filter out as much contributions as possible. Too much filtering is the biggest problem for Wikipedia: it make every contribution a difficult task. Filtering must be only used to avoid abuse, not to reject contribution you don't like because it don't fit an excessively restrictive policy.
Wikipedia must evolve to retain as much contribution as possible, even from expert, even with self-referencing. Instead of filtering out, it must keep and classify the contributions.
By deleting information, moderator have to redo the same again and again each time an user express a viewpoint that don't match the current policy. By keeping alternative viewpoint, others users can see that it already have been expressed and can contribute to either add more information to it or to change his classification. The moderators work will be lighter, and the contributors will be more happy to add new work.
We are human, and this fact is critically important because human don't simply manipulate facts as a computer do, human interpret facts using his own personality. Since Wikipedia is for human (as now), it must evolve to manage the human interpretation instead of regress into an useless factual only system.
For new embedded design I now use Qooxdoo, so the application work with any computers, tablets, or smartphone with any OS as long as it has a decent web browser. The usual setup is to use lighttpd web server for the statics Qooxdoo files and a FastCGI service for the JSON command parser. This allow remote operations and since the Qooxdoo part is static, this lower the load of the system to the minimum.
Best of all, the user don't have to install anything to use the application: It just have to enter the URL of the system.
I can't count how many time a page with some hard to find information has been deleted simply because someone just have no clue about the fact that that information is hard to find. The usual excuse is that there is not enough reference to verify the information. Hell, this is precisely why this information is hard to find !!!
Basically Wikipedia is now a sandbox for frustrated asshole that only show there ego by destroying others contributions. Every contribution must be retained: aside of complete joke or manipulation, people express there new viewpoint about a fact and this is important.
There is now way in expressing a unique viewpoint about a fact. The only solution is to retain all viewpoint and to classify them.
I should have used the Gnome libraries dependencies instead of GTK+ to compare to the Qt complete library.
The GPL license was a showstopper for non-open projects that don't wants to use a commercial license. The LGPL changed that important nuance.
The difference in the language is certainly a massive concern in case of a direct merge, but I don't think there is any features of one of the project that cannot be implemented in the language used by the other project. This is still a hug amount of work...
A other even more ideal dream, C and C++ should also merge. Each new standard tend to share the best feature of the other, but this process is depressingly slow, and the C++ name mangling fiasco that make each compilers incompatible is still not even in the radar of the foreseeable next C++ standards.
LGPL vs GPL was the key point for non-free projects that instead was forced to use the commercial license.
GTK+ was outrageously superior to anything out there about 5 years ago and today it's a declining community without clear goals and without strong support from developers that need this kind of library. I don't fully understand all the details that make this happened, but I clearly remember that about 2 or 3 years ago, something changed radically when Nokia changed the Qt license and when the Gnome leaders started to act against there own community with the suicidal Gnome 3 project.
There nothing to hope when a few peoples take the power to deny the criticisms from a large part of there community. The community simple change to get away from the toxic. That's the strong power of the open source, and it's a shame that leaders from leading open source project don't understand that simple rule.
In a ideal world GTK+ and QT should have merged there most valuable features in a new neutral project as soon as QT was fully open source. Real developers don't car about the name of the project as long as the quality and the community are driving the project up to the edge of there expectations.
You can find how to service the battery at the end of the manual, page 272. Basically in involve the back cover, 6 screws and 2 connectors. It's not that difficult but certainly most of users will be afraid to do this alone. But I think that the biggest problem will be to buy the battery part at a fair price 3 or 4 years from now.
Like for the standard USB power adapter, a standard range of phone batteries could be an advantage in the long term for the end users.
FPGA allow a lot of fun design, but there are still more expensive and complex to understand than a simple Arduino kit and IDE. Many FPGA need multiple power rails, external bitstream memory and external oscillator. Not really as fun as a small highly integrated small uC. But I hope that those two technologies will collides and bring the fun of FPGA flexibility to the uC world. There is more and more experiments on that matter from more and more manufacturers, but none are actually as open and as simple as the Arduino fans are expecting.
The most basic microcontrollers like the attiny4x or attiny8x, witch are easily supported on the Arduino IDE, allow to program design that perfectly fit your "full color on a string of individually addressable leds" and "Power, Ground and data. And even that went from needing two data wires to just one." goals.
I just shipped boards to a client that need to control a string of 20 lasers from just a single strobe signal of a camera with the capability to modulate the strobe signal to modulate additional datas without disturbing the laser synchronization. The datas allow to detect each individual board connected on a hierarchical tree (there have 1 input port and 2 outputs ports each), assign a individual address to each of them, end then to control detail of each 4 lasers outputs per board as well as an optional tricolors LEDs on each boards. All of this with only a attiny84 on each boards, and all programmed on the Arduino IDE.
By the way, I am 43 years old in a few days...
If the more powerful boards in questions would get a easy Arduino IDE and a simple Arduino API, would that change your mind ?
I don't know the future, but I really hope that the Linux will adopt the Arduino library for basic I/O programming that fit a lot of simple applications.
Have you ever programmer a AM3xxx I/O ? Just read the appropriate user manual to figure out how complex this can be. And last time I checked you have to statically do the multiplexer configuration in the C board file and have to change the definition header file too because only the internal signals defined for the evaluation board are defined, witch is only maybe something like 1/4 of the possibilities of the multiplexer. There is no way to even like a simple GPIO name to the corresponding multiplexed configuration to output that GPIO on a pin, all is manual and really non trivial. For the record I have wrote a code to automatically multiplex a GPIO when you open the corresponding /sys file and a can tell you that this is just a nightmare.
And maintaining a custom kernel module is a consuming task in the long term because of the non-stable API nature of the Linux kernel. Not that I want a stable API, but it's just stupid to have to many peoples doing there own private small kernel driver when probably most of them would have been very happy with a Adruino API on Linux.
And you are luck to even have 3.3V in your design. I have worked on a AM3xxx design where we have to use 1.8V because most of the peripherals components where 1.8V. I did't have a noise problem, but the AM3XXX have so complex I/O programming model that some tasks are now handled by a external CPLD, to prevent lost of knowledge in case we change the processor in the futures, witch is about to be the case after 3 or 4 years. A standard and easy library like the Arduino provides would have been very welcome on that design.
The AM3359 I/O capabilities easily outperform the ATmega32u4, so why not use the CONFIG_PREEMPT_RT patch and porting the Arduino libraries directly on the AM3359 ? The response is probably the time to do this work, but I hope that the Adruino API will be in the future directly integrated into the Linux kernel, this would make the basic I/O programming far more standard and easy than it is today. Setup a basic PWM output or an analog input is still too hard on Linux compared to an Arduino.
Yes Arduino is about making things easy and the hug success of the project prove that it fit this goal very well. Now there is no reason to not bring this feature to more powerful platforms. Actually, this is still not as easy to code basic hardware interaction on Linux. There is no a standard and simple API to do on Linux what you can actually do on a Adruino. There is project like Comedi, but there are not focused on SoC. There is almost a different IO API for every SoC on Linux, even it there is ongoing work to fix that for the most basics operations. And maintaining a specific Linux driver is a resource consuming task on the long term because of the non-stable API nature of Linux.
Think of a future when you can program a hardware focused Linux real-time application as easily as today with the Arduino IDE but on a more powerful chip where you can for example use a full database and a webserver to allow your user to interact with your device datas by using a nice Qooxdoo application from remote computers, phones and tablets. Ok I am biased, as a already do this kind of design since many years now, and the clients are really happy with it.
I do embedded systems since early 1990 and while I have see some machines running DOS at this time, I never see for at least the full last decade a new design based on DOS-like OS. And a simple Linux driver allow direct access to the hardware on any platform probably even more easily as you can do on a DOS-like OS because Linux provides already a lot of services to make drivers as simple as possible, witch is really not the case of a DOS-like where you basically have to write everything by yourself. Now if you really want the simplest way to program hardware, then the Arduino libraries is exactly with you want already.
The AM3359 is a far more flexible chip than the BCM2835 of the Raspberry Pi, just look at his datasheet: http://www.ti.com/lit/ds/symlink/am3359.pdf. And at USD 23, the AM3359 is a very good deal.
Sorry for Intel, but the just announced Arduino Tre is far better from any point of views.
http://blog.arduino.cc/2013/10/03/a-sneak-preview-of-arduino-tre/?utm_source=Arduino+World&utm_campaign=9f14cc4ca3-MakerFaire_World_201310_2_2013&utm_medium=email&utm_term=0_69a7d1abe4-9f14cc4ca3-76843037
* Run faster than the Intel solution: An Atom core yield the same code execution speed as an Cortex-A8 core at the same frequency, so 1GHz A8 will easily catch on a 0.4GHz ia32).
* Cheaper and simpler to design on a custom board: just look at the chip package and at the PCB routing...
* Simpler power supply design, again just look at the schematics and at the PCB.
* HDMI output.
* More I/O, and all are integrated directly into the two CPUs, not using peripheral chips with low bandwidth.
* Already supported by larges communities, for the two processors.
Intel is just trying to enter a new market with a big buzz, but there actual solution still far away from the concurrent solutions. There just don't understand that in the embedded market nobody is bounded to the ia32 instructions set. Integration is the key and there Quark X1000 don't bring anything new on the table.
Don't know about the food, but if you are able to translate this link, it would give you a more actuate picture: http://www.tdg.ch/geneve/actu-genevoise/champdollon-barre-700-detenus/story/16620565 . In resume, the occupation was 186% at the time of the article and is even higher today. A other link about this problem http://www.apt.ch/en/news_on_prevention/record-overcrowding-geneva-prison-is-a-pressure-cooker/ (even if the source is not completely neutral on that matter). Not exactly a club med....
Very true. This is why there is more and more discussion in Switzerland to change the army role. While the majority of the population is afraid of not having a traditional army (we voted on that exact subject just a week ago) there is a raising concern about his efficiency against more modern threads, like government/commercial data theft and manipulation, or terrorism.
Even the French military power will not be able to kill millions of peoples. The end result of an invasion will be a massive exodus into the other foreign countries, a strong guerrilla into the Alpe and a big international reaction that will certainly not be in the advantage of the invader, nor in the short term, not in the long term. Think just a second how the EU would allow a such aggression from one of his member.
Yes, Geneva is probably easy to invade from the military point of view, and this will not be enough to affect the rest of the Switzerland. But this will cause a major international problem for the invader because there is a lot of international institutions in Geneva, and there will have to react to assert there credibility. Almost half of peoples living in Geneva are not Swiss to give a other view of the picture.
The Debt Limit is stupid.
Until the credibility of paying the debts rate is lost. History have show that this kind of event blast disruptively fast and the most unexpected moment.
That upper rank on the CV was always covered.
While this somewhat was true on the last century, this in not the case anymore. In fact the "federal vacation" (about 2 weeks per years of obligatory military exercise) is now perceived by the companies as a hug vast of there employees time.
Actually most Swiss jails are overcharged due to a decade of criminal activity increase. Recent scandals have forced most of them to be very restrictive, to the point that blur the lines of international laws in that matter.