skysight-inc/HackerNews huggingface dataset:
Yeah there's absolutely no way I would ever pay for something with DRM.

This will end up going the way the textbooks went.
The current price is $400 per year not $199, if you get a discount or have a grandfathered rate that should not be used as a talking point to defend their pricing as a person signing up today will not get that rate. So you have to base the argument on today's prices...
Easy Ways to Raise Capital for Your Startup
Raising capital for your startup gets easy if you choose to plan a concrete app development idea. This will help to raise the capital easily from the investors.
> All is java

Possible tip: sneak in ABCL when they're not looking. ABCL is a Common Lisp implementation for JVM, with (what seems like) relatively OK interop between Lisp and Java code.
Algolia's API show comments upvotes up to 2014 I think. So basically hnbc only shows old comments.
I would say color discrimination is easier because it's basically 1-dimensional. In the best case you could do it with a resolution of a single photoreceptor. If you account for ambient lighting, shadows, etc you still just have a 2-dimensional task.

Shape discrimination is a 3-dimensional task. In the worst case you need to change your point-of-view or the orientation of the object.
You should really give "Three Body Problem" another chance. There are a lot of diversions and off shoots but the main story really comes together 1/3 of the way through the first book and really picks up in "Dark Forest".
Wouldn't the instruction be bigger if EAX was used? I guess it would have to have 4 byte constant then, with this encoding it's one byte. How would you clear the 2 lowest bits in the second byte of the EAX?

For the reference, we talk about:

andb $252, %ah

I believe it's not an effective speed optimization, given the way modern CPUs work, but it does produce a smaller instruction?

Additionally, what I miss in this story is which source code actually produces "I need to clear exactly these two bits while keeping others" in a loop. For that CPU bug to manifest, it has to be inside of "short loops of less than 64 instructions."
You Are the Product Owner of Technical Debt
>I could not care less about what is the colour of people writing it, their sexual orientations, or how well represented they all are. It may seem relevant to you but it certainly is not to me.

Well, you can certainly ignore all that and just use the language. Nothing forces you to do these things, they're just forcing themselves to do these things.
I don't feel any of those limitations using SQLAlchemy. Most projects just end up implementing a subset of ORM features poorly. I think your experience as an ORM author and contributor may rather uniquely qualify you to write "a bit of DRY glue code".

Good ORM lets you use a small slice of their features without any big performance hit in terms of development or actual. With a nice object model it just seems easier to remember and work with code.

When I need complex SQL I just write a raw query... It is trivial and concise in any ORM to drop down to raw SQL when needed.

I can agree they are no silver bullet, but a good ORM does so many chores for me I can't imagine bothering to do them myself, anymore when the pattern of using objects in my code and storing them in a SQL DB solves the problem at hand.
You commented on two points:

A) ip spoofing
B) netflow

On IP spoofing I said plenty already https://idea.popcount.org/2016-09-20-strange-loop---ip-spoof... . There are two major points:

- We will always have DDoS vulnerable UDP protocols. In past we had DNS. Then we had NTP. Now we have SSDP. The next one is going to be some gaming protocol. We should fix them as we go, but a more comprehensive solution it to actually fight the spoofing.

- Even without using amplification, with IP spoofing it's possible to launch a direct attack, which will be untraceable. We regularly see 150Mpps+ packet floods going _direct_ from the attackers to our servers. The ISP's are clueless. There is no way for anyone to trace the true source of the attack. (without netflow, that is)

This brings us to second point - netflow. You say - the ISP's are incompetent, they do not have netflow and this is _good_. No it's not good. The ISP's can track you / deanonymize anyway, but when I ask them: "hey guys, I see this 150Mpps flood from your network, can you do something about it?" they say - "no, we can't identify the source because the IP's are spoofed". Yes, I herby recommend that each of the ISP's should take care of their network. Be able to answer historical questions about DDoS. That means the netflow collection point will have statistical metadata about customer connections (1 in 64k connections will have saved data - source port/ip, dest port/ip, length, packets, bytes). This might be used to attack your privacy - but the ISP can do much worse things anyway. Doing netflow right will allow us to finally trace the IP spoofing.

