skysight-inc/HackerNews huggingface dataset:
I think this overcomplicates the problem. I have not written a high performance messaging system in PHP, but I have in both C and Ruby, and the quip about a "sufficient complicated concurrent program" was moot in both cases, because

1) there are plenty of approaches to doing this cleanly without writing a "complicated concurrent program" - here's one (I've done this in production; it worked great and all the work on federation has been done for you): use qmail or the qmail approach, of decomposing into small independent programs, and of which case crash and get restarted without causing any damage. Incidentally, yes, this depends on process isolation just like you'd expect with PHP, and yes, this is run of the mill stuff you can do with anything. That's the point - Whatsapp like message exchange is not rocket science, and how to structure this so you can just let processes die is something we solved literally decades ago.

2) even if you write a concurrent program to handle the queuing, the logic is simple enough that e.g. my first production queuing messaging system in Ruby was <700 lines of code, with ~10 lines protected by a Mutex making up the only place where the threads interacted with each other at all.

I'm sure there are many spaces where Erlang could make a huge difference here. And as I said it's very much possible it'd have a performance impact, but this specific example isn't a complicated problem space. At all.
> Has anyone here ever actually been called a "DINO?"

Not much since center-right neoliberals became clearly and solidly the dominant faction within the party, since “DINO” was largely what more progressive Democrats labelled that faction; the label also applied to actual conservatives in the party, though they mostly completed the migration to the Republican Party shortly after the Republican congressional majority in the 1994 election (since they had stayed in the Democratic Party largely for the organizational benefits of being in the majority, despite increasing ideological tension through the long post-civil-rights partisan realignment.)
Part of the site are in German, other parts in English. Also, the home page looks a little too amateur.

But I'm not your target customer. Internet access is not ubiquitious here, so having everything in a cloud is not for me.
I much prefer using the $5 wrench anyways.
In the context of poor students in India trying to learn skills that will get them a well-paying job, computer science knowledge without knowing how to program is effectively useless.
I am confused. I thought Docker was no longer based on LXC. Am I wrong on this?
"What's interesting to me is that there doesn't seem to be a modern filesystem that works across all major platforms."

What's interesting to me is that there is no modern filesystem that has a useful ACL mechanism. Say you have a tree of say 100M files and subdirs: now give rights at various points - it takes ages.

Your complaint can be worked around by remounting via an intermediary system and VMs are cheap. Mine is not really a complaint - per se - but a challenge: Why on earth can NSS (off of the 90s) do rich, recursive perms based on a "trustee assignment" on the fly but NTFS and Unix's finest not?
I'm not arguing that it's too difficult integrate Rust with C or C++ projects. I'm simply trying to get at the distinctions that the article is making, which are rather subtle.

One aspect of Rust that fits well, IMO, with the characteristics the article argues are under appreciated is its emphasis on POD--objects as compact, flat bytes. That puts Rust much closer to achieving what C does best (again, according to the article), which is first-class syntactic constructs over memory--namely, pointers. But it falls short in the sense that to _export_ Rust objects (rather than import alien objects into Rust) you have to do so explicitly. And presumably the author would argue that Rust is significantly undervaluing the benefit of a stable ABI that would allow other applications to import Rust objects without an explicit language-level construct (i.e. explicitly annotating APIs with no_mangle).

Obviously when you're building a large application, cathedral style, the requirement to explicitly annotate is not only less burdensome, but quite useful (for many reasons). But in a larger, heterarchical ecosystem of software, that's actually quite limiting. Our first instinct is to argue that permitting such unintended peeking behind the curtain is dangerous and unnecessary, but the article speaks directly to that.

Imagine a Rust with a stable ABI that was exported via Sun's CTF format. CTF is like DWARF but much simpler (and thus little incentive to strip it), and it's being integrated into both OpenBSD and (I think) FreeBSD to facilitate improved dynamic linking infrastructure. Rust could even, theoretically, continue randomizing member fields. And this data could be consumed by any language's toolchain, not simply Rust's toolchain. That sort of language-agnostic, holistic approach to interoperability is largely what I think the article is getting at.
I'm afraid I am right there on the same page as you. I have a hunch many readers are consciously, or unconsciously, ignorant to the problems you described above.

I suspect that you should feel some of these things should change.

Perhaps a lower bail? Perhaps house arrest instead of jail?
Perhaps a less costly legal process that vehemently screens for reasons to not go to trial in non-violent crimes? (child porn possession is debatably non-violent).

How do we increase the possibility of bringing about these changes?
Attic/borg can do most (all?) of what Dropbox does without access to user data.
The kind of scary thing is that if someone else hacked into your account and posted bad stuff, even if you are later able to prove it wasn't you (alibi/IP address/etc), it may already be too late. Personal relationships will have severed. You will have lost your job. People may never look at you the same way.

