skysight-inc/HackerNews huggingface dataset:
A link to another video of the same level. This one, however, adds 6 + 6 to get 12, which (in the final scene), shows how the digital numbers are created (timing flying bomb-ombs exploding near ice blocks).

OP's video shows 4 + 4 = 8, in which none of the ice blocks need to be removed, so kind of magical when you're seeing it the first time and wondering how those blocks got there.

https://www.youtube.com/watch?v=rCTGXUNg2fE&feature=youtu.be
I believe most of what it's doing under the hood is explained in the article. Sorry if it isn't 100% clear.

Short version:

- A provider has its own store (or it can share a store with other providers if you need it to).

- When you have a `propType` matching a provider's `actions`, those actions are automatically mapped to the store's dispatcher; so when you call `this.props.someAction`, it's essentially calling `provider.store.dispatch(provider.actions.someAction())`.

- And when you have a `propType` matching a provider's `reducers`, that component will always have the latest state of that reducer.

Without the `@provide` decorator, you would just `export default provide(SomeComponent)`. I've opted to use the ES7 decorator because it's cleaner, more concise, and immediately apparent.
The Poetterisation of GNU/Linux (2013)
Also, plain old data interfaces are very desirable. They decrease coupling. Get the data off the interface and restructure it (renaming, preprocessing...) in a suitable way before implementing the actual functionality. This decrease in coupling makes representation changes in the interface more practiceable.

Of course sometimes stateful (procedural) interfaces are a must, but it's surprising how many painful OOP classes can be replaced with a "const struct foo" interface with a clear meaning to the data in it.
I think this is the article you're referencing: http://www.nytimes.com/interactive/2015/05/03/upshot/the-bes...
Perchance to Scheme: A field guide to the menagerie of Scheme dialects
FYI, unary operators and C-style for loops have been depreciated in Swift.
Presumably it's to the point that both of them are satisfied that the answer is established one way or another. I'm pretty sure Kip Thorne and Stephen Hawking are both acutely aware that all their questions do not necessarily have binary answers.
Could be but this study correlates with many other studies, some of which have factual data. e.g. things like teenage pregnancies are well-studied and can be observed without relying on self-reported data, and they indeed have gotten much better. Smoking is another one which has gotten much better.

On the whole it seems quite reliable, although some stats are not very meaningfuk. e.g. watching TV is a bit of a silly stat if you ask me, kids have just moved from traditional TV but they're probably 'wasting' as much time on media entertainment as before through other channels.
Saxon-Node: Modern XSLT, XQuery and XPath in Node.js
> re2c is probably just as fast in practice, i'd imagine.

Probably, but re2c requires every pattern to be run through a C compiler. Not useful if you want to use it as the embedded regex engine inside a language interpreter.

Also recent iterations of Intel processors contain specialized string-scanning instructions -- I would love to see engines that can take advantage of these. It would be hard for C compilers to recognize these patterns, I think, without explicit use of intrinsics: http://blog.reverberate.org/2009/07/gazelle-is-going-to-love...
I'm not sure what the subsidies story looks like for rooftop solar vs grid solar, so I'm not sure if that is distorting the distribution atm.

In some places the cost of maintaining a distribution network may be higher than maintaining a distributed installation/maintenance network (eg Hawaii seems about right), but I don't see that being the case in urban areas.

So I feel like it's more likely that (well run) utilities will pick up solar+storage when it becomes cost competitive, and prices should fall, causing the "savings" obtained from rooftop solar to disappear.

Particularly, if storage tech does fall as this article predicts, I don't see why it wouldn't just replace peaker plants directly.
Sometimes cleaning up code has positive business ramifications - for example, I took the time to design a component carefully in the past few weeks for work, and when it came to start a new user story for a nearly identical feature for another view, the careful cleaned up design carried over seamlessly & got finished in about a day of work. This will be assuredly reused again for another feature with nearly identical logic/models, and thus saved the company almost 2x the time of development.

