skysight-inc/HackerNews huggingface dataset:
> That has nothing to do with PGP. You could do the same by base64-ing an OTR session (in fact, people do that all the time).

But PGP also works for printing stuff on a post-card (or you know, email) - asynchronous communication. While Axolotl does push OTR-like modes towards asynchronous use - they do involve a lot more than getting hold of a public key (say, one published in a magazine, or shown in a frame of a movie, or...).

There's been an argument since the early crypto-wars about whether gpg/pgp could (should) be made easier to use. And I absolutely think it could (and should).

Key distribution is still hard, but it's not helped by a silly cli app, and no great recommendations on how to manage trust (I suppose the gist is: get a hw token for your key, print a backup and store a revocation order in a safe, sign keys you trust and upload them to the keyservers. But even if that list seems easy, users are left with questions like: which hw tokens should I use? When I lose it, "re-trusting" keys? How big a problem is it that I've just exported meta-data about who I communicate with? Which clients easily integrates with my hw token so that I can use gpg on my smart phones, my laptop and my desktop? What if my phone lacks NFC? Can't use USB host? And last, but certainly not least -- why isn't there a fork of gpg2 that does "the right thing(tm)" out of the box -- and make this "best of breed" flow easy, rather than making all kinds of sub-key shenanigans equally cryptic?)
>They are fully democratic and focus on producing empowered self directed citizens who understand how to share limited resources and cooperate.

The more pertinent question is whether the citizens they produce can read and write, know how to multiply and divide, can name the parts of speech, and have at least a passing notion of the history and culture of their respective countries, regions, and locales.

Somehow, I doubt it.
Don’t Punish Journalists for Software Problems
And by asking everyone to remain perpetually solemn, the war never ends.
This was a learning project for me. I changed careers from doing animation last year, and used this project to learn coding, React, using webpack, using linux, Docker, building a api(which reformats an Amazon api), setting up servers, ect.

Sorry if this is not impressive enough, but I learned a lot making this.
Well put. Serendipitously, Dan Dennett and Sam Harris just discussed this last week and released the recording of their conversation[0].

The conversation was interesting and disappointing.

Harris argues that the commonly-held notion of 'free will' is nonsensical. Dennett doesn't disagree but worries that people may construe this to mean that 'all bets are off' and the world will descend into chaos. Harris attempts to explain why this would not be the case; that we'd still have good reasons to imprison people who want to do harm. Dennett agrees but then restates the same worry differently. They never manage to get past this.

Still, a good listen.

[0]https://www.samharris.org/podcast/item/free-will-revisited
You're completely correct, but we take that further in modern medicine. We synthesize, adjust and target particular drugs, even though they might have originally stemmed from "natural" sources (as if some molecules are natural and other aren't...) so that it is more effective for particular use-cases. Treating penicillin as traditional medicine is being disingenuous, considering traditional medicine also "prescribes" keratin from rhino horns as useful...

My point is that generalising both traditional medicine and "western" modern medicine misses the mark. Treat everything on balance, specific to the medicine in question, not the class it came from, in my opinion.
I'm inclined to agree that there probably aren't any great reasons why you would benefit from FreeBSD rather than Debian, but just to correct one misconception:

I don't have GBs of free memory for ZFS

In the early days of ZFS it required many GB of memory -- it was developed for Solaris, and designed for servers with lots of memory. But it has improved dramatically since it first came to FreeBSD, and people run it with far less memory these days.
It's only a matter of time until wage slave becomes a more literal term..
yeah, how many homesickness..
FreeBSD is really cool BSD OS I like it. In other hand CentOS is my default Linux Server :D Debian is really cool OS too..
I tried freebsd. Gone back to ubuntu. In this day and age not having proper dependency resolution for packages is not acceptable. I've more than once had some tool based on ports just go into an infinite cycle when asked to upgrade some packages.

