skysight-inc/HackerNews huggingface dataset:
I had a new PM come in and give a similar speech. "If we fail spectacularly, it is going to be my job. But if we just fail, it is also going to be my job. More importantly, in neither case is it going to be your job. So now is the time when you can do spectacular things in utter safety; I'm asking you to take this opportunity and run with it!"
I hear AWS is certified for credit card processing. Is that not the case?
Lazy people plan more and in that are more likely to find the optimal solution.

They also put of things and alot of tasks negate themselfs or were redundant to start with. Manager asking for a report say. You could do it then and drop other things or you could leave it and if it is important you will get chassed up for it. If this happens alot a lazy person will write a script to do it, not tell said manager and gain from it. Others do the script, tell the manager and then get workbombed for no extra return. Lazy is in many ways another word for smart. Thing is though when you say lazy, most people think of poor hygiene, says alot about them mostly.
Cheating on getting comments? I really didn't care if we had comments or not, I thought it was a good enough post on its own. I thought giving the first 5 people a prize through a YC company wouldn't be seen as scamming.

I could see the argument that if everyone did that HN would be shit. But I don't really see HN having many opportunities for people to do that.
Toronto Airport Taxi | Toronto Airport Limo | Airport Limo
allowed to toronto airport taxi come most persons believe a automobile is a over priced first class getting a low cost higher airport terminal car is simple provided you have the suitable info almost all companies that use limos have endeavored to provide a relatively inexpensive limos to all people
Calling the megaupload seizure a "backdoor SOPA/PIPA" will instantly lose you credibility.
"or telling me the weather when I don't care or can obviously tell by looking out a window"

Damn right! That's why the Iphone failed. Pffft, who needs to know there is a storm coming in over the internet. Hail coming in? I just check if my knee's a-shakin!
The limitation of apps not saving to the iOS file system is not a bad thing. It is progress.

There is nothing preventing my shiny new iOS app from sharing files with other applications. Apple is just preventing those files from being stored on the device.
Instead, if an app developer wants interoperability, they can have the app save a file to Drop Box, or my Google Drive. Any other application can access that same cloud storage and access the file.

The beauty is we've moved beyond sharing between applications on a single device. Now EVERY application I run on EVERY device I have has the potential to share the same data seamlessly.

This is why iOS doesn't open its file system. It wants the app developers to use something a little more flexible and reliable.
I like it...
tip - use embed.ly to get better favicon / image / title / desc to the course list, will look much more of a list than a search engine result...
Good point. And if you sign up to Coinbase anonymously and acquire BTC reasonably anonymously any data that gets subpoenaed is worthless.
Toronto Airport Transportation | Airport Limo | Airport Taxi
allowed to toronto airport taxi come most persons believe a automobile is a over priced first class getting a low cost higher airport terminal car is simple provided you have the suitable info almost all companies that use limos have endeavored to provide a relatively inexpensive limos to all people
$ find ~ -type f -atime -1w | awk -F/ '{print $NF}' | awk -F\. '{if (NF>2 || (NF>1 && $1!="")) print tolower($NF)}' | sort | uniq | wc -l
83

Granted a lot of those are system files.
I'd suggest they design the device as something that clips on to spectacles. I don't see why anyone would wear this thing if they weren't going to wear spectacles (why have the whole stupid frame?) and it's not going to work for spectacle wearers (which is a lot of us).

As for the comment about making something that doesn't come between the user and the physical world -- how about not using this device?

I think it's an intriguing concept, but right now it's a solution looking for a problem. Building software this way is relatively cheap (Google Wave...) but hardware?

It makes me think that an audio-focused UI that allowed commands via throat mike might be a good way to go.
I think you're right, I just made the same comment in this thread. That could really be the key to getting, say Node.js to turn completely mainstream.
>It seems crazy, but it may be more intuitive for some people.

