skysight-inc/HackerNews huggingface dataset:
The only part of this article that I really disagree with is the title. The main issue here is release engineering, or rather, the lack of it. Software development and system administration have well developed traditions, but release engineering doesn't seem to get much attention in comparison. Given that supply chain attacks are now all the rage in the black hat community, maybe release engineering will start to get the attention that it deserves.
> No persistent connections

As far as I know, at least AWS has two WebSockets based services.

> Expensive

I think there are use-cases that are rather expensive to solve with serverless technology, like realtime games and such, but overall? I don't know... many companies I've seen using serverless aren't even getting out of free-tier.

> Limited programming language availability

At least AWS has allows to bring your own runtime, it just has to be compiled for Amazon Linux 2.

> No local state

I don't think this is a good thing, but I think Azure does something like that with Durable Functions.

> Cold starts.

Only a problem if you use FaaS and that isn't a requirement for serverless. At least AWS allows to build some types of serverless applications without Lambda. For example APIs can be build with API-Gateway alone or AppSync.
Torrent trick?
How to be agile:

https://www.youtube.com/watch?v=GtkouFS-GSQ

Inventing on Principle:

https://www.youtube.com/watch?v=8QiPFmIMxFc

REST/GraphQL alternative:

https://www.youtube.com/watch?v=IS3i3DTUnAI
> the async-await code is much easier to read, write, and validate.

With the exception of necessarily serial code that I referred to, this statement is not true in my experience. Your "legible" example is only legible because you are not doing anything actually important like error handling and logging. In the real world each call may need different logging or even error handling logic and that is when promises really turn into a rats nest.

Validation, i.e. tests, are really the same regardless which approach you are using.

I do agree that async/await made promises actually usable, as I said above.

For running a bunch of asynchronous functions that do the same thing the semaphore + collector pattern works just fine and is not much more verbose.
Uh, I mean, of course I don't know any better than you, but I think parent wasn't entirely serious... obviously. Was he?
Reagan Institute: Panel on Tech and VC X Defense
Our brains could be collateral damage in our body's fight against infection
Never noticed. What's his problem though?
>> Edit: Some systems that arguably implement a superset of Datalog, but for which their Datalog subset is not a subset of Prolog are LogicBlox, Datomic, Datascript and TriQ-Lite.

That's interesting, I didn't know about that. I might have a look now that you mention it.

Regarding correctnes proofs, I think triska knows this subject better than me but my understanding has always been that if you stay within the pure subset of Prolog (i.e. no destructive update of terms, no reads and writes to the database and basically nothing with side-effects) then you can actually fully reason about your programs at least in principle.

