skysight-inc/HackerNews huggingface dataset:
> I've read the research on willpower being a resource that you use up, and definitely agree with it

I don't enjoy subjecting you to cognitive dissonance here...but some highly cited research shows this belief may be a self fulfilling prophecy.

> Study 1 found that individual differences in lay theories about willpower moderate ego-depletion effects: People who viewed the capacity for self-control as not limited did not show diminished self-control after a depleting experience. [1]

> Study 2 replicated the effect, manipulating lay theories about willpower. [1]

> Study 3 addressed questions about the mechanism underlying the effect. [1]

> Study 4, a longitudinal field study, found that theories about willpower predict change in eating behavior, procrastination, and self-regulated goal striving in depleting circumstances. [1]

> Taken together, the findings suggest that reduced self-control after a depleting task or during demanding periods may reflect people’s beliefs about the availability of willpower rather than true resource depletion. [1]

[1] Ego Depletion—Is It All in Your Head? Implicit Theories About Willpower Affect Self-Regulation
http://icelab.psych.uw.edu.pl/wp-content/uploads/2016/02/job...

[2] Beliefs about willpower determine the impact of glucose on self-control
https://www.pnas.org/content/pnas/110/37/14837.full.pdf
I agree! It's been misused to mean things someone doesn't agree with too often :)

In this case we have been gettings tons of claims that what apple doing will see them charged with child porn felonies etc with almost no foundation.

We've also had lots of claims based on a failure to actually read about what apple is doing (ie, will scan all content not just that scheduled for upload to icloud etc).
RabbitHole – Earn crypto through using the latest crypto applications
From what I infer from articles like https://jeffreykegler.github.io/personal/timeline_v3 , the original Earley paper had a bug, and wasn't a good fit for 1960s hardware, and had poor performance for some types of grammars.

By 1991, "Most researchers see the Parsing Problem as "solved" -- a closed issue. Earley parsing is almost forgotten, and Leo's discovery is ignored. Two decades will pass before anyone attempts a practical implementation of Leo 1991."

It takes Aycock and Horspool's work in 2002 and Kegler's work in 2010 in Marpa to have a "practical implementation" (quoting that link).

(I quote that also because Aycock distributed SPARK, an Earley parser, which was included as part of the Python distribution, in the Parser/ subdirectory, and a couple of people here on HN report having used it.)
Wow these are really weak. And I'm not much of an IDE lover...
If I understand what you're saying, that's not what was done, at least here in Israel.

