skysight-inc/HackerNews huggingface dataset:
there are three parts to your problem
1. recieving mail and processing it. Since you are planning to host it by yourself answer would depend on what are you using for hosting. Solution can be as simple as reading a file(i.e. recieved mail) and extracting relevant fields using whatever language you know python/shell ecript etc. This part would be highly specific to what you use as your mail server.

2. server that responds to the api request made by chrome extension. This is where you can use django it would provide basic security as well as cater to the api request made by your extension here any server would do as your use case is quite simplistic. It should be few lines of code depending on your familiarity of language.

3. Chrome extension this would be in javascript.

are you developer? or do you have access to developers? if yes than it should be straightforward.
It would be helpful if there was a website with demos available.
If guns are your thing - probably most things by John Browning. His designs are basically still in use more than 100 years later.

https://en.wikipedia.org/wiki/John_Browning
> hey will start to turn on Putin

Sanctions usually don't lead to the population turning on the regime, after all it tends to make the population more dependent on the regime, but sanctions do frustrate the regime's ability to wage war etc.
Yeah, nc 80. Or openssl s_client for https, you can also run through stunnel.
Mind sharing what those use-cases are? Most of what I've heard of blockchains for non-cryptocurrency, non-token things are either cases where the blockchain is still permissioned (with some sort of root-like user with god powers), or could just as well be a DHT (like ipfs & bittorrent), or are things that sound interesting as a thought experiment but could never scale to their intended use-case, or something that is already solved by much simpler tech.

I'm open to the idea that blockchains are interesting as a tech but I have yet to see what they would be the best solution for besides illegal activity or speculation.
I've eaten at three Michelin Stared restaurants in the bay area. Gary Danko, CPQR and Manresa. All were interesting experiences. Gary Danko was by far my favorite. The other two felt like it was all about he ego of the chef. Gary Danko was all about my enjoyment of the meal. They have three courses separated in sections, but you can mix and match. If you want a taste of filet mignon as an appetizer and a huge plate of escargot for your main, that's fine with them. Their wait staff is by far the most elite I have ever experienced. No one asking you if you need anything and not a waiter to be found, unless you need something then they magically appeared just as the thought was percolating into consciousness. Amazing.

CPQR was weird. We did three courses from the menu. Appetizer was the best, but the most memorable was the second course, though not for the taste. I order a pasta dish and before they serve they place a steak knife next to me. A steak knife, what the hell did I order? The dish comes and looking at it I'm still wondering what exactly I ordered...

Manresa was also a unique experience. First all the dishes were absolutely, amazing. One person in our party did not like fish except for scallops, which they accommodated. We proceed to have five fish based dishes in a row. Even though all five were fantastic, at the end my mouth felt like a tide pool, and having grown up on the beaches of Santa Cruz, I know that taste/feeling well. On the third fish dish, our friend got his scallops and boy did they look good. Then on the fifth and last fish dish he was served squab. The rest of us looked longingly at that bird, our collective mouths watering. He was lucky to leave that table alive...

I think the food was more inventive and more perfectly cooked at CPQR and Manresa but it's Gary Danko I would like to go back to.
This is a great example of where the way people use the word "simple" comes along with lots of caveats and mean different things to each one of us. Increasing simplicity in the user experience (by removing seemingly arbitrary restrictions to the type system) mean increasing the complexity of the implementation. We've already seen that with match ergonomics, the borrow checker and async: "adding complexity" results in "a simpler to use" language.
Ça fait pitié.
The intent of fork() is to start a new process in its own address space. That *fork() variations that run in the SAME address space are confusing. A use case today for fork() might also be sandboxing apps. Certainly I expect browsers use this approach to spawn unique pages. But generally fork() is very specific from my recollection.
If you want your function to block until the promise resolves, then the function calling it also has to block, and the function calling that has to block, and so forth.

At the top of the chain, this ultimately blocks the entire event loop (Javascript semantics are generally not concurrent), so no UI/network events can be processed until that promise resolves and the page/server is left non-responsive.

(And that's assuming you can somehow define clear semantics to run any Javascript code involved in resolving the promise; otherwise, you're deadlocked!)
I mean both. Web development is easy. But the majority of software development jobs are web development. A huge majority.

This majority makes it so that the broad statement of software development being easy mostly true.

Think about it in terms of availability of jobs over the breadth of engineering topics.
How do you get through books like these, especially if you're not a fast reader / native speaker?

I find that they have a core theme that could be explained in a few pages, but somehow they try to fill 200+ pages with the concept with examples, anecodotes and such.