The philosophy laid out in this article seems more like rationalization of historical accidents more than anything else. Linux file system layout is just as predictable as anything else. Configuration goes in /etc, PID files and other such things go in /var, things local to the users go in /usr/local, cron related things go in /etc/cron.d, and so on and so forth. FreeBSD file system layout on the other hand makes no sense to me and the rc system is even more bizarre. Do I really need to specify "XYZ_start=YES" when upstart, systemd, and others have this stuff all sorted out already. Well not systemd so much but close enough.

Overall the BSDs are too low level for development and play purposes. For deploying proxies, caches, NATs, and other such single purpose things I'm sure they're great but anything else not so much.
>>wow... 5 years already...

Hah, my thoughts exactly! Time flies...
Juno probe: Nasa spacecraft successfully enters Jupiter's orbit
Web Components: I think that web components are absolutely the best way to program a web application. Keeping the CSS, HTML, and JavaScript within the boundaries of a component works wonders for organization. It was such a relief coming from the Angular 1 world I usually work in.

Polymer: The polymer elements that Google provides are good. The polymer-cli is fantastic, it just works and I didn't have to configure gulp/grunt/browserify/webpack at all. The project needs no node modules, all dependencies come from bower! Non-google custom elements out there lack robust browser support and I find that I don't trust them out of the box.

Ecosystem: support for web components has come a ways in the past couple years but still has a ways to go. Chrome natively supports web components but every other non-blink browser uses polyfills, which slows things down. Firefox and WebKit are implementing part of the web components spec, so hopefully it'll get better soon.

It's an exciting technology that is very pleasant to code in. Learning the ropes and building the entire site took 20 hours, most of that was dealing with nitpicky browser support issues with scrolling and animation effects. I hope it continues to gains traction and I would definitely use it again!
Do you find it disrespectful that the Axis can win in a game of Axis and Allies? Games are fundamentally open-ended by their nature. They cannot accurately represent history because history is not open-ended. That is in fact the defining characteristic of history, and it stands in direct contradiction to the concept of a game.

And this is an advertisement for a game. Complaining about it not being serious enough is not really that different from complaining that alcohol commercials don't show enough drunk driving accidents.
1. zfs runs well on a lot of systems. You might have to change a setting or two but it's not as you say.

2. pkg install and the related pkg utilities have existed for awhile.

5. systemd isn't and shouldn't be a requirement for applications going forward. Any application that requires it is limiting its portability for unknown reasons.

The joy of trying a new system is the little things you learn that you weren't even aware of before.
I might be. I just do not understand why one should use more complex and less accessible web technologies if it does not lead to new functionality. When I learn a new framework, it usually is so I can do things that I could not do without.
That's a little silly when you can find 10+ other retailers and sites that monitor price histories for just about any product to ballpark its actual market value.
Thanks for the tips. I think (1) is a good reason to switch but I am not familiar with the topic of (2) yet. I will do some more research & talk to people.
Not quite the answer, but well spotted! It still seems to be just KMS - we can do crypto operations in secure hardware as well.

Thanks!
Rust is more similar to C++, not Swift, here.

The distinction is in the programmer model involved. With Swift and GCd languages, you do not know about when the deallocations will happen, because this requires analysis of the whole program and the executions. You program with this in mind. Since GC/ARC is the only way to share, you end up using it often. The compiler can prevent some of this, but not the majority, because there isn't enough annotation helping it.

(There is this difference between Go and Java, too. Go is more explicit about sharing than Java, and needs annotations when you share things (* and &). Java does not. So while Java 8 is getting escape analysis, it can never be as good as what Go does or potentially can do because the compiler just doesn't know enough. Go also generally avoids sharing unless necessary, whereas in Java you will see things shared willy-nilly because the distinction only lies in the optimizer. These annotations aren't as fine grained as Rust -- they're at the same level as Swift, approximately, but I'm trying to give an example of the same annotation-drives-optimization-and-design thing at a different level.)

