skysight-inc/HackerNews huggingface dataset:
Hey thanks for the awesome thoughts on the book!

> 1. Please, please use the metric system units ... 1000mph (1,674.4km/h).

Absolutely. Will do!

> On the Sun's chapter, you drew it yellow.

Oh yes, it's actually bright intolerable white once you're outside the atmosphere. I wrote this book for my nephew and he totally loves sitting next to me when we do these creatives. So I'm gonna leave it like that for now and revisit later in the day (it's 5:30 am here in DC!) with him.

> There are too many links that forces the reader to constantly deviate from what he reads ...

I realized it midway that traversal would be more-or-less linear and then reduced the number of anchor links per page later on. I guess I'm gonna leave it on the writers to choose what's best for their book. Will come back on the look_up feature later, but thanks for sharing your insight here.

4. No love for Pluto :(

There will be love for the dwarfs very soon! :-)

=====

Meanwhile, to those who are unhappy about the idea of having books with flipping animation on the browser, here's a little note: A lot of kids, especially my nephews, love it. It might be that you are not the right audience for it, but kids really love flipping the page as it is. And they love the animations and visuals within too. There's a reason why Apple chose to have flipping behavior for iBooks - cuz otherwise it'd feel more like a slideshow. Fast/performant is another thing, but books must have a bifolia experience that flips comfortably at a soft reading pace. There is no doubt about that.

While I understand the passion with which people want to impress what should or shouldn't be on the web, but there's no point making it a turf war. There have been several occasions where exactly the same thing - i.e. books - have been appreciated by hackernews on the browser itself. By the very same people who at other times chose to batter the idea.

For example, this book on Startup School Doodles from my friend Greg Koberger was loved invariably by all of you:

https://news.ycombinator.com/item?id=8449652

So it's all a matter of context and audience.
Non-blogspam link: http://pluto.jhuapl.edu/News-Center/News-Article.php?page=20...

Just because it is the guardian does not mean it is not blogspam. They do not add enough info to the original article IMHO.
Azure has tended to be price comparable to AWS, but does offer some compelling options for storage, that I wish other providers did too.

My biggest complaint about MS/Azure is they can't seem to get single signon/off working right... Login to one account for personal email, another for work email, and another still for my personal Azure account... Sometimes gets stuck in a loop, just doesn't work, whatever... I often keep another browser, that I don't mind wiping all cookies on just to get the damned thing to work. Let alone the other day where my payment didn't go through for some reason, and my azure account was locked, as was my live account, that I had to go through a convoluted recovery process that was different because of 2fa, only then to have my email (application password) revoked... grrr.

Despite account issues, I've really liked actually working with Azure.. though I think their node tooling could use some TLC, and better documentation... wound up writing my own wrapper (azure-storage-simple) to have a cleaner interface... also wrote mssql-ng as a friendly abstraction on top of mssql.
Show HN: UX-App – Interaction and User Experience Design App
Re: "There are still a lot of people who don't own or regularly use a cell phone and others who prefer not to be reachable all the time"

Well, I'll grant you that there are still some people - but I think it's a stretch to say, a lot of people.

For example, in Singapore, it's inconceivable to not have a cell phone. Indeed, a ton of the businesses, banking, etc.. presume you have a cell phone for their two-factor authentication.
This is similar to node_modules + npm, in essence.

Having used node and npm on both small (~200 transitive deps) and large (~1000 transitive deps) projects, I think this is an approach that's conceptually not a good idea (outside of possible implementation issues with npm).

With vendoring, end up with a _very_ large tree of transitive vendor'ed dependencies. You have no idea or control over what's in it, and what versions of what packages are in it.

Nearly all of the time, the two allegedly incompatible versions of a library that you install separately turn out to be 2.0.13 and 2.0.14, and you only get two because well, somebody hasn't upgraded yet.

This might seem trivial, but in the end you have a project tree where every dependency gets installed separately for everything that depends on it, so you end up with something like O(number of deps * number of deps) installed libraries, which obviously doesn't scale.

