skysight-inc/HackerNews huggingface dataset:
I remember thinking I was doing great in tradewars

Then overnight I got my ass kicked, handed to me, and my hold was filled with money (or whatever it was). Happened to a lot of people -- someone who really did do well was clearly fed up with not having any real competition.
Non spammers send from a consistent pool of IPs and domains that don’t send crap. By contrast, spammers either send high volumes of crap from a small set of IPs and domains, or they spread a single content pattern over a wide diversity of IPs and domains that do not have a good track record.

So long as you can keep track of literally billions of counters in real time, you can effectively combat spammers.

Source: MailChannels CEO
That didn't help with the case where the "kidnapper" is actually the "victim".
Maruti Hard Real-Time OS (1996)
Modular nuclear power isn't proven to reduce waste storage costs, for one thing. Look at how long it took renewables to go from a theory to being a mature technology with a declining cost curve and full lifecycle experiences that make predicting cost of ownership very reliable.

It would be nice if there was a zero-carbon source of concentrated power that had a track record of being cost effective and not having nasty end-of-life surprises. This is why nuclear is seductive. But it has never lived up to expectations.
Indeed. https://groups.google.com/forum/#!original/comp.os.minix/dlN...
Surely people today have watched Wargames - Broderick used an acoustic coupler in his nefarious attempts to get into his classmate's pants
The Joy of Missing Out
I'll add one more: https://www.fool.com/investing/2016/09/06/microsoft-stock-hi...

Take a look at the chart. Ballmer was CEO from January 2000 to February 2014.
THis. I think the type hint system adds so much visual noise it starts to look like perl. When an attempt to build huge (100k+) project with Python failes, it is not because of the duck typing, but simply because Python is not designed for such use cases.
This is the best answer. This way if the insurance company is defrauded it's only your own rates that increase, not the percent the company has agreed to pay.
All measures that make sense to 'business' revolve around three things failures, delays and cost. Revenues offset everything but that is always attributed to sales for some reason so don't bank on that. If you can somehow show a direct co-relation between learning swift (however you plan to measure that) and reduced failures, delays or costs then you may have a buy in.

But in my experience, this isn't something you can explain to business. They either understand it (or at least try to) or don't.
Fundamentally, thermodynamics and information theory share a slew of similar ideas. Because in a lot of ways information theory came out of a thermodynamic thought process applied to signals. Even more recent work in ml like Boltzmann machines are directly taken from this overlap. That being said stronger theoretical connections are well worth the effort as these fields do have some different ideas that if shown to be similar can yield discoveries and push our understanding forward. Some thoughts that come to mind are compression, model generalizability/ convergence.
You apply to the lowest position, that has the least amount of risk to hiring you as you're unknown to them, and then work internally your way into your role of choice. Or try a recruiting service like this: https://triplebyte.com/
Show HN: Riveto – iOS app for product discovery
Elon Musk calls British diver in Thai cave rescue a 'pedo' in baseless attack
I saw a review of Incredibles 2 which opened with "you may remember the original from when you were a kid"

Sigh.
Concurrency has overhead. On top of that, synchronous is easier to reason about.
I was wondering about that, but I didn't update my post. Was there an acoustic hang-up signal? I've forgotten.

Regardless, the 1200 baud modem, in addition to feeling like it was "keeping up" with the user, also made connecting more convenient.
Wow, a near clone, huh? Did you compare display resolution, trackpad quality, SSD speed (hint: NVMe), etc, etc? Come on..
(for anyone not familiar with the term, K&R policy is a "kidnap and ransom policy")

Like rdtsc said, pointing to times when they did guarantee the return of an employee would be pretty close. Not entirely foolproof, since past performance is not indicative of future results (if they got the insurance policy without telling anyone, they could easily drop the insurance policy without telling anyone).

