skysight-inc/HackerNews huggingface dataset:
Hi! We have just released our free chat widget to facilitate and boost customer communication through messaging applications. To install the widget, you will just need to create an account, connect your Facebook page, add your WhatsApp number, your Instagram and Telegram username.

You can choose which channels you want to add and if you want them to appear on desktop, mobile or both. If you like it, you can also change the widget icon with a picture or a GIF .

Copy and paste the script into your site and you're done! To do so, you can use Google Tag Manager or paste the code in before the end of the section of your website.

After 24 hours, you will be able to see statistics on unique visitors / visitors, clicks on the widget, clicked channels, devices and localization straight from your dashboard.
I'll accept that if there's a vote that doesn't affect you, and you aren't qualified in the particular area, then you may not be adding much by voting, I don't think you can extrapolate that out to not voting at all, which is what my original parent was suggesting.

I'll go further and accept the mere possibility of you being able to vote prevents the very worst outcomes.

I'm doubtful you would knowingly have a worse than average opinion though, Dunning Kruger (and the reverse) I would guess, would dominate, so if you think you're worse than average, that would make you better than average, and make you duty bound to vote to cancel out the guy who thinks he knows better.

Question.
If I created an index and tracker that tracked low carbon companies, and that tracker voted against things that would increase the carbon intensity of it's businesses, would that tracker still be passive?

I would say yes, it is still tracking an index, and its following simple rules to further the aims of that tracker, and by extension, it's investors
GC (of the kind where an external context walks other thread machine stacks) definitely falls under implementation-defined :-).
The People's Republic of the Future
You left out sense of humor. https://www.youtube.com/watch?v=rnMsgxIIQEE
Kinesis is not necessarily well-suited fan-out. It is very well suited for fan-in (single consumer, multiple producers).

Each shard allows at most 5 GetRecords operations per second. If you want to fan out to many consumers, you will reach those limits quickly and have to implement a significant latency/throughput tradeoff to make it work.

For API limits, see:
https://docs.aws.amazon.com/kinesis/latest/APIReference/API_...
I'm generally against adding interactive features to CLI programs if there isn't a good reason for that. I don't want to remember which options I can/can't use in a non-interactive script.

Plus youtube-dl already has multiple GUI/wrappers, so there's already a separation for interactive features.
Indeed, it's not on the near horizon. I found this article illuminating:

The Case Against Quantum Computing - https://spectrum.ieee.org/computing/hardware/the-case-agains...
You saysomething about turtles... No wait, wrong smalltalk.