Sometimes you just have to argue for the effort being expended, and my managers all had the foresight to push for doing it right when it had large ramifications.
My personal take on it is "boardroom meddling".

Rather than allow the share price to slump some and their CEO to put his long term play in to action, the board ousted him and brought in a short term sock puppet. And he was given one objective, goose the share price.

You will find this behavior up and down the tech world.

Take a look at HP for example. They went through 3 CEOs in nearly as many years. From that we have an aborted attempt at getting into the mobile business with WebOS as just one example.

Hell, consider what Dell said after buying back his namesake company. That now they were free to pursue less profitable long term goals.
Thanks, happy to have found out about this, bookmarked. Though, I'd like to be able to stay on the website of the content provider, and be able to get a PDF of the page, as I archive some articles I read. It's not clear if this service provides these, I'll try to see if it does.
But only if the cost was very low. Right now this kind of product exists but is way too much for most men: https://www.realdoll.com [NSFW]

Personally, I would not be interested unless the robot was indistinguishable from a real human.
I don't believe this is actually measurable. Any claims about time saved or lost are merely guesses, especially in aggregate for a large project.
Weboob 1.1 app coll able to interact web, without requiring user to open the bro
It's a question about the right to self-determination, which is not technical or confusing. It expands and enshrines the right of corporate attorneys to take countries to court and modify their laws to suit corporate interests. If the people of the US want to pass a law, should the constitution and government of the US decide if it sticks? Or a group of corporate lawyers at a multinational corporation in a third party business-friendly kangaroo court? If your answer is the first one, then the TPP is morally unacceptable, full stop, no more discussion needed.
Ah, I recognize these from Depth (http://www.depthgame.com/guide/?command=diver). Didn't know they were real-life firearms.
DestructHub: We want collaborators and people who loves challenges
The proposal of organization is a dump of each solution of common and bizarre challenges presents in programming world. Why? Because is fun, because is usefull for learning and we can learn with other people! Now we can be small, about one year old and we have about 20 members.

We want more polyglot programmers possible. Actually we have solutions in Python, C, C++, Go, Haskell, Elixir, Lua, Clojure and Common Lisp!

If you're interested, you can send a email to me: ryukinix@mail.com

You love math? We love too! Actually we focusing on Project Euler since the creation! We have almost 100 solutions (counting the alternative solutions on all programming languages)!

Join to us and enters on the sea of destruction!
It's interesting to see the Apple aesthetic of abstracting and hiding things from the user in general is many decades old and was there since the beginning. No command line, paths, or even a simple debugger is present. (Compare MS-DOS' DEBUG and EDLIN, which were included in version 1.0.)

Apple's way is inherently more idiot-proof, but makes a sharper division between developers and users. PC magazines in the late 80s and early 90s had articles consisting of short assembly-language programs the user could create with DEBUG, and I think in general it encouraged somewhat more open culture of tinkering and learning with their machines than Apple's philosophy of opaqueness.

It wasn't anything like the walled gardens of today, but I remember the effort required to even get started writing applications (or just modifying existing ones) on the Mac was significantly higher than the PC.
A combination of tuning the runtime heap size, number of threads and compiling with -threaded made the same implementation run in 0.5s for me.
I read it about a year ago and thought it was excellent, and definitely the kind of thing an HN reader would enjoy. It has a point of view that's a little hagiographic but whatever, that's easy enough to get over. Michael Lewis is so technically skilled as a nonfiction writer that it's always fun to read him.
He's actually incorrect about the "Set Startup" option being removed. The author claims it was not replaced by "startup items" in the system folder but that is another thing entirely.
The references are a nice touch.

http://www.rfc-editor.org/rfc/rfc2822.txt