With Rust and C++, you know just by looking at a function what will be deallocated and where. C++ has API designers implement drop flags anyway (in the form of nulling the internal pointer, or something) for all types with a move constructor. The model of dealing with data changes; you explicitly think about where data comes from and how to share it. The additional annotation of zero-cost borrows (instead of just saying "Share this ... somehow", which is what Go and Swift do) means that zero-cost borrows will always be zero-cost, and not only if the optimizer decides it knows enough to be able to help.

Note that ARC is much much costlier than than pointer-sharing. Not directly because of the increments; but because dynamically allocating for every instance of sharing, and then accessing that allocation whenever you wish to do a read/write or bump the reference count; is horrible for cache performance. This can be assuaged with a tuned allocator, but is less efficient than the usually-to-the-stack borrowed references of Rust.

I will point out that Swift satisfies the academic definition of garbage collection and Rust/C++ do not, but I don't think terminology is as important as understanding what's actually going on.

Rust is "automatic", in a sense, agreed, but automatic memory management is a vague term that can mean anything.
Because reddit is blocked at work.
In the UK he would have had to have offered the candy bar for sale at $1,200 for at least 28 contiguous days in the last year.

But that's easy enough for retailers to work-around these days when they can ask suppliers for multiple UPCs for the same item
> The one coincidence that Oxfordians have to explain is how Vere wound up publishing under the name of this real individual, Shakespeare.

The other "coincidence" they need to explain is why all contemporary references to Shakespeare the playwright point to the Shakespeare from Stratford - from other members of Shakespeare's troupe like Ben Jonson, Heminges, Cowell. Nobody questioned his authorship till hundreds of years later.
Then it is not a democracy in any meaningful form, but a tyranny. It is insufficient with pure majority rule to form a democracy - democracy requires participation and at least basic levels of protection of all participants as well.

There are many ways of doing this, with various suitability depending on context, but e.g. one alternative is simply to guarantee the right of withdrawal - if you can always remove yourself from the group if a decision is unacceptable to you, a majority will need to seek compromise if it wishes to avoid shedding members. Other alternatives include requiring super-majorities for particularly important decisions, guaranteeing rule of law and basic human rights.
> 1. I don't have GBs of free memory for ZFS

ZFS does not require large amounts of RAM any more, unless you want to benefit from its impressive caching features and have large amounts of disk space.

> 2. I don't have GB of RAM, CPU and HD space to build everything from ports, and most importantly, no need.

Since FreeBSD 10, pkg-ng has been the standard. It unifies binary packages installable similar to apt and other linux package managers with your custom ports built packages as needed. Now you can mix and match seamlessly and there is no need to have an entire ports tree unless you have special needs.

> 3. License - I don't care. GPL is free enough for me.

Each to their own, but MIT and BSD are, to me, free-er and more friendly to business applications.

> 4. Base vs. Ports - Why should I care? Debian (testing!) is stable enough for me. Except for dist-upgrades, I never ran into issues, and then it may be faster to nuke the server from orbit. Now had BSD "appified" the /usr/local directory (rather than keeping the nginx binary in /usr/local/bin and conf in /usr/local/conf it would have kept everything related to nginx in a /usr/local/nginx) it would have been interesting, but now?

The layout you're discussing is basically what happens by default when things are `make install`ed most times without any customizations. The layout that you're lamenting makes sense enough and has merits, with no need to be "appified" -- that is what packages are for. Again, I implore you to check out pkg-ng, it is a core feature of the OS now.

> 5. systemd? The reason Debian went with systemd was (IIRC) because they didn't have the manpower to undo all of RedHat's work in forcing all applications to integrate into systemd (such as GNOME). I don't know how FreeBSD is doing in that regard

People are experimenting with alternative init systems in the BSD world, though we will likely never directly have SystemD, there are some efforts to support systemd unit files as well as some new directions taking into account Apple's work as well as lessons learned from systemd to build a BSD licensed alternative to all of the above.

> But FreeBSD?

