skysight-inc/HackerNews huggingface dataset:
> I won't speak for anyone else, but in my experience: if you hang out with
> truly world-class climbers, occasionally getting through a 5.12 doesn't feel
> impressive at all

Yes, it's true that if you hang out with world-class climbers, 5.12 looks like a warm-up.

But it's also true that if you poll amateur climbers, being able to consistently red-point 5.12 is rare. being able to consistently on-sight 5.12 is rarer still. I think we can say that consistently climbing 5.12 is not world-class, but it is statistically rare amongst amateurs.

Both statements are compatible. We can quibble about whether "elite" means top 1%, top .1%, top .01%, &c. But in general, 5.12 is above the gym or crag duffer level, even regular gym or crag duffers.

Occasionally getting through a 5.12 isn't consistently climbing 5.12, mind you. IMO, the only ratings that count are the grades we can consistently red-point, flash, or on-sight. I can say whatever I like about this one Red Gorge 5.12c that had a couple of dynos, but I'm tall and I used to like to dyno. The truth is that the best I ever climbed was to consistently red-point 5.11 outside, with a few flashes and on-sights along the way.

Likewise, I think I have two V5s under my belt, but I absolutely never could count on sending even a V3 in one or two tries, so I really think that I climbed about V2 consistently outside, with bunches of V3s that I projected, with the memories of a few V4s and those two V5s to sustain me though my twilight years.

---

All that being said, advances in training methods and the increasing popularity of difficulty climbing and bouldering as children's sports is rapidly raising the standard of excellence.

Starting young makes as much of a difference in climbing as it does in every other sport. There's nothing quite like hitting your peak physical prowess years with a half-decade or even decade of training under your belt, and your body hasn't put on its adult weight yet.

I'd say that 5.12 is rare amongst a certain generation of climbers, but this is not for long. It will soon be common for fifteen year-olds to swarm up 5.12s in gyms, and not long after that 5.10s will be known as "That thing your parents can play with while waiting to drive you home."
Contributor Spotlight: Tom Miller – The Blogging Musician
1600foot=0.48768km
Thank you for your reply, and for reading the article. The comment you linked to is dead, so I guess we were both right about that.
Yes, but for mostly free.
Rewards of Up to $500K Offered for FreeBSD, OpenBSD, NetBSD, Linux Zero-Days
You seem to think I'm describing some special courier service. I'm not. I'm describing the standard USPS/UPS/FedEx experience all packages get, which is indeed how most of the stuff a retail pharmacy gets will be shipped.

The parent's concern with direct-to-home delivery is valid - the inside of an in-sun mailbox on a 90 degree day is going to well exceed safe thresholds for many medications in a way the rest of the shipping chain won't.
It's not a $35k car; there is no $35k option that you can buy, and no timeline for such an option existing.
I briefly really liked Nautilus because it seemed at least at the time that they were doing science journalism right. Maybe I was wrong all along or maybe there were just a few gems.
You mean you meant to type 91.3% but accidently typed 95%? Were you using your own transaction software?
A couple strategies I've seen work:

* have more-experienced CS reps act as "expert reps"; they handle more of the triage & answering routine questions. They're also a valuable information source since they see more questions than any individual engineer.

* similar but different: have a point person from engineering responsible for answering & collating questions. This is a tricky role to hire for, since it's not a standard "pull ticket, ship code" setup. This person also typically carries the "user perspective" into engineering planning meetings.

* interpret the repeated issues as design feedback. If CS reps are "always getting stuck", figure out what about the UX is causing them to get stuck. If the problems are fixable by the user, can you add messaging to the interface that points them towards a resolution when they get an error? Even better, can you design the system so those errors can't be made? (see also Elm's "make invalid UI states unrepresentable" philosophy)
And what really changed? They used to sell the data, right? Now everybody has it (instead of only a percent). Is that worse?
Fortunately, at this point, with all the leaked data, it's nothing really new that others don't already have.