After the 3rd vaccine, afaik, they compared the rates of hospitalizations of people do did vs. didn't yet get the 3rd vaccine, as compared to what happened the week before. They saw a drop in 3rd-vaccinated, and only in 3rd-vaccinated, implying that it did have an effect. And this wasn't a small population (I don't know exact numbers but I assume several 10s/100s of thousands).
The rise of 3D-printed houses
I think "other developers are aghast" is a bit strong for technical documentation. I was certainly never aghast: knowing that SQLite started its life aimed at TCL, the decision made sense, and the commitment to backwards compatibility is admirable. Nonetheless I certainly welcome this change.

The "doesn't enforce foreign key constraints by default" is much more surprising / annoying to me.
Megacorps or completely alternative things like dive store, backpacker, climbing gym, mountaineering hotel
I've written parsers for context-sensitive grammars, and as it turns out, this is not a desirable feature of a language. The reason you typically see simple parsers is because simple grammars are usually unambiguous and context-free, which is more convenient for humans to understand and internalize.

After all, when you're writing software, you pretend to be the compiler to some extent.

Natural languages, like English, are a good example of something which humans struggle with because they are complex, ambiguous, and often require context. Sure, it's extremely expressive, but that is the sharpest double-edged sword in programming languages.
I use twitter via RSS feed in inoreader only. Looking at it naked is too confusing but consuming it via twitter is manageable as it allows you to see the whole tweet on a single line.
(Nitpick: I assume you mean learning both the syntax and the semantics. That isn’t always trivial, as some languages have features one may not have seen before)

I think we mostly agree, too.

However, I distinguish between learning a programming language and learning to use it. I learn many programming languages without ever writing any line of code in them.

Once you’ve seen enough languages, if you combine that with reading about other people’s experience with working with the language, that can give you a decent idea about how the latter is without having to spend the effort (without being as good as doing it yourself, of course. Apart from “which one is the brake pedal”, I think I know how to drive a car, but I also know I can’t drive a car)

That’s why I posted my first comment: the poster you replied to may share my opinion between “learning” and “learning to use”.
At work we are batch-processing a decent amount of data every night using Spark. The way the workload can be split into parts allows the following strategy:

- Generate jobs only containing metadata and distribute those jobs to workers. There the actual data that is required for that specific job is queried on the fly from the db.

For a similar task however we later switched to the following strategy:

- Load all data to be processed at once, use all sorts of distributed transformations and aggregations on the full data set and do the splitting at the end of the workflow.

The reason why we switched? The only real reason was that it seemed more the "Big Data style" to do stuff. With the first approach we actually would not need all the fancy Spark functionality right? We would only abuse the framework for a fancy way to distribute mostly independent workloads.

However, I very much regretted that decision later as it made our life harder in many ways. For example, I could easily execute and thus debug one of the former jobs locally within a minute. Try that when the workflow is designed in a way that it needs to load several gigabytes before applying any logic. To be fair, the total load on the db was somewhat lower using the second approach, but that just wasn't worth it.
???

You seem to imply that Malaria has killed more humans throughout history than heart disease. Laughably, you do not show any source to back up your statement ¯\_(ツ)_/¯.

I disagree based on extremely easy to obtain numbers from sources like [1]. Malaria at 200k/year is not even close to Ischaemic heart disease at at about 9M/year. That is an almost 50-fold difference (!). Given that we have experienced an exponential growth in population in the last 100 or so years, I would not be inclined to believe that something in the past has enough weight to shift the numbers in such dramatic way to invert this trend (50 to 1); and that's being VERY generous and assuming that somehow, in the past, for whatever reason, nobody died from heart disease, at all.

If you have a substantial contribution to make please do so and provide data to support your arguments, otherwise, refrain from spreading lies and FUD.

[1] https://www.who.int/news-room/fact-sheets/detail/the-top-10-...
Great to hear you've had success.

[1] is an interesting paper which gives you some hormonal examples. Effectively when you try and lose weight your body responds by increasing the hormones associated with greater satiety and weight regain. And these change may persists for a while — this papers documenting the change lasting past a a year. This will very by person however so if you have something which works for you keep going.

[1] https://pubmed.ncbi.nlm.nih.gov/22029981/
> A majority of people carry the potential to become a genius.

Sure. Totally believable.
> As we’ve explained in Deeplinks blog posts, Apple’s planned phone-scanning system opens the door to broader abuses. It decreases privacy for all iCloud photo users, and the parental notification system is a shift away from strong end-to-end encryption. It will tempt liberal democratic regimes to increase surveillance, and likely bring even great pressures from regimes that already have online censorship ensconced in law.

What’s clear is the potential for future abuse mandated by various gov (though that could easily be the same even without all these CSAM measures.. not a new threat). However, the other things are erroneously lumped in with it. It only weakens privacy for iCloud photos if you have CP or photos in a CP database, and it doesn’t prevent E2E with texting… it just gives an additional parental control in addition to the many numerous parental controls (with them kids have no privacy already), and is totally unrelated to the CSAM effort.

I admire the EFF in many ways, but I wish they’d be more exact here given their access to expert knowledge.
Janet is small, simple, efficient, and practical. For me it has nice syntax and sensible semantics. Great little package manager too. Very happy with and excited about Janet so far.
I usually write zsh scripts and I think there’s a shell option in zsh that allows the loop at the end of the pipe to modify variables in the enclosing body: I remember at least one occasion where I was surprised about this discrepancy between shells.
"Issues are independent. Properly broken down, work in a project has dependencies"

A trick I use a lot is to open a "tracking issue" and then link to it from other dependent issues by mentioning its #ID in those issue's descriptions.

The tracking issue automatically shows the open/close status of those other issues, which means I can see at a glance if all of the dependent issues have been completed.

Here's an example: https://github.com/simonw/datasette/issues/1105

It's not nearly as sophisticated as what you're looking for in terms of date estimates and critical paths, but it does work well for light-weight dependency tracking.
Any experience or thoughts on NGOs or government work?

Would megacorps include the G-MAFIA or exclude current tech giants?
Great news, domain constraint enforcement is a welcome new feature. However, let's not throw the baby out with the bathwater; being able to specify an ANYTYPE/VARIANT column on a STRICT table would make this feature more useful. The canonical use case for ANYTYPE is a BIGTABLE or Entity–Attribute–Value (EAV) model.

I haven't checked recently, but I was unable to determine the type of ? parameters in SQLite prepared statements. Maybe this is something that can also be accommodated with STRICT tables.
That’s it, right? That’s the game? There’s no way the DoJ doesn’t have a slam-dunk case with that one quote.
That's kind of the problem. The database absolutely should get in your way if you try to put nonsense data in it.

For the kinds of uses SQLite sees, the loose approach to data integrity may not have caused much grief, but I can't imagine many situations where it would have helped either.

Having support for enabling sane behaviour is welcome even if it has to be opt-in for compatibility.
Thank you for the excellent response and citations. I think you and Richie are on to something here - wishing you the best of luck.
>trivial to do

>stopped all real workloads

Says you. Tesla don't need to be in the Top500 list to have a supercomputer that they are using for other more useful things.
What I fear most about the coming decades is people making tortured analogies between Rome and the US. It’s going to get real repetitive.
Exactly. They couldn’t not investigate, but they also knew where it went and didn’t exactly want to dig too hard because they might accidentally find too much evidence.
FAGMAN
Sure, and so? Like many mild to moderate psychological habituations, it's not quite comparable to the persisten chemical addictions created by certain narcotics
Overall, I believe the average workplace (in tech) is much more into only tolerating the "correct" viewpoint than previously. There are lots of examples beyond vaccines, even if having health choices and subsequent proof of them forced on you seems like the most extreme.

Even before the vaccine stuff, one of the big factors in my change of job was all the protesting and politics and extremism. It's pretty easy to just keep your head down and go through the motions, and I expect that's what most do. But given the choice, I'd rather "bring my whole self to work" which includes holding and discussing opinions in a non- fanatical manner and not being forced to, as you say, signal my alignment with non-work related groupthink.

For example, I don't use drugs but I would not work somewhere that subjected me to a drug test. It's no different than being vaccinated but not agreeing to share that information with my work or anyone else that asks. The first opinion seems acceptable for now, the second gets me called an anti-vaxxer
I am sometimes thinking about use master branch of my repo and add a folder called 'tickets'. Then in this folder create issues as markdown files. Use some Vscode, Emacs or Vim plugin to automatically number these markdown files and present comments as lists.

No more dependency on online saas tooling and you can use the search option of your ide / os / command-line to search through them.
For the raft algorithm to be correct Fsync is required on a majority of node otherwise you are technically not implementing Raft.

The reason is that in Raft if a node acknowledges to the leader that it wrote something to the log it must not later accept a different write in the same log position.

This mean if for some reason server rebooted with dirty buffered writes that could not be flushed in time. it’s supposed to forgot everything it know and rejoin the cluster using a brand new node id.
I use the Visual Studio Code TLA+ plugin, it's significantly nicer to work with.
I doubt human nature has changed all that much since 1998.
Sure, but as someone who agrees with you, I’m not sure we can call that ‘misinformation’. It’s just poor understanding and bad arguments.

I have seen a little misinformation relating to this subject - direct lies, fake news, fake links etc, but a negligible amount.
>> the head of our "family" (a.k.a my boss) would, in varying levels of directness/corporate-speak, let me know what an "incredibly difficult decision" it has been to "part ways" before kicking me out of the firm

The head of my family kicked me out of the house when I was 19. I'm sure it was a mildly difficult decision, and of course the correct one. But at least no boss that I've worked for has ever sold my first edition Dungeons & Dragons manuals at a fucking garage sale.
I've created ~five new projects over the past year using SQLite and I've got into the habit of creating tables like this:

CREATE TABLE tIssue (
id INTEGER PRIMARY KEY NOT NULL CHECK (typeof(id) = 'integer'),
col1 BLOB NOT NULL CHECK (typeof(col1) = 'blob'),
col2 TEXT CHECK (typeof(col2) = 'text' OR col2 IS NULL)
);

This has saved me from a lot of errors and has been useful, but it's just so easy to let things drift, e.g. removing `NOT NULL` constraint and forgetting to also update the check constraints. I'm also horrified at the auto-conversions that I've just learned about from this link that I'm not protected from.

I'm very much looking forward to using strict tables.
An alcoholic, or a heroin addict or even many heavy smokers are going through their own special types of hell that are capable of literally killing their physical health or taking their lives, and it trivializes them to compare these things to someone having a heavy social media-checking habit.
In which other industry is a massive subset of workers r-ped each day?

There were children working in Industrial Revolution factories that ended up perfectly healthy. You and I recognize the practice as immoral (I assume?) because the exceptions don't matter
Oric-1/Atmos/Telestrat!
Yep exactly - the prescription drug element requires state-by-state medicine licenses.
No, the attacker is committing a crime with the attack you describe, but has plausible deniability that they are not with the Apple-nonsense enabled attack vector.

This is a huge difference as not only does Apple facilitate a gain-of-function in terms of potential detriment to the victim of an attack, the newly-enabled vector also indemnifies the attacker.

The effort required to come up with a hash collision in SHA256 is something on the order of the power output of a trillion suns for a billion years (or some other meaninglessly-prohibitively-large amount). Despite such metrics and off-the-shelf solutions being readily attainable within this field Apple has implemented a system that has resulted in a collision within days, followed by a free automated collision generation tool.

This demonstrates absolute gross incompetence in design, and permanently eliminates any trust any sensible individual can ever have in the system despite your protestations.

There is simply nothing you can say to convince any sane person otherwise, the situation has been factually described and it is what it is.
Cloudflare Workers KV is really promising, but needs a better local dev story (no stable project so simulate services locally e.g. cloudworkers). Pricing is reasonable depending on what you interpret "scale" to be.
Ouch, that sounds nasty!

There's a pattern for enforcing datetime formats using a CHECK constraint which I've not tried myself yet but which looks like it could work: https://sqlite.org/forum/forumpost/4f4c96938f4bef32?t=h
Thank you for creating Janet. It is a fun language and it's exciting to watch it evolve. With the addition of the event loop and networking I'm curious to know if an http client and http server based on these will be added in the future?

I am aware that there are already libraries that cover these to an extent like circlet and halo for http. Joy also features an http client. Maybe it's outside the scope of the project, but I think an http server and client as part of the core would really add to the utility of Janet. It would also answer some of the licensing questions for distribution if these were included directly in Janet core. For example, circlet is MIT, but it is based on mongoose is GPLv2.

Also, seeing Janet on HN a year or so ago was what got me to watch The Good Place, so thanks for that as well.
A more charitable interpretation of the tendency of error in both is that humans and the world are more complex than expected. Sure, there are examples of fraud, etc but my general intuition is that people are generally well intentioned and interested in honesty and that those qualities are not immunity from error. So, malice, incompetence or a world that defies our finite minds?
Those aren't at all analogous.

The automatic state for content is "protected by copyright," unless a different arrangement is made.

The automatic state for contract terms is "not agreed to," unless a different arrangement is made.

tl;dr You need proof (written or otherwise) that a contact happened; not so with copyright protection.
CNC mills are super useful. But not all the time. I regularly (not all the time, or even a majority, but regularly) choose a manual mill over my cnc because for simple jobs that only require a part or two, it's faster than setting up the 3d model, deciding on cutting strategies, setting up the tools, etc.

My choice in editors follows the same logic. If I just need to jot down some notes, or knock together a simple bash script or something, it doesn't really matter what I use. Whatever has syntax highlighting and is available on that system is great. Something more complex, where I don't want to spend brain cycles on repetitive tasks or management that the tools can handle for me, I'd rather use something that will handle that for me.
Gartner Magic Quadrant for Cloud Infrastructure and Platform Services
> (though that could easily be the same even without all these CSAM measures.. not a new threat)

Apple has historically avoided being pressured by governments to allow this kind of surveillance by arguing they can't be forced to create functionality that doesn't exist, or hand over information they don't have. It's the argument they made in the San Bernadino case.

If they release this, it'll be much harder to avoid giving governments that existing ability for other, non-CSAM uses.
How are you measuring harm? By number of people who die? The cost to the healthcare system? If so I reckon the number of people suffering from diabetes vastly outnumbers those suffering from cirrhosis of the liver. Treating these people costs a lot.

Certainly we should restrict access to sugar, or at least tax it. But in most places, such policies are non starters.
Depends on the QR code. I spent some time in nyc and saw some really good and bad implementations. The good have QR code’s per table and allow you to have a dedicated experience where the server knows exactly who you are and the bill is automagically tabulated whenever you are ready to pay. The bad ones where literally a link to their not mobile friendly menu.

QR code menus are still nonexistent down here in Texas..
I think more programmers should learn how to write parsers by hand. You need them everywhere; for protocols, file formats, user input, little languages. They often use regular expressions or other crutches when a parser would be the better choice.
One way which isn't great, but an option nonetheless… The zsh parser is happy with that form:

$ zsh -c '< <(echo hi) while read a; do echo "got $a"; done'
got hi

My position isn't that it is a good reason to switch shells, but if you're using it anyway then it is an option.
A browser extension with some custom filtering rules could be handy. I'd love to never open another blog post from someone who thinks finding out that becoming internet famous for two days is bad for you is some kind of revolutionary insight and that everyone needs to hear about how stressful it was to be tweeted at a lot.
IDEs are tech equivalent of power tools. You need them. Of course you can always chisel down when needed, but tooling helps.
> The key is to only have pay depend on location to the extent that the company constrains the worker's location

When the worker has agency to chose remote vs in office, tying pay to physical location seems like coercion though. Doesn't that constrain the worker? "Live in this specific area and come to the office and we will maintain your current pay. Else, you have to take a pay cut for the same role and work output"

Maybe this is a reason why some companies are hesitant to have it both ways and are inclined to force people back to the office. Could they be reducing legal exposure to equal pay lawsuits?
It makes some sense - if you replace Netflix with MS, the list will be the 5 largest tech companies. Netflix is only there because of how the term was coined in the first place - FANG (originally without Apple) was a list of stocks that Jim Cramer liked around 2013 and the acronym caught on and evolved from there.
xargs defaults to all whitespace because it was designed to get around the problem of short argv lengths (like, I'm talking 4k or less on older Unix-y systems, sometimes as low as 255 bytes).

So the defaults went with principle of least surprise, pretending it's like a very long args list that you could theoretically enter at the shell, including quotes.

You could, for example, edit the args list in vi and line split / indent as you please but not impact the end result.
Bigger spend is definitely important. Drug approval, decentralized decision making, consumer norms all also important.
This STRICT feature is a brand new (currently marked as DRAFT) and hopefully scheduled for the next release of SQLite. I believe this document only showed up on the website today.
https://archive.is/jVIE0