https://www.ietf.org/rfc/rfc2821.txt
The long way to Growth Marketing
Yeah, sometimes even though it works from a functional stand point, you can say it 'isn't working' and still be honest to yourself, since the messy code won't work in terms of long-term maintainability.
Tech Against Humanity
Growth marketing is the next evolutionary step for marketing. We have come a long way from peddling our wares on markets, to building giant billboards, to online marketing, to what some of us now call growth marketing. While using the tactics from any time in marketing history, the strategy has changed significantly. This new level of marketing isn't satisfied anymore with just acquiring new users all day long as cheap as possible. Growth marketing owns the user flow throughout its lifecycle. The acquisition is now step 1 of the marketing process, followed by concerns about user activation, retention, referrals, and revenue (thx Dave McClure for the AARRR metrics). Rigorous experimentation is its new methodology.

Persistent evolutionary change only happens by necessity dictated by the environment. The environmental change for founders and marketers these days are an insanely fast-changing world, the ability to adapt much quicker and to get deeper insights into the user flow within the own product or service. We have seen the adaptation in the world of software development to these changes in the form of agile development and Eric Ries' "build, measure, learn cycles". But where is the change in the marketing world?

Marketing has become a bad word in the minds of today's creators, the engineers and developers that spearhead most startup. I get it .. to a degree. Coding a product feels like the ability to read and write a book. Now imagine you would have to work with a bunch of illiterates on writing a book. Add to that the pervasive beliefs of "it all about building an excellent product", "the product is the best marketing" and "Facebook didn't do any marketing". These beliefs are based on the old school model of top-of-the-funnel marketing. Those excellent products are often created with integrated growth strategies in mind, by teams that are aware of the importance of user flow from acquisition to activation, retention, referrals, and revenue.
> Nowadays, a full system folder easily tops 100 megs, and can easily have over a thousand items in it. A thousand! That's a far cry from the six that made up the original system folder.

And now, on El Capitan, I've got a /System that's 8 GB, with just over 296,000 items in it. And that's not even the whole OS these days, since there's the unix-y stuff in /, a few bits and pieces in /Library, and some more stuff that ships with the OS in /Applications.

Makes for an interesting contrast.
How to brick an iPhone by changing the time
From the government's point of view, lowering the degree to which people are upset about what the government is doing is a feature of the education system, not a bug.
The point is to sell Swift. In the C++ example, he didn't cast each integer to int64, but he manufactured a reason to do it in Go and Swift. Perhaps this means that Swift's compiler optimizes that particular case almost as good as Go's. It doesn't matter much because it's a single threaded useless benchmark. It's the kind of thing that can change with a new Go or Swift release. As you know better than I, Go slowed down a small amount when the recent GC optimizations were done. Is that a reason to use Go less? No. The GC is quite amazing (and there is HTTP2 support).

In general, why do I care if there are slight variations in the speed of a for loop? The bottleneck in any app is the database or network access. Maintenance and readability matter to me a lot more than minuscule variations in speed.

As someone who programs in Go and Swift, I can tell you that Swift has some things Go doesn't. For one, it has generics. Even still, I would likely never use it over Go on any code that runs on a server. This is due to readability and the Go standard library. I would still choose Swift over Go for iOS development. This is due to how the iOS stack is premised on object inheritance.
Context: Lennart Poettering is the systemd guy.

https://en.wikipedia.org/wiki/Lennart_Poettering
And Java has async network IO. Single threaded example from article would be fairly simple to implement with Grizzly or Netty.
In my comment I support domain knowledge experts.

In my comment I purposely mentioned erlang because to implement algorithmic efficiency you must have domain expertise.

"I don't know erlang that well but I'll be damned if I don't spend the time to find out how to properly do M:N with efficient tail recursion."

Tail recursion is an efficiency, doing it right in erlang requires domain expertise.

Building new features and adding value is business. Someone with domain knowledge in any of the langs will be able to implement those business values in the best possible way.

If your business is built with shitty coders doing shitty things you will eventually find yourself in hot shit. Even if it takes 5 years. What comes around goes around.

I would take the domain knowledge developer over any monkey anytime. That's your 10x developer. That's who built all that awesome open source stuff you use all day. Not the business feature value guy.