In a broader sense, the way this (disclosure without disclosure) is usually done is escrow of some sort. There is an agreement with a third party that the agreement will be upheld, with money down to that third party. If the money is required to be issued from the first party to the second party, the second party does not need to rely on the first party to uphold their end of the agreement. The third party (escrow service) has already assured that, and now the third party is responsible for issuing the payment. For example, if I'm promised payment for source code and I want to ensure I get the payment upon delivery of the source code, the company submits the payment to escrow and I submit the source code, and the escrow company is responsible for ensuring the payment and code get swapped appropriately.

I'm not sure if proving an escrow policy of "we will make sure you get home" and putting down $1m just in case of ransom violates that K&R clause or not. But without a contract saying specifically "we will get you home no matter what", there is no real assurance. Escrow might be the closest you'll come.
Newton and friends had nothing to do with discovery of feedback controls :)
You're right, it's the wrong book for the OP. Let them be warned:

Greg Egan's Diaspora is diamond-hard scifi. If you aren't well-read in a variety of scientific concepts, aren't comfortable doing on-the-fly physics thought experiments while reading a novel, or won't be comfortable reading an extremely high vocabulary, then Greg Egan is not a good fit.

But if you can read it, the reward is great. Magnificent, alien, profound. It made me realize I don't like soft-scifi.
That's the tragedy: you can almost see the conversation between an engineer and the author.

Lost in translation, indeed.
If you want easier concurrency with higher overhead, that's exactly what OS threads do. The OS kernel is the "event loop" in this case, and they're highly optimized for this, though there is some overhead which is hard to avoid.

Rust has gone back and forth on this. Pre-1.0 versions of Rust had a "green threads" mode. It was removed in favor of OS threads because it wasn't worth the complexity.

Go is a language in which "all functions are async" and it's pretty cool. But it needs a runtime, and interop with C / C++ has some real overhead related to switching to a C-style stack. Rust did not want to make those compromises, it wanted to be appropriate for bare-metal or kernel programming, and for libraries used by big high-performance C++ applications. In these cases, Go's model does not work well.

I personally use Go a lot, it's great for network services and command-line tools, and that's mostly what I do.
Did CiX also charge per-minute access on top of that? Compuserve did.

In the late 90s, pre DSL, there was a pressure group to allow unmetered phone calls. The site is still online: http://www.unmetered.org.uk/
Actually the control of the bicycle is surprisingly simple regarding how complex the vehicle dynamics are. A simple proportional feedback control based on a roll rate measurement can balance a bicycle, causing it to always steer into the fall.
For me, past ~3000 lines, I really work best in a statically compiled language.
The type-checking allows me to catch most bugs at compile-time.
Some people use DEA to abuse of trial services of SaaS, for example. They register again and again after the trial has expired. These users consume resources but they never effectively become customers. Some companies ban users using DEA, anonymous proxies, TOR, VPNs... or even Free Email addresses (the conversion rate comparing a user registered with his or her company email and a Free Email (gmail, hotmail, protonmail...) is much higher).
> a function needs to await something

