skysight-inc/HackerNews huggingface dataset:
Visual programming is a broad term that has been used to describe programming with visual aspects. Lets not even discuss visual programming languages, like Quartz Composer.
Which OS X? Unfortunately it supports only 10.9 or later.
I think companies like webvan figured this out 15 years ago.
But there's a related problem with docker.com: The site is so afraid that you might miss any of its very important links that it misses any comprehensible organization of its content (at least on the main page). Instead, it presents the content in various ways, often in parallel, leaving you without a (mental) map. Thus, you will probably miss some of the content advertised there ...
That's a really interesting idea! I'll have to try it out and see how it correlates with measures like the SSQ: http://www.twentymilliseconds.com/post/measuring-motion-sick... Might only measure dizziness and not nausea, or vice versa...
I recommend this to everybody with even a little bit of interest in mathematics: http://camdavidsonpilon.github.io/Probabilistic-Programming-...
Is there a reason they have white dots on the new prototype? Are they doing any kind of external tracking?

Edit: Ah, yes that's apparently how they're doing 360° head tracking.
> This seems to reinforce a pervasive stereotype that Android users are utilitarian while iOS users are much more concerned with aesthetics and form

The root is probably in iOS users being richer and coming from a richer countries. It's like the interior design of cheap kebab shops and hairdressers vs hipster artisan shops.
You're getting down voted so I'm going to post that I agree with you, but maybe add some perspective that you might have missed.

I agree that the Apple app store is better without the ugly apps because there already are so many apps out there. Another poster made a comment about "reviews" and "screenshots." Yes, there are reviews and screenshots, but for some app types having to weed through even what does make it through is very time consuming. So this saves me time from having to look myself. I'm not sure what could allow a more lenient acceptance strategy and help me weed through apps I'm not interested in, but I'd certainly appreciate it!

There are some app types/categories where it would be too bad if an ugly app didn't make it through, but I think in the grand scheme of the Apple app store these sorts of rejections are a positive.
Doesn't matter, any major compiler will transform this into an bitwise and.
Maybe you shouldn't care about cycles, but using a loop for something that can be done without branches is a definite cognitive overhead.

If we want to avoid bit twiddling, how about this:

(mqhp->mq_maxsz + MQ_ALIGNSIZE - 1) / MQ_ALIGNSIZE * MQ_ALIGNSIZE;

I would expect a compiler to emit the same instructions as the original, but at worst you would have an add and two shifts rather than jumps or complex float operations.
I really wish they submitted their iOS 7-8 icons to themselves to get a rejection and maybe improve them.
Was this supposed to be sarcastic? Because the app is still ugly.
> Since Apple has the dominant appstore, they can afford to be choosier

Which creates a feedback loop in which the store improves in both quality and quantity - unlike WP and Android - sadly.
"The AI neither hates you, nor loves you, but you are made out of atoms that it can use for something else."

—Eliezer Yudkowsky, Global Catastrophic Risks p. 333.[1]

Apparently Nick Bostrom's Superintelligence: Paths, Dangers, Strategies[2] does a better job of highlighting the dangers of AI, though I haven't read it yet.

1. http://www.amazon.com/Global-Catastrophic-Risks-Nick-Bostrom...

2. http://www.amazon.com/Superintelligence-Dangers-Strategies-N...
Hi, author here. My align_2 implementation is indeed very naive. Part of that was to show just how much overhead a naive implementation could add, in this case 3 orders of magnitude. I'm also new to systems programming. This article should serve as a reminder to experienced hackers that idioms are often only obvious _after_ they've been explained. My last 4 years were spent working on a distributed database; I could bring up "obvious" idioms from that world that might perplex a kernel hacker.

But you are right, this is indeed a very obvious line of code once you understand it. Thank you for your comments.
My original goal wasn't ever to really create a visual programming environment, though the mismatch here might just be us using the term "visual" differently. We wanted to make something that allowed people to create whatever representation of their code/project/etc they want, but I didn't really expect that to ever turn into code generation via graphical media.

Code Bubbles isn't visual programming as the term is typically used, it's just a way of organizing text in a more meaningful way.
So the problem with the Apple Review process is that Apple is making the decisions on what constitutes good or bad UI.

The Google Play store (and others) already give you feedback - customers give ratings and can provide a comment. This is much better than a central authority dictating what is good and what is bad.

There are many apls that have no need for a great UI - that a perhaps more functional in nature than aesthetic.

