skysight-inc/HackerNews huggingface dataset:
That's a good point about the risk not being in control of the officer through something like skill. Though, I don't think that changes the essence of my point, which could be summed up as diminishing returns. If we had a much higher rate of officer fatalities, then I would say pursuing this technology makes sense. But I think the resources can be allocated better elsewhere.

Totally agree that the mere presence of a gun being an alarm bell of sorts is the biggest issue here.
Hello World in Mavo – create web apps using only HTML [video]
Rhino 5 Crack and License Key Free Download [Win and Mac]
http://www.bankofengland.co.uk/publications/Documents/quarte...

Cash will be around for a fair time yet, but you have a point for any form of regular or recurrent expenditure. As the above pdf explains 'hoarding' of notes as a store of value seems strangely popular...
Tells you how dead TFS is.
Google Cloud Source Repositories now GA and free for five users and 50GB storage
A human eats maybe 2500 calories per day, right? That's about 100 watts, I think? That's a pretty serious restriction.
> "what is the definition of post quantum" where a lot of people call 1995 or so after Shor "PQ"

I use the term quantum-resistant, which I think is more clear: crypto for which Grover's algorithm or Shor's algorithm cannot efficiently break it.

> The algo in your linked paper is very convenient. However its newer and not as seasoned

Totally agree, but it does show that you shouldn't just assume quantum-resistant crypto is necessarily computationally expensive.

> I'd like to see a proof that there exists no possible theoretical quantum speedup against LWE.

Don't hold your breath :). We don't even have a proof that integer factoring can't be broken in polynomial time in classical computers. We don't even know if one can make public key crypto unbreakable to classical computers (equivalent to P vs. NP problem). And the relationship of BQP (problems solvable in polynomial time on a quantum computer) to P and NP is still an open problem. It could turn out BQP=P, and quantum computers don't even give an asymptotic speedup over classical computers (I don't think that's likely, but it hasn't been proven one way or the other).
Maybe when spaceships will not be based on rocket engines.
That said, at the moment it seems difficult to see what could do better than a ionic engine, given the huge margin of progress there exist in this area.

Also the main problem is not a new propulsion technology, but a new energy source, passive like in solar sails or active like in liquid/radio-active rockets.

After thinking about it, the origin of this expression may be the difficulties there was to understand how the combustion chamber works. Actually they had to create instabilities to obtain a stable exhaust jet.
Databases from finite categories
MQ shines in async calls/event delivery. gRPC / http2 / websockets / thrift is better for synchronous calls ?
Intel Extends Advanced Analytics to Grand Challenge of Genomics
I would pay money to see a video camera of Linus' face reading this article. I think we'd probably get impossible new shades of the color red heretofore unknown to humanity.
Because thanks to the extreme cautiousness of Bitcoin developers who have abundantly communicated the (small) risk of accepting zero-confirmation transactions to the public, people have generally heeded the advice of waiting for at least 1 confirmation.

But in reality, if it is OK for a shop to tolerate the risk of credit card chargeback fraud (which is real and is exploited every day) then it is OK to also tolerate the risk of accepting a zero-confirmation Bitcoin tx. Notice the language I use. "Tolerate" doesn't mean "annulate", but "accepting some degree of risk that can be controlled."

Of course the downside of this cautiousness around zero-confirmation transactions causes people to think Bitcoin transactions are slow, when it's not true. They are as fast as, if not faster, than CC transactions.
Technology and Car Companies Are More Intertwined Than Ever
> No more crypto, no more NSA. It's that simple.

Not at all, they will still record all your comms to make sure you aren't spying on the US. Also keep producing malware, etc.

> DLP will also be the death of AES and any ciphers based on S-Boxes.

Source? The PDF you linked says nothing about AES and it looks like it would if this was true.
Killing a congressional inquiry into America’s high transit construction costs
Background music does not work for me (Fx/Win10). Devtools console says "Unsupported sample rate : 48000"
Or maybe more accurately a Japanese feature phone like this:

https://www.engadget.com/2015/03/13/japan-loves-feature-phon...
I think the tide is turning against this type of interview. The industry is starting to notice how ineffective and stupid it is. The big tech companies don't care and will continue doing it because success hides all failures. When there's an endless flood of new college graduate applicants and near-monopoly positions bringing in billions of revenue, nobody cares if the hiring process is bad. They will care someday if those conditions change, but that's in the distant future. Most companies, especially small companies, are not in this position and should have a different process. It's becoming a competitive advantage, especially if a company is looking for senior engineers, to not have this interview process. For example, this list of companies was in a HN story a while ago: https://github.com/poteto/hiring-without-whiteboards The trend is growing and it's a good change for the industry.
TL;DR: D is faster than Python.
Gave it a try. I like deeper integration with social services, but I'm not too excited that it's primarily just a shortcut to the app's chat feature (which I don't really use, honestly).

I was hoping that it would let me send signed/encrypted tweets, or Gmail messages right on the page. Is that within the scope of the project, or is everything meant to happen from within the app?
Until you've produced a sample. Then some statistician can write a paper on it and someone takes it to the supreme court and 20 years later they will decide that there was probably something fishy going on.

Like I know?

But if you compound different systems, like the ai handgun thing and dont store the data in the same place, it becomes exponentially less likely that suddenly 2 critical systems failed at the same important moment for some reason.

the real issue with police brutality is the fact that it is, in fact, legal, and police is trained to respond in such a way. what protesters get wrong about police brutality is that its supposedly illegal. it is not. most instances of police killing someone are actually legal. which doesn't make it right. but its legal. saying somethings illegal when its not just makes you look like an idiot.

people need to protest for better laws, not getting individual cops sentenced, because that wont ever happen with any kind of regularity.
That is not entirely truth. Bullied kids often become bullies as they grow older and stronger. When people with authority abuse the authority, the kids are likely to mimic it once they grow. It does matter where the hardship comes from and whether kid understands it.

Also, generations that grew up during bad times (like war) had higher criminality rates then later happier generations. People from bad socioeconomic situation had worst results then spoiled middle class kids. While you are not serving your children well by spoiling them, too much hardship has worst statistically measurable consequences.

Yet also, I remember some humiliating experiences that ended with me not willing to try activity that lead to experience - ever. Or at least not when someone is looking.
This is sort of what I'm wondering. Are the compile times as good as Go? Is the GC as good as Go, or do you end up having to do manual management to get similar performance to Go? What is the build tool ecosystem like (I found Go's to be the one part of Go that was not easy to pick up quickly)?
> Mark Walton overlooks one of the strong points

I think his main point is, if you really want such a phone, you can have it for much less, even from the same vendor (with the Nokia 150 that goes for 20 instead of 50 bucks).
Anyone who wants a 3310 can buy a real one on Ebay for less than twenty quid including postage.
It is very telling. Google has a cloud supercomputer doing nothing but building code to support their devs. I don't know about Facebook. (I really don't -- I'm constantly amazed that they have as many engineers that they do, what do they all work on?) Where I work (https://medium.com/salesforce-engineering/monolith-to-micros...) there's a big monolith but with more push towards breaking things up, at the architecture level and also on the code organization level. We also use and commit to open source projects (that use git), so to integrate those with the core requires a bit more effort than if they were there already but it's not a big burden and the benefits of having their tendrils being self-contained are big.

Which brings me to the point that in the open source world, you can't get away with a single-repository approach for your large system. And that also is telling, along with open source's successes. So which approach is better in the long run? I'd bet on the open source methods.
See GRPC for a common alternative to HTTP. Kafka and Kinesis are common event buses.

But message queues are usually an added complexity for realtime inter-service messaging.
> that was essentially just a bug

I'm not sure that's right, everything was working correctly, it just didn't read out a low-probability move very deep.
Thanks! I picked that up after reading a lot of SCSS on GitHub.
nit/rant: I think it would've been better if JsonNet was named differently, since there is "Json.Net" and googling for "JsonNet" find it (or looking at say ht.algolia.com).