FreeBSD brings to the table a free, cohesive, highly engineered and integrated operating system that is coming into its prime. There are a multitude of advanced features in terms of filesystems, networking, and more. FreeBSD has first class support in AWS and some other major cloud environments. However, FreeBSD has been and continues to be a server focused operating system. Even so, FreeBSD on the desktop is coming along, but it's certainly nowhere near linux in that regard.

In the end, each to their own, if you find a reason to like and use it, then great, but at the least you should look into it and learn what you can from it, like any system.
As a strong chess player (around 2000 blitz on chess.com) I find it very surprising that time was not the most important factor. I know from experience when you get to under 1 second per move remaining the probability of blundering goes way up.

In regards to the skill-anomalous positions, I'd have to look at the positions to be sure but my guess is that these are end game positions where the most reliable path to victory is not the quickest path to victory. In a winning position an experienced chess player will try to simplify and win reliably over winning quickly. The model might consider this a blunder because it gives up some material advantage, but it doesn't actually change the end result of the game. My guess is that given these positions where a lower skilled player allegedly does better, in reality the better players win a higher percentage of the time.
Shouldn't we stop storing configuration files at $HOME ? Most terminal emulators also start at $HOME by default which compounds this problem.
It's really not just a rationalization. BSDs control the kernel and the userland, meaning that file system layout is coherent. Check any Ubuntu installation and packages are all over the place. This is perhaps unavoidable.

Also, OpenBSD, DragonflyBSD, and FreeBSD can all be used as server or desktops without much fiddling. Their installers are better than anything in the Linux world. You can have one up and running with a nice wm, browser, etc, in 15 minutes.

They are more finnicky about hardware, but when you can buy a laptop for $200, that's not so much an issue.
Swift cannot implement ARC without conditional releases. Rust can. What Rust effectively does is compile an if statement into something a tiny bit more complicated (two if statements, really), in certain conditions. It doesn't need to. The if statement uses function-local information known statically, so it could be compiled in a different way without the drop flag. Basically, the condition already existed, Rust just inserts another one instead of piggybacking on the one inserted by the programmer. ARC needs new conditionals everywhere, and whether or not something will be cleared is often not obvious without looking at the whole program, and even then it could be undecidable.

I can't answer for Patrick, but I don't see the term "automatic memory management" as useful as distinction, I look at it more as a spectrum, and Rust/C++ fall squarely on the "more manual" end of that.
Linux is Python, FreeBSD is Scheme ;)
Ask HNs: How you disable the new Google search results page
Google has this new results page with white boxes on grey. I tried googling, but how do you go back to the old screens?
So far as I know, the only historical document that even suggests a link between the playwright and the actor is the preface to the First Folio, by Ben Jonson and (purportedly) Hemings and Condell:

http://www.shakespeare-online.com/biography/firstfolio.html

Even in this text, the connection is pretty artful. And the Elizabethan era is not exactly well-known for frank, transparent confessions in print. The Folio is a rather slender evidentiary basis for supporting a large breeding population of zebras.

You have to remember how status-conscious the Elizabethan era was. Imagine if a scathing academic novel becomes a bestseller, nominally fiction, but obviously a scathing roman-a-clef about the NYU English Department. But the name of the author, as shown on the book, is the name of an illiterate immigrant from Senegal, who happens to sell sunglasses on the pavement outside the NYU English Department.

A zebra would be that the immigrant is actually a brilliant writer, who has overheard many conversations among the professors. A horse would be that the novel is written by one of the professors, who asked the immigrant his name and thought it sounded cool. Or maybe was the immigrant's lover. Or maybe it's just a coincidence.