The beautiful thing about an open policy like the Google Play store is that you can not just get actual customer (Apple reviewers are probably not your customers) feedback and actually REACT to the feedback by uploading a new version right away... While on Apple Store users have to wait 7-10 days for the App to be "approved" - and if it gets rejected you have to wait another 7-10 days.
Apple would be choosier even if they had Microsoft's market share in the mobile space. It's just how they are. As it works out, the strategy seems to have paid off for them.
Well, I work on a number of different Unix servers that it make more sense to me to configure bash{rc,_profile} for each server I'm on.
I think you would find that most iOS users are just as utilitarian. The vast majority of complaints you see on iOS app reviews concern functionality. If anyone, you should accuse Apple of being (overly?) concerned with aesthetics.
There is a talk from Andrei Alexandrescu at Going Native 2013 where he mentions one of Facebook KPIs is request per watt.
Not bad. Reminds me of Hackety Hack.

Bret Victor's criticism of KhanAcademy is just as relevant here http://worrydream.com/LearnableProgramming/
Of course there's no consistent standard here, so it's a completely arbitrary decision by the reviewer. On another day, the first version could have passed.

(The iOS HIG is supposed to be the standard, but strict adherence requirements would remove 98% of the apps on Apple's store.)
By the end of the year, Google's crawler will render all JavaScript
Decent overview of the past two decades. But it's ironic the navigation and decoration on that site are also great examples of bad web design.
Relying on App Store reviewers for feedback is a bad idea. The whole process is capricious. It's likely had he submitted at a different time and gotten a different reviewer, the app would have been approved.
I appreciate what Apple is doing, and holy crap it was indeed ugly. Still I'd rather let the market decide. A better approach would be for Apple to tell you that your app was approved but it would be harder to find (like you'd have to scroll/click/etc a bit deeper) until you prettied it up (or until it got a bunch of good ratings despite its appearance).
Interesting, I wasn't aware that this was due to new policy. I've definitely noticed a dramatically increased police presence on the streets of New York, especially in poorer neighborhoods near gentrifying areas. I also frequently witness police stopping traffic to randomly select cars for some sort of odor/ballistics residue testing. As a resident of Philadelphia, where I seldom see police outside their vehicles, it all feels slightly draconian and disconcerting. I can only imagine what this presence feels like to someone other than a young, white male. I've never felt unsafe in any of these neighborhoods prior to the new "Omnipresence" strategy.
Instead of text editing, sliders and knobs to manipulate values work well. Music lends itself well to graphic interfaces, because of it's sequential nature, you don't usually work with text or conditionals. Especially for the _feedback_ anything visual works a treat though.

With expert systems you work blind half the time, because of the size, that you can't get all into scope. So you simplify and make abstractions, but it's complicated to map multidimensional decision space onto 2d. Therefore a good visual programming environment would have to be a complicated system, that, well, you'd have to learn to navigate and memorize.

Don't know what you mean, how to _incrementally_ add or reset a button, like Undo/Redo?
It probably wasn't Swartz's fault the servers were slow, but even if the slowness was unrelated he probably popped up in one of the queries they used to diagnose the system.

Or it was a conspiracy. Parallel construction has me freaked out too. I just don't think that it's the most likely explanation.
That's correct. There are so many things we'd love to do with LT, but the truth is (as Sean knows quite well) our current programming models simply don't support a lot of the experiences we should have.

We started to hit roadblocks with our current paradigms and we happened to get lucky enough to stumble on some ideas that could move us forward. What we're working on now is the foundation necessary to do things we've always wanted to do (and awesomely, far more).

We'll be announcing some cool stuff soon, but the gist is that we have to look at the whole stack to find something better. So that's what we're doing.
The key being "once you understand it." I look forward to sending this around to make sure folks "get it" -- that which I grasp intuitively is magic for them[1], and kernel hacking is rarely the deep topic people imagine it to be. I doubt I have the right perspective to explain this as clearly, and if I could, I lack the time to do so as deeply.

[1]Their words, heard within the past month.
This is much better than a central authority dictating what is good and what is bad.

