skysight-inc/HackerNews huggingface dataset:
About 20-30 minutes into town. That town was traditionally agricultural but became what was considered the bedroom community for going another hour out to where a lot of people worked, or one more hour out to where more people worked. All that aside, rural means relating to the countryside rather than in town. We were out of town for sure.
A comparison of ingredients in McDonalds French fries in the UK and US from a 2015 story:

https://boingboing.net/2015/01/22/usa-mcdonalds-fries-have-1...
I hate Node's model of async concurrency. I need one thing to happen, then another depending on the result of the first, and so on, way more often than I can let several things happen at once or in any order. Probably something like 100x as often. Even when I can have multiple pieces of logic executed at once or in any order, it's usually just a couple, and internally they usually comprise more of the same dependently-ordered execution. If I can really kick off a ton of something at once it's usually one function/operation, which again... consists, internally, of a bunch more stuff that needs to happen in a certain order.

It'd be way more convenient if Node just assumed it couldn't carry on with the next operation until the current one was done, even if the current operation is async I/O—feel free to go off and process something else, just no more of my code—unless instructed otherwise. IOW, caller decides, yes. I 100% do not understand the appeal of a system where you have to specify that you do want the next instruction to wait on the result of the previous one. "But you'll block node's single thread during your I/O!" no, it can go do something else, just no more of this particular line of logic in my code unless I specifically tell it otherwise, thanks.

Caller decides is both easier to follow and more useful.
Lets understand why we're here. Corn was first to be hybridized and resulting seed marketed. As yields grew, farming became more stable and farmers less poor. Corn got cheap and many commercial applications (starch, syrup, protein, fibre) seized on it as a practical source for many products.

Like VHS vs Betamax, sure there are better choices for food and commercial uses. But corn won, won early and won big. It'd cost trillions to switch to something else now.

So complain all we like; still we find ourselves in the same place. Corn is king.
Hmm, fascinating. I took advantage of the exact same thing on "Mama Celeste" frozen pizza at "Stop & Shop" here in the US a few years ago. But the free pizza vouchers were printed on the sales receipt, rather than on the product. So I could return the single purchased product and end up getting all the pizzas completely free. I emptied their pizza freezer. The store figured out what I as doing pretty quickly, but didn't much care as they were reimbursed by the manufacturer and thought it was pretty amusing.
If you don't have async markings, you can't know where in your code you have concurrency and this would require you to use synchronization primitives. For shared memory languages this means all that error-prone shared memory multithreading, like in Go [1].

[1] https://songlh.github.io/paper/go-study.pdf
> why you are against the protests?

Note that GP never stated that. They gave an assessment (correct, in my view) of mainland opinion about the protests, they never said that they subscribed to that opinion.
Great news! XFCE still is my favorite desktop environment on normal PCs for being the right balance between features and snappiness, although I tend to use rox-filer rather than Thunar for operations on most used directories for it being faster than Thunar (although Thunar did improve a lot). To do so I keep those 4 or 5 icons on the panel each of which calls rox-filer and one of the paths as the argument (example: "rox-filer Documents" as command with "~/Documents" as working directory). This makes it much faster especially with crowded dirs.
Abacus in the 0000's...
No, that would usually be intermediary. If you want to be more specific you can say reseller or broker.

Monster in the middle is at least cute and conveys the authors intent that this agent is untrusted and assumed malicious.

People in this thread clearly don't like being called a monster which I think demonstrates exactly that words matter and these ones are doing their job.
That was part of the problem on the USS McCain: the crew lost track of where essential control inputs were being routed from.
the bitkeeper license disagreement impacted how the tool was used. Git's license really only impacts how its developed.
Leaving it up to the caller to decide seems reasonable, but you only have control over the top level, you still have no control over how the function you're calling calls other functions.

Also, blocking on a future is trivial (just call poll).

So I would argue that async/await does a better job of leaving it up to the caller to decide: use await if you want async, use poll if you want sync.
Modern React testing, part 1: best practices
You can run an async routine synchronously if you use the correct runtime, or block while polling until the function succeeds... "async" functions are functions that can be suspended and turned into an opaque thunk that you can pass around as Rust data, and "synchronous" functions aren't. If you like, you can think of async functions as being functions that can run either synchronously or asynchronously.

You can't (in safe Rust) easily replicate what async does for you because it understands how to handle borrows across yield points, which turn into self borrows when you turn the stack into a concrete object in Rust. That's not really an issue in garbage collected languages so it's not quite as much of a necessity to have a specific keyword, but it's still inconvenient in most languages to write everything in CPS or use combinators to acquire thunks.

As for why you would want a function that's not asynchronous... well, various reasons, but one is performance. Creating a thunk and then sending it to a runtime which decides what to do with it (or polling) usually has some overhead compared to linearly calling a function on the stack.