Seriously, though, this is just getting out of control. I'm almost to the point of writing my representatives. I don't think the industry can adequately self-police.

[Edit] By "industry" I mean any company who handles my personal data.
There's a tool now that can do matrix calculus: http://www.matrixcalculus.org/
> Rust uses Hindley-Milner to infer types in general

True, I had forgotten that you can just write let foo = bar. (Not a regular Rust user.)
Hmm.

So I have mixed feelings about this. I think it is good that StichFix is publishing how they work, and I have complete admiration for what they have achieved.

I still use their post about the ability to add a "pregnant" vector to an item of clothing and find a similar item in a maternity version to explain how objects can be embedded in a vector space.

But this post seems both too complicated for the general reader, and not deep enough for a paper.
I think the USA has (a) much more homeless people and (b) much less buses than random places in the UK. (I remember reading a stat from ~5 or 10 years ago that San Francisco had more homeless people than England).
Beware the conclusions drawn from the first read through the writings of our
functional programmer forefathers (and the second, and the third), for "a
little knowledge is a dangerous thing". The unprepared mind of the imperative
programmer is especially prone to following the revelations of the old masters
before achieving real understanding.

A while ago, I was working in company X, that sold a web platform for job
boards, with multiple big and famous clients. One time, there was a bug in our
platform, that had to do with a for-loop with an always-true condition. The
loop -which was in our core platform code and so deployed in every single
website we maintained- caused untold havok, as resources disappeard down a
black hole and all our servers dropped to their knees and asked for mercy.

In the aftermath of the incident, when an explanation had to be given to those
UpStairs running the show, it was put to them that the cause was an
(effectively) unconditional loop. Now, as a lowly junior dev, I was not present in the deliberations
but, given what followed, I can imagine the conversation:

Those UpStairs: "How can we ensure that the same thing never happens again?"

Senior Software Person: "Well, there is no way to ever be 100% safe. A for-
or while-loop can always go wrong."

Those UpStairs: "Is there any alternative to for- and while-loops?"

Senior Software Person: "Not really. I mean, there is recursion of course..."

Those UpStairs: "Recursion? What is that?"

Shortly after, we had a big emergency meeting to discuss What Should be Done
to Avoid the Same Problems in the Future, where we were instructed to not use
the looping constructs of the langauge in which our platform was written,
anymore. Instead, we should only ever use recursion to write loops.

The language of our platform was C#, mind. A language that (to my knowledge,
and certainly at the time, around 4.0) does not even support tail-call
optimisation. Not to mention, it's just as easy to go into an infinite
recursive loop as it is to go into an infinite imperative loop, if not easier.

Suffice to say that nobody followed the instructions given from On High,
either because they found it too much work, or because they found it too
stupid, or because they were just busy pulling their hair out.
> You heap allocate all the time in drivers. You just shouldn't do it from interrupt context. Source: I write plenty of drivers for a living.

