HP Releases Open webOS 1.0 51
An anonymous reader writes "Hewlett-Packard has announced the release Open webOS version 1.0: 'We now have an OpenEmbedded build that allows a full webOS experience running inside an OE emulator. We have added core applications — email & browser — while continuing to support the desktop build environment. The 1.0 release also brings support for Enyo2. You can now take apps built on one of the best cross-platform JavaScript frameworks and easily run these same apps on Open webOS or other platforms. In the past 9 months, we have delivered over 75 Open webOS components. This totals over 450,000 lines of code. ... The source code for Open webOS can be found in Open webOS repositories on GitHub. Combining today's components with those from the previous releases, Open webOS can now be ported to new devices.' HP also reaffirmed plans to continue work on Open webOS, and to bring support for Qt5, WebKit2, open source media components, and more."
Re:How long did that take? (Score:5, Informative)
Time to get WebOS running, ten minutes
Time to get OpenEmbedded build working, ten weeks
amount of time taken asking questions: 0 seconds. ability read and follow instructions: 0%. ability to complain: 100%. ability to file bugreport or contact forum or mailing lists requesting detailed instructions: 0%.
_come_ on, dude, you know the drill. if you can't get something working, *ask the developers*. give them detailed reports, help them diagnose the problem with the build instructions, so that they can be improved. over time, things get fixed, yeah?
what would you have the developers do, huh? if you understand what openembedded's "bitbake" command is really about, and understand how powerful it is, you wouldn't be complaining, you'd be somewhere in awe or possibly shock. openembedded has a bang-per-buck ratio that's wayyy above anything else available from the free software community. gentoo's portage, buildroot, debian's build system - they're all child's toys by comparison.
tell me if you know of any other cross-build system that, in order to correctly configure a package and cross-compile it, fires up a *native* gcc compiler and runs the autoconf configure script in a qemu command-line virtual environment. now that's just so fucking smart - it solves *all* the problems that all the other "autoconf cache" broken workarounds just can't get right.
the people who came up with openembedded are just... unbelievably smart people. they know that they don't have a lot of resources, so they come up with solutions that make up for it, and do the work in an automated fashion. they've been at this for over 10 years, so cut them some slack, ok?