skysight-inc/HackerNews huggingface dataset:
What I'm thinking of are a subset of your first thing: powerful task-specific interfaces that act somewhat like DSLs, but usually come with a sophisticated GUI. Some examples: Excel, Photoshop, AutoCAD, Ableton. I think (and hope) these sorts of solutions will proliferate and a bunch of good ones could make a major dent in the world's need for people who program professionally.

I think the "we won't be automated away until REAL AI happens" thing is a trap. Certainly it's true that there will be some programmers working professionally until that point, but I see no reason to expect that it will be a huge number.

I wish I could agree with you more that "learning to code is just learning to be very precise with your instructions". I'm sure there are some programs that stress that, but most of the things I see (especially those targeted at adults) are more focused on the minutia of how we actually write professional software in 2015, because they are targeting job re-training rather than the acquisition of a skill that is broadly useful.

In summary, I'm just not convinced that "learning to code could be a useful insurance policy" is the right message to be sending. Maybe I'd be on board with something more like, "learning to code is probably better than the alternatives", but that leads me to think that we could use some more alternatives.
Kind of interesting premise but the article doesn't really take it anywhere.

"Food used to spoil in refrigerated containers but now it doesn't because of science." OK, but there's almost no elaboration about what was changed. "They pack things differently and cool from below" seems a somewhat inadequate payoff.
Probably because I can't illustrate!
Feeding good illustrations like this through my tool should produce equally good results.
Nice injection of the word 'required' there...
I mean, we could live fine without them.

I forgot all the advances in agriculture, which is arguably more important...
The lovers, while possibly blinded, are at least interested in the details.
Searching the page for "Chrome" returns 3 results. One is a namespace's name, another is part of a URL, and the third is a short mention of a planned feature for Chrome.

While I was technically wrong, I think my point stands.
Not everyone has a TV in the bedroom already.
I suspect 3D touch will cause more cases of iPhone induced tennis elbow. Matt Bonner (San Antonio Spurs) and I are two victims. Forcing us to press harder will trigger more cases.
You can start with my security framework that lets you see all the risk in modern systems along with many techniques for addressing it in development process:

http://pastebin.com/y3PufJ0V

The stuff on the bottom, esp hardware, usually need either faster hardware or extra hardware to isolate functions on dedicated chips/boards. Except in most brilliant designs, the more things you counter the more chips or energy you must use.

An example is a VPN where you have one node for trusted side (Red), one for crypto component, and one for untrusted side (Black). This is called Red-Black separation: used by many high-assurance, crypto devices. Having a node/chip/board each lets you make separation work to your advantage. The Red and Black nodes will each handle transport, input validation, conversion from complicated (i.e. standard) interfaces to simpler ones (esp non-DMA), and administration to a degree. The crypto node, running state machines for just security part, can be built on all kinds of hardware, have minimal onboard software, and use about as much security as you like. Such a combo of physical isolation, interface protection, and implementation simplicity lets you have confidence that even strongest attackers hitting Black node won't steal data from Red. That's three pieces of hardware at a minimum with more if you isolate crypto node's logical functions (esp I/O).

Another angle comes from an approach I advocate against nation-states called Security through Diversity. The risk is that markets converge on a small number of hardware, peripherals, OS's, etc. Nation-state resources are large & necessary targets are small. High odds of 0-day development. Also, increasing worries that modern stuff might be subverted by NSA, China, Russia, etc. Easiest way of dealing with this is to diversify one's hardware (even processor types) and use portable software that cares not what it runs on. Plus lots of randomization and obfuscation. All this makes the job of getting from known software issue to working, stealth exploit harder. The best hardware choices are all old hardware or embedded which takes more hardware (i.e. servers, boards) to equal modern performance. Will use more space and energy.

Combining these two models will certainly use more space and energy. Plus, a lesson established by criminals and spooks alike is to treat all the equipment as disposable: constantly changing it. Sure someone might use it if you erase it and drop it off at a pawn shop, etc. The trend still causes more hardware manufacturing and waste, though.

So, there's a few ways that security against High Strength Attackers trades against the environment. There's some tradeoffs that can be made with MCU's/CPU's on low-power process nodes but development costs are prohibitive. New projects will likely combine existing ASIC's onto boards with redundant, power-using components. That power usage itself is a security hole (eg side channel attacks) guarantees this.
The docs say you use something called "TVML" to lay out the UI, and inside the TVML you can have JS. I think.
A large software project is about communication more than anything else. Inside a company, a large codebase is often extremely hard to navigate. There will be different coding styles, redundant library usage, outdated comments, obsolete / unused code, code written by people who left long ago, ugly workarounds for OS / api bugs that may no longer exist.

