skysight-inc/HackerNews huggingface dataset:
It really is going to be interesting to see how far webOS goes with this approach.
I'm glad they did this, webOS is a great OS and is really nice to use on tablets.
"under an open source license" is vague. I hope more details emerge soon. If it's a liberal license this could be very interesting.

Without a group leading development the project may languish so ideally a competent group, with a vision, decides to run with webOS.
Interesting solution to their problem with webOS. I am not convinced that open sourcing it without any HP hardware to officially run it or any announcement of partners that will produce compatible hardware will allow webOS to take off. At least this is a potential credible alternative to Android open source model... if some HW folks decide to go with it.

[copied from my previous comment on the 'precentral' news]
Two glasses of red wine due to the Resveratrol content, I don't think hard liquor counts in the 2 drink total.
Yeah totally agreed. What I wanted to say is, hey, every app has some degree of social element, let it be sharing, connecting, etc. As you said, there is no obligation to use it, but it's there if u want it. 4SQ for example has the sharing part, but it's opt out.
What are the disadvantages of using Node.js?
Ah the mother of all code.
The other "vendor" is Microsoft:
https://news.ycombinator.com/item?id=3103345
I'm really interested to see if this means WebOS would compete with Android in a meaningful way. Google puts a lot of work into outreach/support/evangelism to handset makers and I think also carriers. Android's big because of being open, but also because of all of the efforts Google is making. HP is not really known for being reliable lately in their strategic direction... My prediction (for all that is worth) is that this doesn't change the landscape very much.

Totally interesting. Can't wait to see what happens.
That's idiomatic C code. You're right that it's not particularly readable if you aren't a C programmer, but if you came to a job interview and couldn't grok it immediately, I'd write "facility with C: marginal" in my notes.
email, which seemed to work ok since I had a pretty decent response rate.
please don't do that. part of what makes using jquery plugins so horrific is that every new version is a "total rewrite" and/or drastically changes the API.

the API might use hungarian notation, and you might have fallen out of love with it, but so what? it's a pretty decent API and there's no real benefit to users in changing it. they'll all to have to update/rewrite their JS to stay up to date with the library for effectively no reason.
I would hazard to say that you are probably one of the more thoughtful consultants who are good to have around. I actually consulted as well for several years. Since I have also worked on staff I tried to be very conscientious about not leaving messes for the full-time devs.

Anybody who has written software knows that it is never really "done." And as a consultant you get forced into a mentality of meeting your spec requirement so you can get paid. To do otherwise you risk working on one project forever and never actually meeting your contractual requirements. It's just the nature of the business. If you understand this as a client then you can make it work to your advantage, but if not you can wind up with a huge mess.
Was half expecting them to donate it to the apache foundation.. seems to be the in thing to do right now
I wasn't questioning their creditionals. The fact they supply a comprehensive report and make the data behind it available puts them leagues ahead of most. As you say it's just good to know where studies come from.
I'm not surprised most of the 152s are probably from the 1970s and are used constantly for training it's amazing the last even with strict control of inspections and repairs.

I learned on a Cessna 152 too but one day we had to use a 172 it was like a Cadillac compared to the 152.
I would argue the prior art for that is the iPod Touch which was out a year earlier, and probably conceived earlier than that. When I heard "iPad" rumors in 2009 the first thing I thought was "a big ipod touch." So what's to say these guys didn't see the pod touch and say "Yeah. That. But big"
thanks for the comment dude. And congrats for ur new note. Even in my circle, I have seen this trend that all of a sudden Apple Users are using Samsung gadgets especially the phones and tabs.
The hammer is cocked when your embryo is conceived, and you can find out if the chamber was empty a few decades later.
It looks like they took at least a little inspiration from Panic's Status Board: http://www.panic.com/blog/2010/03/the-panic-status-board/
Meh... No reason android devices can't be ported to webos.
I would really like to edit LaTeX in emacs (people always tell me how great the latex emacs packages are).

Given I am on Mac OS X, can someone give me a way to way to get to a "all the shiny bells and whistles" emacs with latex editing?