It seems crazy, but it may not be more intuitive for some other people. :)
Ad Biz Claims It Must Disregard User Privacy to Safeguard "Cybersecurity"
I think we all know this is unfeasible.

I don't think we can expect the general public to even be _acquainted_ with acronyms like SSL; or an understanding of why passwords need to be completely different.

And this is a startup that hopes to train people in hacking...I was just expecting a bit more on the security-side I suppose.

What we can hope to do is place warnings that let them know when things are safer and when not.

I guess I haven't followed many launches recently (to see if people are starting things more secure or not).

I checked out Hacker Rank because I _really_ like their idea. And hope to let some younger friends (brother etc.) to use the site.
Hey Mike,

I had signed up for the Venture Labs course earlier this year and found it very interesting. Unfortunately, due to time commitments and various other issues I did not follow through with keeping up with the course.

Could you give me some pro cons of the Venture Labs course itself? How has your experience been so far? Keep being awesome.
I sure hope Bootstrap doesn't become "standard".
JOBS Act Tangled in Red Tape, Coming 2014 at the Earliest
Nah, you're already screwed. If you get to the point of the pop-up it is already too late.
Yep, this is a great way to begin exploring electronics. If you want to get a little more crazy, there's also the Beaglebone board, which allows you to run a complete Linux system on an embedded device. You hook up your accelerometer, etc., and they're then accessible in /dev. Lots of fun to be had.
This is a very good point. Merging file changes between applications is not a trivial task and usually applications just end up saving their own copy (as you mentioned).

For example, if I share a photo from the Android Gallery app to Instagram, add some trendy filters and share the modified photo in Instagram, I end up with three copies in the filesystem: The original, and two copies made by Instagram to preserve both the original and filtered version.

After all, Instagram doesn't know/care whether the photo came from a camera or from another app, so it always saves a copy of the original.

Also, each time I share the photo to Twitter, Facebook or other cloud service I create another copy with different resolution, (re)compression and even dimensions, which is saved to the service out of my reach.

I guess having multiple unsynced copies of the same information is a problem that won't be solved as long as we want to have the ability to distribute information freely. One interesting development would be better content-based matching of files (e.g. Google similar image search, content-based indexing of photo subjects in Google Drive).
Infographics aren't broken. It's just that people think that they are explaining something by putting it into a graphic. It's like the 10s equivalent of the PowerPoint craze - bullet point all the sentences!

There is information, and there is explanation. One rarely follows from the other.
I guess I'll chip in here.

The handful of advantages that make PHP popular are also some of its worst liabilities. Yes, you can deploy with just FTP... but then you have upload security to worry about, and have to protect all your library files, and yadda yadda. Yes, you can do SQL right off the bat... but you have to take care of SQL injection yourself. Yes, you can stick your code right in your HTML... as hard to read as that may be. Yes, there's no resource leakage... but every request has to recompile the code and reconnect to your database.

None of these things are problems at first, but they become problems quickly once your software expands beyond two pages or a hundred hits a day. Some of them may not even be obvious problems, but you'll pay the cost anyway when some kid steals your database.

Other platforms, meanwhile, tend to have fairly simple solutions to all of these problems, for the price of a minor increase in upfront learning. But since the problems are all things that happen later on, newcomers will just see that language X is harder.

This poses something of a difficulty. How can other languages introduce the ease of PHP that everyone's demanding? We can't just port exactly the same features over, or we'll have exactly the same problems. mod_python was a bad enough idea that it's dead now. Heroku is a neat thing, but still requires writing configuration files, and nobody enjoys doing that. Nothing is really well-suited for single-page fire-and-forget, either.

I have been thinking about this since writing that damned fractal post, but I'm not clever enough to have thought up a solution yet. So, you know, it would be useful if we could brainstorm on how to fix the learning curve and deployment instead of "just turn everything else into PHP!"
Of course, me included. I like hierarchical organisation.