Another reason is that, in Rust, top-level asynchronous functions normally need to be quite conservative with what they own if you want to use them with an actual asynchronous runtime--many of them like to send the thunks between threads in a static thread pool, which limits you to thread safe constructs and owned (or static-borrowed) data. As a result, even if there was no overhead for using an asynchronous function synchronously, you would still in practice have to either sacrifice performance and generality by keeping your data owned and thread-safe (to make things work with thread pools), or embrace all the usual stuff you would do in synchronous code (like borrow things from a previous stack frame) and lose the ability to use your async function at the top level in most existing asynchronous runtimes. So from that standpoint, it's not really up to the caller. This is again not really an issue in garbage collected languages that only allow references to managed, heap-allocated objects.

There are more reasons than that (being able to efficiently call out to blocking C APIs, wanting to use builtin thread locals across function calls without worrying about how the function call is going to be handled, current issues with recursion, etc.). They may be considered artifacts of the implementation or otherwise resolvable--I'm not necessarily saying they aren't--but they are reasons in practice why you want to have synchronous functions available.

So tl;dr I think most people's immediate intuitions about how async/await should just be sugar, or async should be up to the caller (i.e. all functions should be async), don't straightforwardly apply to Rust even if they are valid for most other languages.
Or when a cat brushes past, in our case.
I swear, I read the python headline, turned away, then read this headline and thought I was going insane because I swore I read python.
Maybe. One of the issues is these seem to depend on having a very accurate model of the animatronic models and how their materials will react to forces so that the required damping motions can be baked into the model.
Disturbing True Block Party Stories Animated
It seems like pipenv and poetry fill different niches: pipenv is intended for application deployment, so you're likely to only have one version of python, while poetry is intended for building libraries.

I found the tox support a bit hacky, but not bad, and got 3.5 to 3.8 testing just fine.

Poetry does make the publishing process pretty seamless for the simple case. If you're starting a new library, poetry is great.

I think poetry needs a "fuzz option" to test random valid solutions to the version constraints, to check if the older versions are really valid.
> OpenBSD does not use GPL code

OpenBSD has used a lot of GPLv2 code, until recently their platform compiler was a heavily-patched version of the last GPLv2 version of GCC.

There are git implementations under permissive licenses as well. And it seems like GOT is yet another such implementation.
They did not know you. To them you were "the stranger". Imagine them as blacks, saying the same things about "those strange white people". Racism is kin-preference , kind of ingrained in people, and it takes a sophisticated society like ours to rise above it because we, truly, don't need it anymore, it's a relic. Do you think that their view of strange people has a bearing on the other things that they said, or do you think their teachings express truths that are universal among people? There has been very intense research in the "racialization" and "genderization" of science and philosophy in the past decades, but maybe ask yourself if we learned useful things from it, things that are actually actionable.