Passwords are everywhere, and most people don't use MFA. If dozens of celebrities had their iCloud accounts hacked, there's no doubt that thousands of normal people could have their dropbox accounts hacked - for the purpose of adding nefarious files, not downloading sensitive ones.
The actor model deals with concurrent computation.

The threading models on node and browsers do not allow concurrent computation, except for the case of web workers, and the proposed threading additions of JavaScriptCore.

Because of this, the actor model can be overkill when you have no threads. More specifically, you may introduce queuing where no queuing (or other type of synchronization) is necessary. This is because an actor is basically a worker with a work queue (aka mailbox).

For the most part promises can solve most of your async issues.
Event emitting/message passing is valuable, but queuing is optional in many cases.
I'm ex-sun, kernel group. I'm retired, early at 55, but after reading Brendan's write up, I'd work for that guy. Holy smokes, he is all over it. Reminds me of me when I was in the groove. Brendan if you read this, I'm old school, not good at all the ruby on rails etc, but systems, yeah, pretty good. Not looking for money, looking for working with smart people, I can be paid in stock. If it works out, great, if it doesn't still great because I like smart people.

Sorry for making it about me, you all should read his post, it's someone who is completely in the groove, has breadth and depth, knows about systems. These people are rare, but hugely valuable when you need to scale stuff up.
> This went ok, but I still have no idea which of the 6 string types I should use for a library like that. None of Swift, Go or C have this problem.

There are two string types: a string that owns its contents and a string that references its contents. This is the same as in any language that uses smart pointers for resource management.

Can you name a string type that you think should be removed, and explain why?

> First I tried to make a skip list with performance matching the performance of my C implementation. I discovered that even with unsafe there was no way to make a struct with a dynamically sized array at the end, like I can easily do in C.

Yes, you can. You can make a one element array and allocate and deallocate manually, just as you do in C. The offset method on pointers allows for arbitrary pointer arithmetic.

> Despite all the hype, adding a dynamic item to the event bus didn't work because it wasn't 'static didn't work.

I haven't used Tokio, but couldn't you use a boxed trait?
If Dropbox logs the IP address used when the files were uploaded, and the ISP can verify that the IP was assigned to the user's home when the files were uploaded, I'd think that gives more weight.

There's still the possibility that some malware on the user's laptop uploaded the files and then deleted itself, but if that were a reasonable excuse, you could use that to get out of basically any computer-related crime.
I assume that Dropbox knows where and how you access their service... TFA said there was a single IP. If there were multiple then there would be reason to doubt that you were in the sole possession of those files.
Someone else has pointed out that Dropbox has never promised end-to-end encryption of data, partly because it would be difficult to provide various user-friendly features. Also because it would be difficult on their end to apply the efficiency measures they have for doing diffs and file history.
> Pascal might still be around.

Well that's a bit rude. Pascal is still around! And I love it. Behold:

https://www.freepascal.org/

https://www.embarcadero.com/products/delphi
Not off the top of my head, but I think it qualifies as a synecdoche:

https://en.wikipedia.org/wiki/Synecdoche
Once you add the standard set of IT shitware, Serious Enterprise Endpoint Security, legacy line-of-business apps, and poorly written drivers for the cheap components in those systems, 8GB/i5 is closer to a reasonable minimum for usability.

And if it comes with spinning drives, just have it shipped directly to the landfill.
GDPR applies globally to any company - there are no safe havens. If you keep data on an EU citizen then you must comply.
I'm pretty sure if you asked a bunch of their customers (certainly corporate) they would find this very surprising.

I mean, I just went to their "about us" page and here is what it says:

We create products that are easy to use and are built on trust. When people put their files in Dropbox, they can trust they’re secure and their data is their own. Our users’ privacy has always been our first priority, and it always will be.

Wholesale scanning of user data with heuristics and automatic police reports out of no legal necessity whatsoever certainly doesn't spell "privacy always our first priority" to me.
I do mostly agree with you. What if someone roots my machine and uploads from my house?

What if it was (somehow) accidentally uploaded byy little brother who torrents?

Technical evidence, is difficult to associate with meatspace users.

I'm not trying to give criminals potential defenses---

I am trying to prevent people from going to jail for malleable evidence.
Typically in Indian private schools the students are responsible for purchasing textbooks at the start of the school year, not the schools (I don't know how it works at public schools). And they won't change their textbook mid-year.

Textbooks don't usually have much resale value, though I'm sure poor students buy them secondhand. They are paper-bound (and not even as sturdy as the average paperback) and tend to fall apart after a year unless you rebind them with cardboard. The quality of the paper isn't great. These are all good things because the books are inexpensive to purchase new (and it's possible some government subsidies may be involved).