I really think that DDoS is a threat to the internet as we know it. Think about centralization that it causes: can your server sustain trivial 100Gbps SSDP attack? I really think that doing netflow right will allow us to keep the decentralized internet.
Oh, looking at their site, I now see that it's a substantially different cost and set of constraints than those that applied when I allowed my subscription to lapse. Disregard.
No he's probably not boring rather. He's over-hyped because he's well connected in the Valley & known to heavy-weights like Sacca & Naval.
You're definitely not the only one. I'm in the camp too. The language isn't perfect, but it's so much better than the popular dynamic ones that it's a shame it's still relatively obscure. And the development model of Common Lisp is what I strongly miss everywhere else.
https://bittrex.com/
Register dot com domains, as many as you can.
I just looked up my own O'Reilly book on ebooks.com.
http://www.ebooks.com/95729334/designing-data-intensive-appl...
I can't see anything about DRM on the page, but under "supported devices" it says "e-readers with Adobe Digital Editions installed". Isn't that DRM enforcement software? Could you clarify please?

Edit: this page explicitly says that readers need to be compatible with Adobe DRM https://support.ebooks.com/hc/en-gb/articles/214119286-Guide...
The Weimar had lots of extremist parties on both the left and the right. It just as easily could have gone communist as fascist. Part of the reasons the Nazis were supported was because they were anti communist. Somehow I doubt modern Germany is just as hard on extremists on the left though.

The people being silenced aren't necessarily anti-democratic either. The Nazis were pretty clear they wanted to eliminate the republic, as you mention. Not just people upset at immigration policy.
Libre Computer Board – Next Gen 4K SBC Dev Board for Makers
I rather liked The Three Body Problem - but I listened to the unabridged audio-books rather than reading them which definitely makes many books easier to consume.
Stackhackr: New Malware Simulation Tool
> Tipping off a rogue sentient AI that killed off their own creators is what I am more afraid of.

That kind of AI would be more busy harvesting new worlds than trying to care about an inferior species like ours (and they would likely not even be in the vicinity so no reason to travel up to us either).
I do the same thing, reading articles on sites like medium is a nightmare since it demands I tweet my currently selected text. Annoying!
> That is what it is, but if the company is allowed to be driven by profit motive, he should be too. It is within the best interests of his profit motive to continue with the automated work. For some reason when the person is an employee, it's no longer okay to be a sociopathic profit-motivated machine, we're actively disgusted by this type of behavior.

I can go along with this fairness argument, but you can hardly argue then that the one obvious solution must be "well, then everybody should get to act like a ruthless sociopathic profit-motivated machine".

Obviously the reverse would be a much better outcome for all.

The mistake is accepting companies behaviour like that.
We Need Next Generation Algorithms to Harness the Power of Today's AI Chips
I'd say the latter.

Even looking at most of my cow-orkers, who do spend a lot of time using the web, they're still Internet foreigners. Tourists to the web. They go sightseeing, but they don't know the actual culture. So is the case with most of out-of-work people I know. And I imagine so is the case with most of people employed to write about the web. They don't know shit, because they're not part of any on-line community.
> The signals proposed by the METI community

Yeah but they would need interstellar-type of timescale to reach us anyway even if they moved at a fraction of speed of light, so the risk is close to nil. We are way, way more likely to be hit by an asteroid or to destroy our planet than to be destroyed by a very remote alien civilization.
I mostly use this now: https://pandas.pydata.org/pandas-docs/stable/generated/panda...

Which is basically an easy to use API that turns a SQL query into an efficient columnar table in memory.