I tried this a few months ago and got stuck behind packages, package managers, macro packages which are for various versions of emacs. I was never sure if I'd actually got things loaded.
Does anyone know what is powering the analytics? Is it gecko board? Or a custom solution?
HP Is Keeping webOS, but Veer-Sizing It As Open-Source Project
He mentions Geckoboard
We shouldn't call people idiots, or, really, trolls. Berate the argument, not the commenter.
There's a weird assumption in your comment, eggbrain, that swgoof "expect[s] people to like [this] site".

I agree with the factual content of everything you say, but the tone and the assumptions and the context seem way off-base.

There's nothing wrong with sharing a low-investment project, and letting it have whatever success or failure it has. The problem comes with false promises, false entitlement, and to a lesser degree false expectations, but I see no reason to believe any of those are happening here. So what's the problem?
Somewhat tangential to this, but CBC radio has a droll piece they've been running for the last few years around this time. It's called 'Men Who Give Gifts and the Women Who Buy the Gifts That Men Give' It's in hour three here: http://www.cbc.ca/thesundayedition/shows/2009/11/22/november... It's about the frustration women feel when they become the official gift buyer for a male gift giver. Perhaps there's a business opportunity there.
How cool is this? I bet Touchpad buyers feel even better about that firesale buy. If XBMC is any indication, nothing can reanimate old hardware like dedicated OSS nerds.
Antirez's decision is decreasing complexity and time for him and the people who help maintain his project.

The code is right there. Any of your BigCorps are free to grab it and make it work. They are not free to demand the time of an open-source dev.
I don't think that an advert has provoked me or anyone I know to buy anything. Samsung's latest ad campaign is a definite strategy shift though that has grabbed attention (as was the point of course).
Here Is the Absolute Saddest Business Card in the World #webOS
> There's a BIG difference between "no one else will implement" and "no one else CAN implement."

That's true, but is it the right question?

Browsers could also have implemented ActiveX, back in the day. There was nothing stopping them - except that it would have been very bad for the web and for non-Microsoft OSes. Thankfully, other browsers did not implement ActiveX or else it would have still been used today.

The real issue is that no one but Google thinks NaCl is good for the web. In that sense it is similar to Microsoft with ActiveX. Of course, there are big differences too - NaCl is open source, so it would be easier to implement, if another browser changed its mind. Still, that is just a matter of technical convenience - if NaCl were closed source, the other browser vendors could still reimplement it. But again, the issue is that only Google thinks it is worth implementing in a web browser.

Kudos to Google for making it open source, but open standards are just as important for the open web.
> "HP will be an active participant and investor in the project"

"competent" is up for debate, but they're planning on still running the show.
This is fantastic news. WebOS has always been full of great ideas, but held back by shaky underpinnings. It's like the inverse of most open-source projects. Great UI, not-so-hot implementation.

There's a lot of folks (myself included) that would have been happy to jump in and assist, but couldn't due to the closed-source nature of the platform.

The real prize, however, is Enyo. It's a great Javascript framework, and works in virtually any webkit-based browser. The biggest problem was the licensing terms: You could only use it on WebOS phones. Now that barrier's being removed.

I'm really looking forward to this. Can't wait to dive into the code. :)
Dumb question, but what's in it for HP?
I smoked for a while through college and for a few years afterwards. I don't know if there are real physical benefits, but I found it relaxing. Also, going outside for a smoke break was a nice way to meet people I wouldn't talk to otherwise.

Also, it was a nice way to take a break think over what I was working on. It would also help me concentrate afterwards.

That said, now that I've quit I'll never start again...
I like the idea of linked control, like on the small planes. That's "the principle of least surprise" and also gives the copilot the right information of what another guy is doing -- that was obviously missing here!

However if you add force feedback of the plane computer "correcting you" you'd never know if it's plane or an another guy. Therefore, force feedback from the computer doesn't sound to me as a good idea. Some kind of feedback would be a good thing, but in panic, it wouldn't be noticed. I guess I'd put something like something "protruding up" on the stick when in another mode -- you'd feel and see it.