You also end up with the versioning problem. Imagine there's an important reason to upgrade some package P, e.g. a security issue. Now you have to hunt down every single project in your transitive dependencies that depends on it, and ask them to upgrade or fork.

You also still have version issues. If you transitively depend on the same library C in versions Cv1 and Cv2, and you want to pass an object/data structure/... from Cv1 to Cv2 through some path, you open yourself up to all kinds of hilarious version mismatches and failures.

This isn't new - e.g. Eclipse/OSGi did the same thing with separated class loaders, and it was a mess.

I think flattening your dependency/vendor tree to only ever have one version of library C, and hoping/testing for minor version mismatches to work out, is the most viable thing to do.
Doesn't running in a web browser pretty much mean that?
Not to mention that it enabled them to quickly put together a good streaming service which has been highly praised so far (complaints all seem to centre on UI complexity, not the service itself). And if that didn't work out at least Beats makes enough revenue to earn back it's acquisition cost in a few years - Nest would've been a much bigger gamble.
CLASP (https://github.com/drmeister/clasp), a Common Lisp, can optionally use one of Boehm or the Memory Pool System (http://www.ravenbrook.com/project/mps).

Open Dylan (http://opendylan.org/), a Lisp-like language without Lisp-like syntax, also can use Boehm or the Memory Pool System.
> 1000mph (1,674.4km/h)

Could we all agree to use a space (or nothing) as the separator for thousands? In French culture this is read as less than 2 km/h.
Running it on GPU Amazon instances, inception_4c
To be fair, why don't you let people spend money how they want? People should have a right to be fooled if they wish so...
> the browser has no idea when you are supposed to be
> operating on a secure channel (HTTPS)

Agree about the sentiment, but there are some ways to help this. The server can for instance tell the client to always require https:

https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security

Doesn't help if the client hasn't yet connected to the right server at least once, though.
Thanks Vespasian, great to hear you're happy with GitLab.
It'd look that way, but perhaps Kickstarter incurs a penalty automatically? Or maybe it's the crappy headline which sounds clickbaity. Maybe the author should have used something solid, like "Kickstarter is promoting scam company with fake holograph".

The video they have looks like it could have cost a fair bit of coin itself. And they claim to have a CFO, CTO, and CEO, already? Their "Our Story" page [1] says they've been around a couple years and have 20 people. So a $250K campaign gets them what, another 6 weeks' runway? It's gotta be for the press value.

1: http://www.hplustech.com/our-story/
Athens capitulates to creditors
What about:

if((somevar != checkvar((byte)othervar)) & (i != 3)) somefunc();

someotherfunc();

A bit exaggerating, I agree, but not far off from some real-world examples and quite confusing.
Blatantly lying to people by showing fake products and fake badges hardly counts as "if they wish".
Deployment is hard, system administration is hard. As a software developer you think there should be one way but there can't be one way. There never will be. If you want to make good software really spend some time learning the intricacies of packaging, deployment and sysadmin life. You make a lot of people happy by just knowing the problems, even if you can't apply the correct solution to each problem.

Come from the same island as you, trust me. But the more you learn about this the more you see how complex it is. You can't even say that one solution is better than the other (like apt vs yum). Each and every one of them has their pros and cons. And more often than not architectural decisions make it impossible to get both solutions into the same system working together.

rSync is not deploying. It's syncing files. But even if you have a 1:1 copy from your development computer on a server it still might not work because on that server package xyz is still in version 1.4.3b and not 1.4.3c. Deployment is getting it there AND getting it to work together nicely and maintainable with the other things that run on that computer/vm.
I remember the guy already being a running joke on RPG Codex in 2008-2009. Glad to see they managed to eventually release the game!
Eat in a manner commensurate with your activity level. I might be lucky in this regard, but I simply don't get hungry when I'm not sufficiently active. Drinking lots of water might have something to do with that, but I'm really not sure.

Make being active a part of your daily experience: walk, run, or bike to your office. Get a gym membership nearby so you can clean up before going to work. Go back to the gym to do some lifting on your lunch breaks Mondays, Wednesdays, and Fridays. This will perk you up in the middle of the day and keep you from falling into a post-lunch food coma. After your day at the office is over, you've got another burst of activity awaiting you in order to get home.

Diversify from workout routines and take time off. Block six to ten weeks for the routine, then take a break for two weeks and try out informal, social exercise (pickup sports, dance classes). Go hiking, do yoga, or catch up on your social life in an active way, like a pub crawl or one of the boozy bicycle group tours.
Well empirically most math developed in the past turned out to be useless up until now. Are you suggesting that it will suddenly become useful in the (near) future? Are the past few centuries not enough time for you to generalize from?
You put the wheels into a git repo? That's the most sad thing I've heard today. You know that if you add a file in commit A and remove it in Commit B each and every clone still pulls in that file? It's okay for text files but it's very much not okay for binaries and packages.
Alcohol can damage the bladder and bladder control in several different ways.
Ones answer to that probably depends on where they live.
Hi, This has been my side project for a while now. I've posted lots of updates recently and would love to know what you think.

Cheers,
Eli
Nothing would change, except that there'd no longer be an Uber controlling the prices they charge and the cars they use and taking a cut. In other words, the thing that would change is that they'd actually be independent contractors with control over their own working conditions.
Dex Signals REVIEW BINARY Need to Know *THE TRUTH*
It seems to me you could use any number of solutions for something similar to DynamoDB, though Cassandra would probably be my first choice.
Samsung Galaxy A8 Spotted Testing Ahead of Launch
The church & the productivity increase brought the weekend.
> ... So teach people not to abuse them, and, those who do, or become addicted, have medical issues that should be treated as such.

Therein lies the problem: addiction does not readily yield to teaching not to abuse the drug. In the US there has been an intensive 50 year campaign to educate people not to use tobacco, yet nicotine dependence remains a top public health problem.

Addiction research has shown compulsive drug use is associated with actual alterations in brain structure and functional circuitry. Treating addictions has proven to be a notoriously difficult problem to solve, meaning prevention is a far higher priority than attempting to cure.

I believe the scientists studying the matter would disagree that rate of drug abuse would decrease solely on the basis of education, especially among the subset of the population that is most vulnerable to developing compulsive use in the first place.

Trouble is, drug response, including bad effects, is probabilistic. Exposing large populations to a drug with predictable harmful effects in a substantial subset, it's really a crap shoot who will wind up in trouble. Minimizing initial exposure to the drug may be a reasonable preventative strategy.

But don't take my word for any of it. Check out the scientific info sources for yourself, see: http://www.drugabuse.gov/

The states permitting wider use of cannabis admit it's a kind of experiment, a bet on the hypothesis that the harmful effects of it (abuse/dependence, MVAs, health problems, more child/adolescent use) will be offset by decreased burdens imposed by criminal justice systems. The jury's out on the question, we'll have to wait a few years before the verdict is in.
I still can't get over Moxie wanting Google and Apple and Microsoft to be gatekeepers of what you can and can't do with your device and calling sideloading "that old broken desktop security model".

I admire your work Moxie, but sadly we stand on different sides of war on general purpose computing. I can't help but be saddened that "the other side" got someone so talented and dedicated.
The GC won't do anything for stack allocated objects so you can still use the RAII goodness for all of those. You just don't also need to use things like `std::unique_ptr` and `std::shared_ptr` to manage heap allocated objects.
Wait until you see the artwork/more practical course work. Lead light windows, sculpture, metalwork, woodwork etc. The difference between the work that comes out of the (New Zealand) state system and the Steiner system is vastly different and (imho) Steiner students are more artistically developed. The absence of a formulaic approach is quite striking. My view is rather skewed however! The flip side is that I'm sitting here wishing I knew how to work logarithms properly.
How private equity cheats pensions
That's kind of similar to oppose the employee status because eventually employers will meet candidates who don't demand the benefits required by a legal contract. That's why that is simply illegal.
That and duct tape - corner stones of McGywerneering..:-)
While in C++, RAII is a good practice, it has it's fair share of problems you should not ignore. Debugging, profiling and unit testing are a bitch. Performance becomes completely unpredictable in more complex applications. And then error handling.... Destructors shouldn't throw exceptions - and you don't have any other choice than just catch them all and 'log and forget' - which can be seriously problematic.

Both RAII and the explicit cleanup of resources have their advantages and serious disadvantages. In C++ you better use RAII, in GC'd language, use explicit cleanup. What is better depends on the language.

> I kind of wonder if a preference for GC languages is in part responsible for the way distributed systems are typically designed these days -- namely, the emphasis on stateless servers, which avoids the need to do remote resource management (which is hard without RAII), at the expense of requiring a lot more machinery to make performant (e.g. complicated caching layers because all state changes have to hit storage which is sllloowwwwwww)

Don't wonder, they're not related at all. We have a few stateless services running that are written in C++. They are the only sane option once you start working beyond a certain scale - which is the point when you decide you need a distributed system. The reason for them being stateless is simple: nodes WILL fail. Hardware failures, power outages, line cuts, ... This is not the reason for 'more machinery'. Resource cleanup is hardly a bottleneck? RAII does this for you, but the only difference with GC'd languages is that you need to do this cleanup yourself.

There are other reasons for having to add 'more machinery' to make things performant: going for 'easy' scripting languages to get things up and running in record time - which is important for startups to have something to show for as quickly as possible. Performance at that moment takes a back-seat, and it's hard to go back. Micro-services are becoming a trend for this reason too - you can quickly write your services in <slow hipster scripting language>, get everything up & running, identify your bottlenecks and optimize them. Just look at the upcoming trend there for 'optimizing' distributed applications is to rewrite parts of your service in Go, which is a native compiled GC'd language. Easy to write, little memory overhead with decent execution speed, and designed to do concurrency well. Does it compete with C++? Not at all, but it gets things done that would be pretty damn annoying to do in C++ - and it does it with little memory and CPU overhead.

That - or going for some Java enterpricy application with tons of frameworks which eats up all your memory. Hello 32-core machine with 96Gig ram to generate some silly reports.
Sole to soul – foot tapping to a new beat
Locking the basic data structures seems like it would destroy Python's simplicity. How do you determine the scope of the per-list lock? Do you add a lock to every single data structure that you are required to grab before reading or modifying it? If you require the programmer to do it, you can easily get race conditions which will only show up once in a blue moon causing incorrect results or corruption at worst - something Python's GIL guaranteed not to happen (as long as you didn't do anything risky in your C extension). Is there any solution that doesn't use purely functional data structures?
Balloon: A drop box for your Dropbox
Native apps are planned. Here I answer some of these questions about us: https://bubbl.in/faq

I believe that it must be simple for the book writers to create, publish and sell. And probably have an extra legroom for creativity too -- using the power of the web and all that.

I have some rough ideas on where and how we'll proceed towards integration with other formats/platforms. But this is a fairly large undertaking, so I'm gonna need all the help and guidance we can get.

Note, Bubblin is FREE for the authors, a non-profit, so we need financial aid too. Read more about us here and donate if you like:

https://bubbl.in/foundation
The 5 Cs of Modern Marketing in an Era of Consumer and Convergence
Xcode 7 beta 3 fixed 38 % of all Swift crashing bugs
I'm not a big fan of RAII because it falsely conflates lifetime with reachability. This assumption breaks under a number of circumstances, e.g.:

* Closures capturing their environment and keeping local variables alive longer than intended.

* Debugging code keeping a record of objects.

In either case, you have likely failure modes in that either the resource can be deallocated prematurely and then accessed through a stale reference or that it is kept around longer than its intended lifetime.

RAII also does not provide a solution to a number of resource management scenarios, such as requiring access to an unbounded number of resources of which only a finite number can be reified at any time (e.g. due to the maximum number of file handles a process can manage). The obvious solution – a caching mechanism that will disconnect a resource from its in-memory representation upon eviction and reconnect when it is being used again – needs to attach itself to resource usage, not resource creation and destruction.

Most scenarios where RAII is being used are either trivially handled in any language that supports closures or macros, or benefit from explicit reasoning about resource lifetime, anyway.

Speaking of closures, I think it's no coincidence that RAII first arose in a language that until recently had no such concept; closures both create problems for RAII and also obviate many common use cases.
Years ago I heard Dr. Dean Edell(a U.S. Doctor, media personality, and a rational guy--whom other doctors admit to listening to-), say this,

'If I was going to be addicted to any drug--it would probally be Opioids? It does the least damage.'

I'll always remember that statement, but I think he meant in a perfect world(where you could get legal, pharmaceutical grade product)? The addicts, I know, have so many ancillary diseases, and health problems--I don't think I would ever try it--even once. (I imagine the health problems are due to dirty needles, and unknown handling, and "cutting" of the drug?)
Nah, I've had plenty of mates that have done far far less than that (a few grammes on the weekend for a while) that have totally fucked their bladders.
I was thinking primarily of older people; the odds of owning a smartphone decrease as you go into the 50+ age brackets, and cell phone ownership in general falls off as you go into 65+ (http://www.pewinternet.org/fact-sheets/mobile-technology-fac...).

That Pew page states that 10% of American adults still don't own a cell phone, but of those who do, I would expect there's a healthy percentage for whom the cell phone is infrequently used as an emergency contact system, or just-in-case for road trips, or for the occasional phone call. (They don't have numbers on usage patterns though.)

I couldn't hazard a guess at what worldwide usage looks like. I'm surprised every time I hear about the creative ways that countries I would least expect to be heavy cell phone users are using cheap cells for things like currency exchange (http://www.cnbc.com/2013/11/11/cashless-africa-kenyas-smash-...).
And there is a good chance it will change again to have compact String in OpenJDK 9, see http://openjdk.java.net/jeps/254
It's a little strange that they share their offices with an investment bank? https://www.bnymellon.com/ca/en/index.jsp#ir/offices
The dangers are real. I've known multiple recreational users come close to death from ketamine addiction, either from the effects or from general self-neglect.

The problems are threefold: firstly, it does not impair you to the extent that you cannot "live," you can still limp along through a normal life high out of your mind on ketamine every day. This means it is not self-limiting in any way, and people are not forced to change until they are seriously ill.

Secondly, the tolerance curve is very steep. If you use it just a few times in a week, the very next week you will need to consume noticeably more. It continues in a sort of hockey-stick arrangement. This is how people suddenly end up on 5g a day, destroying their urinary tract with this caustic, highly alkaline stuff.

Thirdly, some people seem to just really like it. Ketamine has a subtle psychological effect that really seems to resonate with some people. I guess this is why its connected to long term depression treatment. Unfortunately when combined with the other two factors I have listed, it becomes a trap into which people can fall for a long time. Especially the young.

It's basically halfway between marijuana and heroin. It's as destructive as that sounds.

For the record, I'm in favor of the freedom to use drugs, but ketamine is nasty stuff.
I thought Doom was developed on NextSTEP, at least wikipedia says so

https://en.wikipedia.org/wiki/Development_of_Doom

"We wrote all of DOOM and Quake's code on NeXTSTEP"

http://web.archive.org/web/20140310124554/http://rome.ro/200...
Or it might be like with skype - where according to some report (I don't have link right now, sadly) the encryption is used mostly for obfuscating the protocol and to make building alternative clients harder, but it is give so small entropy pool that it's useless for security.