I see this in practice everytime I write an extensive piece of Prolog code (for the record, I do that a lot, for my PhD) and I end up using the assert/1-retract/1 mechanism to update the program database as the program runs. The problem with that is that it kicks you right out of the cozy world of immutability, right back to the world of programmig with mutable states. Once your program reaches a certain degree of complexity it becomes impossible to predict its state at any given point in time. [Edit: the reason is that if something goes wrong and your program fails unexpectedly, the program database is left in an unpredictable state - and you have to understand each such state with great precision or it all goes to hell in a handcart. You're back to doing memory allocation by hand basically].

The hurt I feel everytime I use the assert/retract mechanism, or rather, the difference between the level of pain using assert/retract compared to not using them, is, for me, a great measure of the extent to which pure Prolog code is predictable. I'd even say amenable to formal proofs of correcntess but I've never actually tried that, to be fair.

As to decidability, my understanding is that you can either have Turing completeness, or decidability, but not both. So to slightly correct my comment from above, Datalog itself is decidable only given a finite constant and predicate signature (the set of constants and predicate symbols). But finiteness means incompleteness.
What difference does it make if you run `make install` or `curl | bash`? In both cases, you are running code you have not audited yourself. Or are you the kind who inspects every Makefile and installer script before installing? If not, why is one better than the other?
i like this as it provides another state between on and off for video. the fact that a colleague can un-blur the feed is a little uncomfortable at first but when you think it through it would be the same if you were in the office and a colleague approached you at your cubicle/office/desk. the fact that a notification is sent and the un-blur occurs on a delay i think is a great feature. i'd definitely give it a try.
> It depends on your field of work, of course, but in my experience these situations are really not that common.

Very common in my field. A single function that loads a file, parses metadata, then transforms the binary data into a different format can consist of 2-4 async calls that need to be executed in order. Await is incredibly helpful here, and makes code much more readable compared to the chain of then statements we previously used.

Even something simple as the fetch API to load a json file consists of two async calls in a row:

const response = await fetch('http://example.com/movies.json');
const myJson = await response.json();

https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/U...
My experience with dealing with the DKMS implementation of the Nvidia drivers left a sour taste in my mouth. Not fun when something goes sideways with an update and thousand nodes need to be recovered
Show HN: Version Control for Databases
European CCs provided by banks are often direct debit. On top of that, having a CC as backup for travel is common too. Transaction volume will show a very different distribution.
The Environmental Catastrophe in Your Joint
> jealous, insisting that every language has to conform to their way of doing things

Not at all. The large majority of packaging systems have reasonable and similar requirements for upstreams, like not bundling dependencies or not hardcoding paths.

> fundamentally not very good, having very limited ability to do things like install packages for a single user or install multiple versions of the same package

That's completely by design, and for good reasons.
> 2) jealous, insisting that every language has to conform to their way of doing things

Well, programming languages clearly should not be in business of software distribution. That creates unnecessary tight coupling between language, build system and distribution, causes proliferation of language-specific package managers incompatible with a platform way of doing things.
Is there some secret of intermittent fasting I haven't understand yet? According to the guidelines I've been doing that naturally for the last 10 years probably, eat once at 2pm and once at 6pm that's it every day
But I don't feel better than the days I eat whenever I want and how much I want, apart of feeling less hungry in the morning
This is actually nice, although I had to dig into the source code to read his essay, was too tired of scrolling.
My son, just yesterday, asked to get some fancy gaming glasses. I've always assumed it was junk. However, the particular brand happened to have a credible review on YouTube by a presumably unrelated eye doctor who does a series on eye stuffs. In this brand's case, they have slight magnification and slight prism effect (like uncrossing your eyes) that places less strain on your eyes when being close to a screen. Those seemed like real benefits. I'm not sold on the blue light part aside from when it is time to get ready for bed. But the glasses came in on sale for like $15 with shipping, so we will find out if they are any good.
I agree. Promises solve superficial aesthetic problems that only beginners trip on and unnecessarily add dangerous hidden state and corner cases.

You can further simplify that chain() function by removing promises altogether:

function chain () {
(function loop (i) {
if (i > 5) {
// set state to failed
return;
}
check((err,result) => {
if(err){//set state to failed
return;}
if (!result) {
return loop(i + 1);
}
// set state to finished
});
}(0));
}

Callbacks are much simpler and less error prone:

https://medium.com/@b.essiambre/continuation-passing-style-p...
I believe it is a few things. Light finger to get single shots versus repeated. First few shots to figure out how bad the sights are. Shoot around the star until you have a good perimeter. Shoot the center to pop it out.

Though you can find credible marksmen that know all this, yet fail to win. It's rigged.
> It sounds like there is a missing incentive to go under budget.

Other way around. Right now there exists a negative incentive to go under budget, being that if you need extra budget next year you suddenly don't have a buffer.

The correct way to fix things is to simultaneously prohibiting end-of-FY budget-keeping purchases (e.g. by mandatory reviewing of purchases) while at the same time allocating a company/organization wide buffer for stuff that needs immediate / projected stuff that was not in the planned budget.
I can't speak for everyone, but in my case it's "yes". I'd also be fairly comfortable claiming that there are a lot more people using component architectures (React, Vue, Elm, Ember and Angular) than are using GraphQL.
Kuwait leads the world in per capita emissions but has a population of 4.5 million. No problem?