Finally, switch flipping is unnecessary if you have a force feedback. It think that's really the major feature missing!
the "big ball of mud" that gets wrapped around factoring-1 IS the re-use. its not like a team writes one component, then says "OK we're done!" and writes the next. you write your infrastructure hand-in-hand with the code that uses it. but as you understand your infrastructure problems, you don't fix them, because "we'll just write a few more things around it for this milestone". for the next five milestones. software human process doesn't happen in nice, discrete chunks which are easy to understand, talk about, and justify.
Greenstart hatches four energy startups, from gamification to biofuels
I almost accepted a job offer from Digg when they were at their peak. Kevin seems to be using "PHP" as though it is some kind of derogatory term for developers. I don't think that's very fair. My opinion is that Digg went off course with their major update fiasco which changed the nature of the site. It had nothing to do with the programming language. I have my own opinions about what made Digg great, and subsequently what made it not-so-great after that update, but I really don't think it had anything to do with PHP.
Be great if this was true. Hope it doesn't have a 2-hour battery life though.
Not a single mention of SOPA in the article...
MongoSV Live-Blog: MongoDB’s Storage Engine Bit by Bit
Good concept, bad pricing. Not owning your product and selling it at a high markup (starts at cost + ~$20 for small items and converges to 20% markup for more expensive items I believe) will prove to be a non-viable business model. Consider offering some customization, bundling, or outright proprietary products - difficult to do, but that's often the way to own the space. Eg look at Warby Parker and how owning the product allowed them to disrupt the glasses market.
'Contribute to open source'? More like 'dump onto open source'.
I'm buying my 150€ dev touchpad right now. I was hoping for something like this before committing to the platform.
> Now, if you mean that no one is writing full-scale professional desktop or web applications by piping together sed and awk, then of course you are correct.

That very much depends on where you draw the line. If Ruby on Rails, Wordpress or Jango are "professional web applications", then so is werc [1] "web anti-framework" which is built entirely on rc, the plan9 shell.

xmobar [2], dzen [3] and geektool [4] are all notification tools that can watch files for changes or accept, process and display input through pipes.

Quicksilver [5] uses piping, though this is arguably a different paradigm — select object first, then the action, then details. I wonder why this paradigm isn't more popular and articulated, especially in the light of ubiquity of indexing tools like Spotlight on OS X, wonderbar in Firefox and DDG bang operators [6]. It would be interesting to see the trend continue.

Overall, this piping stuff around approach is very subdued, but virtually omnipresent. Modern cell phones (Samsung Bada, anyone?), TVs and other "smart" appliances provide a glimpse of the non-composable world.

[1] http://werc.cat-v.org/docs/

[2] http://projects.haskell.org/xmobar/

[3] https://sites.google.com/site/gotmor/dzen

[4] http://projects.tynsoe.org/en/geektool/

[5] http://www.blacktree.com/

[6] http://duckduckgo.com/bang.html
DoJ: Take AT&T/T-Mobile trial off the fast track
Let's be fair though -- Microsoft went ahead and grabbed the open-source code and provided a patch that makes it mostly work under WinAPI. In my book, that's pretty decent behavior.
Musician packed MegaUpload Ad
Gartner Prediction Underestimates Cloud Security Concerns
If you read the book's PDF (http://epicenterconsulting.com/book_source/Obsessively-Thoro...) you'll also note that:

"Hal was the first to introduce the concept of building an interactive demo as a key part of the software development process"

Really? I can't imagine that's true
Honest question: to what end is this happening? They receive no money from a sale of the project, they still have to commit engineering resources, they lose some level of control over its development and its future,and how is it going to be placed into someone else's aboveboard commercial mobile product if there aren't any guarantees against patent attacks?

What is the upside?
Why do I doubt Samsung's ability to pull that off?
PR. They haven't got a clue about what do with webOS, so instead of announcing its shutdown, they 'donate' it to open source.
Yeah, eeeeverything about the navigation needs work, and it seems prime candidate for early minimal work.

How do you get a new random idea in category X without clicking Back and then re-selecting the category? Without voting, I mean.