Yes, this still requires writing actual SQL. And yes it does not help you insert or update data. But for 95% of uses it works well.
Google Area 120 Incubator Gets an Early Access Program
Watch 35 years of the World's economy evolving
Main problem is completely non-user friendly of crypto currencies. Bitcoin is a very simple thing - you have a wallet, number of transactions in your wallet and button to send funds to someone else. Bitcoin was like this since day 1. Ethereum right now is not usable at all. How i suppose to explain it to my mother? In default client always distract me from counting money and sending money. First screen - smart contracts? Okey... how to use it? Even hello world is 20 screens of documentation and involves many weird things like copying "compiled code" or visually comparing hashes. And in couple of years there are no useful applications on ethereum - so why bother to learn things? If you are working in some organization that needs/wants to use blockchain - sure, open sources of ethereum, start your own nodes over kubernetes and try to implement something. But your work will never go to a any public ledger - there are no reason to do so.
Stop waiting for perfection and learn from your mistakes – Amazon CTO
> There's probably a reason why there is only one intelligent species on Earth, and it isn't pretty.

ONe intelligent species on Earth? So you are assuming most animals are moving objects without any thought or emotion?
Yeah I couldn't stand Three Body Problem - far too slow and uninteresting - and don't get the popularity of it at all.
I agree. If a culture makes the effort to become space faring then it seems likely that either they had a preexisting motivation/goal, or the experience would change them.
Something that has always puzzled me is why only GA follows the saner approach to push all the function calls in an array which the async loaded script can pick up later. Many of the popular analytics solutions (like, Segment, Mixpanel) create a factory function that initialises all API calls with a generic body. It seems rather unnecessary and only adds to the boilerplate. Take a look at the GA's init code and compare it with Segment's [1].

[1]: https://prnt.sc/fpj9ec
Aside from many 'theoritical' reading suggested by others here, I found that this tutorial is incredibly helpful: https://medium.com/@lhartikk/a-blockchain-in-200-lines-of-co...

I myself have also made the PHP version of the code implemented there. You could see it here: https://github.com/azophy/naivechain-php

Hope it helps
Same here. Facebook will just make you loose your time and fill your brain with useless data.
It's now called GraphQL. Let me explain.

First, the need for data has moved from the server to the client side in API-centric architectures. The backend is often just a dumb HTTP layer on top of a (sometimes relational, sometimes not) data persistence. Heck, I even built apps without server, using PostgREST.

Second, on the client side, we don't need an object-oriented interface to the datastore, because JavaScript. But we do need a powerful declarative query builder, and static data types to build up on. GraphQL provides that.

Third, if the purpose of the ORM was ever to abstract the SQL dialect of the database, GraphQL has resolvers, which turn a GraphQL request into a request for the database of your choice. So it does that job, too.

Last, for the data crunching jobs that you decide to do on the backend, you often need specialized data stores (event store, document store, full-text search index), and ORMs don't address that. And since these jobs are often resource intensive, you need the best performance - therefore falling back to raw SQL in most cases.

ORMs were a good solution for the kind of software architectures that were used for the web in the 00s. Since then, we have different needs, which require different solutions.

Disclaimer: I was the maintainer of a popular open-source PHP ORM [1] for 3 years. I no longer use ORMs.

[1] http://propelorm.org/
ShadowBrokers sent out First dump and threaten to dox former NSA hacker
Filtur |Compares Supplements and Vitamins
$1.1 billion ... slight chance I could make the same money today by doing a blockchain-Tumblr ICO...
The reason why the arguments spell isogram is because you can't have two arguments with the same letter. So they chose the most meta isogram, "isogram." Surprised the author missed that and assumed it was just reference to the script itself.
Other fixes would have been possible. If the hash table could be resized when necessary there would never have been a performance problem.
Nobody has mentioned the dependently type prog-lang Epigram† yet?

“Epigram uses a two-dimensional, natural deduction style syntax, with a LaTeX version and an ASCII version. Here are some examples from The Epigram Tutorial:

Examples

The natural numbers

The following declaration defines the natural numbers:”

( ! ( ! ( n : Nat !
data !---------! where !----------! ; !-----------!
! Nat : * ) !zero : Nat) !suc n : Nat)