According to a famous quote, the source of which escapes me, "await does not wait for anything, and async is not asynchronous." (This could be specific to C# though.)
You can. I'd recommend a rate gyro instead of an accelerometer though.
Seconding "A Fire Upon the Deep": a fast-paced, high-stakes action adventure in a zany, 5th Element-esque space opera universe. Explores the idea of strong AI in a unique and interesting way.
Why would anyone assume that a GC is needed for async/await?

The Future object seems to do the all bookkeeping needed by the borrow checker (which I believe is what rust uses to track the lifetime of objects).
"Orville", a semi-serious version of Star Trek by Seth MacFarlane has one amusing "Black Mirror"-ultra-lite episode about this: "Majority Rule". In this world, law has been replaced by a simple upvote/downvote system and pictures of people doing stupid things can go viral on a "global feed".
Suarez's books are so underrated. The buddhism / sci-fi thing is great
because the 'market' decided that style was valueable and io was meh.

a bit like cellphones with glued batteries, they removed 'user replaceable' for thinness.
Are you saying that the happy path of SBCL static typing—given you also want to use lists, and also not be inundated with spurious warnings—is to declare everything to be of type T?
The cert issuer is required to revoke a compromised key, so I would contact them. Note that you should probably have your stuff off that webhosts' servers first, as they may feel inclined to retaliate.
Btw where do you get the key in chapter 2?

_edit_

Nvm figured it out :3
Do you mean zero gravity? The "bricycle": https://www.tandfonline.com/doi/abs/10.1080/00423114.2014.95...
Rust worked this way earlier in its development. The keyword as others mention is “green threads”. It moved away from this because this model has some overheads, and not every application is a socket server. Languages with this feature include Go, Haskell and Erlang.
I think that answers is equivalent to the company not convering ransom and kidnapping, is the employee who establish and pay such coverage. So technically is a different problem.
Seems that plotly throttles # of views per plot if the user doesn't pay for an upgrade.
Probably just an example. The real condition could be a hiring policy that is technically illegal, a question about prodict that is a trade secret, or questions about business sustainability that might be secret etc.
This would need some modeling to prove that you actually get that level of efficiency. Autonomous vehicles have a brownfield problem in that they would have to share the road capacity with conventional vehicles for a fair distance into the future. That consideration alone would likely reduce the efficiency gain considerably.

On the other hand if you could distribute traffic flow vertically the potential for scaling goes up considerably. It's a hard problem to solve (read: expensive) but building roads is not exactly cheap either.

BTW I'm not against autonomous vehicles. It would be great if they worked. But I think we're more likely to see near-term investment payoffs using it for incremental safety improvements, something that already seems to be happening.
Is AV1 smaller?
A blockchain controlled by a single entity is just a really crappy database
Lot of great recommendations in here. The Martian by Andy Weir is my pick. Absolutely exhilarating.
The Nokia fiasco is a big blot on Ballmer's record. For a good reason: It shows the consequences of great arrogance. Nokia's marching orders were to make Windows Phone a success, and not to dilute that mission with a drop of alternative products. Just because he could, he took one of the finest companies on the planet and trashed it with a doomed strategy, at a cost of tens of billions in foregone value to his own shareholders and Nokia's employees. He took that much money, put it in a pile, lit it on fire and blocked the fire brigades, whether for vanity or for a weakly articulated strategy.
I don't think so. It's just easy to over-optimize things because you can.

Personal case in point. I've been hacking together some automated plant watering systems around my house. My initial thought was to have moisture detectors, Raspberry Pi, etc. I ended up just empirically figuring out how many seconds per day I needed to turn on the pump and that was good enough and a lot simpler/more reliable.
Could be. I couldn't compare rates, but the general trends seemed similar to me.
Perhaps, what the actual value could be expected to be. So, for example, you don't do a lot of work on top of the current estimates for oldest tool-using humans outside of Africa, that is likely to be overturned in ten or twenty years.
I don't know who "Ornstein" is, but he sounds racist. Using "whiter" as if that was a problem. Just change "whiter" for "blacker" and you'll see.
Improving Wireshark for Wi-Fi Packet Analysis
Python’s type hints have nothing to do with speed.
GitHub User Location Search
I have a lot to thank BBSs for in cultivating my life.

Textfiles.com for nostalgia.
Same. I LOVE Python, but if I want to take a project particularly far I tend to end up porting it to a static language. (Usually go these days.)
It probably depended on the kind of BBS and the era too: in my country, on Fidonet almost everyone used his real name.
This is the #13 repost. A few reposts are ok here, but somewhere between 5 and 10 is too much. The mods may get mad and ban your account and your site.

Try a different strategy, like posting an interesting blog post about the tech stack or the problems you had to solve for your site. Perhaps you can make a post with some statistics of the use of the site, if it doesn't break the privacy of the users.
Sadly true. One can't help but fear the dark extremities of this identification.
Threading sucks. It's a situation where you have some external process (the operating system) deciding when different pieces of work should be woken up, with no way of feeding this back (so it just bases it on relatively naive schedulers).

In practice, most of your threads are in one form of wait loop or another and you've just got polling both inside the threads and with the scheduler.

Have a look at Erlang if you want a better model :) the erlang "processes" (different to os processes) can intelligently only wake up when there is work for them to do.