Open-source the site source code on github! :D
Ideas I've had:

-Dedicated bicycle speedometer/route tracking computer (if it has GPS)

-Remote for my music server

-Timelapse camera

-GPS tracking device/bug

-Sleep analyzing alarm clock (if it has accelerometer)

-Media player (obvious)

-Donate to developers to facilitate porting newer releases/ROMS to older devices

-Networked motion sensor alarm? (I assume an app for this exists)

I'm sure there's more I've thought of at one time or another, if I remember, maybe I'll edit and add them here.

EDIT: Also, the Android Open Accesory Development Board[1] would allow you to branch out of what the phone itself is capable of and work with external devices via the USB port. Perhaps robots, for one idea?

[1]http://developer.android.com/guide/topics/usb/adk.html
Ask HN: What would you do? Co-founder troubles.
Hello everyone, for obvious reasons this will probably be a bit light on specifics, but I'm looking for some personal opinions and a bit of perspective really.

I'm in the position of co-founder in a startup, and I'm having serious doubts about the commitment/benefits of the other founder.

He approached me initially with an idea, we brainstormed casually for a month or two off-and-on, and then decided to make a go of it... and that's where his contributions have ended.

It was the plan that we'd both build the app together, we're both capable coders, and we'd split responsibility for all the non-coding tasks. It started well, we both collaborated and code was produced; however, due to his family/personal commitments I took on a heavier workload for the programming and he volunteered take responsibility for the more businessy side of things (registering the company, hiring an accountant, acquiring appropriate licenses, hosting, payments etc...).

Fast forward 3 months. The app is now almost complete, 99% by my hand (he contributed literally 1 class in the end), and I'm starting to put in place the finishing touches for launching. I've also taken on all the admin/business duties too, in order to keep the ball rolling.

His contributions:

* Initial idea
* Brainstorming of ideas/vision
* 1 class in codebase ;)

My contributions:

* Brainstorming of ideas/vision
* All development
* Register and manage servers (CI, test, and a prod box, email, database)
* Register company, handle the accounts, and bank account
* Licenses/legislation
* Payment processing

I like the guy, and it was his idea, and we did both do a lot of chatting about what the idea should become; but I'm not really seeing that he's really pulling his weight to own 50% of the company, right now I could've probably got the same value out of chatting to a friend at the pub. I have no feelings that he's deliberately trying to screw me or anything of the sort, he's just not actually doing anything.

I'm not that short-sighted though. I'm aware that doing it alone could be significantly more difficult than with a partner. I'm conscious that he may very well come through in the long haul.

What do you think? Am I being a fool for thinking like this? Or a fool for going 50/50 with this guy because we're friends and it was his idea.

Thanks for reading! Any advice would be much appreciated.

tl;dr: Should I pull a Zuckerberg on my co-founder for welching on his responsibilities and leaving all the work to me?
> If Emacs is nearly an operating system then it's kind of nearly a software Lisp machine.

This is not an accident. GNU Emacs was probably intended to be the first step towards a complete lisp system for GNU, akin to zmacs on symbolics.

The free software manifesto mentions lisp several times
http://www.gnu.org/gnu/manifesto.html
Our experiences don't match. Avoiding nested includes has been a part of the rigorous and useful standards of a lot of important, mission-critical, large-scale projects, and is something I try to enforce in my own code.

There are numerous examples of projects which follow that recommendation. I'm told, for example, that the recommendation on the excellent Blender 3-D graphics system is to avoid nested includes. Other examples:

NASA:
http://sunland.gsfc.nasa.gov/info/cstyle.html

European Molecular Biology Open Software Suite (EMBOSS)
http://emboss.sourceforge.net/developers/c-standards_new.htm...

Atacama Large Millimeter Array (astronomy):
http://www.alma.nrao.edu/development/computing/docs/joint/00...

