skysight-inc/HackerNews huggingface dataset:
This is not a bug. It is a very intentional feature, like the scroll bars, they decide they had to go against the norm to implement it and they went aead with it. The intended use case is to allow the app access to both the screens. Imagine this in say a video editing environment where you could have the video playing on the left and all the myriad number of controls on the right. The problem is, to my knowledge, almost no app has taken to it yet, no one wants to be the first, heck not even apples own apps feel the need to do it.

Conjecture->
The problem is unlike scroll bars you can't have a setting to disable it, because that would mean the app had to retroactively allow itself to run in a single window full screen mode which might be considered unpredictable behavior, something they don't like.
So to give them some benefit of doubt I see where they're coming from.
The article might not be the best (it wasn't the one I read a year or so ago), just a similar article I could find quickly. I don't think the original article was much better though =)
Nope. Don't get me wrong, I love vim, but I don't need to have it everywhere. It makes no sense in the browser. It's lacking some features Eclipse has (although if Eclipse had a proper Vim mode, I'd use it in a heartbeat).
What a nice wet blanket you have.
Umm yeah, it's a Chrome extension...

Also, I'm a C#/.Net developer on Windows. I don't even own a Mac or an iPad. What was all that about me being a Hipster?
What's the significance of this? Upon cursory glance it seems like a community site for android developers. Am I missing something?
Ask HN:  What's with all the Vim posts lately?
It's great; we get it.
I'm by no means a sublime expert, but I'd approach those scenarios like this. For replacing the inner content, Ctrl + D still works. To also replace the quotes, I'd use Ctrl + D, Del, Del, Backspace.

Yes, in the second case, Sublime is one additional keystroke. I know you could come up with examples that would show bigger advantages for vim.

FWIW I do believe that vim has advantages to some editors in certain scenarios, but I think those advantages are overestimated by the vim-inati. If you've spent years learning one editor, of course it will seem more capable than editors you have used less.
Or, if Vim isn't present, at least some version of `vi` will be. (Whether it be busybox-vi, nvi, or Ritter's Traditional Vi.)
I agree this behavior of full-screen mode is counterproductive on multi-monitor set-ups, and it's a serious issue if Apple is encouraging app developers to rely on this behavior instead of providing more useful window layouts. It's a violation of metaphor: "full screen mode" is actually "dedicated space mode," which isn't what multi-monitor users expect or want.

From personal experience, I suspect this feature is intended to make Spaces more accessible to novice users on laptops without external monitors, a common case. I never got the hang of Spaces originally, but once I started using full-screen mode while portable, my laptop got immensely more useful. For me, this was a gateway into the rest of Spaces, and now I maintain 3 desktop spaces and 1 full-screen app, and switch between them and Mission Control with trackpad gestures. Heck, I might even start using Dashboard, since it's sitting right there. (Ok, probably not.) It's a gradual introduction to an advanced feature.

Apple routinely cuts off its long tail as a streamlining measure, sometimes for UX reasons, sometimes for engineering reasons. They shouldn't always get away with it. At least in this case the intent seems reasonable, even if the side effect isn't.
I think the author fails to see that OUYA isn't made to replace the Xboxes, Wiis, and PS's of the world. OUYA is not for the mainstream. OUYA is a cool and cheap experiment. It's a cheap TV gaming box for hackers and developers akin to the venerable GP32 https://en.wikipedia.org/wiki/GP32
Wow. Huh.
By internet, i think they mean the WWW:

http://en.wikipedia.org/wiki/Les_Horribles_Cernettes
Thanks Eli. That's actually because I just created this blog about 2-3 days ago (this was my first post). It'll take a bit before it's picked up and starts ranking. That said, I should see it go up soon, since I use BrandYourself :)
Wow, that's really cool. How big of a screen did it end up being (curious about both inches and pixels)?
I'd love to hear a github team explanation of how that happened.
On the other hand, the current generation of game consoles is very underpowered compared to commodity hardware these days. That means that you can probably produce a product that competes with them in specs very cheaply, which Ouya can take advantage of. I really don't think that hardware is going to be their biggest challenge.
Maybe I am missing something but never seen that in practice (the 'foo(1, $c=20)' bit), that's a really odd way to initialize a variable. Wouldn't mind if they change it, so that it breaks (with a warning or error). Or have you seen this syntax a lot?
Smash into vim I + II (screencasts) helped me a lot.