It's ironic that the company that commissioned the 1984 ad ended up seemingly irrevocably drawn towards centralized authority and secretive hierarchical decision-making. (They were always at war with Google. Always.)
I've often felt the opposite. Adulthood is the real deal, the time when you finally have to face the trappings of the day-to-day life, as you will have to until you die. Delaying it doesn't seem to do much good; although advancing it wouldn't really help. What would be better is to prepare for it. Something like the apprenticeships of centuries past would be vastly beneficial today I think.
Please, do go on!
I don't get the benefits of a vim script manager vs using your distribution's package manager, which seems to cover most (it not all) of the above.
Author here, I won't get to it today but I would like to try the method you describe. I realize that benchmarking is a very tricky thing having followed Brendan Gregg's work the last couple of years. This is why I also ran my baseline benchmark which simply performed a ret. I learned years ago from tuning cars that absolute numbers are less interesting than relative. That said, I am a total newb at low-level stuff like this and I would not be surprised if I messed something up. I'll be curious to use your method and see how it compares.
I would guess that the majority of users on both platforms don't really care, or don't understand the subject clearly enough to verbalize it. But among the most vocal and informed users of each platform, the difference suggested by the GP is quite clear.
Personally, I don't use a script manager, but my distro's package manager. That handles updating in a perfecly clean way.
Themes are nice, but completely worthless to me as a user if the keyboard doesn't work well. I don't even care about how they make the keyboard work (they can hide all their magic algorithms and settings, etc. I don't want to tweak stuff, I just want it to work), I just want the damn keyboard to function properly. Nothing ruins a phone for me faster than a keyboard I hate. And honestly, I've tried a lot of different keyboard apps on my Android phones and none of them (even the highly rated ones) are very good. They do a poor job of word prediction and auto correct, stutter, lag, and just generally piss me off. Keyboards on my Galaxy Note I used to have made me so mad I almost wanted to destroy the phone.

Ultimately, if I like the keyboard THEN I'll be interested in themes for it. But if the keyboard pisses me off then I'll go looking for something else.

All in all, I really wish that we could have Blackberry-quality physical keyboards on Android and iPhones because these touch keyboards are way harder to use productively than something with real keys.
The notion of a Lisp curse and the Bipolar Lisp Programmer is just bullshit. What he describes, true or not, is not particularly tied in any way to Lisp. He perceives it, because he lives in his bubble surround by his Lisp dialects and the attempts to make it popular.
First Hands-on: Oculus Rift Crescent Bay is Incredible: http://www.roadtovr.com/hands-on-oculus-rift-crescent-bay-pr...
Some of your problem predictions are 100+ years in the future. I generally regard these as nonsense.

Looking at the relative rates of technical growth and computing power, it's incredibly unlikely that we'll be able to accurately pick out what the future is going to bring.

Examples of technologies that are expected in the next 50-100 years: 3D printable organs which can be transplanted, based on your own stem cells; the first smarter-than-human general purpose AI; fusion power; the ability for bioengineering to be done with a home lab kit. (We're actually at the cusp of the first and last of these now.)

That level of bioengineering, computing prowess, and cheap power will have an incredibly hard to predict effect on issues like food production, ecosystem maintenance, etc.

So which of your warnings are only problematic at 100+ years?
Neither of those were examples I cited, and I cited two other, specific examples.

I have the feeling you didn't read what I wrote.
First reply, be gentle.
I think the problem you're describing is one that results when an expert tries to teach / design something to beginners and they forget how to present the information in an approachable manner. Sure, with code it _seems_ like "duh of course you need to _know_ the libraries to use a visual editor!" but that goes against the basic concept of having a visual styled IDE.

I'm a UX / visual design guy very interested in learning to program, have been for several years. But it's just not approachable beyond stuff like CodeAcademy, as it quickly becomes a labyrinth of documentation, cryptic instructions, and unclear ways to approach building a worthwhile program.

I digress, as that's not my point. Point is, many visual editors, even Quartz Composer, fail on the same area; they aren't approachable beyond tinkering with the switches and buttons. UX isn't even a passing thought on these tools. I would love to participate in building one of these tools and learning X language in the process. Until a visual designer is involved, these tools will continue being relegated to tiny niches unless a visionary developer comes along (-and actually completes the thing, as was mentioned above about the LightTable Chris guy).

I'm not saying design is _the_ answer, but all the best tools have been co-created with a visual/ mechanical/ industrial/ designer of some kind.
Actually a middle ground would be better - Apple could have said something like - Hey we think x and y look not so good in your app. This might increase the chances of it not being featured or worse result in less sales due to first impression. We suggest you do this and that, but if you don't feel like it, click here to publish it <As Beta | Regular> anyways.

Outright rejection for subjective stuff is just nonsense.

< This whole thing reminds me of the various labels (Your drink is very hot - well duh, I just ordered it!) on things sold to you in the USA which I found very amusing when I first landed! Apple is taking similar approach with their customers whereas Google relies on its customers being somewhat competent and responsible.>
Apple is a part of the market.
The name of the conference/group is Bilderberg, not Builderberg.
A Chromebook Pixel is. It's doable if you are ok with command-line and building/deploying to a device using gradle.

Admittedly there are few on the market.
The problem is that creating the account makes at least some small bit of my personal info public which I might really not want to happen.
With the amount of supporting and abstracting classes supporting the wrapped ones, of grunt work done already, it sure as hell is high level. Visual Programming is not a paradigm like functional or declarative. In this case though, it offers separation of presentation and implementation, if that makes any sense. I never quite grogged that idiom.

This isn't exactly ment for Programmers, but level designers going one step further. Besides that, it offers accessibility that is very immediate. The visuals can provide a direct feedback of the signals processed (may the movement in the background not be random), relating the properties of the signal to other signs than textual symbols (e.g. to show a color's hue just dye the slider).
Some sites say it's 1K resolution per eye. Which is roughly the same as DK2's 960 x 1080 per eye resolution.
I suspect what is driving your question is that you're mystified how you can be paid to produce work which isn't meeting some need, or being tangibly important in some way. If you're working on stuff which never reaches production or is immediately retired or restarted then it probably seems to you like a bad way to run a business.

I can sympathize. I worked for a bank in a role doing tasks which, to me, clearly did not meaningful add to the companies bottom line. In my estimation, my (and my department's) existence was a drag on the bottom line. I constantly found myself amazed that the company spent so much money in inefficient counterproductive ways. So I wasn't honestly all that surprised when my department was wiped out last week and I was laid off.

I think ultimately you're right: when it's all vapor then there will likely come a day or reckoning. But you never know how soon they day will come. Maybe it's a proactive restructuring of the company and they downsize and cut because they realize the error of their ways (and pivot to producing more value), or maybe it happens when the economy tanks and money gets tight.

I think you'd just be smart to continue to diversify your options however long you work in your current position. Play your cards in such a way that if you ever wanted to leave or had to leave, you would be able to frictionlessly pivot to something else. If you can do that then I say don't sweat making a buck off your employer's vapor production. When and if the gravy train comes to a halt, you'll be ready to do other things.

On the other hand, if you're not happy in your job--i.e., if you don't like your work, your colleagues, the environment, or your boss then consider staying there just long enough to make it legit (probably about a year) and then go looking for something else.

Good luck!
Never heard of this until now. The last release was 5 years ago in 2009. Anyone have actual experience with it they can share with us? I'm keen to hear HN'ers thoughts and/or opinions.

The "who uses it" page lists organizations and sites purported to use it [0], though I can't say I recognize or use any of the listed sites.

[0] http://swish-e.org/who.html
Just a note about a likely typo, only worth commenting on because it changes the meaning quite a bit:

> The beautiful thing about an open policy like the Google Play store is that you can not just get actual customer (Apple reviewers are probably not your customers) feedback and actually REACT to the feedback by uploading a new version right away... [emphasis added]

I'm guessing you probably meant it without that not, is that right?

> The beautiful thing about an open policy like the Google Play store is that you can just get actual customer (Apple reviewers are probably not your customers) feedback and actually REACT to the feedback by uploading a new version right away...
The DK2 experience is pretty phenomenal, if you ask me, but if you buy one you should know that it's definitely still not a plug-and-play affair to get anything substantial working, and real long term experiences are still thin on the ground (HL2 and Minecrift are the better ones right now if you ask me).

I have a DK2 for experimenting and some light dev work (I don't plan on releasing anything; I just wanted to toy with VR dev) and I think it was worth it for that, but those are just some things to keep in mind.
I've always wondered what happened to apprenticeships, like they used to be where they were focused more on learning a particular skill. It seems like a far more logical way to develop skills; schools are relatively hands off, you spend alot of time learning on your own, on the job people are often too busy to give you instructions (of course this is a generalization, but still, still profit is the goal). This may be somewhat off-topic, but I always thought the idea of apprenticeships was neat.
Trend Piece
I'm a little sad that neither article (I've read some more beside the ones linked there) about mentions that the idea of logging here and processing there is pretty much the Unix principle of each program handling text (mostly lines of colon/comma separated data records) as input and creating another stream of text as output. Also I don't know if the idea of a central data storage (which is Krep's suggestion as far as I can understand) is really the solution to all our problems in a time of distributed everything.
As someone who is more engineer than designer and can recognize good/great design, but cannot necessarily produce one myself, I feel that this type of feedback is great. If I look at a design or user interface interaction and say "I could had done that," I feel that it isn't that good. Higher standards will push you to better results
I can't really imagine a story with a properly Friendly AI that would actually be a good story and not boring. A story generally needs some tension, conflict and resolution, and a Friendly AI story (other than about its emergence despite resistance from humanity) wouldn't have it.

That being said, maybe "Friendship is optimal" fanfic (http://www.fimfiction.net/story/62074/friendship-is-optimal) is something that you have in mind, as it does have a properly friendly AI. I'm not just sure if it's a good enough story, for the reasons I stated above.
Need Postgresql HTTP API Extension
I used this in the 90s, it's been around almost as long as the web http://swish-e.org/docs/readme.html#swish_e_s_history
First Hands-on: Oculus Rift Crescent Bay Is Incredible
OTOH, software that has no bugs in need of fixing is usually not a realistic goal.

You can say it will probably never be done, or you update your definition of "done" to "it has no bugs stopping a release". Personally I prefer the latter.