Fair enough. I was thinking of low-level things like "shovel a few bytes from some hardware component into a user-provided buffer" without allocating anything, you seem to be working on more high-level drivers.
of course you can, and trivially so; just return the next function to call from (as a pointer or some other identifier as a result of each state function.
Well, superior could mean morally better, more hardworking, etc - so could be equally smart or even more, but might not be cynical enough to even think someone could do this kind of thing.

The superior group is not meant to be "superior" in every aspect -- only to the aspects that matter for the values of those defining it.
Indeed, based on the article posted elsewhere in the thread, it sounds like the publicity this company generated for this guy is what brought him attention and got the property owner concerned that it would turn into a camp.

So, people complaining about the authorities, but the “entrepreneur” in this case should also bear some of the blame.
That's not even remotely a concern as far as their IPO goes. Airbnb's business is a spectacular success and will remain so. There's no serious threats on the horizon, that includes regulation and competition. They smashed their own 2017 forecast numbers, delivering $2.6 billion in sales and were profitable.
Of course not. You're giving an unsecured, interest-free loan, why would you expect that to be safe?
> For example when Consumer Reports identified a braking issue with the Model 3 Tesla had an OTA software fix in days. What other manufacture would do that, let alone could?

Why should that be a good thing? Consider what this means:

* Safety-critical systems are not air-gapped. (Granted, Tesla is far from the only offender here).

* The fact that the fix was turned around in such a short time would seem to suggest that it was relatively quick to diagnose and debug. Why wasn't it caught before release?

* On another note, it also calls into question how rigorous their update fix testing is. I've seen plenty of "this must go out fixes" that broke a lot of stuff by collateral when people felt it was too important to get out quickly to do the full testing.
The island (or the part he’s occupying) would seem to be the property, as that would be the common understanding in English. Is there another interpretation that would make sense to you?
Here in Ontario, that very much depends upon the gym and the date the climbs were put up. There are a lot of 80s trad climbs put up with stiff grades, because the OGs that opened the sport were insanely tough and liked nothing more than for visiting climbers to fall off 5.10s.

It was some kind of magnificent but toxic culture, very similar to surf culture, with hidden spots and tribal rivalries.

The first gym to open in Toronto carried over this tradition, but other gyms eventually opened and went with "friendlier" grades, so there can be a big discrepancy between a new gym's ratings and an old trad climb in Ontario. But newer outside routes, especially new hard sport routes, are put up by climbers with newer grade sensibilities, so the indoor and outdoor grades are consistent.
And the whole enumerator/stream now it’s a mess in Java compared to C#.
In c# you have IEnumerable that works perfectly with LINQ without using a .stream() method call.
You don’t need to collect it explicitly, it will be just “materialised” at iteration time.
If you instead try to pass a stream, even casting it to an enumerator, and it is used twice your software will fail at runtime.
Honestly I can’t imagine how did they manage to over complicate so much Java streams implementation after that Linq was used successfully and in a very elegant way for years...
Aka the throughput vs latency discussion
Can you expand on this? What's a trivial exmaple?

Doesn't it depend on how the iterations are compiled? Seeing how e.g. a normal continuation is compiled in C#.

foreach(var thing in Things)
{
if (thing.IsAlive)
yield return thing;
}

Those will compose (At least I think they will compose in the sense you mean) because they are alrerady sugar for a state machine and not a simple iteration. The for-loop construct didn't imply "loop here until done" in the sense that doesn't compose.
Relation?
Software Exposes People Problems That You Can\'t Ignore
No, it's the compiler. Are you still overlooking the phrase "the multipass compiler code is about 3K lines" in my original post above?
The fact that urls cited in publications no longer work over time is why I often included their content as apendix's to my essays. That way even if the original source is lost the referenced material isn't.

Then again material published in journals and books is greater than material published on the internet, if for nothing other than it can be relied upon to be found in decades to come.
It's been tried. Most directly by Google, but almost any publisher on the internet has tested various forms of subscription model.

While some high-quality publications (the New York Times, Economist, etc.) have seen some success in recent years, the overwhelming evidence is that the economics just don't work out among the general public.

Most people also underestimate the costs. IIRC, Google needs about $100/pa to supplant advertising revenue.

Yes, you may be willing to pay, so why aren't more services willing to take your money? Apart from the administrative hassle of such a program, the $100 (or whatever) are also an average. People willing to pay as much for an ad-free experience just happen to be at the top end of the value distribution for advertisers as well.

In other words: If you're willing to give me 2bucks, it's gonna cost you 5!
That's called a trampoline, and is one of the ways to simulate tail recursion. It requires a global modification to the code: you have to rewrite all your code that you want to be stack-safe to be trampolined. It wouldn't call that trivial, but then Node developers are happy to rewrite their code into CPS so what do I know.
Yup. My phones tend to drop along ballistic trajectories, which is rarely a straight line towards the Earth-Moon barycenter ;)
Let me remind you of the Spanish Civil War of 1936-1939, and its hefty toll on Spain. Like all civil wars, it never really ended.
Global Cryptocurrency Is Coming
Unfortunately, mathematics is one of the areas where Wikipedia is pretty awful in general. The articles seem mostly written for people who pretty much already understand the topic in question. Of course, you always have to assume some knowledge base but the stereotypical jargon-filled Wilipedia approach is particularly off-putting in this area.
Blaming the "startup mentality" makes a good linkbait title, but Occam's razor suggests that when the latest cool-sounding attempt to reform public schools in cities fails, it's probably for the same reasons that previous cool-sounding attempts to reform public schools have failed: politics, turf wars, existing vested interests, and so on.
I know that unflattering depictions of Steve Jobs are the big hits these days, but this one seemed more like an attempt to flatter that left me flat. He sounds incredibly annoying to work with and the people working with him have that hands-on-hips "oh, him!" attitude at some massively dickish moves. Blowing off peoples' ideas so glibly and pointing to the door imperiously to indicate they should leave? Threatening to ditch a demo and terrifying your employee? Ordering 300 custom made white italian dress shirts just so he could wear a brand new one each time?