Link: https://peepcode.com/screencasts
That's a really good idea. It could serve the purpose of giving you a badge, but it could also be a protective measure, because it means we won't let somebody else with your info use the service (since they aren't verified)
Yes, but it doesn't hurt to be skeptical. Everyone who pledges should know they're paying for a product that doesn't exist yet and currently has no confirmed games. The project description does everything it can to gloss that over, and even outright lies in some places (like with the Minecraft thing).
I don't remember if it has to be configured, but I just press Ctrl-Shift-Eject to lock my screen.
Can you explain to me what apropos does?
You may be right-- 6 months isn't much time. What should I look into?
Awesome! Feel free to reach out if you want to make sure you're doing everything you can or if you have any questions pambron[at]brandyourself[dot]com
I think this is all related to the iOS X direction Apple is going with their desktops. they would rather force a broken implementation of full-screen which mimics iOS than rethink it for a desktop. And you know, I hate to say it (as a long time user of Apple computers) but in general they really need to pull their heads out of their arses when it comes to the bizarre direction they're going with the OS X user experience. Imaginary linen canvas everywhere? Horrible slow transitions everywhere, all the time?

Or maybe I just want to get some god damn work done here.

Apple, we know you can do this stuff ever since the days the genie minimize effect was introduced (or shift-minimize for ultra slow!). Please, get some sanity and just put an advanced panel somewhere in the system preferences with, among other things (tabs in Finder?) an animation = slow/normal/fast/disabled option. We should not need to resort to plist hacks.
I think it is industry/point in career dependent, but some good rules of thumb:

Do not use MS word templates
Start with education if you are a fresh grad
Start with last place you worked, or are currently working
Use bullets to denote major things you were responsible for…
And did.

There are lots of resources on the internet for this.
Go to your school and ask them for a sample resume.
Email me (my email is my hn name at gmail) and I’ll send you an example.
I was hired by Intel Corp (finance) and currently work at a prestigious finance company.
Good job, very useful!
Which is the the :wq got inserted and not executed.
Is it possible to have the built in camera record without having the green recording indicator lid up? With or without modifying the device driver for the camera?
Can anyone who's done outsourced hardware comment on how hard that part actually is? I mean, if I met with someone from Foxconn and said, "listen, I need to you to take this 3d model of a plastic case, slam in an Android SoC and some I/O ports and a power supply and have test units ready in two months and another 50,000 ready to go by March, I can give you $80 a piece up front" -- could I plausibly get something of decent quality? What does this process actually require on the retail end in terms of time and money and expertise?

Seems to me the controller might be the hard part -- more UX testing, less standard parts. But I'd love to hear from someone who's solved this kind of problem.
It's a big site with, no doubt, a gold mine of email/password combinations to try vs. other services. Maybe the password storage was secure, but probably not. Maybe a few of those users were using secure one-off passwords, but realistically most weren't.
I think that's something we as a community forget. It's ok to feel proud of being good with your tools. It is fun. As long as we don't turn it into a "holier than thou" situation, it's neat to have an editor that you have such mastery over that you can control blocks of text with keystrokes.

Note: I don't quite have it yet myself. I'm been using vim for about 6 months (with only 2-3 of active use) and I'm actually right on that cusp he mentions--where you are searching less and less, and only for more powerful and obscure commands, and things are just starting to all become extremely useful. It's beautiful.
But, as mentioned in the above comment, you can't "prove" that something is an encrypted data unless you already have a valid key.
And if police only required to "guess" that something is an encrypted data than Falkvinge logic applies - law will be abused (at least unintentionally).
Reminds me of The Phantom video game console from around a decade ago. That one also promised the universe, with PA declaring their skepticism back in 2003: http://penny-arcade.com/2003/01/22 http://www.penny-arcade.com/2003/08/20/ (the links to the product no longer reference that device -- it never appeared)

There's nothing wrong with civilly expressing skepticism about overly-ambitious claims. This article seems to do a good job of doing just that.
Well, licensing Exchange ActiveSync to Apple for the iPhone might have been an error then.

http://support.apple.com/kb/HT2480?viewlocale=en_US&loca...
Introducing mandelbulb.js: 3D fractals rendered using open source Javascript
If I recall correctly, groupon raised something like $100 million immediately after they rejected Google's offer.

At the time, I remember reading that almost the entirety of the investment went to buy out early investors.

So it looks like Mason got the best of both worlds: he got the cash out a substantial number of shares and then hang on for the IPO upside.

You also forget to mention that the Google deal was contingent upon due diligence, which now, in hindsight, may not have even successfully gone through.
Wait, if this system works with a dummy account, then a valid email address isn't necessary at all. Any domain can set up an identity provider to support user@domain. Why drag email providers into the discussion, then? It confuses everyone.
Your explanation makes sense given most of the lights in question, but some have no turning lanes, such as at crosswalks. Perhaps bureaucracy has them required at all new lights regardless. Either way, government at work. :)

