skysight-inc/HackerNews huggingface dataset:
I still think you are mischaracterizing Brin. He does not think transparency "solves everything" or is "the solution". He just believes that reciprocal transparency is the least bad option. If there were a better option, such as complete privacy for all, perhaps Brin would prefer that. But realistically, such is not feasible.
Agreed. I don't think anyone is arguing that you shouldn't do it.

What I believe, and what I think others have also concluded, is that it shouldn't be fatal. That is, when the dust has settled and you trim down usage and have a decent maintenance outage, you should be able to defrag the filesystem and get back to normal.

That's not possible with ZFS because there is no defrag utility ... and I have had it explained to me in other HN threads (although not convincingly) that it might not be possible to build a proper defrag utility.
That's Digiday (which published the article), not Little Things, just an FYI.
This is why smart pointers via templates don't work well. The mold always leaks through the wallpaper. There's no analysis at compile time to catch those errors.

This is what Rust is for. You really need a borrow checker.
Vaclav Smil further collapses this to the decade of the 1880s, for which I think he's got a strong case.

But yes, the 50 years from 1870 - 1920 essentially created the modern world as we know it. Shy television, many plastics, antibiotics (though massive healthcare improvements had already been made), nuclear fission, lasers, transistors & computers.

Robert J. Gordon's The Rise and Fall of American Growth does a stellar job of detailing the various impacts of technology on the period 1870 - 2015, divided into roughly three fifty-year periods: 1870-1920, 1920-1970, and 1970-present.

The combination of electric motors and internal combustion engines seems most specifically powerful.
> As the California Supreme Court made clear, federal law (which permits monitoring with the consent of one party) does not preempt more restrictive state eavesdropping laws, even when the monitored communications are interstate. Accordingly, companies that monitor interstate calls for quality control purposes must consult the applicable provisions of state, as well as federal, law. (o)

i feel another commenter, em3rgent0rdr, may have indirectly answered my confusion by stating:

> Even if judges prohibit such evidence on the grounds of it being illegally obtained, you will still find that prosecutors will use that evidence to find other evidence and for constructing a case that doesn't use that illegally obtained evidence. https://en.wikipedia.org/wiki/Parallel_construction (i)

(o) http://www.mofo.com/resources/publications/2006/07/californi...

(i) https://news.ycombinator.com/item?id=11699146

.. completely offtopic, but how unfortunate is that lawfirm's domain?
2-3 months of light work (it was the summer), in Toronto circa 2011.

I had zero professional experience, and bad grades. I knew that for my first job coming out of school, a lot of places would ask for a transcript...so I pointed most of my energy at places where the HR process seemed lax enough that I'd get to talk to developers (who could advocate for me) before I had a conversation where grades would come up.

At the start of my search, the Star/Globe had an insert with "Canada's Top 100 Start-Ups" - I cold-emailed all the ones in there which seemed interesting. A few got back to me, and one of the ones that did is where I'm still working.

As someone on the other side of the table now (at a ~25-dev shop), some things I think about when I'm considering new grads:

* I'm looking at passion, which I use as a proxy for long-term potential upside. You likely won't be a valuable contributor for 6+ months while I get you up to speed on my domain and what real-life professional programming is like. Some new grads can have an immediate impact, but most of those will have already been hired by Google/FB/etc. before they even think of my company. Convince me that you're the one I should be placing my bet on.