“The declaration says that Nat is a type with kind * (i.e., it is a simple type) and two constructors: zero and suc. The constructor suc takes a single Nat argument and returns a Nat. This is equivalent to the Haskell declaration "data Nat = Zero | Suc Nat".”

Project lives here: https://code.google.com/archive/p/epigram/ and the last commit on https://github.com/mietek/epigram2 is five years ago which leads me to believe that the project is abandon-ware.

† https://en.wikipedia.org/wiki/Epigram_(programming_language)
Documented, including the official unminified source, in Google's analytics.js reference: https://developers.google.com/analytics/devguides/collection...
Right, look, This guy is doing everything that is being asked of him for the price agreed. None of the more wonky ethics of the situation change that, and I don't subscribe to the belief that he owes the company anything more then his fair-priced labor.

The only thing he is doing wrong is under-utilizing his own talents and potential productivity, for which the optimal solution is for him to find a better job. As he seems to indicate that the current options are to stay working 1-2 hours of work or be highly to be unemployed, I believe he seek to preserve his employment in future actions he may take regarding disclosure, and wait for a better opportunity to present itself.

If it's ultimately a choice between providing for him and his son and not, its pretty much no choice at all, ethics be damned. I know which outcome I would prefer.
It was vistaprint, so item pricing is similar ($5-50 typically). The confounding issue is that because everything we sell is customized by our customers, they may be less sensitive to small differences in page speed. (If it takes 15.5 minutes instead of 15 minutes to design a business card end-to-end, maybe that matters less than a web or product search.) This was also 5-years ago, so our mobile experience was very much limited to order/account inquiry and everything else we steered you heavily back to desktop.

Our analysis (for this project) was also limited to session and repeat session analysis, so we would have excluded any effects related to long-run increases in sessions from distinct shoppers (organic search traffic increase or cross-shopper recommendations). I believe those were small enough to properly ignore.

