skysight-inc/HackerNews huggingface dataset:
While I agree with a lot of this as well, I feel like downstream packaging has a lot of issues.

I'm working on a project (licensed under the GPLv3) and I have decided to be my own maintainer, i.e: building and distributing packaged versions of my project all by myself:

1. my project is young and unknown, I have no choice but to package it myself (I really like AUR by the way);

2. it lets me write and maintain step-by-step documentation;

3. it allows me to enforce a consistent interface for my project across operating systems, I know my project can be used the exact same way on any operating system I have packaged it for;

4. I have had bad experiences with maintainers having no idea what they are doing and completely breaking my software;

5. It allows me to build a full release pipeline including both source and binary releases.

The first point is sort of a big deal, having packages is important to drive adoption, therefore I need to invest my time in that. I'm not gonna wait for some random folks to package it a few years down the road (if that ever happens).

My work is not incompatible with downstream packaging, but I do intend to work closely with (or directly maintain) any downstream package.

I really feel like this is sort of a catch-22.
I am offended by this kind of headlines.

In the field of software, Apple uses open source and provides a lot of open source of their doing to the community. So, if there is an imbalance in the field of science, it should be discussed for sure. But if I am offended by Apple's Photos, it is for other reasons.

Edit: my comment refers to the top headline of the article, also used in the link from Hacker News when I wrote it "Why Apple’s Photos announcement should offend you"
The main reason for not turning off notifications is the fear of missing out, decisions being made without you. And it's a very valid fear.
The syntax looks awful? It looks extremely clean. It cleaned up the JS syntax enormously...
They should build one on the Moon.
Chat input is typically single-line, submit-on-enter. Messaging apps seem to be transitioning to optional multiline but the default action for enter still seems to be submit so it's perfectly reasonable to use <input> for chat input.
Ponylang. Just seems to fit my mental model well. Wish it was more ready for prime time.
The _effect_ of what you do (make an "impossible hash") is the way, as far as I know -- whether its vipw, passwd -l, whatever...

Regardless -- I'm not trying to diminish your solution, nor Linux; I elided over the usermod example in the grandparent (didn't recognize it at all), but interestingly, as I look on my NetBSD system,there is a usermod(8), with a -p for already hashed passwords. As I test it though, it rejects '!' as an argument:

# usermod -p ! jnk
usermod: Can't modify user `jnk': invalid password: `!'
Valgrind calls that an indirect leak (stuff that wasn't freed at exit but is referenced by stuff that also wasn't freed)
> I think this is a very common refrain in small startups. If the business side can't sell it, it must be that the product isn't good enough yet.

Correct, but fwiw, and speaking as a techie/marketer/sales I've more often than not seen this happen when the techie founder is not involved in the sales process at all, so methinks the blame is largely shared between the founders - you can't just blame the sales if whoever might be able to say "hey this is super complex, are you sure you need it now?" is not around during the discussion.
Official announcement from the Internet Archive's Twitter account: https://twitter.com/internetarchive/status/74316536307288473...
> Not all school admins are smart enough to disable password saving

So how would allowing a small percentage of web apps to disable autocomplete resolve this? It only makes it slightly less painful for the websites where autocomplete is disabled - everywhere else you have the same problem. You're asking the wrong people to solve this for you here.
Read the wiki page on it, run through the psuedocode on pen and paper a few times and then implement it.

Source: I did this when I wrote a library for reverse geocoding which uses a kd tree.

https://github.com/AReallyGoodName/OfflineReverseGeocode
Another comment from them: "Site is down for hosting a mayor [sic] amount of ISIS stuff."[1] They also tweeted about bringing down several other supposedly ISIS-related sites. I'm guessing they're not aware of what the Internet Archive does...

[1] https://twitter.com/AttackNodes/status/743170229426094080
Magic Gears Grid
Ask HN: What do you think about To Round Task Manager Telegram Bot?
Hey!
We created Telegram Bot for To Round Task Manager. Please, let me know your opinion about our bot (at)toround_bot
What do you think about Telegram Bots? Is it future or not?
Well, inline chat, like IRC is generally a single-line input... though I suppose you could use a textarea rows="1" and strip \n on paste, etc, that wouldn't be too bad as you're likely listening for \n to post the message anyway.

Either way, not using a typical name/id for the text input would probably work better in terms of not getting suggestions...
On the other hand, I am happy to pay for a machine that I know will work perfectly with Ubuntu. I have neither time nor patience with broken linux installations, if a company can guarantee a set of hardware that works under Ubuntu(or any other distro) would be happy to pay for it.
I would phrase it is that it is hard to recruit a good "biz" person - there are plenty of bad biz people out there.
This is the correct answer.

Jokes aside, ES2015 hits the sweet spot for new powerful languages with big-name backers (facebook is compiled in babel).

https://twitter.com/amasad/status/631251607422787584
That would indeed be the norm for forums. But not for chat. Real time chat is typically more usually a single line entry. Having auto-complete on that is irritating and utterly spoils the UI.
It depends on the vendor. I negotiated a pretty big agreement a few years ago and were able to get the vendor to agree to hold data for a year after termination. We also backup to another provider.

That said, over the years I've witnessed all manner of billing and payment fuckups. I'm not trying to say that cloud is bad -- but that billing snafu is a risk factor that you need to understand and account for.
True but NTFS is also far superior to HPFS, so arguably MSFT doesn't need a replacement for NTFS nearly as badly as Apple needs a replacement for HPFS.
Consider the fact that Google open-sourced pioneering RAPPOR when it started using it for collecting information about malicious websites visited by the users on Chrome. Apple on the other hand is collecting far more invasive data about keystrokes while hiding the details of implementation. Why should we trust whoever apple trots out at its keynote? How is this different from people who trusted Theranos since its board was filled with former secretary of state and such.

Apples approach towards research and privacy is designed to make press headlines and fool reporters similar to Theranos. Its time to hold Apple to standards of Peer Review as practiced by Google, Facebook and others.

https://research.googleblog.com/2014/10/learning-statistics-...
Are you actually allowed to go to a courtroom in the U.S. with banners? I find that strange.
"Why Apple’s Photos announcement should offend you"

What a click-baity article.
LOL, love this header on the pricing page: "Enterprice"[sic].
Its science... all experiments have their methodology questioned by critics. These points are coming from the distorted views of Intelligent Design advocates in hopes to take advantage of peoples ignorance of how science works, a tactic that sadly seems to work well.

Edit: again, read TFA
Should be "3rd party hosted server architecture" or "SAAS dependent architecture". It actually means more servers.
We at Dgraph use Trello as well. TBH, the commenting on Trello is primitive compared to Discourse. We still comment on Trello when we're talking about specific cards -- but if it needs thorough discussion, we always go to Discourse.

In fact, it's pretty common for us to create Trello cards out of discussion at discuss.dgraph.io.

Also note that we keep our Slack only for general chit chat. As soon as something becomes more "structured", we switch it to Discourse. We also actively encourage people to just create topics there instead of bringing it on Slack in the first place.
In our user management portal, whenever tech support opens the Create New User or Reset User Password page Chrome helpfully fills their administrative password into the user's password field.
This looked interesting at first sight (considering I work on ORC & Hive) - the single machine configuration with TinyLog and the aggregate indexes look good[1].

But the more I look into the distributed storage section, the more corners I see cut in the data consistency section.

"There are no quorum writes. You can't write data with confirmation that it was received by more than one replica. If you write a batch of data to one replica and the server with this data ceases to exist before the data has time to get to the other replicas, this data will be lost."

"The reason for this is in case of network failures when the client application doesn't know if the data was written to the DB, so the INSERT query can simply be repeated. It doesn't matter which replica INSERTs were sent to with identical data - INSERTs are idempotent. This only works for the last 100 blocks inserted in a table."

"Failover is automatic (for small differences in data) or semi-automatic (when data differs too much, which may indicate a configuration error)."

"When the server starts (or establishes a new session with ZooKeeper), it only checks the quantity and sizes of all files. If the file sizes match but bytes have been changed somewhere in the middle, this is not detected immediately, but only when attempting to read the data for a SELECT query."

These sort of network blips and bad disk problems happen every week at least once on a big cluster and something like hadoop wastes a lot of IO doing bit-rot checks on cold data all the time.

The nature of clickstream data makes it somewhat okay to lose a few chunks in transit - I can imagine at least a few of the beacons will get dropped purely over the HTTP mechanism which pumps data into the system.

At some point, the data consistency costs money, slows down inserts and creates all sorts of limitations on how recovery of data would play out.

But as a general purpose replicated DBMS which serves as a system of record against fraud allegations (for instance), I can't see this comparing well.

[1] - 200 million rows/sec for join+aggregation is ~2x as good as Hive 2.0 single node LLAP on a hot run (https://people.apache.org/~gopalv/LLAP.gif)
I think it has more to do with institutions that lack ladders for people to climb. Who can dream of becoming a politician or a banker? Such realities are closed to most people.
Agreed with all of this, but it's hard to imagine the licensing was truly insurmountable.
I mean, somewhat literally. Here's Internet Archive's HQ (and where the servers live): https://en.wikipedia.org/wiki/Internet_Archive#/media/File:C...
Talking mostly about things like:

// 1.
[a + b] // [a + b] is an array
{[a + b]: c} // [a + b] is not an array

// 2.
{ x, y: x, y} // inconsistent object fields

and there are more examples. After you get to know the syntax, it can be used for good -- but some decisions are making the language more complex.

As written above, I enjoy its new features
> Have you measured how long typical terminals take to respond?

Arbitrarily long. Consider that a user might run your application over SSH via a high-latency network connection. Better to just handle it asynchronously. Your input loop needs to watch for escape sequences anyway, so watch for that one and process it when or if you see it.

Sadly, that only works for interactive screen-oriented applications, not run-and-exit command-line applications that want to use color.

> Regarding the third point, it might be a good idea to just feed it to XParseColor and process it from there.

That assumes you have libX11 and an X Display available. The former is a heavy dependency for a CLI application, and the latter requires you to connect to the X server.

I'd suggest just manually handling the common case of "rgb:R/G/B" (where each component may use 1-4 digits and requires scaling accordingly), and then deal with anything else if your users actually encounter it in the wild.
Based on the OP you would use:

<div style="display: none;">
<input type="text" name="phone" autocomplete="honey-phone">
</div>

The way I understand it, it's not that autocomplete can't be turned off, it's that "off" no longer turns it off. You can still turn it off in plenty of other ways.
Wow, zero-drag satellites are a really elegant idea!

https://en.wikipedia.org/wiki/Zero-drag_satellite
This needs more exposure.
Is that all? That's a pretty generic reason IMO.
Euro 2016: Όλα τα λεφτά το Γερμανία – Πολωνία
Over-scheduling children during the summer is unnecessary
> I've noticed this attitude is widespread among marxists: glossing over differences between businesses, or the products they offer. To a marxist [...]

The author doesn't appear to be marxist in this article. It's interesting that you gloss over subtle political distinctions in this particular comment.
Try getting key-person insurance for a solo startup. A cofounder is cheap by comparison.
Fantasy Meets Horology-Miki Eleta’s BY 21Dez12ME
In the olden days, before AWS, you'd just log into your console as root and fix it.

Now there's no console.
> whats so bad about it?

Other than executing a lot of useless instructions, causing pipeline stalls due to indirection, potentially mispredicted branches, etc. I guess nothing.

Just remember if the actual operation is just a few instructions, the price for all that extra work can be 1-2 orders of magnitude.

If you only need to chase pointers say a million times per second or less, go for it. It won't matter so much. In worst cases you might lose 10% (of total cpu core capacity) performance, if even that. If it's in tens of millions or more, it's pretty likely to be a significant bottleneck.

What does your profiler say? What kind of ILP you're getting?
That's one of the reasons I love arch, it has AUR. Don't like packaging, just create your own.

> Really? Then what about this poor sap who had the misfortune of releasing one buggy minor version

Can't you do a minor do a minor version upgrade? Even the stable distros do updates all the time, just nothing major.
None, because the existing languages were close to good enough for the problems that I try to solve. There's nothing that's opening up new frontiers in a mind-blowing kind of way, at least not from where I stand.

But some languages are kind of interesting:

C++11/14, because it opened up some new ways of writing efficient code safely.

Haskell, because of HM types.

Lisp, because of homoiconicity and macros.
lies?

a) 48 vaccines are 48 types of virii... at least one is a UFO, if not all.

- they are strip miners, and cause devolution (a quick google shows since they 4x'd the vaxx rate 1980 the avg height dropped, marriage rates dropped, abortion rose 400%, miscarriage rose 400%, prison rates rose 400%, mental illness rates rose 400%, autism rose 1100%, breast cancer increased 400-1000% and testicular cancer increased 400-1000%) (btw theyve 48x'd the vaxx rate, almost n^2 every 5-10 years and its a 1.8 trillion dollar profit loop every 60 years for them)

test for yourself: look at your arms, wheres your ufo? look deep inside and say "wheres the ufo"? or say dont show me where the ufo is. reverse psychology works well

my theory is germs are cryptids (deer, rodents, bugs) and some (just some!) virii are ufos (able to spread galaxy cell to galaxy cell)

b) theres a ufo sighting on video every week in south america

c) ex sec def canada paul hellyer testified usa is allied with aliens, youtube paull hellyer testimony

ex-navy phil schneider says blue aliens live underground (yes blue, like the hindu/mexican demons) youtube phil schneider

theres hundreds of famous and credible people who testify aliens exist, hundreds of videos of creatures on youtube

(also im banned from HN and reddit for saying this, and for talking about the mercury toxicity of vaccine)

d) there are reptilian skeletons in the museums, google images "kappa skeleton"

e) there are hundreds of reptilian sightings, on video, ex: "hex county reptilian" "lee county lizardman", youtube: "thailand reptilian" and "son doong cave reptilian"
Tips on Error Handling
Another possibility would be to add two fields dynamically via JS at load, the first populated at load with a timestamp when the form was loaded... then add onkeyup/onfocus/onclick events for the other form fields, and when triggered populate the second field with the current timestamp.

From there, you can compare the numbers, offset from the current time, and do other checks. I mean, you might want to allow for up to an hour of drift, but most people won't sit on a page for an hour then hit submit.

Though it would be circumvented easy enough, if it's custom, would worry less about it.

Also...

<div style="display: none;">
<input type="text" name="phone" autocomplete="section-honeypot nofill" />
</div>
The main reason for not turning off notifications is the fear of missing out, decisions being made without you. And it's a very valid fear.

One team member going away from Slack is bad for the member and for the team. If everyone else participates and you're on the sideline, then you're an oddball and not a team player.

For it to be effective, the whole team has to willingly move away from it.
It'd be nice if HackerNews put a star or something by headlines that have changed. I was really confused about what you were saying until I read your edit.
> they encourage authors to make up random, nonstandard values for the attribute

No, they are encouraging you to give more meaning to your fields. For the example given of a CRM app, using customer_email_address as the input field makes much more sense than using a standard value for email address, as the two fields are asking for different things: The latter always wants your email address, whereas the former wants the relevant email address for the record you're viewing/editing.
Definitely not. ZFS was primarily focused on spinning disks. Take for example the fact that the project discarded block indirection early on: the resulting random reads would be basically fine on SSDs and debilitating on HDDs. Ditto TRIM which is still not (IMO) fully baked in ZFS.
But Netflix was just a distributor then and not a creator. The biggest problem in this is middle men. People want to pay the creators for their work, but there are layers upon layers of middle men that end up getting a far larger slice of the overall pie than the people who actually create the stuff. With the technology we have and systems similar to (but more open than) Netflix, we should be able to have a proper compensation mechanism.
Not sure about OP, but I certainly feel this way. When I want to learn a new language/framework I work on a project using it; instead of watching videos I mostly use the docs and Google/SO when I get stuck or have a code design question, possibly watching/reading any seemingly interesting videos/articles I happen to come across along the way.
> Their contribution to WebKit is the only reason there is competition in the browser space

There have been competing closed-source browsers, plus Mozilla, that weren't dependent on WebKit. Without Apple's open-source work on WebKit, maybe Google wouldn't have done Chrome (or maybe Google would have forked Firefox as its starting point, instead), but there'd still be browser competition.
How's Picat performance-wise?
So don't use autocomplete? I still don't understand your point.

It's not like leaving it on you are forced to use it. The client still has the choice. By turning it off you are removing choice.

If your Administrator is too stupid to stop messing up and using autocomplete where it's not appropriate, then I think the correct action here is a pink slip.

I generally agree you should try to keep users from shooting themselves in the foot, but not at the cost of hamstringing users who may want to use things differently.
I didn't say I want an entirely bleeding edge system. I said a bleeding edge ubuntu, by which I mean keeping up to date on the non-LTS track (I updated my original post to say that, because I can see where the confusion lies here).

Out of the 2500 or so packages installed on the computer I'm typing this on, I want about 10 of them to be bleeding edge. Maybe 20.
Nim because of the syntax, performance, and base library.
According to OP the maintainer fairies will come and package your project!

It doesn't even need a Makefile. They will create one for you.

(They need to package the 3870 other requested projects first, though https://www.debian.org/devel/wnpp/requested )
Lately?

C# triggered by:
- Open sourcing of .NET
- Open Sourcing of Xamarin

I want to live in a world where writing mobile apps for multiple platforms with a single codebase becomes the de-facto way of doing things. C#/Xamarin seems like the only viable way to achieve that.
Expected utility has a lot of nice properties and is the simplest decision system that's completely consistent. Other decision systems tend to have flaws that can be exploited to take all their money, if you are allowed to make bets with them.

However expected utility has really weird edge cases. Like Pascal's Mugging - events with essentially infinite utility and infinitesimal probability. These don't occur very often in everyday life. But programming an AI to follow expected utility to the letter, might have some weird consequences.

If you allow slightly more complexity, you can get decision systems a bit more complicated that avoid this problem, and are still consistent. E.g. "median utility". This itself has problems, like ignoring slightly unlikely outcomes that are really bad or really good. But you can fix that too by adding a bit more complexity. I wrote about how to do this here: http://houshalter.tumblr.com/post/129690629075/against-expec...

This system might be preferable to expected utility. E.g. if you were to play a lottery that had a jackpot so large the expected utility was positive (even after adjusting for the logarithmic utility of money.) It still might be preferable to not buy just to buy just one ticket, because you will still almost certainly lose. But if you had the option to buy many tickets, the odds of winning might increase enough to be worth it.
Lincoln Presidential Library Digitizes First Televised Presidential Debate
Stop submitting your Android N name suggestions, Google’s already found one
Pinterest acqui-hires team behind smart keyboard app Fleksy
I think you are underestimating how hard it is to get those guarantees, how much some people want them, and how long we've needed them.
One thing I don't understand in your post: given how ridiculously far away these black holes are, how could you possibly even dream of triangulating them with two facilities on Earth via parallax...?
Their ... 'English' is just atrocious to read.

Install and https enabled, no any coding, support Windows server and Linux server;
DV SSL certificate that up to 5 domains with one year period;
But it's important to point out that

1) That $1.1 billion was for two facilities

2) LIGO underwent a huge upgrade over the last decade, making the instruments tremendously more sensitive, and the cost of this upgrade is included in there as well.

So I suspect that building a third facility with the sensitivity of the two existing facilities would be a much more affordable endeavor. The first time around is always the most expensive.
I felt the same way, which was why I went Raid-Z2 (dual parity) with two hot spares configured... even had a spare controller next to the box. Still, lost it all.