// Cool link, thanks. Shared with cyclist friends.
That sounds like a disaster. I don't think anyone wants to follow Python's lead on breaking backwards compatibility without a very good reason. A much better reason than a cluttered namespace.
The author of the article is not one of the comic guys, he was the games journalist of Ars Technica for something like 10 years. Now, that's of course not a technical merit. But it does perhaps suggest some familiarity with the games industry...

Perhaps you could come up with some talking points that address the misgivings presented in the article, rather than attacking the author? Possibly something a bit more substantial than just comparing this project to one done by incredibly talented engineers, and backed by the company that had already made world's best selling computer.
As I've already mentioned in another thread, OUYA isn't made to replace the Xboxes, Wiis, and PS's of the world. OUYA is not for the mainstream masses. OUYA is a cool and cheap experiment for hackers and developers who like gaming akin to the venerable GP32 https://en.wikipedia.org/wiki/GP32
Actually you can do it with:

<cmd>-<right>, <option-left>, <option-shift-right>, baz

And considering you didn't have to press <mode>: beforehand, it can be just as fast.

I'm a vim user, but using it for something like Objective-C in place of the wonderful autocomplete in Xcode would be a totally dumb thing to do. It's simply not smart enough to improve my productivity, even with the slight speed increases with text-manipulation.
Where I live the typical usage of a car is one person with small or no luggage from office to home and back. Buying a van for best performance for a very untypical and rare usage sacrifing the performance of the typical usage is not smart.

Smart is to use car sharing. A van when you need it otherwise a Citroen C1.
I've never found that symbols -> buffer is the bottleneck for me. Instead, it exists somewhere between problem -> symbols.
https://github.com/bitemyapp/dotfiles

Highlights: a Python IDE with refactoring, inference, search, etc.

Some hacks for TRAMP which lets me remotely edit content on arbitrary servers transparently.

A Python repl.

A generic compliance checker for Python code.

An undo module that presents undo/redo history as a visible tree that you can traverse arbitrarily.

A git client that has some EXCELLENT features.

A function to dynamically reload my environment.

A macro for my python debugger injector.

Code to unhtml HTML content and a whitespace cleaner-upper.

An interactive environment to experiment with and test regex.

A mode for CSS that highlights hex-values with the colors they represent, making their properties visual.

An interactive HTTP REST client interface for testing HTTP APIs.

A clone of hacker-typer in elisp.

Modes for clojure, erlang, haskell, rust, etc.

And a nyan-cat for my progress bar.
I don't think that using a debugger = you don't understand whats going on in your code. I've had many situations where it helped me understand a great deal what was going on. Plus, its a built in tool, so I don't have to waste time writing logging code or anything of the sort. I've also had situations where I worked with another programmer, who rarely used it, and often times got his understanding wrong when he puzzled it out. He eventually figured it out, but it was debatable whether it saved time from using a debugger.
A New Objective-C Runtime: From Research to Production
> I never think, man, if only Sublime did x, it would save me five minutes, twenty times a week!