I know he accomplished some cool stuff but geez.
> Trying to undo history, or even taking a new mode of design is extraordinarily difficult

"The best time to plant a tree was 20 years ago. The second best time is now."
We still have receipts and tax records carved into ancient Babylonian clay tablets, and letters from the 18th and 19th century, so I believe it's not really true that only papers from famous people were kept, rather that artifacts of interest to elite classes (be they religious or scientific) tended to remain preserved or published.

Although it is interesting (and a bit depressing) that we can't really seem to escape that model for preserving knowledge over the long term. Physical media needs patronage, buildings, printing presses, etc, while digital media needs infrastructure, manufacturing, programmers, etc.
the following is also tailcall:

x = f(a)
...
...
return x
HyperE: Hyperbolic Embeddings for Entities
> shareholders sued Tesla board members for breaching their fiduciary duties

Starting a lawsuit is easy. What’s under-reported is how many of such lawsuits are won.
It seems to me a lot could be solved by making data available and compiling software to webasm, then packaging up a single web page that demonstrates any algorithms used.
It seems obligatory here to mention Peter Watts' Rifters trilogy, the first book of which is set in and around a geothermal power station on the sea floor near the Juan de Fuca Ridge.
I found the post on RealPython easier to digest for a quick glance of the new features:

https://realpython.com/python37-new-features
>Personal information is like hazardous chemicals.

Big data is munitions, ammunition that is loaded into algorithms which are like machineguns that can fire at the speed of light millions of times across the world in under a minute.
> Just that "expected" sounds like there's a certainty about it

It does seem give a sense of certainty, but is not how "expect" is used in probability. The expected value is just the average value per attempt as converges as attempts approaches infinity. So its a useful measure of a distribution (which can be used to make informed gambling decisions), but shouldn't be used to make a prediction on any single attempt.
Given the most recent update, it seems pretty certain the next one will be the last... but I am quite curious about it.
Iterators are better for anything that that requires more than forward only iteration.
Unconstrained goto like you see in C is scoped out of the feature set in part because it makes safety checks and JIT/compiler implementations a lot trickier. A primary goal with wasm is to provide high security so risky stuff like that got bumped out. In this case it's about flow control in general and not just "goto", though - you can represent some uses of goto in wasm.
Well, if it was published it was deposited with the national library - British Library or Library of Congress. I think other nations have similar systems. Covered newspapers, magazines and books. The British Library page:

https://www.bl.uk/aboutus/legaldeposit/introduction/

"By law, a copy of every UK print publication must be given to the British Library by its publishers, and to five other major libraries that request it. This system is called legal deposit and has been a part of English law since 1662.

From 6 April 2013, legal deposit also covers material published digitally and online"
That's what I was guessing. But since I don't understand Japanese, I can't read the article to check.

