skysight-inc/HackerNews huggingface dataset:
Neither Algol 60 nor Algol 68 were very good choices, but it was basically them or FORTRAN which were used back then in published algorithms.

Algol 60 was the forbearer of most modern programming languages. However, implementations of Algol 60 were all a bit different and even after the the revised report came out a few years later there remained serious ambiguities in the meaning of common Algol 60 constructs, see for example [1]. Other aspects of Algol 60, for example the use of call-by-name argument passing semantics, made it not entirely suitable
as a means of communicating algorithms.

Algol 68, had, for many years, essentially no conforming implementations. The language was remarkably orthogonal, every aspect seemed to be fully generalized and usable everywhere in the language, but it was too complicated. At least, it had a concept of I/O, which Algol 60 lacked. Some algorithms were published in Algol 68, but I didn't see many of them.

In this environment, Knuth's books were quite valuable. The algorithms, while not structured or written as we see them now were clear and unambiguous and were written for a time when compilers didn't perform advanced code-optimizations; Knuth's careful designs included optimizations that we would leave to compilers today when talking about algorithms.

Eventually, Pascal came along and it became possible to publish algorithms in an easy to read and unambiguous way. (It was still uncommon to see code formatted in any consistent way. See Wirth's own books!) Pascal wasn't perfect, but it was easy to understand and implementations were portable and widely available.

[1] Knuth, The remaining trouble spots in Algol 60*, https://atlas.cs.virginia.edu/~asb/teaching/cs415-fall05/doc...
Video from Martin Fowler about Introduction to NoSQL:
https://www.youtube.com/watch?v=qI_g07C_Q5I

Tutorial from Felix Gessert about NoSQL
https://medium.baqend.com/nosql-databases-a-survey-and-decis...

and Slides
https://www.slideshare.net/felixgessert/nosql-data-stores-in...
I disagree. I feel like it's a great way for a company to suss out actual product interest before investing millions in fleshing out an idea. Just think of it as pre-ordering.
Internet Download Manager 6.29 Build 2 Crack and Patch Serial Key
Agree on the oversight. From his CFA perspective (which I'm not in any way), divs are somewhat diminished in the new normal (as your link shows), and minority of companies account for the majority of divs. Of course, fiscal policy also impacts div gains. Double whammy. Creates a great climate for the development of productive assets, rather than resting on protective assets.
"Maybe it would be a good idea if some western states have access to a kind of backdoor into Tor/I2P/Freenet/etc."

How will we ensure that only the Western States that are supposed to use the backdoor will be able to, and that e.g. the governments of Russia, China, or Iran will not have access? Remember that Tor was created by the US government for the purpose of evading surveillance and national firewalls, and that many countries would like to have access to that backdoor for less acceptable purposes.

"I get the point that journalists/political dissidents want some anonymous communication channel, but do we have to tolerate shit like this?"

Tor is not really the issue here. Pedophiles do not really depend on Tor as much as you might think. Pedophiles are known to use the postal system to send and receive encrypted DVDs. They are known to operate legitimate websites as "fronts" for pedophile forums (not hidden services). They have used Usenet, IRC, FTP, and BBSes. They use sneakernet.

Child molesters often go undetected for years, despite not using the Internet at all. Child molesters rely less on systems meant to evade mass surveillance than on the fact that we do not live in an Orwellian world of total and pervasive surveillance. I think we would all agree that the priority is to arrest people who abuse children; yet that is a crime that occurs offline, is not in any way aided by Tor, and still remains hard for the police to detect and stop.

It is easy to fall into the trap of thinking that were it not for Tor, the police would have an easy time catching pedophiles or that child sex abuse imagery would stop being produced.
So many Americans do not understand this, and think that universal health care means the government imposes a monopoly.
What a poorly written article.
FormAPI converts any existing PDF into a template that can be filled out via an API call, or via an online form.

If you upload a scanned PDF (e.g. plain images), then you can add form fields in the template editor. If you upload a pdf with a fillable form, then we will automatically import all of the existing fields (and the imported fields can then be modified or removed.)
"continuous partial attention"

"Joe in 1401 was worried that the invention of books would cause "semi-continuous-patial-attention" because it would disrupt the oral stories being conversated about"

This article explains the historical trope of people being unable to cope with technological progress perfectly.
Unless the chemistry book has a chapter titled "how to make a bomb to kill lots of people" with full instructions on how to assemble and detonate one using readily sourced materials, then I'm sure such books will be entirely unaffected by police investigations.
LinkedIn's Tips for Highly Effective Code Review
Looks good. I think some real life use cases would help on the sales site.

So the use case is you have a company that only accepts PDFs as an input and you have a digital data set that you need to get each individual row into one PDF?

How do you handle signatures?
> (the app/store infrastructure being a notable exception)

It was the start of a good thing.

https://np.reddit.com/r/Surface/comments/6ifyxq/spotify_for_...
Reading the title, I thought it might be on some fancy debugging microcode!
I disagree. It's a tool like any other and good tools have multiple applications. If there's no reason it can't do both other than falsely imposed limitations that's a bad tool. The best tools have many uses.
You're completely right. I had no idea.

But I can't make sense of the definition of >>= for the list in Haskell, which is:

xs >>= f = [y | x <- xs, y <- f x]

It seems to imply that I get a list in return when I do xs >>= f, but I need to do the following in order for it to work:

[1,2,3] >>= return . (+1)
The second printing I referenced is from 2003. The (presumably) first printing on my bookshelf is from 1990.
Digital Ocean is still a premium provider.

I would look at providers like OVH and even cheaper (Treudler, TransIP, RamNode, etc.)
For example, an SSD with 2 vCPUs, 8GB RAM and 40GB SSD is 13.49$ per month from OVH.
Microsoft is pretty explicit that it is a stop gap to port applications to UWP.

That has been their main message in any presentation about the Desktop Bridge. Always showing how an existing application gets packaged, followed by replacing Win32 legacy features with modern UWP ones.

The track record of other tech giants is not much different, let alone the usual reboots on GNU/Linux desktop stack.
This article is (2013). Same magazine posted another article in 2014 that provided a different look at the same broad topic:

https://www.quantamagazine.org/beyond-the-bell-curve-a-new-u...
Suppose I find a paper submitted to a conference. The conference lets me download the original latex source of the paper. If I want to take the function they wrote out and take the derivative of it I'd currently have to rewrite the expression. Unfortunately this is very risky with extremely large and complex functions. Ideally it would be cool to just copy a latex expression into your "SymbolicVariable.Parse" method and tell it that it's written in LaTeX.

Copy and paste has a much lower chance to incur errors than rewriting an expression.
And yet the most efficient programs are written in the low level languages, and the slowest programs are written in high level languages where optimization is the responsibility of the compiler.

Compilers can definitely do better than humans in some situations, but you can also use an optimizing assembler that helps with register allocation (not as important for x64) and all sorts of peephole optimizations. The compiler doesn't reason about the data, which means the compiler has to make worst-case assumptions that the programmer knows won't occur. This is a big source of inefficiency. Compilers will never be able to make strategic optimizations because the compiler doesn't understand what it's compiling.

Like with chess, computer + human is the winning combination.
The most interesting statistic here for me is the time spent processing SQL queries. It really only takes a few tens of ms in most cases to processes. But due to the sheer volume of requests over the course of a day,it ends up being days worth of time.
"from their coinbase account to my coinbase account" so if i understand correctly this basically eliminates blockchain and leaves you with plain old database in the backed of some provider to keep track of how much "money" you have. And if provider gets hacked well, tough luck...
It depends on the purpose. For example: You can't hype fiat money anymore, too much liquidity.
Yes, well, once upon a time in the dark ages, we didn't have HN or even the Internet to spend our time on. At home I didn't have a computer, no one did in the 60's or early 70's. I did have a few books so I read a lot including Knuth and the publications of the ACM that I subscribed to when they arrived in the mail. I wrote my code out on paper when I worked on it at home.
More by the author, http://www.computerhistory.org/atchm/author/dlaws/
The OP was referring to an "evil growth marketing tactic" - it wouldn't be as evil if it were mainly for empathy with the user base rather than as a dark pattern.
Automatic OCR of what? The entire document?

What type of documents? No cloud because of a regulation?

Once you have the document what are you going to do with it?
Layer 2 is not money and so can’t be fiat. Lightning network is just a clever way to construct bitcoin transactions such that it is possible to send sub-transactions via different communication channel(not congesting bitcoin network) but preserving crypto currency guarantees.
Vast majority of cases I've come across, if not all of them, only suffer from any reliance on 90s era RDBMS systems.

And it's never about JSON, it's about latency and resilience, about being able to simply add and replace nodes, about just working in a modern distributed environment.
Private Torrent Sites Allow Users to Mine Cryptocurrency for Upload Credit
> Very few employers pay wages denominated in bitcoins.

Very few merchants accept payment denominated in bitcoins, either. And these two statements are clearly tied together. If, upon bitcoin scaling up in the economny, more merchants accepted bitcoins, then it follows that more employers would pay wages denominated in bitcoins.

If the state of affairs remains the same as it is today, then there is no need for me to buy into layer 2 protocols monthly. My monthly spend in bitcoins will remain a fraction of my monthly wage. I could afford to buy into layer 2 annually easily enough.

If more of the economy moves into bitcoins, then employers will pay wages in bitcoins by definition. And at that stage, it will be feasible for them to pay in layer 2.

Either way, I think this exposes a vital flow in your chain of reasoning.
I believe my managers in the roles I left had a similar perspective to what you're saying. For different reasons, the execution just wasn't there, however.

Usually it's because the organization didn't allow them the room to manage the way they wanted. Sometimes they just weren't allowed to provide the raise or promotion necessary. Sometimes there weren't roles for tackling the problems I wanted to tackle. More often, the managers were just too distracted and spread thin in time and/or political capital. They were pressured (or at least felt pressured) to say yes to things they shouldn't (over my concerns and objections) and didn't have time to do much more than keep chopping wood.

I'm not a shy person. I'll be clear and hopefully even handed about my concerns. But I won't throw tantrums, talk about people behind their backs, or make ultimatums. If, after a reasonable amount of time, my input isn't taken seriously, I'll have to find opportunities where I can contribute. Maybe on another team, maybe in another company. Otherwise I'm shortchanging my potential.

> Some folks do have unreasonable requirements that will not be satisfied.

I don't have unreasonable requirements, but good managers will be clear if they feel this way. It will save me time in the long run, at least.
If you're looking for something similar and not in alpha state go check out nest.js https://nestjs.com/ Its embracing MVC, supports TypeScript and DI. Really sweeet.
You may be right at this time, but the suggested fix feels a lot like plagiarizing the work of Wikipedia editors. It takes significant work to gather sources and turn them into an informative article. I believe that work should be recognized, even if it was published on a free access platform like Wikipedia. Is there some middle ground between using their work without acknowledging it and suffering a stain on credibility because of guilt by association?
Maybe interesting to post here are the comments of Steve Yegge (GeoWorks developer) on large scale assembly projects:

https://youtu.be/tz-Bb-D6teE?t=2161

His argument was that while assembly allowed for more optimized local routines, they've lost the perspective on how the system should behave at large (the handling of window drawing routines, etc.)
That is also a pet peeve of mine that even respectable journalists that should know better make: saying Russia when they clearly mean USSR.
Here’s a list of providers by cost:

https://git.io/vps

(PS: Don’t use DigitalOcean, they tend to steal your credit if they feel like it. Lost 100 bucks "promotional credit" that way with only a few days notice)
I have a couple of go to pieces on procrastination/getting things done:

Procrastination is not Laziness (http://www.raptitude.com/2011/05/procrastination-is-not-lazi...)

6 Harsh Truths That Will Make You a Better Person (http://www.cracked.com/blog/6-harsh-truths-that-will-make-yo...)
Having your life savings in cold fusion juice presses is just as stupid as having no stock in the above at all.

You need to think of the reason for an investment. If you are set for life, and want to gamble on it... cool, buy BC. You could also go to vegas, or bet on horses, or start a HFT trading shop. All are reasonable ways to gamble for fun and possibly profit.

If you are looking to build a nest egg to retire when you are old, it is very unlikely that BTC is a good route for that ;)
"About 100 kilometres from Sverdlovsk, a high-way sign warned drivers not to stop for the next 20 or 30 kilometres and to drive through at maximum speed."

Fascinating and scary.
That's all great until you need to perform a join.
Saarinen's TWA Terminal to become hotel
They expired some credits that I haven't used but after asking they just restored them and I could use them. Asking helps.
I highly recommend Martin Kleppmann's Designing Data Intensive Applications(http://dataintensive.net).

It will not only help you understand what's "SQL" and "NoSQL" data stores, it also covers the differences between each of them, what problems they are designed to solve, how they try to solve it, and if it'll help with your problems as well.
Oh, man, we're just looking at the tip of the metaphorical iceberg. There is a ton of new hardware for Apple 2s - replacement power supplies, sound cards, coprocessor cards, solid state floppy emulators, VGA drivers, and even FPGA cards (Carte Blanche).

There is also new software being written for the Apple 2 - take a look at Nox Archaist, for example:
http://www.6502workshop.com/p/nox-archaist.html
EFS is far more expensive than EBS. Price it out; you'll see.
ESIM and the Future of SIM Cards
If an employer is willing to pay the employee bitcoin in layer 1, how much less willing would the employer be to pay in layer 2? Not much, I think. It doesn't seem that it should be much harder to use layer 2 instead of layer 1. If it is, then isn't this a usability issue affecting all users and not just employers?

If the employer is willing to only pay fiat, then there is no new problem, is there?
App badges and persistent notifications making you insane in the membrane?
we use k8s at work. i just have to create PVC and when spot instance terminated along with the container; new container will be created and mount the PVC again automatically.
Thanks! Totally agree, there's a lot of room for improvement on the landing page.

That use case sounds right. I've mainly been thinking about tax and immigration forms, or filling out financial and legal documents, etc.

There's no special field type for signatures at the moment, but you can upload a signature image, or use a text field with a handwriting font (Dancing Script [1]).

I will probably add the signature_pad [2] library to the online forms in the near future, and will add a special "signature" type. There might also be a new flow where you can request a signature via the API, and we'll send an email to the person who needs to sign the document.

(I actually just need to get a few more customers first, so that I'm building something that people need.)

[1] https://fonts.google.com/specimen/Dancing+Script

[2] https://github.com/szimek/signature_pad
This isn't exclusive to the U.S. of course, but there's the pernicious view that they're "bad people", they make bad choices etc.

To this view I would reply with the idea, attributed to Socrates, that there is no such thing as "moral weakness", or that doing good and bad amounts to knowledge of what is good or bad or a lack of it (keeping in mind knowledge could be more than merely mental abstractions).

Now unless this idea can be disproven, how can "moral weakness" be used as a justification to ignore the plight of these people?
Think Tank Cancels Talk by Chinese Dissident Under Pressure by Beijing
Blockchain protocols typically aren't designed to be scalable because, based on what they are actually used for, they don't need to be.

Bitcoin was a cryptography research project that became popular outside of the usual circle of people interested in such things mostly due to these three somewhat overlapping groups: get-rich-quick types, criminals, and people who have deluded themselves into believing that Bitcoin will usurp the world's major currencies.

One those three, only the last group have any interest in massively scaling up blockchain technologies. Those looking to speculate on Bitcoin markets have no such concern, and the criminals are just feeding off Bitcoin's popularity for this rather than having an interest in making it scale; besides, they'd prefer a more anonymized cryptocoin to be popular rather than something that makes public the entire transaction history.

The 'true believers' of Bitcoin are outnumbered not only by these other two groups, but also by the general population who have no use case for Bitcoin at all.

This is why scalability is such a fringe issue for Bitcoin and other blockchain protocols - they're all just solutions looking for mass-scale problems.
Thank you! I will be subscribing shortly. But I'd like to take it a step further and actually setup a honeypot phone number so calls are automatically transferred to the bot without manual intervention.

My elderly parents were scammed this way and I want revenge!
Well, that was patronizing. (I was doing L-system based design in '91 in Arch school. :)

The question to you sir was: which patterns in Alexander's book are "recursive".
In the great HN tradition of complaining about headlines; Shouldn't this have been SlowmoPython? Watching a program execute line by line at real speed would be a short movie.
Even if you don't use spot instances, the technique of using separate EBS volumes to hold state is useful (and well-known). Ordinary on-demand instances can also be terminated prematurely due to hardware failure or other issues, so storing state on a non-root volume should be considered a best current practice for any instance type.
ITT: pumpers
I’m pretty sure that “R&D facility in Palo Alto” was just Vic’s garage, at least for the first several months. My dad told me stories about all the guys coming over when he was a kid. That’s back when Los Altos was mostly orchards. We still have the workbench from that garage.
Are you sure?
Once in Dehli asking for coLd medicines the pharmacy salesman made me a very cheap and very wrong mix of very few antibiotics tabs.
Resistant TB is also 3rd-world originated, right?
Hep-A in southern Cali is another poor man infects rich man story.
It's fairly common, although I agree they ought to do better. It seems to be partially due to the fact that Russia was such a dominant part of the USSR, and partly because the USSR was more or less the continuation of the Russian Empire, which was often referred to as just "Russia."
Where they any different or just overflow?
The design of Bitcoin is inherently flawed at the moment (at least for payments), and due to its decentralised structure, a change can't easily be forced.

I think Bitcoin was a great experiment since it brought us the blockchain, but with the exception of being a store of value (i.e. digital gold, and thus not having to worry too much about high transaction fees) I don't see it going anywhere. But since gold is worth about $8.2tn globally, that might be sufficient.

Ethereum on the other hand.. by the looks of it that does seem to have a bright future. It improves upon and fixes many of the flaws Bitcoin has.
With LN one's able to devise mechanisms where currency is effectively backed by BTC-- think when USD was backed by gold, but where upon the US breaking from that, people were actually able to trade in all their USD for weightless gold
Concentration to the point of extreme deprivation.
It's not that it cannot protect, it's that it actually does harm.
Linux Kernel LTS release is now for 6 years instead of 2
http://kolibrios.org/en/

The opensource fork
Can you explain why? I agree, but I’d like to be able to justify it as much as possible when arguing for SQL.
Why do all of everybody's step 1 transactions have to be within a single block? Do the proposed 'layer 2' ideas only work inside one block? It's not obvious why you can't pay into 'layer 2' from arbitrarily many Blockchain blocks, but I'm not really familiar with any of the proposals.
They won't just bring "refreshing linguistic restraint" though, if you have two campaigns doing the same product idea, but one has a slicker video and can promise bigger rewards, which would you back? For crowd-funding platforms that proclaim support for the "small people", I can understand if some people feel a bit cheated.

Personally, I like to go for the artsy projects because these can't be found elsewhere (except maybe Etsy) so I've learnt to filter out the "money-grabbing" spam. Inevitably you'll have noise in a system, like eBay's counterfeit problem, but I just don't think that you need large companies presence to deal with it.
"0.1 bits/sec with a bit error rate of 1% over a distance of 1.035 km, including 240 m of earth."

I'm not sure that's much better than ULF, with similar issues on the size/cost of the transmitter.

They do mention interstellar communication though.
As with many games of this type, epic gameplay comes with complexity, a learning curve and long play sessions. Anyone know of boardgames that deliver something big from a minimal set of rules and items? I wouldn't mind exploring a dungeon in 10-15 minutes with a random stranger on a train.