He builds businesses that fail 99% of the time. That other guy building that obscure Lang which turns out useful for that niche topic (I.e concurrency) lives on even in concept to build or inspire other langs/ers.

You see, that domain expert knows to pick the right algorithm for the right job.

He knows the right Lang for the right job.

Even if that job is only business value.

Long live domain knowledge experts and those who wish to attain it.
The first thing that comes to mind is Joel's Five Worlds

http://www.joelonsoftware.com/articles/FiveWorlds.html

not all software dev is the same.

Coming from games, every project I've been on was an original title. That meant it was 100% up to the team to decide the scope of the game. Most teams (not all) guess how much they can get done and don't plan for cutting features. "We're going to have 12 characters, 30 levels, 10 power ups, 45 enemies, 600 puzzles, online multiplayer, and IAP for 500 items". And then they just start making it. They run into 2 big problems.

1) They don't know if the game will be fun until they're 50-60% in. If they guessed wrong they're off schedule

2) They're attached to the vision and unwilling to cut stuff.

My point though is this doesn't fit "we didn't start early enough" IMO. They knew how much time they had. No one was/is dicating too much work. They can cut the scope at any time. But they rarely do.

There are solutions. 1 is to prototype with a small team. Unfortunately most teams can't do that as they'd have 90% of their staff doing nothing. Larger companies can do this or maybe if they switched to the Hollywood model, no employees only contractors, they could do it.

2 is to design so things can be cut and to check the schedule and start cutting. This one is hard for most teams because they see the game they imagined in their minds and it's not the game with stuff cut. Players though don't know what that vision is and so won't missed the cut features because they aren't aware of them.
This solves the problem of inflating the Blockchain, now a user can have multiple offline transactions and have it count as only 1 when everything is settled. Anyone else think Micropayments in Bitcoin will be it's killer app?
The goroutine is actually in a separate concurrently executing computation. The "go skynet()" call from the Go example is a real concurrent call that will block on the "c <- xyz" lines and resume execution when a reader consumes the value. Calling Future.successful is not the same thing.
Some embedded software gets pretty close to that.
Well I guess I have to disable automatic time updates to avoid an NTP issue...
Why was the Consistent Instruction Sizes entry not posted but this one was? This entry appears to be yet another way to achieve it.

Maybe I am wrong, but if all instruction sizes were the same I could imagine disassembling by simply parsing hexdumps of binaries.
Not us :)
A chain is only as strong as its weakest link. The strength of all other links is irrelevant.

A better measure for a deal like this is the geometric mean of its components. If one component is zero, the entire deal is worth zero, but otherwise each component contributes to the aggregate value of the deal.
Antonin Scalia, civil libertarian?
> "But it adds some checks and GC, so Swift also exhibits a serious slowdown, though well within 2x of C++."

Swift does not employ GC, it uses ARC. While that may be a form of GC, it doesn't suffer from the same "slowdown" that GC would in this context because ARC is doing exactly what your base case (C++) does at run-time (ARC is a compile-time tool).

I think if you're going to be doing benchmarks, you should have basic knowledge on how each system works first.
Hack Academy Fr
because it's more like you get home to find the salesman has let himself into your house
That's one way of looking at it. Smartphones are portable computers! is another way. The portability and usability changes everything.
Show HN: ProductMonth.com – One cool product, every month
We donate 10% of our net profit.
We accept cryptocurrencies.
Hopefully this will fare better than my previous startup :P

https://productmonth.com
Can we download only single articles, or can we download the whole 40M+ collection?
dupe: https://news.ycombinator.com/item?id=11079781
I'm not the author no.
Anyone have any guesses on what the 21 team will release as a product for consumers?

The best theory I've heard is a charger that mines BTC for you when it's done charging your phone for the night.
This has no external data so workers may avoid a cache fetch let alone having enough data for regular cache misses. Even a simple strlen call in each worker could begin to add the kind of issues that affect meaningful performance.