* If your CV talks about a mobile app you built, have it installed on your phone so I can play with it. If you talk about a web app, have it bookmarked and walk me though it. If you have one of those you're not excited to show me, I'm going to assume it's bad or you didn't finsih it (so don't mention it). If you don't have one of those and you're a new grad, I'm going to wonder why not. These don't have to be sophisticated; what you're showing me is that you're excited about technology, and can apply it in a non-academic, non-forced context.

* Show that you can communicate well. We're going to be spending a lot of time teaching you stuff, so I'm going to be probing to make sure that you can absorb it all (emotionally and socially).

* Don't focus that much on your specific tech stacks, aside from enumerating them. I'll assume your experience is of limited/academic depth only, and that you don't have much real-world experience. Don't boast that you know Scala when you used it for a project and a co-op term; focus on selling that if I need you to learn OCaml, you'll be a quick study.

Lastly, re: meeting engineers at meetups etc. - don't forget about follow-ups. Maybe the person you had a positive conversation with was just being polite...but it's more likely that they just forgot about the conversation. Send them an email a few days after to remind them you exist.
Adding to my read later. Looks like a good intro. Does anyone know of a similar resource for ARM assembly?
> Heat vision. [...] MWIR is neither heat, nor is it light. It’s both

No, it isn't. The "infrared light is heat" statement is casually-useful but technically-false, which means it backfires and harms people when they start learning more about physics.

IR radiation is not the intrinsic heat-content of the matter emitting it. Infrared is simply a particular set of wavelengths which happens to be prominent for temperatures which are "hot" for us just because we evolved on this small rocky planet which has a certain baseline temperature.

Go ask some icy crystalline aliens or ones powered by low-grade nuclear reactions what they think about "heat radiation" and you won't get the same answer.
Nothing super interesting, have a look if you like: @lwansbrough
> And while that's not "racist" as it's not about race, it's quite literally xenophobic. You're afraid of something because it's alien to you.

(or (disagrees-with person thing)
(disinterested-in person thing)
(dislikes person thing)) => t

(equal (or (disagrees-with person thing)
(disinterested-in person thing)
(dislikes person thing))
(afraid-of person thing)) => nil

This is the same kind of irrational, manipulative, deceptive talk used to ridicule political opponents.

"You dislike x? So you're xphobic."

"You disagree with x? So you're an xphobe."

"You don't support x? So you're against x rights."

It's hollow and transparent, but sadly, many people fall for it.
ZWTopSelectVcView
That's gold. I'm going to use that one next time.
For a doubly linked list, I think the right approach is to store a unique_ptr pointing in one direction and a raw pointer pointing in the other direction. It is then understood by convention that raw pointers should never be deleted.
One lead came from a lead developer who came across my stuff which was highly relevant to what they were working on. Still wanted coding tests done though.
Can someone comment on how things like kernels, kernel modules, and bootloaders work in Guix? It seems like these sorts of things wouldn't be possible to handle in a purely functional manner since, for example, you can only install one bootloader to a disk, and you can only boot into one kernel.
LOL... What voice prints? What conspiracy to commit murder? Was there any planning or intention? You do know that conspiracy must follow intent to commit the offense?

To shorten things up: "Although a person may simply contemplate committing a crime without violating the law, the contemplation becomes unlawful if the same criminal thought is incorporated in an agreement." [1]

1 http://scholarship.law.wm.edu/cgi/viewcontent.cgi?article=16...
Are you seeing the actual green Vine Reviewer at the top of these comments or the "I was given this product for free in return for an honest review" at the bottom text that a lot of astroturfers are using? I thought the # of vine reviews was limited but it may be up to the manufacturer on how many they send out. Vine reviewers don't choose what they review other than they can turn items down iirc.
I don't understand what's unclear, lifting values to the type-level and pattern matching on those values to type classes is a standard construction [1].

I only claimed that operations on Maybe can be lifted to type classes, you claimed that all uses of type classes can be monomorphized (barring "fancy types", of which Maybe is presumably not one).

Since all pattern matching functions on simple sums like Maybe can be lifted to type classes using the above translation, and given you said all such type classes can be monomorphized, therefore all uses of Maybe can be monomorphized. Alternately, your original claim could be wrong, or you can provide a counter-example to my claim that pattern matching on Maybe can be translated to type class dispatch.

[1] http://koerbitz.me/posts/Solving-the-Expression-Problem-in-H...
It should be changed to pass by value, and then use std::move to move it into the children array. The reason is that if the argument is a temporary, you are making an unnecessary copy of that temporary, when you could just transfer ownership.

This also gives callers the flexibility to std::move into your argument, transferring ownership.

A good rule of thumb is, if you are going to unconditionally take ownership of an object, accept it by value.
At the current state of things, AMD is definitely not a viable route, but that might change in the future with the "Boltzmann Initiative" [1]. Performance with OpenCL is not comparable with CUDA on NVIDIA GPUs at the moment, and support is lacking in most deep learning frameworks.

[1] http://www.amd.com/en-us/press-releases/Pages/boltzmann-init...
> In Rust a string is a sequence of unicode scalar values.

The representation of a Rust String in memory is guaranteed valid UTF-8. To me, a "sequence of Unicode scalar values" is an abstract description, because it could be implemented via UTF-8, UTF-16 or UTF-32.

> I personally find it unfortunate that they dictate the storage of it at the API level

It is extraordinarily convenient and provides a very transparent way to analyze the performance of string operations.

For transcoding, there is the in-progress `encoding` crate: https://github.com/lifthrasiir/rust-encoding

I note that Go does things very similarly (`string` is conventionally UTF-8) and it works famously for them. They have a much more mature set of encoding libraries, but they work the same as the equivalent libraries would work in Rust: transcode to and from UTF-8 at the boundaries. See: https://godoc.org/golang.org/x/text
I will sometimes stop myself from googling something I'm curious about. I imagine a situation where I become falsely accused of a crime and the search I'm about to make coincidentally incriminates me and is discovered with a subpoena.
The 4th ammendment is meant to protect you from the power imbalance with the government. Or at least that's how it seems to be interpreted by the courts.

Kyllo v. US ruled that heat-cameras mounted on helicopters were considered a "search" and could not be committed without a warrant because most people do not have heat-cameras and helicopters.

But everyone has ears (and microphones obstensibly work as well as ears in public spaces). The government has the right to investigate on the same level as normal citizens, in a way. Binoculars are also fair game, because a lot of people have binoculars.

The "expectation of privacy" is usually evaluated as "if somebody could try to spy on me, would they be able to do so relatively easily?"

In a way, this 4th ammendment interpretation is what protects us from NSA mass-surveillance. Because only very few people have the resources necessary to set up such a network, you can end up with an expectation of privacy.

And while you don't have an expectation of privacy with regards to tor nodes (anybody running a node could be trying to watch you), IIRC expectation of privacy comes in if , as in the recent case, the gov't runs a very large amounts of nodes and cross-references the data to "find" people.
Wealthy people could have a telegraph line installed, and did. Ulysses S. Grant got news of his election as president in Galena, IL, (along the Mississippi River, near the Iowa-Wisconsin state line) at the house of a local businessman with a private telegraph service.

More generally, though, "email" was called "mail". In cities, there were often two, and sometimes three mail deliveries daily. It would be possible to carry on a round-trip correspondence over the course of a day.

The precursor of online shopping was called "catalog stores" -- Sears, Roebuck & Co. was the canonical example. I just caught an item over Ansible last week that Sears had discontinued its catalog in 1993, the year before Amazon started.

Robert Gordon, economist at Northwestern University, has just published a book on technology and growth, The Rise and Fall of American Growth. In it he notes that the typical urban home of 1920 was connected to five "networks": water, sewer, gas, electricity, and phone. I'd add postal mail and the highway, railroad, canal, and shipping networks as well, though those had a "last mile" component of individual delivery. Still, this largely offered similar capabilities to today's Internet.

Email was postal mail.

Online shopping was catalog shopping.

References, information, and entertainment (as well as advertising, without tracking or pop-ups) were performed via books, encyclopedias, newspapers, and magazines. Phonographs provided audio, as well as over-the-air radio broadcasts. Libraries provided extended access.

Latencies were higher, but the throughput of even a horse-drawn cart is pretty good.
Given that many people come from larger cities, my story is an anomaly probably. I was working on my MS in CS and Applied Math at a local university when I started going to a local meetup. I got to know some people there who were in hiring positions at a local company that had a number of dev teams. They invited me to interview for an internship and ended up hiring me as a contractor instead. My next job after that came from meeting the CTO of a local consulting house at the same meetup. It's all about networking. I haven't gotten an offer from a place that didn't start with a warm intro.
I loved my Pre. Wireless charging. WebOS. Swipe gestures. Optional hardware keyboard. Their notification system is still unsurpassed by iOS/Android today.

Shame that it died.
Two minor comments:

1.) Mistake #7 Has been somewhat fixed in the TS by specializing shared_ptr for array types (similar to unique_ptr<type[]> syntax). What they said was true though for C++11.