You often don't notice how useful something is until you're used to it.
Not necessarily, it stopped Apple developing their own - and you can always "embrace and extend" so the next version of Exchange onyl works fully with Windows phone
They have more than enough money to hire patent lawyers though, who are very expensive, which means that they can definitely hire a college code to write some code, toss it into a useless Android market app, sell a few copies to their friends and tell the court "see? We are too a real business using this important patented technique in this thing that we're selling".

If your plan to eliminate patent trolls can be easily thwarted by spending a few grand hiring an intern, it is not a really good plan.
Apache Avro for Mobile Apps
There is a similar MIT licensed library on github from DZEN Interaktiv: https://github.com/DZen-Interaktiv/DZDocumentsPickerControll...
It's still a work in progress and only Dropbox and Cloud App are usable.
This is why `man` came before `apropos`. :P

http://www.unix.com/man-page/Linux/1/apropos/
My go-to library for binary mucking in Python is the fantastic Construct library. [0] [1] It is a declarative way of specifying binary structures. It handles endianness, serialization, and deserialization for you. You can build structures of structures with Construct. I used it to parse the PS3's pseudo-ELF files (SELFs) and was quite successful except for a few shortcomings in the library. I don't blame Construct though because the SELF format is a wild beast. Corbin Simpson (the author) was quite helpful when I was looking into the possibility of fixing my issues. Look at the ELF parser to see how easy it is to use! [2]

[0]: http://construct.readthedocs.org/en/latest/

[1]: https://github.com/construct/construct

[2]: https://github.com/construct/construct/blob/master/construct...
I probably define ad-hoc macros 10-15 times a day These are for tiny things that save me a minute or two each time I use one. More than the time savings, though, is the sanity savings. I've it's rare now that I do any sort of repetitive editing task.

Also, you don't have to actually program the editor yourself to reap the benefits of a programmable editor. Let's be honest, most modern editors have mostly overlapping functionality. However, one of the benefits of emacs being programmable is that it's self documenting. I can find out how to capitalize a word problematically without having to go to google by using `M-x apropos RET capitalize RET`.
The negative comments about this post by others are interesting; perhaps it's because I'm also a FE Engineer, but I thought much of what you said was spot-on. I've managed to specialize in FE only because I can also do back-end work; I have a hard time hiring other FEs because so many only know jQuery, and a spot of html and css, and I simply don't have room on my small engineering team unless they can supplement more or are very fast learners.

To be an effective FE, you need to understand the whole stack - not just how to install a jQuery plugin, but also CSS, Javascript the language, html, where these technologies are going (html5, ecmascript 6), what the back end stack looks like, how data gets from the database to the browser, how the browser rendering engine works, pragmatic optimizations, functional and OO concepts, version control, browser quirks, the TCP stack, and deployment. No, you don't have to specialize in these things, but you need to be familiar or willing to get familiar.

And you're right, most companies don't understand what FE engineers need or what they should be.
It searches for a keyword in the manpages and tells you what page contains the text.

$ apropos printf
fmtcheck(3) - sanitizes user-supplied printf(3)-style format string
format(ntcl) - Format a string in the style of sprintf
fwkpfv(1) - FireWire kprintf viewer
fwprintf(3), swprintf(3), vfwprintf(3), vswprintf(3), vwprintf(3), wprintf(3) - formatted wide character output conversion
printf(1) - formatted output
printf(3), fprintf(3), sprintf(3), snprintf(3), asprintf(3), dprintf(3), vprintf(3), vfprintf(3), vsprintf(3), vsnprintf(3), vasprintf(3), vdprintf(3) - formatted output conversion
wprintf_l(3), fwprintf_l(3), swprintf_l(3), vwprintf_l(3), vfwprintf_l(3), vswprintf_l(3) - formatted wide character output conversion
You answered your own question: given a choice, if you can buy from the supplier that sells to industrial/commercial users, the quality will usually be better.