My guess is that the publishing company would prefer to keep printing the same book and make minor updates year-to-year, instead of investing in writing a whole new book. Unless the number of students enrolling increases dramatically they're not going to make more money by writing a new Python book.
Unique pointers provide no protection against use after free, because you can take a reference to their contents and that reference can become dangling. Because the destructor of a unique pointer is invoked automatically per the language rules, as opposed to in C where an explicit call to free is required, this makes C++ more prone to UAF than C.
> Would anyone advertise a company that doesn't have a "High Quality Codebase"?

I think they can mitigate this by making the companies pick a limited number of "most important values". That way they're incentivized to make sure they mention all the things they're actually valuing, and leave out things that they don't actively prioritize (so you may think you have a high quality codebase, but if it isn't in the top 3-4 things you'd mention to a candidate, it's not a value of yours necessarily)
> Nope. Dropbox has never claimed they don't have access to your files

I don't mean to nitpick and it's been a while, but Dropbox used to claim that "even our employees can't access your files". People called them out on the misleading language and they changed it.

https://www.cbsnews.com/news/at-dropbox-even-we-cant-see-you...
http://www.lettersofnote.com/2012/03/i-am-very-real.html

>It is true that some of the characters speak coarsely. That is because people speak coarsely in real life. Especially soldiers and hardworking men speak coarsely, and even our most sheltered children know that. And we all know, too, that those words really don’t damage children much. They didn’t damage us when we were young. It was evil deeds and lying that hurt us.
> keep your money if you earn it

Earned? My ass.

A fortune amassed from profits skimmed off of HFT isn't earned and produces nothing of value.
Too bad an IP address isn't really proof of anything. Do you mind if I use your phone for 5 minutes? How about if I don't ask nicely? How good at jiu jitsu are you?

I'm guessing 90% of the time a dirtbag just confesses, but the potential for abuse and negligence here is nearly unlimited.
My Uncle had to do something similar for the NZ police. He had young children at the time, it was a distressing job for him.

I don't envy anyone that has to deal with child abuse at any level but I guess someone has to do it.
First class communication as a feature. Notice that many of the more popular languages value the ability to link to C libraries. Most languages have a way to call (or even statically link) external C code. It's not as easy to do the same with other languages because they lack this ease of interfacing. It's easy in C because it's low level, everything is plain old data and function pointers.
This is really cool. Things that only the developers and the most hardened and dedicated of fans would have noticed.

As much as we feel like games are set micro universes with static rules, they change for the sake of fun/intensity and that is wonderful.
Reinventing cross-origin requests, without CORS
I remember a story where someone uploaded a large file known to be popular (a new torrented movie if I recall correctly) that would have a reasonably chance of already being in someone elses dropbox.

The file uploaded in an instant, lending a lot of credibility to the theory that the software hashes a file and looks for the same hash in a central database, and if there's a match doesn't bother to upload the file but simply adds a pointer to it.
Well I was in the process of writing my own tool to do this after starting to hit the limits of what I could do with cookiecutter... so I'm hooked.

I expect I'll be writing quite a few pull requests.
It's Ephesians 5:28. I can promise you it's not a thoughtless meme that people bat around. I've heard it cited in at least six wedding sermons.
Wow, that's incredible. Even more surprising is that the media company didn't write a story about this.
Perhaps nihilism was too strong a accusation, but I still fear your position is leaving a loop hole open for nazis. Your case for logic and rationality reads like the status quo should be left alone, which in our current circumstances, tends to benefit whites (thus my remark). Groupthink may be groupthink, but you know how we combat that – we fund public education. We don't need to let nazis to empower themselves to guard against groupthink.

I must comment on this:

> When your "activism" starts depending on the magnitude of horribleness of the enemy for its justification, this is a historical sign that something is out of kilter.

To what activism are you referring to? My activism would be related to moving closer to a society where the starting floor hasn't fallen out for others based on class, race, and gender. Nazism, you know, kinda gets in the way of that.
There is another kind of Rust graph that uses indices. Indices are just bounds checked addresses, so this is a natural fit. The most popular graph crate, petgraph, is of this type.

> CRT debug heap / MALLOC_CHECK_ / libefence, depending on the platform/compiler

None of these are effective at preventing use after free problems in production.
just a second voice to add -- i do drink, but still don't appreciate alcohol in the workplace or cultures that are focused around after-work drinking. it's something i do with friends and family, not coworkers, and especially not my boss or subordinates.
50C is not much for heat engines your limited to under 15% effecency in the best theoretical case. So solar + battery is going to be a net win unless your thinking of flipping panels at night for ~1% more power over pure solar panels which is silly from a cost perspective.
Wondering if the radiation tech could work in sending the heat generated from other sources like clothes dryers etc as well?
That sounds about right. I've spent more time than I care to admit trying to decode baseball signs. To me it has always looked like signs from the dugout are far more complex, but catchers' signs not so much.
We keep commercially sensitive documents on Dropbox yet have to keep nearly all of those documents encrypted locally. If someone broke into our network they'd have a very hard time opening any of them, yet it seems Dropbox could just jump in and read them. Not sure how Dropbox got approved as secure?
And what does his profile photo have to do with being PC?
Re 3: read "behind" as "backing" not "orchestrating in the shadows"