For a language to efficiently use cores, it really needs to include it's own scheduling.
It's just your standard school yard bullying amplified to web scale
"When You Watch Sports, Your Brain Thinks You’re Playing" doesn't match the article title, or appear in the text.
It didn't "go viral " it was shoved onto the scene by a very nosy self-promoter who piggybacked on the popularity. I'd say it's the same as illegally profiting off other people's experiences without their consent.
This problem could be related to asymmetric information. In case that a huge converage of K&R is known you become a valuable target for kidnappers so the cost of the coverage should increase, so if the coverage is known the insurance company could negate payment allegating that the ground rules has changed.
>Actually solving a constraint graph is an NP-hard problem

How big of a deal is this IRL? Assuming you have 1000 modules, how long should it take to solve the graph?
As an embedded system dev, I'm wondering if these async features can be implemented on bare-metal (or without runtime)? Maybe I'm dumb and it might be a wild thought but it would be great if I could easily integrate async language features with hardware interrupts.
...which happened just around the time batteries became good enough for both daily use, as well as a phone’s typical lifespan.

10 years or so ago, a three-year old cell phone battery would still be good for maybe three or four hours per charge. Today, I’m using a 5-year old iPhone that still gets through a typical day on a single charge.

There are also battery cases, or external battery banks, whose introduction has solved most people’s battery-related questions, except “why are people still complaining about non-removable batteries?”
Self plug: If you enjoy this and want some (less technical) insight on connections between ML and thermodynamics, you might enjoy my series of blog posts: http://henripal.github.io/blog/stochasticdynamics
Both studies were of groups as a subset of larger groups. That is, these fans were not individuals home alone. I'm curious to know how that might effect their body's reactions.
At least consider changing your webhost.
Love both of these. Perhaps more so "A Deepness in the Sky", with its darker tone, very thoughtful programming-related remarks, and the reversed "alien invasion" concept.
it is the title of the webpage, though. Pretty strange.
ya, but the game isn't going to launch for another 7 years, so you are worrying about % of revenue that is so far in the future, it might not even happen
> they removed 'user replaceable' for thinness

Also better water resistance.
Everything is of course possible, but at what cost?

In my experience, with large projects, you get to pick 2:

Dynamic typing
Development velocity
Reliability

I've seen multiple large projects grind to a near halt in their development speed, and I've seen some retain development speed, but unreliably crash after various changes.

UT coverage is expensive. System tests don't catch everything. Either you fear changes, and the system rots, or you work very slowly with coverage for everything.
I wish this were true of programmers of average ability.
Minor nitpick: Boltzmann machines are hardly recent. They were introduced in the eighties.
My guess is the algorithms and infrastructure serve search functions across all of their products. The "search market" is really the "Display advertising" market, and sure, they suck at that because no one goes to bing. But bing isn't worthless.
They are, but calling a function asynchronously takes a lot longer than synchronously. For small functions the execution time could easily be increased by more than 100%. It's something that only really makes sense if the function will do (slow) I/O or a lot of computation, and the program has other things it could do in the meantime.

Making every function call asynchronous is likely to make most programs a lot slower.
It's probably not about the complexity of the wipers, it's about the complexity of the wiring system. By putting everything on a bus you only need to run one set of wires around the entire car, rather than individual control wires to each gizmo.
Ranked choice would be much much more effective than getting the vote out for addressing the problem of in a more than two way election having the least desired candidate win because the more desired candidates split the vote.