How a language handles misses/blocking/threading is more important than what it can do in a perfect cpu only world.
Funny you mention monolithic code. The post expressed a very important thought:

> we’re trying keep the parts that change frequently, away from the parts that are relatively static

Modularization and good code contracts help "sequester" code parts with different rates of change.

And this is my guiding hunch when I am splitting up code and deciding on module surfaces: how confident are we in the subject matter that given code describes? This does not replace actual proper concept modeling, but it is an intuitive feel for helping future iterations go smoothly.
I hereby define 1 megawatt to equal 7^7 watts, because I find that more convenient. Any light bulbs not sold in base 7 units are part of a conspiracy by light bulb manufacturers.
https://news.ycombinator.com/item?id=11079781
> I don't own a smartphone, because it's a consumption device rather than both consumption and production, is just silly. So is a photoalbum, so is a book, so is a TV, so is a music player. A smartphone is all in one

A palmtop computer (I insist on this more accurate name) is even more than you say. It's something that you use to run arbitrary programs.

Now I have a couple questions: why can't I tether my computer to a docking station with a big screen, a keyboard, and a mouse? Laptops can do that, why not palmtops? Why do I have to use a separate desktop computer to develops software for my palmtop? Why so many palmtop computers don't even let me have root access? Aren't they supposed to be mine? Why can't I use my computer as a freaking computer?

Because my computer fits in the palm of my hand? Because my computer can talk to the phone network? Because my computer has a camera and a GPS sensor attached?

The only way this is not utterly ridiculous is because we fail to call those devices properly. No one would ever restrict your "computer" thus (Just imagine Microsoft trying to enforce a "Windows store" in 2005). But a "smartphone"? Sure!
Did you have a chance to compare it to Apple II? My memory is fuzzy already but I vaguely remember it to be significantly more open?
Most Americans want tariffs. We've seen what removing protectionism and globalizing the economy has done: things are great for American elites and corporate interests, and American workers have been thrown in the dumpster. "Removing tariffs" is a negative, not a positive aspect of a law for most Americans at this point.

And the fact that it is up-or-down without our input makes me more inclined to simply say no. If you don't want my input but you want me to agree, you had better tailor-make your proposition with my interests in mind.

"This deal or nothing" is an easy choice much like a bully saying "my way or the highway" -- the highway is fine, thank you.
Location: SF Bay Area, CA

Remote: No

Willing to relocate: Yes

Technologies: Web Dev, specializing in Full-Stack JavaScript.
//
FE - HTML/CSS, Vanilla JS, Angular, React, Backbone, etc. | BE - Node/Express, NoSQL/SQL databases, RESTful APIs.

Resume/CV: https://www.dropbox.com/s/y9g3y1hsaln4k98/AbelWangResume.pdf...

Email: alsoabel@gmail.com

============================================

I'm Full-Stack, specializing in full-stack JavaScript. I am strong in both vanilla JS and MVC frameworks, having built webapps with jQuery, Angular, Backbone, and React/Redux. I am equally comfortable in the backend, strong with Node/Express but have enough experience with Python and Ruby to pick up Django or Rails quickly.
Same as Haskell and IO, really. Every interesting language has side-effects, Haskell just forces you to be explicit about where you're using them.
What is Open Recursion? (2013)
As developers shouldn't we view it as a smart phone problem? When trying to reach Poitras and Greenwald Snowden turned to a technical solution, encryption, for what is a government problem, spying on private communications. Using a VPN to bypass the Great Firewall is certainly easier than tearing it down. A VPN isn't a permanent solution, you can see we play a cat and mouse game with the GFW, but we should use our talents in the most effective way possible. Whether or not developing technical solutions to government problems is the best use of our skills I do not know.
When computers first became a thing, that's what people thought of them as. Many did not see their potential outside of raw number crunching. ordinary's position, which I share, is that the "smartphones are just portable computers" sentiment is repeating this mistake.