Also, realize that american attitudes towards race are somewhat different from the rest of the world. Race in modern america is politicized, while for most of history around the world, races generally mixed with little political component, especially under great empires.
Given how surprised Jeffery Epstein was to find out he committed suicide, shouldn't anyone anywhere making such a comment get downvoted?
Is it normal for Xfce stable releases to take 4+ years? If I was a user waiting for HiDPI support I probably would have just given up.
SSL termination isn't the same as MITM and you know that.
they would be useless if they weren't bioavailable
"X is eating the world" is eating the world
As standard of living rises, number of people able to afford leisure and travel increases. Yet the number of destinations is fairly fixed (the Earth isn't getting any bigger). So every place gets crowded.

Its not tourism; its growing affluence and diminishing 'touristy' places. No longer as easy to find an ancient monastery to tour, when they've installed AC and rebuilt with electric lights and indoor plumbing.
In an alternate universe, Pepsi utilized this navy to enforce the dominance of its brand.
It will be nice if the use case of TS only being used as a static checker be supported better, but then there will be no point in TS as a language
This describes at least half of all programming efforts
Yep, therefore tourism==Python.
In order to train the model, wouldn’t you want a physics simulation, so you can train the model quickly? But if you had a physics simulation, aren’t there much easier methods to use than machine learning?
>No big system has ever been built in an untyped or weakly typed language. Well, except just about every bit of software we all use everyday. But it does seem like some small startups can't get by without it.

Many have built models of the Eiffel tower with toothpicks too, so?

You can still built things with inadequate tools: inadequate != prohibitive. You just have more problems going forward.

Which is exactly the lesson people who write large scale software have found.

What is this "just about every bit of software we all use everyday" that you wrote about as been written in weak types?

Most major software is still written in C/C++ (anything from operating systems, Photoshop, DAWs, NLEs, UNIX userland, MS and Open Office, databases, webservers, AAA games, what have you). One could use just that C/C++ software, and they'd have almost all bases covered.

The rest is e.g. Electron based software and online services. For the latter, most of the major ones (e.g. Gmail, Apple's iCloud services, Microsofts, online banks, online reservations, etc, etc) are not written in "weakly typed languages", only the client is.

And those that were initially written in a weakly typed language, e.g. Twitter with Ruby on Rails, others with Python, etc, have rewritten critical services (or entirely) to statically typed languages (e.g. Twitter went for Java/Scale, others for Go, etc).

And even for the client, most shops are now turning to Typescript (and FB to Flow) because they've found weakly typing is not good enough for large scale. So?
alternative to typescript would be facebook's flow.js, which works with 'normal' JS code
Python is Eating the World

Tourism is Eating the World

Software is Eating the World

[...] is Eating the World

I guess there will be nothing left to eat soon.
The contents list doesn't link to the pages.

Also why no HTML version?
That's great, thanks. Boston Dynamics is a good one too, although less frequent: https://www.youtube.com/user/BostonDynamics

Anyone know of other channels like these?
Thanks for updating for me. I was just looking at "The mutex object referenced by mutex shall be locked by a call to pthread_mutex_lock() that returns zero or [EOWNERDEAD]." and saw that it returns zero or EOWNERDEAD and thought that zero = EOWNERDEAD. Thanks for all your comments. They were helpful and I learned new things by reading your posted links.
That's kinda my point :)
You're talking at cross purposes. You are talking about how you think the world ought to be, and the person you're responding to is talking about how the world is. They're fundamentally different conversations, and it's not particularly useful to mix them, especially in such a critical manner.
You got the legitimate interest wrong. I wont bother explaining, as I am sick of downvoting (would love to discuss recitals), here is presentation from Tim Walters, check the legitinate interest (or the whole, you might be surprised): https://www.youtube.com/watch?v=-stjktAu-7k

Bottom line, "the grain" of GDPR is user interest. Not "user expirience", not bussines interest.

Users interest.

And it is HARD to decide instead of him, I would rather pop up consent dialog with opt-in than showel everything under legitimate interest.

As it is so easy to make it wrong: sure, you are sending a packet to the customer, you need (legitimate interes) address, phone number comes handy (requiring it is fishy), forcing it to protect login on a social network? I wouldnt do it. For me, as a security aware person, you would crawl trying to prove I am in danger with 15 letter random generated passwords generated for each and every site. Unlike for John Doe. So, it becomes optional, while forcing it, in my case, violates GDPR. It was just one example.

But anyway, check Tim Walters.
Food. Food is eating the world.
I think this article justifies 'simpler' as more than just "characters to write". Rust is a fairly different language in that it isn't GC'd, and the async/await sugar really alleviates a lot of pain around that (among other things).

As for calling async from sync, I imagine you just create a runtime and block on it.
Double redundancy for the Saturn V memory, how were disagreements resolved?
Certainly, women have unconscious desires. However, the existing situation is a “tragedy of the commons”. It is in any one woman’s individual interest to hold out for the best possible match that they can get.
However, if that strategy is shared by the vast majority of women then they will end up in competition over a very small (somewhere between 5-10%) of the most attractive males.
In view of this, it would be rational for many women to consider settling for less attractive men who still might be a good father/provider.
Presumably most of these are accidental, which makes that an ill-fitting term.
That whole twitter stream is a good example of "bias" claims that seem to actually explicitly be "this article doesn't say exactly what I want it to say".

I don't think the word "attack" is as loaded a phrase as that person thinks it is... and less loaded than the tweets linked to.
> because of parental social neglect

Very well said! It is also quite disturbing to see how many parents today do make their children become sugar and youtube addicted.
Sherlock: A Deep Learning Approach to Semantic Data Type Detection
rom a practical perspective, it's much easier to deal with `fs.readFileSync` in top-level code than to dive face-first into callbacks. (Remember, `fs.readFile` doesn't return a `Promise`.)

If `fs` was promise-aware and top-level await existed, it would be a different conversation. As-is, for writing a one-off script, avoiding callback hell is pretty nice.
In C# you can't await an async in non-async function, but you can block until it's done. There is no drawback to having all code async.
Attracting and keeping top remote talent
> How do you deal with a situations when you have non-async/await code, and then you need to call just one function, which happened to be "async", and you can't do until you mark all your functions async as well?

Just call the poll function on your Future.

Just because Javascript sucks doesn't mean the similar feature in Rust does too. :)
Both tourism and Python use an insane amount of energy, thus they are equally bad for the environment. But they both feed a lot of people so we can't just get rid of them just like that :/
Regarding all the Social Security number issues, it somehow reminds me the Onion title "‘No Way To Prevent This,’ Says Only Nation Where This Regularly Happens" (I know USA is not literally the only one, but almost) - plenty of places have something similar to that number, but USA is pretty much unique is treating simply knowing it as some kind of identity proof. "Something you (and a bunch of others) know" doesn't cut it.
You've got it backwards.

(Sound) Type systems guarantee correctness for the invariants encoded as types. If it compiles, you know it doesn't have any type related errors at all. With more evolved type systems even your program's logic (or large parts of it) is guaranteed.

Tests just allow you to test random invariants about your program. If it compiles and your add() method works when passed 2, 2 and gives 4, it still might not work for 5, 5... (contrived example: imagine it with much more complex functions, though even a simple e.g. "one line" time conversion can have similar issues).
Modern, rich countries externalize their polution-causing activities to developing nations.
Using AWS Kinesis with the Kinesis Producer Library
Wow, people really like standing in front of and on top of trains. I was expecting falls from height to be far more common (at least relative to trains).
Clearly, the Hacker News gestalt is providing us a solution here; set Python on the tourists. "Sir, in order to visit the Eiffel Tower today, I'm going to need you to tell me what this Python code does...."
I read an alternative interpretation somewhere about this. Take it with a grain of salt.

1. High status men have access to a lot of attractive women. With the way men's biology is wired, it wouldn't be surprising that they would choose an attractive, relatively lower status woman over a highly accomplished but not that attractive one.

2. High status men often have stressful work lives. They would probably prefer a partner that makes them feel relaxed at home. High status women usually have careers themselves so it would be difficult to provide this need.
The solution to this problem is for consumers to organise and buy produce on their terms, by forming food co-operatives.

Buy the food you collectively want in bulk from the wholesalers and then sell it back to yourselves as customers. This removes the overhead of profit (and often labour, the highest cost, if co-op members do shifts at the store) and in many cases marketing, packaging and other costs. It thus allows you to have access to healthy, fresh, local, sustainable, etc. food at a reasonable price.
If that's the use case you have, then Facebook's Flow is a better fit.
I’m guessing the target market is users who are not proficient in scripting, but rather business users who want to monitor their employees or non-coders who want to retroactively be able to construct time logs of their work.
> Although the more ergonomic syntax is not ready yet, asynchronous I/O is already possible in Rust with ecosystem around futures, mio, and tokio.

Does this mean all 3 of those crates are required to achieve async I/O?

tokio is a large project. Which part of tokio specifically is supposed to be used in conjunction with futures + mio to achieve asynchronous I/O?

Edit: it seems futures + mio are dependencies of tokio.
But it does require knowledge of generators. You're suspending a function during execution; that's what a generator is. We could've just named a global `async` that declares a coroutine FN on promises, and named `yield` as `await`, and the whole thing would look identical to now except for an extra paren and asterisk. You wouldn't need to understand their inner workings any more than you do with async/await now.
Type 1: Not sure.

Type 2: The Master Algorithm by Pedro Domingos
The point of the thread is that US manages to look like a bully not because it sentenced him to prison (which it didn't, indeed), but because it placed tariffs on EU agricultural products in retaliation for it refusing its beef stuffed with hormones.
We still have the billionaires
Contains the most profound written wisdom:

A Discordian is Prohibited of Believing what he reads.
Well, Facebook is trying to make OCaml happen for web development (ReasonML). Not sure if they're succeeding, though.
To be clear, either of these methods can have problems, it's not unique to curl and your shell of choice. Some of the better open source projects will say up front that if you are concerned about this kind of thing, feel free to read the installer script and decide for yourself if everything's kosher.
The claim being responded to was that there is no evidence that "growing with chemicals" has increased crop yields. Evidence was provided that crop yields have increased as the industry has switched to "growing with chemicals." The percentage of those yields ultimately going to livestock is unrelated.
count how many 'you', 'them', 'i', and how many pronouns are being presented to each individual, group by source
Indeed, here in the UK we have the very similar "National Insurance Number" for tax reasons but it's never used for identification as it's assumed to be public knowledge.
Wonder if Plaid is enough/covers most banks
I was able to read it in incognito mode.
Reddit Thread: https://www.reddit.com/r/PHP/comments/coe5a7/p_faq/
Does that really happen?
What's the point? You'll create dimensions never used by users (CPU sensitive), you'll store files not used by users (storage), you'll miss some configurations for sure. They're creating files once and store them in a cache (CDN and local cache). Basically, they are doing something similar to your suggestion minus creating unnecessary files.
Amazon PSA: Sort Reviews by “Most Recent”
It took me a while to get comfortable with it too. The intuition I use is that in the past it used to be DrawWindow(), DrawWindow(), DisplayResultsofSlowFunction() and then the window would freeze for a few seconds, but with async/await theres a queue basically and your DisplayResultsOfSlowFunction() gets put to the side while awaiting so DrawWindow() can keep doin what its doin and your app doesnt appear to freeze, for a gui example (idk if that helps or if ye already knew it but just in case, for me all the internet explanations never talked about the scheduler for some reason so it took me a while).