It's not that critical to the project itself, just naming and discoverability.
When you can't even trust your own Blood Boy [1] not to get stoned, eat twinkies, and write a tell-all expose about you, how are you supposed to hire an employee trustworthy enough to handle all of your most sensitive keys and information? (Let alone three of them, one for each company.)

[1] https://www.theverge.com/2017/5/22/15676696/hbo-silicon-vall...
Photo printer that uses AR to create moving pictures
It's not the standard version of the game. If computers were consistently beating the best in the world in blitz chess but not standard tournament rules we wouldn't say that "chess is solved".
No, corporate notwithstanding, even lots of purely logical things still need some form of ugly hackery to get it to work right.
A 10 year old PC carries 2.1 GiB/s (= 17 Gbps) over bog standard pipes without tuning or parallelism, as measured by "pv /dev/zero | cat > /dev/null". Uncompressed full HD is 1.5-3 Gbps. (Less actually, since codec output is going to be 4:2:2 or similar)

Yeah, you can come up with high bandwidth scenarios like stereo VR 144 Hz 4k HDR running on barely capable hardware. But 99% of users don't require such tricks and never see any upside from the performance-over-security compromise.

Even if you decide basic IPC is not fast enough, a shared memory buffer for raw frame data is reasonably secure too.
Desktop Twitter-lite application
That's irrelevant. As an advertiser, you WANT people who don't want to see ads to run adblock. Because you don't get billed for those impressions from people who wouldnt have bought anyway.

Adblock is a problem for publishers, not advertisers. Adblock actually helps align advertisers with consumers.

If you've gone to such great lengths as to installing adblock, you're probably pretty proficient in "exhibiting anti-marketing behavior".
Well it's interesting then, that I have come across more situations like that, working as a software engineer, than when I was doing typical retail jobs. The software industry sure is great, isn't it.
I remember that, in the 90's, you'd often get new UI elements in Office releases that then would eventually move into Windows. There was a technical reason - the cross-cutting - but there also seemed to be a marketing reason - the moment those UI elements became part of core Windows, all developers (yours truly included) would be able to use those elements, effectively negating Office the fresh look before the competition.
> has poor support for numerical computing.

The issue comes from being lazy by default.

When you are writing lazy functional code, you essentially build up a system of thunks[0] that collapse to a value when you need it. This works great for abstractions like infinite lists, or essentially only paying for the value you need. Unfortunately, they are kind of expensive (I believe they are usually implemented as a tagged union, where they are either a value that is returned immediately or a pointer to another function or thunk) when you don't need the laziness. In any sort of numerical computing, you are usually dealing with enough values that you lose a lot of performance when dealing with these thunks. Working around this is doable with a bunch of strict annotations (so that these thunks are immediately collapsed to values), but that is only half the battle: you still need to reduce the immutable function applications to a mutable version so you don't lose out by copying your values back and forth in memory, and you don't do a bunch of unnecessary calculations. All this requires "a sufficiently intelligent compiler" or a lot of compiler hints and peering into Core: the intermediate language of GHC. It isn't for the faint of heart.