You may find pieces of beautiful code written by enthusiastic new employees next to files written by jaded, checked-out veterans ready to move on. Coffee-fueled bug fixes checked in right after the tests passed, to be documented later (never). There may not be a person in the organization who knows how to fully build and deploy an entire codebase from scratch.

You'd think this only happens at "bad" companies, but any company that grew fast and became hugely successful will have lingering technical debt, some of which does not need to be paid.

If you want to experience this, pick a relatively unpopular and large codebase open sourced by some company and try to understand it. Imagine someone had just asked you to add a new feature with an arbitrary deadline. Now realize that this code is probably much better than a comparable closed-source system, after all the company wasn't embarrassed about sharing it with the world.
I'd rather have both. Are there a fundamental laws of physics that we're hitting with battery thickness and/or component efficiency? If not, I'd rather people keep chugging away on the engineering problem, supported by my willingness to pay them for any progress they make.
Yeah but it's not a 1:1.

i.e. a 50% smaller screen doesn't use 50% less battery for the screen, let alone cut 50% battery.

For one, part of the screen is powered by a controller that's pretty similar whether it's a 4 inch or 5 inch screen. So if you cut the screen in half, you save maybe 40% battery going towards powering the screen.

But then the screen is only a fraction of the power usage, let's call it half. So cutting the screen in half drops battery usage not by 40%, but 20%. And then the screen is off half of the time while the phone is still using battery, which is why it's even lower than that.

So half as big a screen might reduce total battery usage of the phone by say 20-30% tops. And that's without taking into account that a big chunk of a phone's internals are going to be non-battery (e.g. flash storage, cpu, ram) which don't get bigger (or at least anywhere near 2x as big) if the screen is twice as big, and so the battery-to-volume ratio on a bigger phone is bigger than on a smaller phone.

In short, while yes obviously smaller phones have smaller screens that use less energy, overall bigger phones have better battery life because they have comparatively bigger batteries.

As for tablets vs phones comparison, it's an apples/oranges comparison as they do different things but, no way.

If you want to make the comparison, top iPad has a 42 watthour battery, iPhone 6 has 6.9. About 6x battery difference, despite the fact the 9.7 inch vs a 4.7 inch screen. That iPad has 3x as many pixels to power but 6x the battery to do it.

But again, it's apples/oranges.

Compare the iPhone 6 to iPhone 6 Plus. According to you the reason tablets get worse battery life is because they're bigger and have bigger screens, which are the main battery sink. So the 6 Plus should have worse battery life, according to you under the same principle.

But it's wrong, the iPhone 6 Plus has 60% more watthours of battery, despite being 32% bigger. And if you look at Apple's references (usually pretty good), they rate for the Plus vs the standard iphone: 10 hours more talk time, 34 hours more standby, 2 hours more internet time on 3G or LTE, 1 hour more on wifi, 3 hours more video playback and 30 hours more audio playback. Note the video (where the screen is one of the biggest battery sinks you can imagine), it's got a battery lifetime of 27% more despite a 32% bigger phone, for all the above mentioned reasons that a percentage increase in screen size has a somewhat larger percentage increase in extra battery volume.

So I'd say that the notion that bigger phones have better battery life, in general, is true. And when choosing the plus version on the iPhone, the battery life is a benefit. While choosing say the mini version on android phones (even as they're often underpowered, such as the Galaxy S mini series), tends to diminish battery life.
Most of the times cloudflare is fine, they've gotten a lot better over the years.

However we have found random areas to temporarily go down for random periods of times. You will not be able to see these downtimes if you are only checking from 1 location.
Node Machine – An open standard for Node.js modules
The 10 most important things from Apple's iPhone 6S event
How so? You get AppleCare+, which is $99, and if you compare that with AT&T, it's cheaper per month, unless I'm missing something. It's also unlocked so you can freely switch carriers.

I think there's a lot of people that will be enticed with this.
And that's exactly what's wrong with all the syntactic-sugar-based language marketing. "Write your code using X, and you go from 10 ugly lines of C++ down to 3 beautiful (if syntactically weird) lines of X!"

Great. Now tell me how X scales on a 200,000 line project.

One of the places people make this mistake is with Go. Go isn't designed to make your 2,000-line project shorter or easier. It's designed to make Google's 20,000,000-line projects maintainable for a couple of decades.
This is neat but kinda useless without some written analysis. I am not a crypto expert so the graphs mean little to me.
I'm not suggesting people should take videos instead of photos. It was just ridiculous the way they trotted it out as a brand new and of course revolutionary idea, considering it has been done before and also is just video taken simultaneously with stills, something camcorders have done for a decade.
"If congestion pricing were implemented, employers would have to be more flexible or pay their workers more. "

That will never, ever fucking happen. Employers don't give a shit.

"Congestion pricing isn't regressive since it's easy to split the cost."