But looking at photos of the island, it doesn't look like a good place to farm. So that's what led me to believe the island and the property might not be the same thing.
I know the feeling - working on (undocumented) legacy systems is a nightmare for so many reasons.

But not all companies are like this.

It sounds like you need to a) quit and find work some place with less legacy/debt (ideally a startup), or b) ask to be moved to another department that has less of that kind of work (if possible.)

Continuing with work like this will, as you've found out, burn you out sooner or later.
more sad than interesting because we normally don't know when and which firm(s) got our data. I never heard of this company until today.
Google's data take-out has proven fairly robust.
That's not right, unless the "... ..." is empty, and even then, it depends on whether x is a global variable, and even if it isn't, it depends on the language.
I'm also Australian and didn't realise it was because of this. Actually, I'm still skeptical this is the main reason since it's like a 260ms round trip to East coast USA. Let's say the latency for someone not living on our big old island is 80ms round trip. I don't think the extra 180ms will make that big of a difference if the app is well designed. That's still enough time to detect scrolling and have the new data ready by the time the user turns the mouse wheel twice.

I should add that I've always suspected a lot of developers don't test their apps with latency in mind, so they make silly decisions like serial requests, etc. They never see how awful the experience is for someone not living next door to their data centre.
Can we harvest it?
Aren't you are cranking up the debate on biased media in this thread?
For loop don't have to mean counters. We had automated for loops for years, generators and comprehensions that are basically map/filter integrated in syntax. E.g you have map and filter in python but they are rarely used for that reason.

No need to be dogmatic.
My understanding is that in this approach, rather than producing a long sequence of DNA, they're making tiny sequences of address and data snippets, then assembling them with enzymes randomly. Containing addresses allows the data to be assembled back into the correct order.

With typically three base pairs per amino acid, encoding complex proteins in 30 base pairs isn't possible. That said there are other methods to assemble longer sequences.

Nothing is technically stopping someone from writing a deadly virus, except that you'd have to engineer its DNA (not a trivial task). Why do that when nature has created plenty of deadly viruses to choose from? Furthermore, for military purposes, you would want something controllable, so you can deploy it without also killing yourself. Bacterial agents tend to be more suited to this.
yes, and they are no more. Turns out that general purpose ISAs beat application specific ISAs every time.
I've always though that Law of Jante was good, while also equating it to "the tallest blade of grass gets cut first."
One common critique is that in the toplevel (REPL) you must terminate your inputs by ;; and sometimes you will see code that puts ;; between function definitions too.

Also, nesting pattern matches is a bit ugly:

match x with
| Foo y ->
match y with
| Yes -> ok ()
| No -> not_ok ()
| Bar z -> whatever()

does not work, it must be:

match x with
| Foo y ->
begin match y with
| Yes -> ok ()
| No -> not_ok ()
end
| Bar z -> whatever()

which is not a big deal but surprisingly easy to forget.

Some people would also really like to write

let x = foo
let y = bar
x + y

but it has to be

let x = foo in
let y = bar in
x + y

and those many "in"s accumulate.

A bunch of these things look a lot cleaner in Haskell. Although it does it by being indentation-sensitive, which other people love hating.
without *any* contribution

I'm not a lawyer. If I were, that phrase would give me a toehold or restless sleep depending on which side of the pile of money I was on...ok, actually if I was on the "hands on the money side", I would just advise avoiding the risk because that's what lawyers are expected to do.
Or to put it another way, the argument that works created by the program are not copyrightable might tend to be more expensive than simply paying licensing fees in a business context.

But again, I'm not a lawyer.
What it takes to be a category king
Indeed, however, the impact of such breaches has yet to be made explicit. It seems only a massive cyber attack would show the public what is possible with such information
When Protocols Replace Companies
It will be interesting to see how this plays out.

If nothing else, Tesla customers are buying (or attempting to buy) a piece of history.
In the case of adversarial legal disputes? They are rarely economically productive in isolation. Normally it's actually negative-sum.