skysight-inc/HackerNews huggingface dataset:
For a Start-Up, Visions of Profit in Podcasting [2005]
What new features would you want? I still use Tiger on my primary machine and haven't missed much (outside of performance boosts) in the subsequent releases.
Cornetto - Dilo con foto
I am not sure why laconica (errr, whatever identi.ca's code is called these days) doesn't fit the bill for him...
If you put a list in a list in Perl, don't you have to specifically dereference the sublist when accessing it?

You mean "array" instead of "list", but yes. Are there languages which don't require some special syntax for accessing nested data structures?

Otherwise you get what looks to my eye like a pointer (a weird random number).

When you stringify a reference, you get either the default stringification or an overloaded stringification, if you've overloaded stringification for a particular class. When you numify a reference, you get a unique number. Think of it as a cheap object identifier, because that's effectively what it is. It's not a great interface to expose to users, but that's its intent.

I argue that it's not a pointer, because you can't do pointer arithmetic with it.

...pointers are not a distinct type...

You mean "reference", and indeed they are distinct. They're RVs. That's a scalar type (SV).
I'm sooo confused...

Release early and often.
Get eyeballs, then monetize.
Bootstrap.
Get basic version working, then add features.
Get basic version working, then scale.
Get basic version working, then license the technology.
Get basic version working, then sell to enterprises.
Get free version working, then upgrade them to premium.
Get free version working, then sell support.
Get free version working, then sell services.
Get free version working, then put it on your resume.
Raise money, hire wisely.
Be first to market.
Be second to market.
Wait for market to clear, then enter with second wave.
Find your niche.
Have the lowest price.
Have the highest price.
Use technology as a barrier to competition.
Win a business plan competition.
Get into an incubator.
Get into a seed accelerator.
Find an angel.
Find a mentor.
Crowd source fund raising.
Get press to raise money.
Raise money to get press.

I think I'll just fall back on the only thing I know:

Build something people will pay for.
IE8 does sometimes put multiple tabs in one process, but not all tabs are in the same process. I think Microsoft should move to one-process-per-tab too;

The problem is that all these processes run in the same sandbox (at the integrity level "Low"), so they are not protected from each other.

But, I'm not sure the rest of what Chrome does would be useful in IE

Again, like IE, Chrome itself uses OS mechanisms for the sandboxing.

In particular, one thing that's strange about NaCL is that plugin processes have stronger security than Chrome itself

This differentiation seems reasonable because Chrome itself is considered trusted code, whereas these plugins aren't.

I would still like to know, theoretically, what Chrome's design stops that cannot be stopped using IE8's design, modified to have one tab per process.

Since IE has one sandbox for all processes, one compromised tab could affect other tabs. Not so in Chrome.
If IE switched to one process per tab and one sandbox per process, things would be more similar, but NACL in a Chrome sandbox would still be more secure than ActiveX in an IE
sandbox because of NACL's additional layer of security. A NACL plugin would need to exploit weaknesses in both NACL and the Chrome sandbox in order to do any damage.
Which is what makes it even worse: it's not that they can't do it on the iPhone, it's that they won't.

And why not? It can't be a question of RAM: Java has had GC back when the average home computer had half the memory available in the first gen iPhone. Nor can it be efficiency: most GCs these days are efficient enough for the average program, and a developer can always disable it if she prefers manual memory allocation.

My point is that it just ends up being yet another example of Apple making arbitrary restrictions that do little for performance or user experience, while causing a lot of pain for developers.
uh, will someone just do a fc.exe /B already?
They're playing with fire. If I can't trust Steam games to be 100% virus free I'm a heck of a lot less likely to continue buying them. They owe their customers a full and complete explanation.
I would go for the cloud storage because it makes it easier to switch to a new computer. Unless the system is design to transfer data from my local computer to my new one easily it might not be worth the privacy gain. This problem of moving your locally stored data to another computer might be compounded if you are switching operating system as well as computers.

Anyway, it will be interesting to see how they work around it.
MEMO 4 ME
自分メモいろいろ
I think that your issue is that you're thinking of a commit in git in the same way that you would think of a commit in svn. They are not the same. To commit in svn you are forced to push to the remote repo. Therefore you screw everybody up if your commit hoses things. In git, you can commit locally, and you are not even required to push those changes out. You could trash those commit without anyone ever knowing that you made them. You could make small atomic commits of small changes, and when the feature is ready to be pushed out to the 'canonical' repo, you could squash all of those small commits into one large commit, then push it out.
Try a Little Powerlessness—Pitfalls of Self-Control
Amazon EC2
Amazon EC2の導入設計から運用・保守までをトータルでサポートするサービスです。
Heroku happened.
By the same reasoning, it's my fault if I leave the door unlocked and my house gets burgled. Maybe so, but it doesn't make burglary OK, not in that case, nor in general.

Maybe they should distribute differently, maybe not. That doesn't excuse illicit downloading.
>Will it store your friends data as well

That make sense for redundancy.
I suspect that a lot of saw operators wear gloves. I wonder how well it works for the gloved hand. Also guy on video wet his hand before the test, kind of cheating a bit.
Just in case anyone is wondering, you need a "preponderance of evidence" in order to win a civil suit.
>>Verizon and Apple are both in strong positions they might want each other, but neither yet needs the other.

I think he is mistaken on this. imo Apple needs to break out of its exclusive-tieup with AT&T and Apple needs this more than Verizon.

Being locked to AT&T has greatly reduced Apple's market share and it is the only reason why more US customers are now buying Android phones than iPhones.

Verizon will continue to be the #1 US carrier without the iPhone. However, if Apple continues its exclusive arrangement with AT&T for a very long period, Android will continue to gain new-smartphone market share at Apple's expense. That will also mean that more developers will migrate to Android. All of this will hurt Apple in the long run.
Who cares? This is what the Times frequently does - these types of articles are less about finding something actually currently-breaking-ground rather than the NYT appearing to be hip to the latest trend.
I suspect that many people feel the same about computers in general...

I don't use Hg-Git, but I do use git-svn. Just like Hg-Git, I'm sure there are some caveats, but what finally got me to switch is that (at least for git-svn) it's a real live Git repo. Which means the code I write, my actual work, is all still there. The fix to my nightmare scenario? I do a fresh svn checkout to a new directory, and I do git checkout, I copy the files out, I do an svn commit of that version of files.

Definitely far from ideal, to be sure, but in my mind, knowing that was the worse case scenario, put me quite at ease. (Sure I'd read about git svn dcommit, but knowing that did set my mind at ease.)
> You're not going to come up with some solution that allows the user to "just do it" without also destroying history.

Really? I've got state A and state B. I tell my DVCS to merge them into state C. After reviewing the automatically guessed changes and manually changing the things which could not be guessed, I commit C'. C' is successor to both A and B.

What exactly has been lost / destroyed here?
"But what is the solution ? Should a good programmer dumb down his program for the sake of average ones to come ?"

Sadly, I've seen this. I worked for a company where some really smart people wrote a kick-ass fast, lightweight, and powerful Web framework in Java. It was sweet, ran great, and was making money like crazy driving Web apps.

Company ends up getting bought, and the new owners decide that Web apps are now to be built using J2EE (as it was called then) with WAR files, EJBs, and all that shit. Why? Plug-and-play Java coders FTW. Seems the last thing they wanted to have to count on was having smart, motivated developers.

(By coincidence, most of the smart, motivated developers ended up leaving shortly thereafter.)
If you know that your users are infringing copyrights, as Limewire surely does, and you facilitate that copyright infringement, as Limewire arguably does by providing P2P software principally to copyright infringers (as does seems empirically to be the case), and your product has little other purpose outside of copyright infringement (unlike, say, BitTorrent by itself), and you receive direct financial benefit from the actions of infringers, as Limewire does by charging ~$35 for their software, then you are exposed to a bunch of different vectors for indirect copyright infringement.

This is not a particularly complicated legal area, except to the extent that it necessarily skirts a bunch of grey areas in copyright law.
Sadly I guess they most of them don't make much sense without context or the discussion/thinking that led to them.

But for example, this is my snippet for merging my current branch into master and pushing that to origin (hopefully merging/cleaning up in between as appropiate):

# on local branch
git fetch origin master
git rebase origin/master

# tidy up
git rebase -i origin/master

# merge to master
git checkout master
git merge $my_branch

# push to master
git push origin master

# go back to local branch
git checkout $my_branch

I didn't originally come up with all that, mind you. It's pulled from a workflow tutorial and you'll find basically the same procedure recommended in every tutorial (keywords: feature branches and "don't work directly on master").

And yes, I paste that multiple times per day and still throw up a little bit inside my mouth every time.
Well, I can see the reason why. I just don't think they will pull this off. I'm thinking that for every profile, there will be a node(computer), so for instance, if a computer is not connected, will it not be available for viewing that users photos,etc..

But, if they save all of the content (personal info, friends info, pictures...) locally like say a repository(GIT, SVN, etc..) wouldn't this miss the whole point of owning your data, since instead of my picture being in one server..it's living in all of my friends computers.
"Do we need to understand the implementation of block allocation, snapshots, atomic writes, etc. to save files?"

No, but consider what you need to know about file systems to use them. At the barest minimum, you need to know that:

* Data is stored in files

* Files have names

* Files are contained in directories

* Directories have names

* Directories can contain directories

If you had no understanding of what a file or a directory was, I'd imagine you'd find the behaviour of "grep" or "cat" completely unintuitive.

You don't need to know how Git stores data internally, but you do need to have a basic understanding of its design, just as you need a basic understanding of a filesystem in order to use it.
Linus didn't write git for you. He wrote it for himself. Git works exactly the way Linus (and his merry band of kernel hackers (and others, who thought DVCS was a cool idea when they heard about it and were prepared to relearn SCM to use it)) wants it to work. If you want to learn to use it, cool, welcome to the party. If you aren't prepared to invest the time, that's cool too. But don't try it for like a day expecting it to be svn++ and then complain that it isn't. That's like a Windows user declaring that Linux sucks because it isn't Windows. It wasn't meant to be.

Although, complaining about Ubuntu not doing things the way they "should" is more valid, since Ubuntu is targeted at everyone. :)
Engineers to the Rescue
The real problem with a crowdsourced startup is that there's less room to pivot to a new product or business model once it becomes clear the original plan's not going to work.

VCs are happy when startups pivot as long as they get a big payout. Folks who donate to an open federated Facebook aren't going to be nearly as supportive of major shifts in focus.
They still make huge bank in the enterprise DB space. I would imagine middleware for mobile is a tiny amount of their revenue.
It's an oversimplification to see facebook as one product that can be replaced by another product. Facebook as it is now fulfills a lot of roles, some roles are going to see competition, some roles like facebook connect are here to stay.
It's all part of a natural cycle.

New media companies are being sued by old media companies because the old media companies bought the laws that made what the new media companies are doing illegal ...

just like how the old media companies were sued by older companies like Kodak who paid to have the laws make the recording industry illegal...

When companies like LimeWire or BitTorrent become multi-Billion dollar corporations, they will pay to have copyright law rewritten in such a way to prevent the next generation of competitors.

See, it's a cycle.
The skewed incentives of academia hinder CS education
Or instead of an incentive they should just drop taxes across the board for everyone.
The numbers cited in the post (as he points out) do not take into account all the antipoverty programs we have. When you take those into account you get a graph like this:

http://4.bp.blogspot.com/_djgssszshgM/SvtscpywvOI/AAAAAAAABD...

There actually is a dead zone. Which is horrible.
Excellent example of thinking outside of the box.
This comment should be hyperlinked from the main bar of HN.
I know some people use it as a web proxy :P
This was probably more than just a no-cd crack. Most retail games are protected by some type of packing system (meaning the .code section of PE executable is encrypted on the hard disk and then decrypted once in memory). The cracker has to dump the .code section to the disk once it is unpacked while in memory and then rebuild the executable (hence the ability to put the Myth logo in the file) to run properly (and probably cracking the additional no-cd checks).

So this is could be bad, real bad, since it's a executable that was basically rebuilt from a memory dump, not by a compiler.
That might be how you define gifted, but if that's the case, then it would be erroneous for you to draw any conclusions about the "gifted" based on these data.

These data are based on standardized testing of young children. Nurtureshock makes the argument that because performance on these tests is a bad predictor of later success, early testing and tracking are doing children a disservice.

This article makes the assumption that its the latter education that's flawed, and that the tests are accurate.
great analogy. gabe weinberg is absolutely correct. Being a tech person, I can build sites quickly and put them out there... but the real difference between a startup/entrepreneur and just a hacker is what you do after the site is released and your commitment to the product. As a side note: maybe the term for changing directions should have a term that carries more weight as @jbyers suggests.
This is like holding Boeing liable for 9/11.
Exactly, I don't think this project will get far trying to deliver privacy at the expense of redundancy/availability.
Git checkout also switches branches. "Checkout" sounds pretty safe, and svn has a checkout command (Which doesn't do anything but print an error message if you're in a working directory. It's the equivalent of git clone.). Finally, in most commands, git is paranoid about not destroying your changes. Combine all of these and you're in for a nasty surprise.
I'm on a Mac, so this doesn't quite applies. But thanks anyway. If someone else on a Mac had the same problem, I'd love some help. Thanks.

Update: Okay, somehow my download resumed from where it crashed last time. Not sure what I did; i think their servers are just really slow, and if you keep trying, at some point it will work. I think that what I did is go to "library", then went to Portal (my only game), and the "downloading" thing on the left ended up connecting after a long time. Then I could click on the downloading progress bar on the bottom and I can see the download speed. HOpefully it'll work this time.
I expect to need exactly the same level of knowledge to work with a DVCS, because I'm editing files. SVN was very close to providing that in many ways and it worked. I don't want to know about a staging area unless I explicitly use it, for example. I don't want to know about the design or patch handling, unless I explicitly request or apply a patch. Merging is merging - it's good couple of levels of abstraction above patches.

Basically - I want my DVCS to require as much knowledge as cp, diff, patch. I could live with them, if I had to (see - `quilt`). Now a DVCS should be easier to use, not harder. Otherwise, what's the point?
Absurd Complexity of Facebook Privacy Settings
State of text rendering in free software
Can anyone reading this thread with expertise comment on the idea that such 'donations' to a for-profit entity (or other project/implicit partnership) would be subject to income or gift taxes?
I completely agree with you.

This seems like a niche for social networking, rather than a alternative to FB.

Social networks works because they are up and running 24/7. If the data is on my computer how will others access it if I turn off my computer ?

If you ask me, they are doing a great viral buzzing money funding. This is like the 5th post I see on the web less than two hours about this.
Ask HN: Homepage header links - any best practices?
When it comes to what links should be in the header of web app's homepage, is there any common wisdom on what should or shouldn't be there?

For example:

http://www.braintreepaymentsolutions.com has Services, Buzz, About, Pricing, plus a smaller nav bar with Developers, API, Blog, DevBlog, Twitter, and Contact

http://www.picwing.com/ has Home, Tour, Pricing, FAQ, Contact

http://mixpanel.com/ has Sign Up, Demo, Pricing, Documentation, Login

http://bingocardcreator.com/ has Home, Purchasing, Free Trial, Support, Contact Us, Blog, and Sign In

Not all of these apply to my app, but most do. I could reasonably have a Home, Tour, Pricing, FAQ, Contact, About, Buzz, Examples, Sign Up, Sign In, and Twitter links up there, but that seems a bit excessive, and I'm not sure how to boil it down to the essentials. The order seems important too.

Any recommendations?

PS: The site in question is http://www.preceden.com
Missed my point.

The piracy is not their fault.

What is their fault is that they didn't make "enough" money, and now they need some extra from the pirates.
If it contains addresses and they are going to be marketing (mailing) to those addresses then salt the database with a few fake addresses under your control. If you see mail going to those addresses which wasn't part of your agreement with them you have grounds to sue. This is common practice in direct mail databases where you will rent a list for a limited number of mailings.
What if high taxation somehow contributed to make CA what it is?
No, it will not.

Yes it will. Imagine you check out revision 1, which consists of two files:

foo:
a

bar:
b

You do some hacking, and end up with:

foo:
a

bar:
b
d

While you were doing that, though, someone else committed, revision 2,
which is:

foo:
a
b

bar:
c

You go to commit your changes, and svn tells you you can't, because
you are out of date. So you have to svn update. Now you have:

foo:
a
b

bar: CONFLICT
>>>>
b
d
====
c
<<<<

Now, how do you roll back to what you had before you updated? The
state of "foo" has been lost forever by the successful merge.

For example, git checkout filename is equivalent to svn revert filename.

Annoying, maybe, but this is user error, not design error. With git, if I want to losslessly discard my working copy, I can just "git stash". If I want to losslessly update my svn working copy, though, I have to make a copy myself, and then manage the copy.

By your logic, "rm" is flawed because it doesn't ask for confirmation when you pass -f instead of -i. Well, yeah. Sorry.
Would you rather the proxy be sentient like GLaDOS? ;)
Part of the difference is also that he's looking at single people, while your linked graph is for a family of three, and there are much more generous grants/transfers for families.

There has been some effort to get rid of dead zones by changing thresholds into phase-out zones, but not everything's been changed, and some programs probably need more gradual phase-outs, especially if you consider their impact when taken together. There's an issue though that gradual phase-outs are hard to structure in a way that's politically popular: most people seem to have a mental phase-out that's fairly steep, so it's popular to give food stamps to a family of 4 making, say, $18k, but unpopular to give food stamps to a family of 4 making, say, $30k. But if you phase them out from 100% to 0% within a $12k range, you produce a significant implied tax over that range. Either the phase-out has to start so low that genuinely poor people get <100%, or it has to go up high enough that people who no longer really qualify as poor get some low but non-zero amount.
Scaruffi's history of Silicon Valley (Work in progress)
I guess this is why only rich people care about tax changes, because the rules are so complex, poor people don't have the time to study them. Rich people don't have the time to study them either, but the differences can be so great, it is worth it for them to hire an expert.
Why can't they crack it themselves?
Git is gaining a lot of attention lately. It's becoming "the dvcs" now. And that means, if you start using it for your project, you should consider what does it mean for contributors / users. If it creates an additional step where someone will say - "it will take me more time to learn, than creating the patch itself", you've lost. If many people start using git, we can start expecting things from git. It's just not about an abstract "you" anymore.
Why I Hate Textmate, Or How I Got My Emacs Groove back
Note that the ending changed since we all first played it!
I'm having deja vu about the decentralizing-diaspora that followed classic-Napster.

Diaspora == Facetella?

Ultimately, one of the biggest winners there was the closed-source but relatively efficient and enforcement-resistant Kazaa, from the Skype founders. But open-protocol (Gnutella) and open-source (LimeWire) options also did alright.

Today, Skype as an again-independent company could be a dark horse candidate for a decentralized, enhanced-privacy but closed-code Facebook-competitor.
So basically, you've written your own revision control system that integrates with Subversion. Fine.
Git makes PGP so ridiculously easy to do (as far as unix goes) that it shouldn't be that big of a deal to add the option.
Are you sure that the binary is virus free? Why do you believe so?

(I suspect it is, but how do I know?)
My company still uses Sybase. Wish we didn't, but our stored procs are so complex that switching vendors would be very expensive.
Not sure if you are asking to review your idea, but its sort of a cool utility. Anyways, in your case, I would use Examples , Guides & FAQ , and Login. In your case I would keep it simple, because overall your product looks a little overwhelming.
True Friends - How to tell if someone is a "real" friend