That has absolutely nothing to do with it being regressive. It's regressive because it disproportionately affects poor people.
That's already a thing on Amazon's Kindle + FireTV, for us it's really only useful occasionally moving my daughter to a tablet so we can use the tv.
They are also mostly over.
I've found LaTeX pretty practical. Not quite as easy as handwriting, but practical enough. Once I got enough practice I have access to the documents everywhere, don't have to worry about my horrible handwriting, and can copy-paste equations into Wolfram Alpha to check correctness. An editor with customizable key commands helps too. Took me about two months to get fast enough, but now I use LaTeX for basically all note taking and homework.
It's the first time we get a new interaction idiom since 2007 really. I think it will bring great changes and improvements to mobile app UIs. Adaption gonna take a while though, 2-3 years for it to be considered standard on iOS, another 1-2 years on Android, I'd guess. Also given it's from Apple the implementation will probably be rather solid.
How would you fit an efficient antenna for pertinent and desired LTE frequencies bands in a frame too small to hold such an antenna? The speed of light is the speed of light, and so wavelengths of set frequencies are themselves set, and constrain the physical dimensions, no?
I called a spade a spade. Their comment was nothing but how they were entitled to stuff.
No evidence that it makes any difference compared to uBlock Origin on desktop.
Using HTML to learn ClojureScript
If I were to try to give a complete answer, I'd probably spend fifteen minutes googling "Ensure vs Soylent" - there are some good matches there through discussion boards that analyze the ingredient breakdowns, also some replies from the soylent people too. Ensure is definitely more expensive in those analyses, and that's from before soylent's recent price drop. Beyond that, it appears to be a rather different ingredient list - looks like Ensure doesn't have much in the way of fiber, has more sugar, etc.
Why does every Soylent news story come along with the requisite 'Soylent doesn't make sense to me so it can't make sense for anyone' post? Stop for a moment and remember that everyone's lives, finances, schedules, priorities, etc are different.

I use Soylent 1.5 along with my girlfriend. It's a faster, easier, and less expensive way to have breakfast (and sometimes lunch) each day. It's especially handy when funds are tight. It's easier to prepare and far easier to track calories for those of us shedding a few pounds. And it's more complete nutrient-wise than what the majority of Americans ate for breakfast.

I don't do it so I can work more 16 hour days changing the world at Hooli. I do it so I can enjoy my life more. It helps me have the funds and the time to relax and enjoy the meals I do prepare or go out for with friends.
The bidding system on online auction sites like ebay has always been a joke.

If an auction ends at a precise date and time, then the only thing bidding early accomplishes is driving up the price.

If someone wants to get the item for cheap, they should NEVER bid until the last second.

The whole concept is flawed compared to auctions in real life, which start with a bid price, and then drive up the price with additional bids. The auctioneer simply ends the auction when people stop bidding.