So someone who pollutes a lot can change nationality and pollute more?
Intermittent (between 16/8 and 20/4), with 36 hour fasts if I feel the need; get a nice buzz at the end. I try not to do anything too demanding during longer fasts.
The point of dating apps is generally to meet someone who might be someone you’re interested in, and then meet them in person as soon as possible to find out. Talking online generally doesn’t reveal in person chemistry.
Tried IMF for two weeks recently, and my mood was so bad in the mornings I had to stop it; my wife thanked me afterwards. I'm a little disappointed I didn't get "over the hump" which reportedly lasts 3-4 weeks, and then mood is supposed to stabilize.

Anything relatable in this sentence, and any tips to help "get over the hump" you might have?
Russia banned from 2020 Olympics and 2022 World Cup over doping scandal
On the contrary, it's much worse. There's no way for 3rd parties to collect, test and redistribute installers in an organized way.
>building a CSS framework library

I think that might have been the root cause of the problem.
I’ve seen this before somewhere. Reddit maybe?
I'm not sure how to share it, but the key was using ifttt to add a or of data to the Google Spreadsheet.

If you search for shortcuts for logging weight, there are a bunch that log it to the Apple Health App, which is probably a better solution. I only have an iPad though and for some reason Apple won't let you run the Health App on an iPad.
> The study was small, just 19 people. All the participants were overweight and had a cluster of risk factors (elevated blood sugar, elevated cholesterol levels and high blood pressure) that put them at higher risk for Type 2 diabetes and heart disease. A larger study, funded by the National Institutes of Health, is underway to examine daily fasting in people with metabolic syndrome.
I made this, and have been using it in production and for local development for the past year or two. It's been immensely helpful to quickly save or easily restore the database to a previously know 'good point'. I have also been using it to quickly load staging databases into development and vice versa. So far it's MySQL only, but the connection points for other databases such as PostgreSQL are in place.

It's main goal is to simplify development - it's not intended as a replacement for writing database migrations or to work with production databases. I would be grateful for any feedback, preferably in the form of pull requests ;-)
A (New) Simple Proof of the Quadratic Formula
Sure thing. Just reach out to me if you need any help :)
This seems like a really interesting post, but the text width is just 22.4% of `<body>` width... sure I can zoom in, but then the font is obnoxiously large.

It seems like maybe it's a mobile theme being misapplied to a desktop user agent? FF 71 on macOS.

edit: `#wrap { max-width: 45em; }` is the culprit. If I remove that the un-maxed `width: 70%;` is much better.
> you have to buy an entire new head unit or a new car with built-in Carplay to use it

It's everywhere now though, even the used econobox my family bought this year has it.

Ironically, the major brand to NOT support it is Tesla, making it actually a mark AGAINST them.
It’s Time You Considered Building Your Own White Label Crypto Exchange
That's what, $2.5MM/yr?
And your error handling? ;)