I suppose you could mix the Windows 8 approach (all groups) with iOS-esque folders, and allow subfolders, and then you have the best of both worlds.
It's a little more than a key-value store. The keys are impure.

One of the first issues is that the disk likes to work in terms of blocks, which tend to lend themselves to arrays, preferably of fixed size so that related data is contiguous. This leads to a limit on the number of files in a directory and so nesting directories is one of the easiest ways to contain more files.

But it's also a little more than that. Directories can group semantically related files together. This means their meta-data is in the same directory inode and so can be read in as a group. This creates more efficiency. Chances are that you'll often access many related files at once, even if it is just to list a directory, so it helps the file system to have some structure so that the meta-data of related files is all read in at once. It's an optimization that takes advantage of our own semantic information to structure the data.

This arises from disks being a really crappy way to access data. They are slow and work best with sequential reads of large amounts of data. It really isn't that useful for a persistent key-value store whose meta-data alone may be much larger than the amount of available memory.

But I tend to think of it as a KV store most of the time anyway and often wonder why we have the silly idea of directories.
How long until I can connect my Lego motors with this?
There is a hierarchy of organization structures that are typically used for "content." For content with low numbers, a list works best. For example, the home screen is a list. With a medium number of files, hierarchical structures like traditional file systems work best. However, when you reach many, many files, tagging and searching is typically needed.

Files do exist. They are the values in the filesystem KV store, but they are also a schema for the value so that interoperability works. If we followed your logic, apps would not exist either but we all agree they do.
More commentary - http://techcrunch.com/2012/06/29/zurb-launches-foundation-3-...
Petition protests Megaupload data seizure
"Linux is only free if your time is worthless"

Had to do it. I like linux a lot, but It doesn't make the quote false.
There are about 20 posts a day like this in Craigslist job feeds.

Working for free is stupid and working for 'equity' is like working for a jar of farts.
All we are talking about here is a loss of performance in Javascript benchmarks. In every day usage you simply don't notice a difference between Chrome and Safari.

So I think you have the volume turned to 11 on the idea of it killing innovation.
Tablets now drive more ecommerce traffic than smartphones
Simple solution for tech savvy users. All system prompts should include a photo of a user selected image. If the incorrect image is displayed you know its a scam.

For example when I install Windows 8 or Mountain lion one of the first prompts I must address is:

"Please choose an image to help you identify
valid system prompts"

The user is then presented 10 images (a tiger, a house, a moose, etc) from a library of 10,000 images.

"The user decides to use an image of a tiger"

Next time a user gets a system prompt if the system prompt doesn't have the picture of a tiger they know its a fake prompt.

See site key: http://en.wikipedia.org/wiki/SiteKey
Could someone convince me that Hacker News is not "serial navel-gazing". No, I didn't read the article. Do you people work? Not everyone can be a billionaire, and you can't eat ego (or butthurt). I'm really open to coming here--maybe not posting, but looking for interesting things to read. There is only so much time in the day--I can always hug my dog. My dog doesn't care about ego (or butthurt).
Doesn't seem crazy to me at all. It works well for that use case, but it doesn't scale well to hundreds of entries.

Once you get into groupings you're creating the same problems that people have with filesystems (implicit or explicit organization challenges, loss of discoverability, etc).

Search (or something like what we call "search" today) might be the best step forward from here, but you can layer that on top of any other (or no specified) KV metaphor you like.
Code signing is the reason why iOS and game consoles are closed platforms, so only the first party controls what you can run on it. They're just protecting their profits.

It has yet to be shown that code signing helps significantly to improve security. It relies too much on the competency of those that write said signed software. Measures like sandboxing are much more effective.
An HTML Endpoint That Doesn’t Suck… and Custom CSS
Why I left LAMP: A story of getting out of the comfort zone with Node.js.
No, it's exactly the point Marco was making:

> But when I wanted to write Second Crack, I went right back — it was a quick little project that I only wanted to spend a couple of days on, so it didn’t justify the overhead of learning a new language.