Clinical Neutron Therapy System (for radiation oncology):
http://staff.washington.edu/jon/cnts/impl.pdf
Great point. Most of the popular open source projects in the JS space (jquery or node.js for instance) have a person that serves as the voice of the projects. I think if someone from the webOS dev team stepped up to take that role, I'd be a lot more confident in where the platform is headed.
Yea..provocation was in the sense of Perception change and building of interest. Earlier, when I wanted to buy or gift a phone or a tablet to anyone, Apple had a clear position in my brain..but now I take Samsung as a very serious and good option to think about along with obvious Apple. But yea, immediate buy decision is near to impossible with this ad or any ad campaign.
Seconding the excitement about Enyo. This could/should be absolutely huge. Speaks to the level of disorganisation in HP that the blog they link to has no mention of the open sourcing, though. Woops.
> You sir, are apparently willingly ignorant.

Hm yeah, it appears I am. I think you're actually right about that.

Have you come to this thread to bash anyone who "admits" to using Microsoft software? It feels like that to me.

I don't consider buying software from Microsoft to be "choosing a side", just like I don't consider buying Apple products to be choosing a side in the child labor wars, just like I don't consider buying a chocolate bar means I choose the side against slavery in Africa. If you're as hard-line as you demand, everybody becomes a hypocrite.

> Cool. Don't be surprised that your choice of platform and tools, e.g. the latest-and-greatest .NET 4 Entity Framework, limits your access to other tools, e.g. redis. Life is a tradeoff.

Completely true! Did I ever say anything to the contrary?

There's a big difference between "There are valid use cases for Redis on Windows" and "I demand that Antirez port Redis to Windows, now, for free". I really only made the former point, but I have the feeling that you're passionately ranting against the latter.
> If you can't write your own green threading library, you are either lazy or a parasite. Please let's be reasonable about what is worth rewriting and what is not.

I was mocking your statement, in case you missed it. I don't think that if you don't write cross platform code you are lazy -- especially not high performance code that derives some of its performance from platform specific features!

And no one needs to rewrite anything! Just use your own fork with your PATCHES. Read my lips again: NO REWRITE NEEDED!

> This attitude is why so many man-hours are lost in the community, and why so many pointless forks exist.

For some reason, you believe the community owes you something. And what exactly are those "so many pointless forks that exist"? GCC has had 5 significant forks through its life, non of them pointless.

> Come now, do you honestly believe this is a more efficient/sound/useful solution than trying to get antirez to just add support in mainline Redis (without even having to start from scratch)?

Of course it is efficient for parasites like you when antirez spends the time -- especially since you don't care about development efficiency and speed on Linux which are essentially guaranteed to be harmed, at least in the short term and possibly for a long time to come.

The only question is: why should antirez care?

> Care to elaborate? I'm not fluent in "tired cliche".

SPEND TIME (which translates to SPEND YOUR INCOME which translates to SPEND MONEY) MAINTAINING A WINDOWS FORK, TO ANTIREZ STANDARD OF PERFORMANCE ON LINUX AND CLEANLINESS OF IMPLEMENTATION, and if you manage to achieve that, I can almost guarantee he'll merge it in. The problem is, it might not actually be doable -- but TALKING ABOUT IT IS CHEAP FOR YOU, so that's what you do -- which is what others tend to call BULLSHIT. Is this elaboration enough?

> My team and I do a lot of cross-platform C code, and this would've made our lives a lot easier.

Translation: We would have gotten something for nothing.

Question: Does your team release any of its code? If so, can I have a look? If not, why not -- and why do you feel entitled to someone else's source code?

> Then again, if people complained (as I did here!) perhaps things may have gone better?

Oh, you are so naive. The only reason the posix subsystem existed in the first place was so that NT would be eligible to compete in Government tenders (predominantly, but not only, US). It was always a 3rd class citizen, hardly supported or usable, although it was very successful in the business sense of letting MS compete in those tenders.

Microsoft only fixed browser standard compliance (and not fully) when they realized they're starting to lose the browser war again. That's 10 years of very vocal complaints that went unheard, and for a very simple reason: It conflicts with their lock-in strategy. Same thing about the posix extensions.

You might be a very good developer for all I know, but you really fail in understanding how the world works.
I wonder how much of this has to do with the RIAA lawsuit