We are inclined to find the "zebra" version heartwarming and believable, because we believe in the American dream. Elizabethans did not believe in the American dream. They would have found the "country-bumpkin actor wrote courtly sonnets" theory preposterous, and paid very little attention to attestations on paper -- which were notoriously fraudulent. Today's professors have all kinds of problems in figuring out which Elizabethan actually wrote what.
I don't think the layout is coherent at all. Ubuntu layout is much more coherent. If I need nginx configuration I look in /etc/nginx. Following the same pattern if I need mysql configuration I look in /etc/mysql. If I need to figure out the actual daemon configuration for each I look in /etc/init. It's all very nice and tidy. Actual binaries go in /usr/local/bin or /usr/bin or /bin. That's pretty much all I need to know for any binary or daemon. This is not true in FreeBSD. So where exactly is the incoherence?
Regarding your point 5: Application developers embrace systemd (and thereby reject portability to some extent) because it makes it easier for them to not do infrastructure work. A description of that phenomenon in KDE can be read here:
http://blog.davidedmundson.co.uk/blog/systemd-and-plasma
I mean it in the sense of mother-tongue. It's like knowing Latin (to truly understand you own language) rather than struggling with complex sentences in native language. I've seen people who can hardly express themselves in their one and only language (Spanish and English in the cases I've seen).
Memento Mori.

I want to simply declare that the iMatix state machine generator (Libero) and cross-platform library(ies) (SMT/SFL) saved my project/company from certain destruction in 1996. And I never had the opportunity to thank you/him/them for that.

I'm a C guy, so admittedly old-fashioned, but I still use that FSM generator language more than twice/year. FSMs rock (I came from circuits) and this is the best business-language-to-compiled-software-description thing I have ever met.

Thank you.
I should've used Texas in my example. Apologies to the good people of Alabama.
> Swift doesn't have a separate processes managing memory during the runtime

Plenty of GCs don't have this. You can have cycle collectors and other GCs which run the GC pass on release events (depending on some heuristic) too.

This is a terminology issue, anyway -- in academia reference counting is considered a form of GC. In software often the term is used to mean "tracing GC", or sometimes "any system that can automatically handle retain cycles".

-----

This still doesn't answer why Swift has a wider range of possible applications, though.

I do agree that Swift is or will be better suited for development on iOS, because of good API integration. Rust can program for iOS too, it's just that you will have better support for Swift :)

But aside from that, Rust should be able to apply anywhere Swift does.
The amazing thing to me, aside from the inhumanity of the war and weirdly anachronistic things like the French cavalry uniforms and tactics at the beginning of the war, was that shell shock/PTSD/etc. wasn't recognized as a real thing, instead the armies would execute soldiers for cowardice. At least many of those have been posthumously (and far later) pardoned, not that it really makes much difference.
Must be how Sports Direct operates. Everything was at least 60% off at all times in that store when I was in the UK 2 years ago.
I wonder what PCs would be like if Intel bought Compaq in 1991 with people like Rod Canion and Jim Harris staying on. I think they were there when Compaq reverse engineered the IBM PC BIOS for example. Thinking about it, an alternative would be buying AST Research instead, which shut down in 1996 (just before ACPI was created) and was having trouble even beforehand. I assume that eventually AMD would do the same thing too.
I suspect quite a few more people in the Western militaries today have seen 155mm go off as IEDs, now. I assume it's roughly comparable to a ground detonation (usually they were buried slightly, either in a culvert or below grade, but only a few feet).
WhatsApp Introduced New Feature “Quote Messages”
This also reminds that Hynix had to be bailed out in 2001 and in 2003, US and EU imposed high tariffs as a a consequence. I wonder what would happen if Hynix actually failed.
The Terrorists the Saudis Cultivate in Peaceful Countries
> Each to their own, but MIT and BSD are, to me, free-er and more friendly to business applications.

True, but I'm not going to sell OSs, and plenty of corporations are working on Linux
FWIW, it published Q1 numbers on April 4th...which would be 4 days after the end of Q1. April 4th was a Monday. I don't think too many people would critique them for waiting until the 5th of July, the Tuesday after a huge U.S. holiday, to publish news:

http://ir.tesla.com/releasedetail.cfm?releaseid=963460