I'm definitely not arguing that page speed is bad, but do question the gospel that every 100ms is worth X% more traffic and conversions.
If you want to be even more disappointed, have a look at Xerox PARC technical documentation about Interlisp-D, Smalltalk and Mesa/Cedar workstations.
Page cache and disk cache are quite shared between containers...
CA is a not really a valid/possible thing in the context of CAP. The original phrasing of the theorem was poor and the "choose 2" myth persists. You can choose to (or accidentally) give up C or A but you don't get to choose to not have partitions. Not being partition tolerant doesn't really make sense (you're just broken?) if partitions are going to happen. A better phrasing of CAP is "in a network with partitions a distributed system cannot be both consistent and available." (note: this doesn't guarantee that you are one of C or A, you just can't be C and A.) You can see that definition used in formal treatments, e.g. Theorem 1 in https://users.ece.cmu.edu/~adrian/731-sp04/readings/GL-cap.p...

(Briefly, note that the original article is critiquing that definition of availability in practice which is legitimate but not relevant to this sub-thread.)

What I'm saying is that EC is most definitely NOT a requirement of physics/the speed of light (what your original post claimed.) The speed of light only sets a (theoretical) limits on how fast you can implement a consistent system.

The original Paxos paper ("The part-time parliament") uses an analogy of a quorum of parliamentarians occasionally getting together in the the same building and agreeing on something. Of course it being the same building is arbitrary and doesn't actually matter, but it's easier to intuit that the speed of light isn't an insurmountable road-block at that scale.
The author has a twitter account with 70k tweets, so I think that should qualify him for shit-knowing citizenship in the "on-line" community.
I come from a heavy C# background. I can say that MS has been revising their Entity Framework platform and it's a perfectly good ORM tool to use.

Being stubborn and old-school, I prefer the lower level roll your own approach for speed and efficiency. That said, if dealing with an enterprise application where ease of code mendability/adaptability is key, I'd happily go with something like Entity Framework.

It would be interesting to see if code generation tools have progressed in this domain at all. I remember several data layer class generators which although not exactly an ORM, could provide many of the same benefits.
Judges refuse to order fix for court software that put people in jail by mistake
systemd has had close to 1000 contributors now (as recorded by git), with 30-40 active per month. Higher than I imagined.
https://www.openhub.net/p/systemd
Proprietary stuff comes and goes. These are merely the latest in a long line of proprietary APIs. They were not so "little" in their time as well. This seems to come and go in cycles; maybe the new generation of developers will come to realise the folly of vendor-specific lockin just as the previous one did.

These new APIs will either stand the test of time and become standards in their own right (POSIX, after all, is codifying existing practice from multiple vendors). Or they will die with the end of life of the products using them.

It's worth noting that POSIX is the fundamental basis of all these products. It's not perfect, and there's certainly room for new revisions or even a complete replacement in the longer term. But open standards are worth fighting for any using, given the alternatives. We got the current open standards through it becoming a requirement that vendors provided them and supported them, and that came from grassroots developers pushing for it. The current big players will eventually have to do the same, and we can all play our part pushing them to do so.
Fantasque – a programming font
The signals propagate at the exact speed of light, but you're on point on the risk being minimal. Space is big.
That is, until those people realize that they most likely will need that assistance at some point of their lives (child birth, major health issues).

EDIT:

To expand a bit, my wife is currently in one of those situations. A government program allowed reduced social taxes for small businesses (<5 employees, <720EUR/month wage). The place my wife has worked for the past 5 years has been like that (her first workplace).

Now, with a child underway, we came to realize, that the social benefits she will be getting before and after birth will amount to maybe few tens of EUR/month (compared to 60% of previous wage when full social taxes are being paid).
Derma roller: Remove Acne scars- fine lines- stretch mark and MORE
I've bought well over a hundred O'Reilly books over the years, and after 2002 or so, I bought almost all of them as DRM-free PDFs. But in recent years, I've only averaged an O'Reilly book or two per year, because they've been slow to publish books on new technologies I cared about.

I find that, with few exceptions, Kindle programming ebooks are annoying and unpleasant. Some of the "textbook"-mode ones (where you can highlight diagrams and not just text) are tolerable on a Chromebook in tablet mode, but just barely.

And there's no way I'm going to pay $399/year for Safari, not when I'm currently spending $0-50/year, and certainly not for the privilege of using what people tell me is a mediocre mobile app. So going forward, this means that I'll buy maybe one O'Reilly book every other year through Amazon.

Does this also mean that O'Reilly is no longer going to be offering "early release" books for people who don't buy Safari? I think that something like 90% of my technical book purchases in the last 10 years were early release.
Because progress is the net result, directly or indirectly, of the work of everyone living in that society. When you pay taxes, when you buy things, when you select which products to buy, you're contributing.
Google’s Elite Hacker SWAT Team vs. Everyone
What have you used PostgREST for?
I really do think curiosity is the most important bit out of all this.

If I see some bit of our code doing something a bit odd, I'm nosy, I'll go and look why. Why does one of our classes use an IDisposable? Why is that property using a custom class? Why is that code using async/await when it looks like it should take nano-seconds?

If it's for a good reason, you'll have invariably found a gotcha, or gained a little more knowledge about the domain you code works in.

But surprisingly often you'll find that it's for a bad reason, or an outdated reason, or someone not really understanding how the functionality they're using works.

In the early days of a language/framework especially, when people really don't understand how it really works, what you see is a lot of cargo-cult code. Doing without understanding. .Net, Jquery, Ruby, Javascript, Typescript, Node, I've seen it happen many times (and of course done it myself too! I remember making loads of pointless singletons in one project a decade ago).

People do something because they don't have the full picture. They make up totally wrong rules like "If I add IDisposable the GC must work better as I believe IDisposable has something to do with the GC so it can't hurt".

A great example right now, in the .Net world, is people are littering their code with async/await. They can't understand it's making their code worse, not better. They don't understand that the performance gain is almost always negligible, but the code complexity increase is expensive.