There have been a bunch of work on avoiding some of this: hmatrix[1] is a lapack and blas library for finally doing the calculations once you have reduced the graph, "subhask"[2] is a standard library for Haskell that attempts to add some support for basic numerical work and "numerical"[3] is a library that I believe is trying to make a well typed linear algebra library (I'm not sure if it is going to call into hmatrix/blas/lapack or not). The issue with a lot of this is that until there are good tools for this kind of thing, no-one does serious numerical programming in Haskell, and there are only a few people working on the tooling because there aren't that many people trying to do serious numerical programming in Haskell.

(note: I'm not an expert in this, so don't depend on any of this for love or money. I'm sure someone will come along and tell me how I'm wrong.)

[0] https://en.wikipedia.org/wiki/Thunk, https://wiki.haskell.org/Thunk
[1] http://hackage.haskell.org/package/hmatrix
[2] https://github.com/mikeizbicki/subhask
[3] https://github.com/wellposed/numerical
Also git rerere

When maintaining multiple release lines and moving fixes between them:

Don't use a bad branching model. Things like "merging upwards" (=committing fixes to the oldest branch requiring the fix, then merging the oldest branch into the next older branch etc.), which seems to be somewhat popular, just don't scale, don't work very well, and produce near-unreadable histories. They also incentivise developing on maintenance branches (ick).

Instead, don't do merges between branches. Everything goes into master/dev, except stuff that really doesn't need to go there (e.g. a fix that only affects a specific branch(es)). Then cherry pick them into the maintenance branches.
> A resource-hungry 3D game or similar does not fit into my definition of “app”.

Interesting. Why not just say "There are categories of apps that my argument doesn't apply to"?

> You can push updated JS, CSS, HTML, fonts, and images directly to all of your users without needing to recompile the app’s binary and getting App Store approval.

That's a benefit to the developer. It's only a benefit to the users to the extent that the developer's and users' goals coincide. I strategically refuse to update certain software on my phone. Software that doesn't give me that choice usually ends up uninstalled, because it usually changes unexpectedly in a way that makes it unsuitable for my use.
chess is nowhere near as popular as it was in the 1980s, and chess clubs have been declining for some time.
Humans should just use more power. But they can't which is why machines are superior.
Kubernetes supports a microservices architecture through the Service construct and performs rudimentary L4 load balancing and more.

But it doesn’t help with higher-level problems, such as L7 metrics, rate limiting and circuit breaking.

This is where Istio comes in.

Disclaimer: I work on Istio.
Pretty cool, some advice:

- Add loading bars of some kind

- Some of the older content send me to 404 errors[0]

- It's not clear what the value-proposition is (why should I use this over Google New?)

I'm actually working on something similar, albeit targeting a completely different market:

https://projectpiglet.com/

Of course, I'm trying to track all the content myself - which has been interesting.

[0] http://tracket.com/url
SICP is arguably the best source to learn the core concepts from. (It uses Scheme.)

https://mitpress.mit.edu/sicp/
Predictive of what?

Edit: I've read studies that found psychological benefits from a single use of LSD, six months later. Anyone able to comment on whether or not this is true for mushrooms?
I agree. I also don't like the fact that my "likes" are being sold. One of my friend took a snapshot of an ad featuring my "like" an ad about "Asian Dating" website... How embarrassing!
Thanks for the heads-up and backstory. I didn't know this article had this kind of history here on HN.
Samsung Foundry unveiled aggressive roadmap scaling down to 4nm
triplebyte mentions taking a particular problem from CtCI and solving it within 30min on a whiteboard (pen/paper, plaintext editor).
Yeah, this article is practically begging for a snide response from, say, Jacobin.
That's a far cry from VC funded startups. There isn't a real equivalent to Silicon Valley, for example.
Kind of agree, but if you look at the curriculum of universities teaching game development degrees, they have all moved into Unity/Unreal, plus the console SDKs.

Also the love they are getting from MS and Google for VR/AR.
Its too bad https://www.mowglii.com/itsy/ stopped being developed (for understandable reasons). That was lite, vs a browser in a frame.
Turn your iPhone into a vintage Macintosh
You might be interested in this:

https://mikegerwitz.com/projects/git-shortmaps/about/

It creates the aliases as you do, but also includes tab completion, and only takes effect when you're in a repository path.
This represents simultaneously everything that makes me hopeful about WASM - a really clean, fun and nice game that performs super well - and everything that makes me dread it. I was curious so I opened up https://www.funkykarts.rocks/demo.wasm and there's nothing there that I can really read and learn from. I'm not saying it isn't worth making the trade, but it seems like a fundamental change to a part of the web I really loved - the ability to read and learn from things you experience that are cool - that doesn't seem to be considered very much and it makes me a little sad to see its inexorable end spelled out. I think I'll soon miss the days where we all had to show each other our code on the web.
> new accounts can't downvote either; you have to build 100 comment points -- which keeps that group think going

At least they're more generous than HN's downvote restrictions. But I suspect it's the upvote limitations on voat that turn newcomers off more than anything, since every other site encourages you to handout 'likes'/upvotes like candy, making it quite the culture shock when you run up against that wall.

That being said, it's hard to tell whether any of these voting mechanisms are actually any better at producing fruitful discussion than a plain old-school forum. Seems to me like having any kind of voting inevitably leads to amplifying the effects of group think.
your videos on algorithms with hacker rank really helped me a lot. I just thought I'd take this chance to thank you for that.
Some Businesses Bleed Black
Great Post! Most people understimate the depth of simple-looking tasks: it's not just managers that make this mistake. Even experienced engineers can end up not realizing all the complexity in the beginning.
It is a bit perplexing that neither the review, nor any of the comments are mentioning ruggedness and reliability, which were the reason 3310 became a legend.
If it is similarly enduring, the 50£ price tag might not be that stupid after all.
> As an advertiser, you WANT people who don't want to see ads to run adblock.

No, you want people who wouldn't​ act on your ads to run adblock. The degree that that correlates with "people who don't want to see ads" is far from clear.
Publishing encrypted tweets wouldn't work too well with the character limit and all, unless I suppose we use images and OCR[0].

For things like encrypting emails inline, we could explore it but I'm not convinced it's a good use case: To get all the benefits of Keybase (identity verification, key/device provisioning, improved encryption over PGP), the recipients would also need to have Keybase installed which means you could just use Keybase Chat instead.

[0] https://twitter.com/shazow/status/605748307688890368, https://github.com/Lukasa/entweet
Perhaps they meant predictable? If so, I'd be inclined to agree.
The pain increases with the square of the number of files and to the fourth power of the dependencies between specific versions of them.

I'm not sure a big repo is a wise thing, even though I understand it may make sense for multiple reasons for a company, understanding it may damage brains far more sophisticated than mammalian ones.
That's excellent news! I've been using the macOS version all along (and happily paid to upgrade to the new version that came out recently), but I've definitely missed the iOS version.

On a side note, much as I love the app, the circumstances behind it being pulled came across as shifty. Whatever actually happened, I hope it never happens again.
Thank you for your opinion and explanation.

As long as proxies remain transparent to services, I see no problem. It becomes a problem, when proxies are getting smarter in terms of providing cross cutting features, like routing on payload level (not speaking of message headers) or do authentication and authorization on a per-resource level. That puts constraints on how services are built in this particular environment.

But I see the logic behind approaches, developed by Netflix, and now Istio. If you have a lot of services, orchestration and more central communication management is probably a good way to govern, if the constraints (described above) are accepted and services still have the ability to opt out and pursue a different strategy.

The old SOA world was driven by governance. This was a result of the general engineering methodologies and mindsets of this time. Still, API Gateways / smarter proxies / etc. could bring that back...
I'm so outdated when it comes to memes, so forgive me but: Isn't this particular frog lately associated with racism and intolerance?
I agree with the principle of equal opportunity, but I disagree with the implementation. Providing the "opportunity" to buy stocks on margin to people with less than $25k in their accounts is more like selling cigarettes than selling education.

Just today I noticed a sign posted in the window of my corner store, "Customers of [convenience] store won $1,490,823 from [state] lottery in 2016!" I wish it were required to post the total paid as well. It'd be much better for the public if the sign read, "People in your neighborhood paid $3 million to the state lottery and only won $1 million back."

Similarly, if the brokerage is going to offer margin accounts, they should post easy to understand statistics on how much customers earn and spend. A nice histogram showing returns with sliders to select a bucket for initial amounts invested and proportion bought on margin.

Enforcing free information access is another way that governments can help provide equal opportunity.