2.) If the data within a shared_ptr is not owned by any particular object but is otherwise constant, use shared_ptr<const type>. They can be created from a shared_ptr<type> object. This helps with the aliasing problem mentioned in mistake #1

And a slight nitpick on #4 - I imagine the performance of make_shared depends on the library rather than the compiler itself (and I imagine the performance gain is minimal - it is usually used for readability). Also, C++14 add make_unique, which was overlooked in C++11.
So I clicked on the link and, for the umpteenth time, was greeted by their pop-up saying "we can't go on like this" and asking me to whitelist them on my adblocker. I am a subscriber of their online edition. Oh, the irony.
Its a better way of doing things - you can handle things in their native format rather than have to arbitrarily convert to UTF8 (which is an 'encoding' itself).

[edit] I remember a talk where Matz was asked this specific question and tried to explain it clearly but seemed confused as to how the questioner could have such a poor grasp of unicode (the difference between monolingual americans and japanese i guess)
Introduction to Multithreading in C++
Hmm I wonder how this would work considering its all things openly available to be recorded.

Follow a federal agent home from work and film them and their house. Film their children going to school and post pictures locations and times online, also taking photos of other relatives, friends etc and where they live and their phone numbers and post it all online.

Have your friends join in and keep posting every detail and picture you can get of federal agents and their families etc and compile it into a website.