Seriously though, small talk is fleeting. You pick a generic subject (Something like: what's up? How are you doing? (if the person is doing something interesting) What are you doing? How does it work? Why are you doing that?). Just ask questions, don't get too personal at first. Pick up on clues, ask about what you hear. Keep it light. Backchannel a bit ("oh, I see", "uh-huh", nod, etc), but don't overdo it.

Oh, and practice, preferably with people that you know well.
What you described is not essentially different. It's the same phenomenon with {0, 1} (classical) and [0,1] (bayesian).

What makes bayesian reasoning interesting is its dynamics, how does evidence change beliefs? But does it even make sense to talk about posteriors associated with classical deduction?
Practical Quantum Computing is in a quantum state where it's at the same time around 10 years away and never gonna happen.

(To be serious: That's roughly true, you'll get credible scientific opinions on both. What's not true is what you occasionally read: That we're almost at a state where quantum computing will be a mass application.)
> ML makes predictions; testable predictions.

Well, no. ML solves the classification problem, not the prediction problem.

E.g.: The "is this a cat picture" problem is effectively solved, but we _still_ can't reliably predict something as primitive as a simple binary proportion.
Perhaps, but also a huge number of public OSS projects.

To take an example of a large OSS Project hosted on Github: The Microsoft .NET Core framework[1].

If I want to contribute a code change - their guidelines require me to submit a pull request on github.

If I want to submit an issue - their guidelines also require me to log the issue on github.

This is not unusual for most OSS projects which use Github as their central collaboration point.

Today that's all A-OK for Chinese devs. The scenario discussed is if the trade-war extends, and either the US or Chinese governments block access to Github for Chinese users.

Now, perhaps it's easy enough for someone to set up a mirror copy of everything in China - but that's going to limit or block collaboration. Bug fixes, changes, issues - they're not going to get across as easily. I can't email a pull request to the .NET CoreFX team saying "Hey, I fixed this".

This is going to lead to fragmentation of popular OSS projects, and will be an overall net-loss for everyone.

[1] https://github.com/dotnet/corefx
Same goes for your country

Technically
It's a good analogy as long as Intel was the first to experience the end of Dennard scaling (https://en.wikipedia.org/wiki/Dennard_scaling) because their fab lines were ahead of the rest of the industry's. And fabs are all "semis", due to the massive amounts of capital and talent needed to move to the next node.

So much so that we're now we're down to two companies in the whole world who are successfully executing the smallest CPU nodes, unless Intel manages to make their "10nm" work, or pulls off their "7nm".

While we're hearing the very roughly equivalent TSMC "5nm" node is starting risk production (https://wccftech.com/tsmc-5nm-production-euv/ beta testing, you might say, someone outside of TSMC has to be the first, second, etc. to try to get real world dies that work on a new node). Intel isn't saying anything, but Semiaccurate has reported at least two fab lines that were slated to move to their 10nm are installing lots of EUV equipment consistent with using them for their 7nm node (and at least one fab moving back to 14nm).
A few years back I decided to start a new colourscheme in Vim which I called “bland”. It started out with reverting all of the colour and term portions of syntax/syncolor.vim, and using black (#000) on white (#fff) (I had hitherto used a dark colourscheme, but decided to try a light one), with keywords bold, and that was it. After a week of that (a deliberately enforced delay), I succumbed to adding a little bit of text colouring, #cc0000 for strings, #009900 and italics for comments, and for no particularly good reason #0000cc for numbers. I added pale background colouring for diffs too. It’s grown a very little more complex since then, but not much. I haven’t ever switched back. I made a dark variant of it last year for the odd occasions where I want a dark colourscheme. Then it’s primarily white on black.

Most colourschemes out there are absurdly low-contrast. Part of my inspiration in finally getting round to making this colourscheme, and going for a light background, was experience several years earlier of using Vim on a not-too-bright laptop on a bus with substantial sunlight: I always had to switch to a dark-on-light colourscheme to be able to read the code at all.
That's very interesting. Please, if you have any stories, photos or anecdotes to share, do so.

> He loved the work so much that it gave him ulcers.

I can well imagine. It sounds like the sort of process that only works if someone with great amount of expertise and passion ensures that everything is accounted for. I've never tried to relocate a building, but I assume that any sort of problem quickly cascades from "oh dear" to "oh sh*t" with little to no warning and no possible recovery.
100% agree. The other thing they don't do is worry about failure. Mistakes are a necessary part of learning. Screw up? Fix it and move on. The last month or two I've been deliberately doing things that I'm hesitant to do, and it's really starting to sink in just how important all of this is.
To give you an idea where I come from... I started doing front end in the late 90s, and for the past 5 or so years I've been mostly doing SPAs with Vue, React, Inferno, and Angular.

I'm done with SPAs and the whole modern front end workflow. If there was a solid benefit to a SPA it would make sense to endure all the complex development, ever changing ecosystem, etc, but in the vast majority of cases there is no benefit. Users don't care about SPAs, some of the most successful biggest websites are not SPAs (Amazon, Ebay, Wikipedia, etc).

A static site generator like Jekyll with some sprinkled JS offers a much better experience. When that is not enough a good old server side rendered app with sprinkled JS is the next step I will consider.

There are some perfectly valid use cases for SPAs but those are rare.

And don't get me started on libraries/frameworks figuring it out as they go along. jQuery has had a stable API and methodology like forever. React has made major changes in only 5 years. From createElement, to JSX, to classes, to stateless components, to hooks, and only god knows what they will come up with next year.
Oh yeah, the current version of HN's Dropbox trope. How many years have we had this argument? Since the birth of SPAs?

"You may not need SPAs" is just another "considered harmful" series of cliches fishing for upvotes.

These folks always talk about making the site accessible for everyone by: taking out fancy scripts, images, colors, animations, etcetera; but their sites are the ones that get no traffic, nobody wants to read, nobody wants to use, all that.

Maybe our customers don't want stupid simple shit, on account that it's stupid simple. Even the hypotethical 3rd world user, which everyone loves to cry big fake croc tears about, is using Whatsapp, is using Facebook, Instagram, etcetera.

The only place people know anything about NoScript, let alone convince them, is here. And I hate HH It's one of the worst-looking, hardest-touse to use sites. It is certainly not a paragon of good design, no matter what the ancient neckbeards say.

Just look at the size of those voting arrows. It's ridiculous. How many of yall give downvotes by accident? And all this price to pay for nostalgia?

P.S: This whole "most sites don't need an SPA" angle is just plain bullshit. Anyone with real experience in our industry knows that.
Refer to the example I posted as a reply, above.
I always download with "-f 18".
The multi-armed bandit problem (2012)
As far as I know birds eat them. A lot. But then again, birds eat other stuff, too.
When you are done designing your Webpage, disable JavaScript, disable CSS (if your browser supports that) and check that you are still able to grasp what you want to present your visitors.

If you then don't find the relevant information in the first second, congratulations, you just made a page which is useless to people with old Screen-readers.

I may be old fashioned in this regard, but i only see JS as a Add-on to the text you want to get out and only use it to add functionality which would be impossible with html and css alone. e.G. to give a hint when there are new articles to read, or when a article has changed.

Comment sections for example don't require JS at all, but you can use JS to make it needless to reload the page after you send that HTML Form.
Compare the manpages for find and walk.
Clips from such comedy shows pop up out-of-context in the recommended bar in you tube. Did I turn on a channel?
I wouldn’t be bold enough to call myself a programmer but I have created a few websites and apps which I could have bought a house from the proceeds. I’m not boasting, just trying to give a sense of scale. In the past Some programmers have laughed at the approaches and the ‘framework’ I use.

So to answer your question experience has taught me there are some who do while there are many who talk.
Yes

https://news.ycombinator.com/user?id=alankay1
Lawsuit claims Cento’s prized San Marzano tomatoes are impostors
My vote is for IRC
What happens when a private company makes an error and causes a catastrophe, like an asteroid crashing on a city? The only precedent of that scale I can think of are Nuclear plants accidents. Usually the cost is shared by everyone, even by the people who opposed that particular technology exactly due to these risks.

When a private company takes risks that could negatively impact non customers economically, I feel some of this risk should be reflected in the price, or in taxes, in order to create an accident fund. In many cases this would make the adventure non competitive.
U.S. Army on Twitter: “How has serving impacted you?”
Gogs comes with all the friendly web interfaces and the "stuff beyond the repository" things.
I agree with you. It's always easier to ignore comments than to not have them and trying to figure out stuff.
I vastly prefer a 100 line function with comments every ten lines about what is to happen next to twenty, five line functions with "great" names (they never are), that are sprinkled about the whole file making the whole thing a case study in reinventing the goto statement. Though it often seems many people consider the later to be "better" and "self-documenting" code.

To be fair though, three line comments for every member seems a bit excessive to me as well.
I wasn't, single instance in the same subnet with persistent work queues.
> we Europeans do not (may be rarely have) have locked/carrier controlled phones.

I think it's fairly common with subsidized pay as you go phones (at least in the UK), since the network has to earn back the subsidy somehow. With phones on a contract, it's not necessary since you're locked in to the contract, but even so, it at least used to be the rule that the phone would be locked to the network, but they would provide the unlock code once your contract was over.

EDIT: Yep, turns out all the major UK networks (except Three) lock phones:
https://www.ofcom.org.uk/phones-telecoms-and-internet/advice...
Because it made it easy to create inspirational posters and social media posts/avatars/covers. Its simplicity of creating a "good enough" design is what got non-designers registered, myself included.
Most companies in the US monitor everything. And you probably wouldn't know, things like intercepting DNS are not obvious from users end. Many monitoring tools hide themselves like malware.
Yes, if external actors rather than the self-organizing teams own the process, that is probably the first response, but that won't actually stop the buildup of tech debt and the velocity impacts, though it may produce a one-time, non-repeatable improvement, so even in that case if someone (even the wrong actor) is monitoring velocity and doing process improvement, there will be an impetus for further change.

(Of course, if the wrong actor is monitoring velocity and controlling process, then the team has an incentive to mask the effect of tech debt but continuously adjusting estimates to maintain the illusion of constant velocity, a d avoid the first bad response, or, if that opportunity is missed, to avoid the subsequent external interventions.
PPU is used as 'Picture Processing unit', essentially the graphics card of older 2d consoles.
You can sign up with facebook + there is a free 30 days trial.

I wouldn't be surprised if a lot of people just signed up to check it out and if a lot of other users registered multiple times with different emails to have access to the free trial.
I think there are a lot of similarities between F and C as there are with the use of military time. In the US we use AM/PM for civilian use but in England you see them use military time for things like TV show times, and train/bus times. It all seems very regimental.
Where would you get a printed encyclopedia that's current? The only encyclopedia that I've heard of that's still actively being published is World Book Encyclopedia and that's meant for grade school children. Even the Encyclopedia Britannica released its final edition in 2010.
https://ferd.ca/queues-don-t-fix-overload.html explains it better than pretty much anything I’ve read on the topic.
That’s six years of difference, though. That’s not a fair comparison.

How much has x86 performance increased over the past six years?
wtvanhest, not that I know of. It's hard to collect good usage data without nagging people. I hear from small business owners, the occasional accountant, and I have the impression there are other business/institutional users that don't interact.

Distant future is hard to predict but here I go:
hledger or any good parts of its design are still around and still providing value.
Any past data kept with hledger is still readable and easy to convert, with or without a working hledger.
Highly polished and efficient UIs are available everywhere they're useful.
Data import and multimachine syncing are routine and just work.
Data hygiene/security and personal privacy are routine and just work.
Performance is high, "big data" is no problem.
Resource usage is low, these tools continue to work in the turbulent and resource-constrained future.
There is a strong global community of financially literate, capable, empowered, prospering individuals and organisations using efficient high quality universally available accounting tools to promote, enforce and create widespread transparency and societal insight in finance, business, politics and every ecological issue.
DJI will add airplane and helicopter detectors to new drones in 2020
I agree that learning the DOM API is an important core skill for web developers. But not that you should avoid using jQuery.

jQuery, or something like, it will be around "forever" because a core problem it solves is inherent to the DOM API.

("forever" actually means for the foreseeable future, projecting out where trends will take us in the future.)

The core problem is, there is no DOM API... there's a collection of DOM APIs which overlap (a lot) but that have various differences from browser to browser and from release to release. Just as importantly to software development, the wholly stable parts aren't really a single API either, but a group of APIs with a lot of duplication and variation in the patterns and idioms used.

For good software of any complexity, you're going to want to build as much of your code as possible in terms of a simple, concise, consistent, stable foundation and the DOM API is not those things. It doesn't have to be jQuery.

(BTW, I'm mainly talking about application-level code here. For utilities, plugins or other lighter-weight libraries, NOT requiring a separate library is a significant advantage. And your DOM access may be limited and well-defined so that a vanilla approach isn't burdensome.)
Yes obviously, but there is added functionality from a service like github/gitlab. Pull requests, issues etc.

We wouldn't be using and paying for a service like Github if git had all the features we want/need.
This strikes me as a good, but incomplete, taxonomy of comments.

What about comments that describe our assumptions? I guess that's a special-case of 'what' comments. Such comments are often better expressed as assertions in code (i.e. adding more code to improve readability, rather than reworking the code). Assertions have the considerable advantage that they don't go stale as the code is changed.

> although sometimes git blame will

That's a great point. Detailed commit messages are a good way to record the 'why' points. Unlike in-code comments, they don't bloat and dilute the source. Of course, they're also less immediate. (I guess I'm not sold on comment-folding as an answer to this.)

It's also a point in favour of fine-grain commits. If you squash your commits, 'git blame' becomes less able to help you track a line of code back to its original motivations.
Multilingual Named Entity Recognition: Research to Reality
My wife. Reserves. Two tours in Iraq. PTSD.
I've worked with SQS at volumes in thousands of messages per second with varied (non-tiny) payload sizes.

SQS is a very simple service, which makes it fairly reliable, though part of the reason for the reliability is that the API's guarantees are weak. And it can be economical, but I've had to build a lot of non-trivial logic in order to interact with SQS robustly, performantly, and efficiently, especially around using the {Send,Receive,Delete}MessageBatch operations to reduce costs.

With the caveat that I think my use case has been quite different from what's discussed in this article, here are some of the problems I've encountered:

- Message sizes are limited, but in a convoluted way: SendMessageBatch has a 256KiB limit on the request size. Message values have a limited character set allowed, so you need to base64-encode any binary data. This also means that there's not exactly a max message size; you can batch up to 10 messages per SendMessageBatch but not in excess of 256KiB for the whole request.

- If you want to send more than 256KiBx3/4-(some padding) or around 180KiB of data for any single message, you need to put that data somewhere else and pass a pointer to it in the actual SQS message.

- SQS does routinely have temporary (edit: partial) failures that generally last for a few hours at a time. ReceiveMessageBatch may return no messages (or less than the max of 10) even if the queue has millions of messages waiting to be delivered; SQS knows it has them somewhere but it can't find them when you ask. And DeleteMessageBatch may fail for some of the messages passed while succeeding for others; it will sometimes fail repeatedly to delete those messages for an extended period.

- The SDKs provided by AWS (for either Java or Go) don't help you handle any of these things well; they just provide a window into the SQS API, and leave it to the user to figure all the details out.
The Barnum Effect: Use Flattery to Instill Belief (OR Why Quizzes Work)
Huawei banned from using microSD cards/slots, it wont faze them though
Would you tell your wife/partner someone is flirting with you?

We all know the job market lives crazy times right now; but if you mention you are getting recruiter calls, It might backfire.

Better use that calls to know how to advance your careeer, which skills are un high demand, and use that info wisely.
> Why should it be named uggstralian now?

Because "ugg boots" is now a trademark, therefore unavailable for everybody else, whereas "hamburger" is not.

Can you provide a better name?
I haven't really detected anti crypto, sentiment. Theres many (most?) people who are bearish on crypto, and I would count myself in that number. And when I say bearish I mean Bitcoin won't be worth $Xmillion and be used for some meaningful portion of trade anytime soon.

Actually, I think banks launching their own crypto currencies could be the one of the best chances they've got. I assume the banks have identified valid use cases for them. The ironic thing is they sacrifice the supposed advantage of crypto currencies, which is their decentralisation.
It's also a common tool for non-designers who maintain their own websites. I heard about Canva through my girlfriend who used it on her Android phone to build banners, buttons, and other graphics for her Wordpress site.
Austrian Chancellor Kurz Ousted After Nationalists Turn on Him
Essentially postgres SKIP LOCKED worker queues DELETES an item from a worker queue table, does the relevant work, and if the work completes ok, commits the deletion.

The SKIP LOCKED bit means that once the queue item has been grabbed FOR UPDATE, it cannot then be grabbed FOR UPDATE by any other queries, so it has an exclusive lock on the worker queue item.

It's pretty robust and works fine for servicing multiple workers.