Whether it's webpages or web apps, nothing else is better than PHP for getting something small up and running quickly. That's the whole point of why Marco feels "addicted". I really wish there were something better in this context, but there isn't.

(And what do you mean, "ex-PHP developer"?? I've never heard someone call themselves an "ex-C" developer or an "ex-Java" developer. You make PHP sound like a cult or religion, instead of just a popular programming tool.)
They may be a tolerable layout for your set of apps, which tends to be pretty small, but for organizing all your files it quickly becomes a giant mess.
So ... what the heck is NFC?
I was working on scripting this because there's an easy algorithm to win, but the parsing out the CSRF token to make it work? You should have made it a bit less hurdle-y to script.
Strongly disagree with Rule #5: Have a “no-touch sales process”.

That's actually one of the biggest reasons why companies fail. Founders are afraid to talk to people, they just build something and wait until somebody comes and buys it. What happens next I guess all of us know.

You have to interact with your prospective customers and having a high-touch sales process is one way to do that.
Where is this indirect endorsement? I see nothing on the linked page that supports this. All it says is that Graham has funded a Bitcoin-related startup, and then declares that this must mean he indirectly endorses it.

I don't see how you make that inference. You can infer that Graham believes that there is money to be made in Bitcoin services, but not that he endorses Bitcoin itself.
No. Marco's point was that he went back to using PHP. Are you saying that he's completely ignorant?
i7 laptop with 4 GB of RAM. I haven't measured it, but whenever I kick off a kernel build it certainly takes long enough that I end up going off and checking email, etc. But you're right, I haven't built Linux kernels for desktops and Android devices and BlueGene systems, hacking in changes or just putting in debug prints to try and figure out what the fuck Linux is doing so I can write a hardware simulator. Oh wait, yeah, I fucking have.

The kernel I'm working on now, non-Linux, can build in about 5 seconds--and this kernel works on a pretty large segment of hardware, too.
I've found these 29 minute solutions can often be re-purposed and reused beyond the original intent, in even more innovative ways.
>Chrome Sync syncs your profile (credentials, tabs, bookmarks, omnibox typing model, etc.) across all your devices.

This really is a killer feature, but it needs some tweaking. I do not want iChrome to autofill the same urls it does on my laptop. Let the mobile version default to mobile sites, and the desktop version default to full sites.
Your link to Wikipedia further fuels my occasional trolls there. I know enough about enough things to introduce sophisticated errors beyond the "bill fucks jane" type trolls you'll see in article histories. Self-reflection is obviously a very difficult thing for our species, and perhaps you should reflect that you aren't being very productive making this comment. Hug your cat.
Easy solution. Logging in takes two passwords. After you enter your first password (first 8 chars of your 16 char password) you are presented with an image of a Tiger. You now trust the system. (The picture of a tiger was your secret image). You now enter your second password (the remaining 8 chars of your 16 digit password).

See site key: http://en.wikipedia.org/wiki/SiteKey
Near-field communication.
I will definitely think about it. Thanks.
Right, and in recent years, PHP has been really cautious as to how it adds certain features, but more importantly, has been cleaning up old edge cases.
I don't think you're familiar with how Multi AZ RDS works: http://aws.amazon.com/rds/faqs/#36

The whole point is to protect you from problems in one AZ by keeping a hot standby in another AZ. It doesn't matter whether it's due to EBS, power, etc. This is one of the primary reason to use RDS instead of running MySQL yourself on an instance.
What is your point? There are optimizations for dynamic languages which are typically implemented as self modifying code (e.g. polymorphic inline caching) and need writable and executable pages. Without this you could still create writable pages, compile the code and then mark the pages read only and executable. The performance penalty is negligible compared to not using a just in time compiler at all.

On the other hand, with address space layout randomization this is almost impossible to exploit. Furthermore, without ADSR and stack canaries you can use return oriented programming to circumvent the lack of writable & executable memory.
A lot of ideas sound great to management, and they work too! I mean, other than killing employee morale and resulting in long term loss ;-)