The only way to fix the sniping problem is to fix this fundamental issue with online auctions. They need to make it so that auctions can dynamically end at any point in time (for example, if the item hasn't been bid on for a set time window, or if the seller is simply tired of waiting).

Imagine if you wanted to sell an iPhone or something with this type of auction model. People would place bids up front, and they would have a fast-paced bidding war (driving up the price), followed by a slower bidding war, as they started to reach the limits of what they were willing to pay. If nobody topped the current bid during the following 24 hours, the auction automatically ends, and the highest bidder wins it. Placing a bid automatically resets the 24 hour delay (or maybe it resets it to an exponentially smaller time window to keep people from postposing an auction indefinitely).

I'm imagining a scenario where the person who creates the auction can set the auction automatic no-bid termination time window, and they could also set a true deadline (which perhaps only they would be privy to) when the auction would automatically end.

That is the only way bidding makes sense to me on online auctions. With the current system that ebay uses, sniping is the only type of auction bidding that makes sense.
Even in computers, you had the dilemma of "should I buy now, or wait a year and get the same thing for less money?" That was a standard question for many years.
Yeah, welcome to all analogies. Sometimes, they cause people to form the wrong intuitions. Hell, one can argue that Newtonian physics is itself a misleading analogy that leads to confusion, since people develop incorrect intuitions about, among other things, how time and simultaneity work.

Now, if you can come up with a better analogy, fantastic. But the best science communicators in the world haven't done any better, so I'm not holding out a lot of hope for success...
"There are those of us who do not agree with Copyright and would gladly suffer the negatives to be rid of it."

And most of these people are not people who are trying to earn a living from their works.
As a consumer of what? Because of it's not of movies, TV or games then, gee, I doubt a product aimed at movies, TV and games will have a huge effect on you.
Bitcoin's Shared Ledger Technology: Money's New Operating System
It seems like you're assuming that all games are basically either Candy Crush or MGS5. In reality, there's a lot in between, and various indie games which work well with the touch interface have actually had a fair bit of success on the iPad at rather premium price points. FTL and Papers Please, say, are arguably better on the iPad than on PC (both benefit from multitouch), and go for $10 each.

There's a lot of potential for midrange semi-casual console oriented games like Rocket League or Starwhal here, and realistically, a surprising number of consoles are used mostly for that type of game.

I think there's also some long-term potential to hit the triple-A market, particularly if the console vendors keep up their current ~7 year refresh cycle. This is obviously a lot less powerful than current-gen consoles, it triple-As are still big sellers for last-gen consoles, and the gap will close as Apple refreshes this every year or so. It's far cheaper than a console, and also smaller and presumably silent. I think it'll find a place.
Aggregation at scale is even more complicated than just the number of devices. If you want the conversation to be bidirectional over the highly NAT-driven internet, you will probably want the connection to be persistent. This means you can poll or command a device from the server as well as have your device send requests to the server. This is not directly similar to a web service model, which is based on many fast, transient connections. Latency might also be a question for you, if you have human real time users. We haven't even spoken about sensor data streaming in from millions of devices while you're trying to talk to them. Then you get into availability and redundancy and other guarantees, it gets really interesting. Did I mention security (hello, Samsung?), unless you want miners and spambots running on all your devices, you're now talking secure images and real crypto on a flyweight embedded device.

Yes, there are bigger real world issues for IoT than the protocol.
iOS doesn't run in RAM, it's only bloated OSes like Android that need RAM. /s
And make me pay another $200 for functionality that the damn thing should have had initially?
Pay it no mind. It's the "I don't understand it and it doesn't specifically work for my life so it must be wrong" mindset. I've used Soylent as you have and it frees up time and funds as well as making calorie tracking easier.
I sit about 10-12 feet away from my TV. It sounds like you need to get your vision checked.
You are right that the analogy breaks down at the assumption that humans would allow the paperclip machine to run amok; human wants do powerfully change and influence the market machine. At the same time, the abyss gazes into us, and human wants change in response to the machine as well.

I'll give an example that intersects the Pavlovian scare words of both "capitalism" and "government": the Prison-Industrial Complex. It's reasonable to want to remove members of society who are dangerously violent, or "cheaters" of sufficient scope. Yet iterate this desire over enough time, and it takes on a life of its own: politicians who want to look tough on crime, parents who want their fears assuaged, private companies who want to profit from correctional tax dollars, and most insidiously, the swaths of police, prison guards, and support staff who want paychecks, benefits and job security.

The final product is something we don't actually want: the most populous prison system in the world, which is massively expensive, socioeconomically predatory, and fails to rehabilitate most of its inmates. Yet there are enough stakeholders who do want the institution to persist for reasons of personal benefit (and enough taxpayers who want to imagine a cute moralistic story and are willing to pay for the luxury of ignorance), that a massive machine of oppression is created and sustained out of a simple, reasonable human want.

I'm not intrinsically anti-capitalist; I'm in the camp of Jaron Lanier, in that money, markets, and corporations are all technologies, and neither good nor evil. But technology should serve humans, and not the other way around; that means paying attention to the power of unchecked, autonomous feedback loops and their power to influence human behavior and our various social ecosystems.
Let's melt the whole thing!
I really dig your "we can cook" attitude, but those 500 words aren't going to get people where you think they will.

I think it's a great MVP though and with some usability testing and a little bit of software we could get there.
Nah, there's those that are cheats and those that are solid work. Here's a LISP in 500 lines of C I just found that doesn't seem to cheat:

https://gist.github.com/sanxiyn/523967

It was one of many from the link below. The Scheme in Racket example would've been even easier to specify concretely because it's so easy to implement read in a Scheme. Gets the C and C++ implementations more props for doing things directly. Real question is how small can those go?

https://news.ycombinator.com/item?id=7530427
Typo:

... planned to use HTTPS as a ranking single in ...
^^^^^^

Should be "signal".

Also, I usually instantly close any site that pops up a "Sign in for our email updates!" window before I've even looked at any content. This time I didn't, but I got very little from this article.

Does anyone else think it's interesting? If so, what have I missed?
NewVo – Fast Fashion Advice
There are two kinds of personal computing products in any era:

* Blatant copies of some Apple product

* Rough prototypes of some future Apple product
I wonder how long it'll take AstroPad (http://astropad.com) to support the Apple Pencil.

I'm an illustrator and this is definitely on my list. I am not a big fan of drawing where I'm looking any more, but Astropad + an ipad Pro will let me work in Illustrator in a cramped environment.

And maybe in a couple of years we'll finally get an Air/iPad Pro hybrid. Like the Surface, except running OSX.