fetch((err, res) => {
if (err) {
// yay - error handling! :)
}

const myJson = res.json();
// do stuff
}

What's so unreadable about this? Even if it is 4 calls it would still be readable because if you have any sizeable amount of logic you should be refactoring it into several functions anyway with the above function gluing them together. Much easier to write tests for too!
I have them. The magnification gives me headache (my vision does not need correction)
1. Terms of use can change at any time.

2. Technical capabilities have expanded massively. When Yahoo Groups launched, enterprise storage of more than a few hundred GB was highly unusual. I worked for a Very Impressive Service Agency which was lucky to claim two Sun Starfire servers, only one of which was Large File (> 2 GB) at about the time, for analytic use.

By the late 2000s, AOL were deploying massive-RAM based systems to be able to perform whole-dataset operations in memory.

For the past ~5-8 years, large-scale SSD drives have been A Thing, now available in the terabyte range, for a price. Again, the level of analysis and expolration possible have made tremendous leaps.

3. There is the concept of manifest vs. latent functions, and awareness. The full realm of possibilities of technical systems are rarely apparent to their creators, let alone nontechnical users. See (very generally): https://en.wikipedia.org/wiki/Manifest_and_latent_functions_...

The marketing and disclosures of such services rarely include such disclaimers as "use of this system may subject you to a lifetime of personal and social profiling, grammar-based context analysis, GD ML AI based image content analysis, and imperil the global liberal social democratic experiment."

Hiding behind the figleaf of "you should have considered all possible future implications of your present actions and will have no future recourse" is grossly flawed, and quite frankly, professional malfeasance and malice aforethought given current understanding.

The awareness of risks has changed, and is unambiguous. Providers should foot the costs, or mitigate them accordingly.

(I suspect that at least in part, the actions of Yahoo, Google, and others, reflects this changed awareness, though I'm not aware any providers have explicitly stated this.)

Again: the risks always existed. The previous state was made possible only by pretending they did not. They do. Practices must change.
The maven/gradle ecosystem actually does use signatures. That's one of the things they got right. Maven central has no unsigned artifacts. Also, the signatures are actually checked on download. Other maven servers may be a bit more sloppy of course. In any case, if you are running that on a production system, you are doing it wrong. You run that as part of CI. The output of CI is containers which you start on a production machine.

The point about containers is that they should be immutable. Running chef/puppet in kubernetes is not a thing (I hope, probably somebody went there). Updating a container means replacing it with a new one, that hopefully you or somebody else built in a responsible way.

That last part is indeed a problem that we have moved instead of solved. 20 year ago, people were just sticking whatever they downloaded on hardware they bought at the store and banged on it until it worked (very literally sometimes). So, I guess this is progress but indeed hardly ideal. I remember using puppet. Can't say that that is with any level of fondness. I vastly prefer Dockerfile and having CI systems produce containers from those.

Installing things on a filesystem is no longer that common at deploy time unless that filesystem is that of the container you are building using a Dockerfile or you are self hosting kubernetes (aka. reinventing a lot of wheels at great cost). Puppet/chef etc. are still of use if you are doing that but otherwise it has a limited role in IAAS type architectures. The closest thing is perhaps pre-baking AMI images using packer and some tool like ansible, which is nice if you want to avoid having a lot of startup overhead.

Hadoop is complicated, which is why companies exist that host that for you or will help you hosting it on premise in a responsible way. If you want to DYI, you indeed have to do a lot of things and do them properly. Kubernetes has moved that space forward in recent years; so it's easier but this is not for everyone. If on the other hand you are messing with puppet to get this stuff done, maybe reflect on the wisdom of not standing on the shoulders of giants rather than blaming the internet for your self inflicted pain.
Indeed, that's why I wanted to migrate from it
For sure! I just came across the interesting story of Marvin Pipkin, who, upon starting a job at General Electric, was given a "fool's errand" by his new team, as a practical joke:

He was tasked with finding a way of frosting light bulbs from the inside, without making them too brittle. Not being aware his assignment was a type of joke, he went about the task as if it was something that could be done and had been done before. The first electric light bulb frosted on the inside with sufficient strength for ordinary handling that could be sold to the public was invented by Pipkin in 1925.

https://en.wikipedia.org/wiki/Marvin_Pipkin
Oceanic white tips and Tiger Sharks are man eaters, they have been know to stalk, hunt and consume humans. They will return to devour a human. The meme that Sharks do not eat humans is not entirely true, but the reality is they prefer other meals. Well at least the tiger shark does. Oceanic white tips are the piranhas of the open ocean, they eat everything they come across. It is a good thing they only live in open ocean as if they where a shallow water shark there would be far more shark attacks.

I spearfish, and have spent a lot of time in the water with sharks. There nature is very much like that of dogs. If you show fear, try to flee and basically make yourself look like prey they will get attracted. If you stand your ground, give them a nudge to the face when they get to close. They see you as a competing apex predator that can hurt them, sharks are adverse to fighting for their meal. It is why injured fish is such and attraction to them. I have been in the water with them, just cruising around not paying any attention to anything, someone shoots a fish and all hell breaks loose if you don;t get the fish up fast enough. Once you are in possession of the fish they act as if another shark got it and go back to just cruising around. If they get to your fish before you get it up, they will clean it off the spear in seconds flat.
It is amazing how processed carbs inhibit cognitive function, and how much more aware one becomes when encountering an individual on such a diet.
I don't think so, no. Here is why: the basic behavior of muscles are decently well understood. For example why and how they contract and relax, and why they tire. We know of several reasons why muscles might malfunction. What is not well established is how and why muscles become stronger over time.

Compare this to for example ego depletion, and I would say that the analogy is not apt.
Cybertruck Inspired: Geometry and Brutalism in Web Design
PHP 7.4 OPCache Preloading Benchmark
They could have put a notice in the footer they always add to the messages.
I'm not following.

Either the concept, or how the terminology you're using arises.
Amazon and some other FAANGs build and deploy OS packages, and by choice.

Sad to see how anything that is not container gets downvoted here.
I believe you may be referring to the Romanian orphanages after the Ceasescu communist regime.

https://en.wikipedia.org/wiki/Romanian_orphans
19 people "study" looks like a fake news?
Ask HN: How do you document applications and infrastructure?
I work in a medium-sized enterprise, and while everybody agrees our documentation is inefficient and ineffective, nobody has a solution that satisfies everybody.

We've tried Git, Confluence, Sparx, Word on SharePoint. Typically, it's either too lightweight and lacking features that key stakeholders need, or too heavyweight and key stakeholders don't want to learn it.

Are there any "happy mediums" in this space, in process and tooling?
Kind of an attempt of rewrite of history there. Sure Steve Jobs did many stupid things and had to temper himself. But let us not forget that after he left Apple was on a never ending downward slope. It was when Steve Jobs came back and put product designers in the drivers seat that Apple actually became one of the worlds most valuable companies.

I have seen this over and over again. Where I am from an Apple reseller was first started by enthusiasts and made it big until MBA types took over only caring about the short term bottom line. They killed the company because customers stopped having faith in the sales people having their interests at heart. It was all about selling you maximum amount of stuff.

They got kicked to the curb by a new upstart mac reseller where the owners really cared about the product and customers enjoying their Mac experience, not just getting money.

The problem with the MBA style guys is that don't really see the value of anything. They just see money. That can only take you so far.
Here is my recommendation. Start by eliminating any liquid sugars (soda, juice etc) from your diet for two weeks. Then fast completely drinking only water for 24 or 36 hours. This will “reset” your hunger/cravings. Then proceed with regular imf.
Growing up I was friends with a large group of people deep into psychedelics, I watched them transform from who they were before the drugs to who they were after. These are people took the drugs seriously, the dosages, their "set and setting". Society tells us that anecdotal evidence is false, but thats brainwashing. I can see with my own two my eyes what drugs do. Most likely certain areas of people brains are dampened or flattened by these drugs, and so if youre and anxious person, maybe you experience "relief", but that comes at a cost.
Get a better VPN provider. Or better yet, run your own.
The issue you described (DKMS wasn't able to build the module for the new version of the kernel) will go away once Wireguard is in the kernel "properly" (which is what this announcement is about)
Isn’t it just as likely that the 8% reduction in calories gave all the benefits? I briefly read the study and it didn’t seem like they had a reduced calorie group without time restrictions. Thoughts anyone?
Amazing work. Love it.
Curious to know, how this horizonal scroll is working. Is it virtual scroll