Then let me know how that works out.

Edit: Does anyone know of any USA law that stands against such activity?
Am I the only one who feels the "intro to x86" market is oversaturated?
X86 and x86_64 Assembly and Shellcoding:

http://www.pentesteracademy.com/course?id=3
http://www.pentesteracademy.com/course?id=7
Employment, construction, and the cost of San Francisco apartments
"IMHO different languages are equally annoying, useless and impossible to deprecate"

Not understanding different cultures, thinking their very existence is "annoying and useless" and thus wanting them gone? Yeah, that's being afraid of something alien. And "afraid" is a nice way to put it.

I speak 4 languages fluently and learn more because it's fun, it's beautiful, it teaches you a lot about people and culture and it even improves your understanding of languages you already speak. It's also a wonderful way to immerse yourself into a country you're moving into for the first time. This thread is filled with people who lack that perspective and think their opinion is informed and considerate because "I know I might have to learn a new language and that's fine". Let me remind you how this thread started: "why are we putting up with other languages anyway?".

We already have a lingua franca in the western world and it is English. It's as good as it can get. But the replies here, unhappy with that, boil down to "let's make it official and declare every other language as dead, then let's force that onto the non-english-speaking world".

I used to think like this, btw. I wondered why we bother with different languages. Why going to another country had such a high artificial barrier of entry. Why we didn't just agree on one and left languages to "hobbyists". But I was 8 years old and didn't know any better. I expect more from HN.
Did you look at the above work (qb) or have any comments specific to it?

Not liking gorm or orm in general is a common enough attitude, but it feels like an unfair dismissal to not be specific about the posted library and instead criticize it based on your experience with another.

I also might have a misread here, but I doubt people are adopting query builders because they find sql hard, but rather due to combinatorial explosion in manual sql building in some application types.
Spores seem like an interesting solution. The language designer in me has a distaste for it, though :p