The more good candidates that are widely approved that run, the better the chance in our current system that we'll select someone who is widely disapproved. We can elect someone who would have lost one on one verses any of the other candidates.
So far, I get a feeling that vendoring will be a second-class citizen in the world of modules. Unfortunately, I will not be surprised if the team considers removing the support entirely in a future release. I just hope that a viable alternative will be proposed.
Sell it or run it, there is no middle ground
Then what you have is not "anything". You have an expression problem:

Either each element has some "handler" that does the right thing for that data type.

Or you have a set of cases that each data can be, and you handle them all.

Neither is just "any type". And static types are very suitable to describe either.
Is the MacBook Air dead, then? Light and powerful isn't a valid niche anymore?
Show HN: A practical guide to well-being for singles
I ran QNX as a desktop OS for three years when I was working on a DARPA Grand Challenge vehicle. The vehicle ran QNX, so the development systems did, too. It had an early version of Firefox, the Eclipse IDE, Thunderbird mail, and all the Gnu command line tools. Sadly, QNX under Blackberry no longer offers the desktop environment. And QNX's open source/closed source/open source/closed source transitions angered the development community so much that people stopped offering QNX versions of UNIX/Linux software.

The most striking thing about running QNX on the desktop was the absolutely consistent response. It doesn't page, so everything is in memory. Going back to Linux felt so laggy.

You pay about a 10%-20% overhead cost for all that interprocess communication. It's not a big deal on modern processors, because when you send a message, the receiving process is running on the same CPU and the data is usually in L1 cache since the sender just put it there. So copying is cheap.

Incidentally, all the Boston Dynamics robots run QNX. They're coordinating all those limbs and valves from one CPU. It's not distributed; that would be too uncoordinated. Valve update is at 1KHz; balance update is at 100Hz.
If you are actually worried about getting ransom insurance in case of being kidnapped, maybe you should just skip the job.

If you really want the job, ask for an extra for paying the insurance yourself. That way you are 100% sure you go coverage (if you don't forget to pay the insurance!)

Personally, I wouldn't take that job, even if I could buy the best insurance myself. I just don't like betting against myself.
That’s amazing. I use grain to disguise compression all the time and always this should be possible.
The paper mentions that the source code is available at netstreamline.net, which is now a spam domain. Here's the most recent IA link:

https://web.archive.org/web/20130624173559/http://netstreaml...

If the topic of the paper is interesting to you, you will likely be interested in other parts of the Streamline project.
Alright, so I do computational plasma physics simulations for a living. Given our problem sizes often reach sizes which require teraflop level of parallelism to get done before I retire (that's my scale, I'm sure you're aware of petaflop sims the fluid/engineering guys do) we do need concurrency but it's done by chopping up the domain, literally the volume of space we simulate, onto processors. Now, we could possibly do async at some level (sub node level), but we absolutely need to be syncronized globally because we are simulating real-life physics and we need to maintain causality, especially when we pass information between nodes. Say a wave front passes across one node boundary into an adjacent one, waves must move at a finite and causal manner, of course, just as if you watched a ripple on the surface of a puddle.

If we did the whole problem async (async by default as I interpret it) it would require so much bookkeeping to keep causality that would make it unreasonably difficult. For things that require causality like that, we are lucky that the default mode of computation is synchronous because it fits my problem domain perfectly.

That's why I say "not everything is web" because while async maps well to problems like a server-client type application, it doesn't map well to all problems like my problem for example. Also, as someone else said, sync is easier to reason about for problems that don't require a lot of parallelism.
This is the situation in Scheme, Erlang and Go (although the latter two strongly bind continuations with a specific, built-in scheduling), and what we're doing in Java as part of Project Loom. All Java functions will be able to run inside delimited continuations without modification. Continuations/coroutines are thus a purely dynamic rather than a syntactic entity.