major US banks and whatnot have started to make crypto/bitcoin plays in the past few years. The idea is that these plays are early for them, and their followthrough of these ideas will be good for bitcoin.

Of course they could also die the death most moonshots do.
Black body radiation scales with T^4, but you're relying on one particular band. I suspected it scaled, but T^4 seems rather unlikely ;-)
> . Kernel bugs which allow escaping a properly setup mount namespace or peeking out of a pid namespace or going from root in a userns to root on the host are all treated as vulnerabilities and patched. That clearly expresses the intent.

This is because these vulns can be exploited locally without containers.
That and ext4 support (at the very least).
> If it's legally enforceable, then a legislature gets to decide.

Which in practice, at least in the US, means that unelected bureaucrats get to write the detailed regulations that actually decide, based on extremely vague and broad laws written by the legislature. Which in turn means that people with wealth and power can manipulate the system to get regulations passed that benefit them but are a net loss to society as a whole.

> If it's not, then either the manufacturer decides

Which isn't any better.

> or it doesn't happen

Which would be my desired outcome. If only.
I think some grandmas were invaded by a SWAT team because someone used their wifi to seed copyrighted material.
> And when I want to compose 2 data structures into my own higher-level one, for performance and memory access patterns I need these two lower-level structures to expose unsafe stuff at their API boundaries. The data structures I saw don’t do that, they’re designed to be consumed from safe Rust instead.

Can you give a specific example of something you want to do that you can't?

> I think in modern C++, with these iterators and smart pointers, you’re less likely to screw up dereferencing a wrong pointer.

I don't think this is empirically true relative to C, but even if it is, use after free is still far too common in C++ code.
From the it-ought-to-be-obvious department.
The pitcher absolutely does get to decide what pitch to throw. If the pitcher does not like what the catcher puts down he just shakes his head and the catcher puts down a different sign. Repeat until the pitcher is happy.

The big reason why pitchers don't signal to the catcher is because pitcher and catcher must both know what pitch is being thrown beforehand and the batter can see the pitcher but not the catcher, so it's 1000% easier to keep the pitch secret when the catcher calls the pitches.

However, the catcher calling the pitches is beneficial because it allows the pitcher to better concentrate on the act of pitching.
I really don't think we have seen a winner yet. There is going to be a crash due to regulations, licenses, and just pure shady business practices by both Uber and Lyft.

I suspect that within the next five years we see some kind of cracking down. Whichever one can survive that and/or adapt will be the winner.
Here's a google cache to beat the adblock-block.

http://webcache.googleusercontent.com/search?q=cache:JudXjFz...
They don't but it takes two people to make a marriage.

"Staying married in name only" means anyone under the UCMJ can't have sex _ever_ if its a marriage in name only.
The problem with using mirrors as radiators is that they're terrible radiators. They might be great at reflecting the sky-photons away, but they won't launch their own photons away either.

Shiny things are great at reflecting incident radiation (which is why they're good mirrors) but bad at radiating their own heat. Dull black things are bad at reflecting but good at radiating. The technical terms are reflectance, absorptance, and emissivity.

http://www.optotherm.com/emiss-physics.htm
A lot of parents don't want kids going on the internet and looking at violence or porn, But it will definitely happen. May as well encourage positive things like literature. Also the Harry Potter series is full of themes around heroism, friendship, perseverance, and other qualities you'd wish your children have. I can't wait to reread the series for my kids.
Amen.

Hans Rosling did a great job explaining all that progress.

https://www.youtube.com/watch?v=jbkSRLYSojo
His "how to sell anything" book is great if you are into marketing or sales. It basically boils down to: ask what they want, summarize their needs and ask them if your summary is accurate, tell them how you can deliver on their specific needs, if you can't tell them and move on. If your summary is accurate and fits their needs ask if they are willing to pay for your solution.

This advice seems incredibly simple and obvious yet people tend to do the opposite.
Which means the one under the UCMJ is open to blackmail from their spouse if they fool around in a marriage in name only.

Yeah. Totally a reason to stay married in name only.
Well this is slightly different. DGA seems to actually use it as a rendez-vous host, whereas in this case, it literally is a dummy domain that they didn't even bother registering, with the only purpose of checking if they were in a VM. In which case, generating any long hash domain would most likely not be registered and would do the job.