e.g., I buy my T-Shirts from Tractor Supply. They are cheaper, much thicker and last longer than the ones I bought from American Apparel. Farmers are harder on clothing than the average urban dweller, I'm guessing.

The tools I buy from McMaster-Carr or Fastenal may cost the same or slightly more than the tools (often the same brands) from Home Depot or the local hardware store, but they are much better quality.
"Full screen" mode existed before Lion (10.7), but prior to 10.6 the API did not exist. There are actually three ways to do full-screen in OS X:

1) Use Core Graphics to capture the display,

2) Manipulate window properties to get the result you want, or

3) Send the toggleFullscreen message to a window (10.6+ only).

Let's ignore option #1. It's primarily useful when you need to change the screen resolution without affecting other applications.

You say that the feature was deleted from Quicktime, but that's not what happened. Quicktime 7 and Quicktime X have different code bases. Quicktime 7's fullscreen functionality predate the current fullscreen API, and so there's a chunk of code in the Quicktime 7 player itself to futz around with window levels, types, desktop modes, and animate the whole thing. The Quicktime X application uses a different framework for video AND a different framework for the GUI, I doubt that you could bring much code from Quicktime 7 to Quicktime X.

Quicktime 7 used the old Quicktime library with Carbon. (So the API it was using to go fullscreen is even deprecated!)

Quicktime X uses the new Quicktime framework with Cocoa.

I myself have implemented the "nice" fullscreen technique, it requires some extra code but allows you to decide whether to allow other applications above yours.
Interested in another of Kyle's wacky projects (mentioned in the article)? Check out the year of his life where he logged ever single keystroke on his computer to Twitter. Yep...all of it.

http://twitter.com/keytweeter
No that's not how green threads work, which was the whole point. You can have an API that presents you with "threads", but not have any actual threads underlying it. It is just a state machine running async, event driven code under the hood. The overhead of such a system is no higher than it is using the naive and error prone event loop approach.

Here's a paper on using userland threads to get the API advantages of threading, with the scaling advantages of event driven programming:
http://static.usenix.org/events/hotos03/tech/vonbehren.html
Quotes from Startup Leaders on How to Improve Conversions
Result of sending a cs nerd to bschool
More Rules For How You Should Enjoy Stuff: Stop Binge-Watching TV
I hope that they make OS 11 (or whatever the next major major version of the OS will be) more power user focussed. With the iPad becoming more of a replacement PC for normal users it makes sense they could focus the desktop OS on pro/power users in a couple of years time.
You know, it probably does. When they produce reports, they need to be able to do things like footnotes, tables of contents, indices; incorporate maps and graphics, and scale or otherwise make them print-ready; use a variety of different layouts and templates to make information accessible to the public; expand or modify historical reports and datasheets (ie, load files that were produced at least within the last 10 years, if not 20); and possibly produce these documents in a variety of different languages and/or formats.

In terms of single documents used for correspondence, they likely need things like mail merge, change tracking, multiple authorship (housing departments deal with a lot of legal issues, from evictions to liability to real estate transfer) and so on.

You're falling into a classic developer trap of not being interested in other people's jobs, and thus assuming that the jobs don't need uch int he way of technology. It's the same mindset that leads people to suggest using emacs for everything -because that's what the developer uses all day; or doing everything at a shell prompt - despite the obvious market preference for GUIs; or that everybody should learn to code - though most people clearly prefer not to. One might as well suggest that developers should just stop piddling about with software and learn to build their own hardware instead of pursuing the massively wasteful path of general-purpose computing.
I'm really surprised by the amount of criticism this project is getting, especially compared to the dozens of other Kickstarter 'hits' that I felt were more deserving of said critique.

The real question to me is this - can this team pull it off? If yes, then I don't care about the state of the project, only that the team is invested in it. If the team cannot, then yes, that's a real problem. However, I don't see anyone talking about the team at all.