Is it usually worth reading through the entire book or is there a 'life hack' to reading them faster?
And people would be making essentially the same complaints and essentially the same arguments about the subsidies (see agriculture subsidies)
the requirements of the second case are a subset of the first case, so then it should be theoretically possible to await inside non async functions. Seems to me that JS simply doesn't implement this ability, but it could if it wanted to
Article/project author here, happy to answer any questions you might have about this silliness.
> once something is public, and in control of others, it is impossible to make them 'un-public' without violating the 1st amendment.

I do not think that is accurate.
The general population has indeed been observed to be resistant to change. Max Planck noted that science advances one funeral at a time, and the same appears to be true of social norms as well (e.g. really old people being forgiven for blatantly racist behavior because they’re “from a different time.”)

The fact that a minority of people are able to adapt their views over time does not change how the general population does not do this.
Commonalities Between TikTok and Victorian Parlor Games
JS will await on literals too, it just immediately resolves to the value of the literal.

I use this all the time in async functions with code branches, some of which await and some return an immediate value.
You can’t sell what you don’t occupy
The replies suggest a need to separate mental math from mental arithmetic. I can't do mental arithmetic despite a lifetime of trying to develop the ability, but still have no trouble with the mathematic intuition based on expected costs described in other comments. It's easy enough to round things to 0 or 5 and sum it up for comparison even if doing the actual numbers in my head just won't happen.
With your same example though, now this employee is listed in a bunch of Apple lawsuits and will be unable to ever get a job again because of this kind of search engine.
> I am certain that many people in government would agree with you - they would LOVE to be able to hide what they are doing and not be held accountable for decisions they make (or don't make). We need more public disclosures, not less, imo.

Agreed 100%, a local court has been making precedents with that and...it's unnerving.

https://www.thv11.com/article/news/politics/routine-gag-orde...
Having anything in cache allows you to check for errors and requirements.

So for example if you're going to be away for 7 days and you need to spend $100 a day in notes, you might be able to avoid hitting a withdrawal limit, eg if you bank for some reason limits your weekly to $500.

Basically the estimate serves as an input into your requirements for the next step, and tells you whether there's something to worry about.

Same as if you're painting your house and you need to know whether you need to go buy a new bucket of paint or the existing one will do.
Definitely. But how will they split the 154 questions? The prize pool is already big enough ($13k just a couple hours after the announcement and 5 days before the registration deadline) that 50 people could take it together and walk away with $260 each.
Ways investors review product readiness in startup pitch decks
Why is it so impossible for these people/organizations to accept that they made a mistake and own up to it? The entire response by the State Bar of California is nothing but a deflection of blame that rests solely on themselves and their chosen vendor(s).

What are they going to do next, call Missouri's governor and ask for the playbook to follow? The humans behind the scenes at the bar are looking incredibly pathetic here.
> I have never understood the hostility toward whiteboarding

If anything a candidate that rejects whiteboarding is a good signal that they're not a good team fit.

I personally prefer to conduct coding interviews in an environment where the code can be executed (if that's the main objection for "whiteboarding"), but even so the environment is often too different from what the interviewee is used to (IDE / availability of familiar libs / OS environment) that it's not that different from whiteboarding anyways.

In my personal experience there are indeed occasionally people that I'd recommend for strong hire with their past experience / credentials alone, but it's too rare to make any rule out of it, and if any candidate outright rejects it, it probably gives a signal that I'd personally interpret as negative anyways.
oh very slick!
>procedures far more protracted than necessary because parties cannot rely on written statements of law as reliable guides

I would say it's a problem with laws, not the system itself. Also the continental system does not imply that precedents do not have any force. The difference is that when a law changes the system accumulates new precedents for it instead of using outdated ones.
Is it a fair point to implement first with fork() because of memory protection, then optimize by using benchmarks and potentially vfork() for speed? Benchmark areas can look at synchronous locks, copy-on-write memory, stack sharing, etc.

What are the good practices of security tradeoffs of fork() vs. vfork() especially in terms of ease of writing correct code? I'd thought that fork() + exec() tends to favor thinking about clearer separation/isolation. For example I've written small daemons using fork() + exec() because it seems safe and easy to do at the start.
I was always disappointed by the performance of fork()/clone().

CompSci class told me it was a very cheap operation, because all the actual memory is copy-on-write, so its a great way to do all kinds of things.

But the reality is that duplicating huge page tables, and hundreds of file handles is very slow. Like 10's of milliseconds slow for a big process.

And then the process runs slowly for a long time after that because every memory access ends up causing lots of faults and page copying.

I think my CompSci class lied to me... it might seem cheap and a neat thing to do, but the reality is there are very few usecases where it makes sense.
Those thumb cluster keys look pretty nonstandard
> we should think twice before pumping children full of hormones

Have you ever talked to a trans individual? You literally can't do anything without every professional in the field asking you to do a little more than "think twice".
Because it is an essential piece of infrastructure and without it you lose power to others around the world who would use it to control you.

The cost of not having one is hard to put a number on but very likely much higher than the savings of offshoring all of your shipping.
Highly recommend doing this occasionally. Like so many other things, quantity can be exchanged for quantity. Go to a 5x more expensive restaurant and skip 4 meals at cheaper restaurants.

Restaurants that are expensive-ish but not sublime or memorable experiences can be skipped. Eat cheaply or really expensively. Skip “quite expensive but not fantastic” restaurants. Tasting menus at one star restaurants is where the value is.
Moving strategic assets between ports.
I tried it, but couldn't achieve anything phenomenal with rain sound!
"How not to die" is written by Dr. Greger, a devout and somewhat militant vegan. I used to listen to his You-tube channel which, at first appearance, is research-based nutrition information. However, if you scratch below the surface and read the original papers you will often find that he has slanted the interpretation to be pro vegetable based, while ignoring the sections of the same papers that could be interpreted as pro-dairy or pro-meat. His work is a case study in confirmation bias.
You can see more books that James has summarized here:

https://jamesclear.com/book-summaries
>If you can't even name one example without extensive research then it's likely not so trivial.

If I had to name one off the top of my head it would be ovh.

>And where you get the firm conviction that both cloudflare and existing CA's aren't tapped already?

"why don't you let the government mandate encryption backdoors? Your messaging app is probably already backdoored already"
Pretty much all the options are covered here:

https://github.com/diimdeep/awesome-split-keyboards

Lily58 is a popular minimalist split keyboard
What's the missing fifth tow you are referring to? The f keys
Russia was threatening Ukraine not to join EU, and now Ukraine has nothing to loose.
The law just needs some graph theory
The Crypto Revolution Is an Existential Crisis for Video Games
This is where judges and spirit of the law come in. Laws hav always been imprecise and one remedy for that are judges and trials. I doubt what the company is doing will hold up in court if they want to argue that they satisfied the provision of the Jones Act.
Database functions to wrap logic and SQL queries
The BBC Is Using It’s Own ‘Dot BBC’ Domain (2021)
No longer resolves.
You can fly backwards in a Cessna pretty trivially. Anything with a low ish stall speed will have that happen on a windy day.
I'm pretty sure the only reason we don't recognize this, while we do with movies, is that there aren't rules governing who's credited and what their credit looks like, as there are with movies. You don't get "Story by X, written by A, B, & C, based on characters by Z", and instead one or maybe two names are on there—you do sometimes see a writer credit (separate from the more prominent "created by") on some of those long-running series where the original author stopped somewhere along the way, or two listed for outright collaborations between known authors.

If book writing operated under the same rules as screenwriting, this would all be a lot more visible.
Thanks and you've actually got a demo
John Wesley Hyatt - Plastic

The guy was trying to make ivory-free pool balls and discovered something that changed the future.
So, it actually is X1C and A78C.

https://blogs.windows.com/windowsexperience/2022/02/28/mwc-2... references PAC support, which is only in the C variant of those cores.
There's been a lot of discussion here of the technical reasons for function coloring, but the semantic reasons for it are far more interesting and important to me. I suspect that technical limitations could (and in some languages do) have workarounds, but there's real value to the system as it's set up.

When I mark a function as `async`, I'm specifying that this function will be performing some form of asynchronous I/O. Any caller of that function (or its callers' callers) will therefore also be doing I/O. Such functions may take a while to "return" and are more likely to throw an exception.

Function coloring makes these properties explicit. By forcing all callers to also be `async`, it becomes easy to see which parts of the codebase are doing (somewhat risky) I/O work and which parts will be near-instant. No one ends up surprised when a call to `getFoo()` ends up getting `foo` from the network rather than the local object.
Right, which is why you would never XOR in this manner, and would hash instead. You don't want the password or content retrievable that easily.
Nigeria condemns treatment of Africans trying to flee Ukraine
I agree. On a related topic, I think it's important that we have some low cost software developer labor to make sure that we have the ability to develop things cheaply and compete with other countries.

I propose that we start by reducing your salary by 40% so that we've got some lower cost labor. It's miniscule on the world scale, so you shouldn't complain I suppose? I don't get the doom and gloom.
Do people just memorise their times tables up to 100? Is that what it takes?
> Why can't non-async functions use await()?

To await means to wait for a Promise to resolve asynchronously. That's why async functions return a Promise instance.

async function asyncFn() {
const result = await fetch(url)
const json = await result.json()
return json
}

asyncFn().then(json => console.log('Got', json))
console.log('Fetching result..')

Calling asyncFn() will immediately return a Promise instance. Then each await in the function waits for a Promise to resolve, before continuing to the next instruction. While that's happening, other code can keep running, like the last line in the example above.

In contrast, a non-async function is synchronous, which means it's expected to run all instructions one after the other, then return a value. No other code can run while that's happening.

If await was allowed in a non-async function, it would have to block execution of all other code until the Promise is resolved/rejected.

function syncFn() {
const result = await fetch(url) // Stop the world
const json = await result.json() // Stop the world
return json
}

console.log('Fetching result..')
console.log('Got', syncFn())

This is how a synchronous HTTP request works: https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequ...

To avoid stopping the world, a non-async function can use Promise callbacks instead.

function promiseFn() {
return fetch(url)
.then(result => result.json())
}

promiseFn().then(json => console.log('Got', json))
console.log('Fetching result..')
Looks neat!

So, we made a huge list, cracked the whip, and ensured our engineers checked every box.

Eww.
It's quite a nice reminder at the top of an emacs config.

It's basically the same thing as 5S methodology in manufacturing. Doesn't make as much sense in a garage workshop, but when what you're doing is the pride of your craft and your day-in-day-out, your setup and tooling should be dialed enough that you almost never have to think about it.
Ok, as entertainment. Well, well, I think that is a perspective I'd simply never have realised until you said it. Thanks.

Edit: why on earth did anyone flag this?
How big tech will dupe the EU (Why we need open standards over open APIs)
https://stackoverflow.com/questions/66113393/why-is-async-re...
Apple rejected one of our apps. I looked at the screenshots they sent, they weren't of our app.

Pointed this out - app passed the review process.
I don't know about other countries but German auto manufacturers require (nearly) all suppliers to submit an FMEA [1] for their products. Some or maybe all US manufacturers do this, too, if I remember correctly.

In short, FMEA is a way to calculate risks and prepare for supply chain issues to a certain degree. When done correctly those FMEAs get very large and extensively lay out where risks are high so plans can be made to minimize them.

1: https://en.wikipedia.org/wiki/Failure_mode_and_effects_analy...
The Ratatouille scene may even hearken back to “Remembrance of Things Past”: http://art.arts.usf.edu/content/articlefiles/2330-Excerpt%20...
i was looking at this earlier and thought it would make for a great starter kit for a personal design system. it has enough meat to it to feel like you're not starting from scratch, but not so much that you'd be fighting the defaults very much. i find the choice of hsl colors a little odd (and font weights a little light, as others have mentioned), but overall, it's a solid base. and it accounts for every html tag, not just a somewhat arbitrary selection of them.

i've been trialing some css frameworks (bootstrap, bulma, semantic/fomantic, tailwind) for a side project, and i dislike each for various reasons. bootstrap and tailwind encourage class soup, while bulma encourages div soup. semantic/fomantic have a pretty dated looking design language, though the semantics (ha) are much better.

so that led me to thinking about creating my own design system with something like almond.css as a base, so i don't have to deal with the analysis paralysis that comes with bootstrapping from scratch.
There is something about fork which I have never understood. Maybe someone here can explain it to me.

Why would anyone ever want fork as a primitive? It seems to me that what you really want is a combination of fork and exec because 99% of the time you immediately call exec after fork (at least that's what I do 99% of the time when I use fork). If you know that you're going to call exec immediately after fork, then all the issues of dealing with the (potentially large) address space of the parent just evaporate because the child process is just going to immediately discard it all.

So why is there not a fork-exec combo? And why has it not replaced fork for 99% of use cases?

And as long as I'm asking stupid questions, why would anyone ever use vfork? If the child shares the parent's address space and uses the same stack as the parent, and the parent has to block, how is that different from a function call (other than being more expensive)?

None of this makes sense to me.
I had thought about this, but couldn't come up with anything that would make it visually appealing and represent the randomness of rainy seasons. The graph more or less look the same !
That site saved my bookmarks when Delicious went bonkers, and I much prefer it anyway — well worth the small price.
Agreed.

Closing with "Law enforcement has been notified" doubles-down on "we published everything but maybe if we can get somebody charged for a bogus crime then we won't look so stupid."
Never use Regex or XML to parse PDFs again
NASA’s new shortcut to fusion power
It's not just bad taste. Some of the described actions would legally be considered fraud (both in the U.S., and in France where the author and app are based).
I will list a counter book to this just people can read everything and decide for themselves:

- Nutrition and Physical Degeneration https://www.amazon.com/Nutrition-Physical-Degeneration-Westo...
Tyler Cowen's ethnic food dining guide: https://tylercowensethnicdiningguide.com/

Suggests that, in the US at least, the ethnic enclave suburbs (not the richer ones or the exurbs) are often better choices for food than the trendy downtowns, for that very reason. I'm sure he's right about his home in the DC area, but NYC is its own thing- effectively Queens and Brooklyn function like suburbs in his dining cosmology.