At one of my past jobs, we worked like consultants (we quoted hours that a task would take to get done, tested etc). We filled daily timesheets to ensure that our hours did not exceed our estimates. In fact, the time on those timesheets had to total 40 hours every week. So we worked the full 40 hours. And we billed those 40 hours to the client. In those few months, I was as productive as I've ever been.

Unfortunately, we weren't paid like consultants.. we got a regular salary. Management was doing nothing wrong. They failed to realize that the 'consultant lifestyle' of billing and working in hours only works if there is an equally motivating paycheck to go with it. I've known multiple people to leave because of how hard it was.

You shouldn't need a person to blame field. Good responsible employees will know what they did wrong and work to fix it. And if they don't, having the field in there will only increase finger pointing and people trying to protect their own jobs. And your bottom line will still not improve. So why do it?
I would argue against a 'free forever' plan. Free customers end up costing you more time and energy and are far more fickle than paying ones.

If you've created something good that serves a valuable purpose, it's worth charging for it.
Enough users will end up using certain images such as the tiger making it worthwhile to fake a prompt.
File systems have to evolve. These days, file system means two things: an application-independent API to access common documents, and a hierarchical local storage. But it doesn't have that way.

The best thing I've seen in file system evolution is KDE's KIO: Any KDE application can take any KIO url and use it; all file operations are asynchronious (even if you open local files, and that's very nice even for local files that are big), and any program can use network resources as easy as local with little to no effort.

But we should improve on that: a heterogenous user file system should provide discoverability (e.g. your social network photos are automatically available in any program once you bind the account, and you know where to find them). File system branches restrict some operations on files or hint on their cost (scanning a huge photo bank is a very expensive operation; you can't access the contents of audio files inside a streaming service but you can play them in the program). There also should be other ways to organize files than just dumb hierarcheries (imagine a search box in place of a folder, you need a query and then you enter the search results; or you can have tag cloud in your file system)

There's a great deal of work of innovation here and nobody does it at the moment, so it seems.

Sorry for mistakes 'cause I'm hurrying to go to bed :)
That Wikipedia article defines threads in terms of operating systems. Only one small part of that article concerns how threads are exposed to programming languages.

You can't talk about running multiple streams of instructions or bytecodes in parallel without talking about the nuances of how they share memory. Semantics of a multithreaded memory model are a highly "opinionated" thing -- there are lots of possible ways to define it, and the definition can have widespread effects on efficiency, ease of programming, and the guarantees that the runtime can provide. For example, an important aspect of a Python memory model would be that no Python program can SEGV the interpreter due to a race condition.

I recommend the following reading to get an appreciation for how much really goes into a memory model and how far from "simple" or "standard" it is:

http://en.wikipedia.org/wiki/Memory_model_(computing)
http://en.wikipedia.org/wiki/Java_Memory_Model
http://www.kernel.org/doc/Documentation/memory-barriers.txt

Python is a lot harder to define a good memory model for than say Java, because in Python lists and dictionaries are primitive objects. If you say:

x['A'] = 1

...that is a single operation that must not corrupt the dictionary, even if multiple concurrent threads are mutating it. In practice, this means that you need to either make every such mutation wrapped in a lock (which adds a lot of locking overhead) or you need to use lock-free data structures (which are still relatively experimental and architecture-specific).
Is it just me or is the likelihood of this taking off a little lower than the Segway revolutionizing transport worldwide?
"What exists is a way to name a non-volatile data set."

1. What if it's "code" not "data"? I thought "data" in this case was just 1's and 0's, i.e. what the represent, e.g. electric charges on a medium? I thought that how we interpret these charges is what makes them "code" or "data".

2. What if the "file" is stored on a "RAM disk"? Is that non-volatile? If no, then does that mean this is not, by your definition, a "file"?