For case 1 (capture of mutable references), an explicit copy operator might be better (as in, "I want whatever value this variable is bound to, rather than the storage location") (or even vice versa, where value is the default and there's an operator for location). In a way, spores accomplish this by forcing you to do the copy manually -- but then programmers have to always remember to use the extra syntax, and they need to do it for every captured variable. I'm not quite happy with even this solution, and it may be possible to come up with something even better. Concurrency is always a can o' worms :)

For case 2 (capture of implicit "this"), I'd argue that if (a) the compiler is smart enough to know that "helper" is implicitly "this.helper" and (b) that "this" will be captured by the closure, then (c) the compiler is also smart enough to create an implicit binding for "helper" and capture that instead. This would lead to less-surprising behavior, and intentional capture of "this" could still be done via explicit access. Another option is to, rather than treating "this" as being in an enclosing scope, treat it as though it were an implicit argument to the method (albeit a covariant one). This avoids capture altogether.
Sometimes I wonder if this kind of notion of what's "logical" is a confusion of short-term instrumental thinking with what is actually successful in he long run. In many biological systems, for example, diverse evolutionary strategies play out in competition and exchange with one another with the end result that "life" more generally persists and grows in complexity on a grand scale. Humans seem to have an inverse tendency towards projecting uniformity wherever possible, with the end result being limited models that subsume as much as possible and then collapse under an unexpected pressure (the structuring of Western economies being the most obvious example of this). I wonder if we'll ever develop some kind of meta-logical approach whereby we intentionally foster diverse, but somewhat isolated, strategies and then experiment with varying levels of exchange to arrive at better outcomes.
I have a bunch of boilerplate repos.

https://github.com/Jon-Biz/simple-static-react

https://github.com/Jon-Biz/simple-static-react-router

I'm going to publish a React/Aframe version and one with a server tomorrow.

EDIT: probably not tomorrow, but in the next few days for sure :)
They recommend that because in many cases you can't hold down solid food for periods of time.

Good luck eating your veg and protein when you immediately vomit it back up.
At least do not become a fat fertile ground for it.

BTW, in developing world with traditional simple, not processed foods and setting in a tribal culture eating habits rates of cancers are way lower (and no, it is not because lack of diagnostic tests).
When predicting reliability of next launch, you'll use weighted mean of historical data, not simple mean. And, weight of launches in 60s would be near 0, same for n-100 launches.
Why not just add all of this to Wikipedia?
That is a fantastic programme, and other than the leisure suits, has aged phenomenally well. The opening sequence of the first episode, in and above lower Manhattan, gives me the chills.

I'd also strongly recommend the subsequent programme, The Day the Universe Changed, which follows a similar, though temporally arbitrary, connect-the-dots motif.

The two sequels to Connections aren't as good, though C3 is the better of the two.

Also: if you're interested in the background of technology, look up the story of Joseph Needham and his extended exploration, Science and Civilisation in China. Begun in 1954, it remains in process, with 27 volumes. Needham himself died in 1995. Simon Winchester's written an excellent (and much shorter) biography of Needham.
My understanding is that the way to defrag ZFS is to do a send and receive. Combined with incremental snapshotting, this should actually be realistic with almost no downtime for most environments.

Doing so requires that you have enough zfs filesystems in your pool (or enough independent pools) that you have the free space to temporarily have two copies of the filesystem.
You can't have everything. Where would you put it?

- Steven Wright
That word does not mean what you think it means.

In fact, today it doesn't mean anything, because it means whatever the speaker wants it to mean. It's used simply to denigrate whoever the speaker dislikes or disagrees with, without making a rational counter-argument.

Speaking a language != being a member of a race

Preferring a language != being prejudiced against members of a race

"That's racist!" != it being racist
A Small London Company That Makes Beautiful Globes
This is a more informative article around the topic IMO:

http://www.eastbayexpress.com/SevenDays/archives/2016/05/11/...
All depends on the school.

My 5 in US History yielded 6 credits, 3 in Calc zero credits and 3 in English 3 credits.