skysight-inc/HackerNews huggingface dataset:
There are people genuinely exiting the workforce, however. Biggest of note is those over 65 that were previously working part or full time that have decided to rely solely on retirement income.[0] You have have a lot of exits due to childcare related issues.[1] The workforce has genuinely contracted during the pandemic.

[0] https://www.npr.org/2021/08/23/1028993124/these-older-worker...

[1] https://www.bloomberg.com/news/articles/2021-10-09/child-car...

ETA: Looking on the other side, there is likely some unknowable number of 16-18 year olds that are not entering the workforce yet, that would have pre-pandemic.
Interesting approach. I have some coleagues that actually remote desktops to their powerful desktop computer. I never did that because I fear all the tiny issues I have to deal with, but they tell me it works quite well. Also just offloading the heavy lifting through ssh or other types of build servers seems super interesting (I think some build systems have built in support for a common server, not sure if it is true, but it could be very helpful if it works well)
I can assure you nobody will be able to give a proper answer to such a vague question without more details about what you are hoping to achieve and your background. (Is it about using ffmpeg, learning the internals, are you already familiar with how digital videos work? etc...)
My interpretation of this is they pay for API access and sends anonymised queries to Google and/or Bing.

I'm still puzzled how they get so extremely much better results compared to using any of thise directly or using DDG which does the same only with Bing.

Also a bit worried because I think there was a time when DDG felt the same before they suddenly gave in and started serving answers for queries I didn't ask just like Google but I'm not really sure.
Not quite sure how pointing out that similar symptoms are non-specific is "letting our imaginations run free". You can't really tell for sure.
The right answer
You're hitting at the only source of happiness/sadness for humans: success relative to their neighbour.

You either have to really accept other ways which I think is hard or get better than them which is probably harder.

I grew up in a small town of Normandy, from middle class parents, left home at 19 with a financial buoy from the State and my parents to get a 5-year degree and learned to be very slim in desire, since I was spending other people's money, then lived in relative comfort with my girlfriend when we found okay jobs in Paris.

I was sort of sad then, having like you little fortune to show. I did two things: I saved like a monster, for 3 years, up to 20k USD, and I dived into English, to reach my fluency objective.

After 3 years, I left my girlfriend, moved to Hong Kong, burned half my 20k savings working with my parisian salary there looking for a job. 7 years later, I have a Porsche, earn 4 times my initial salary with a local wife earning even more, and have a lot of money saved in various shapes. I feel I won so far, while I dont forget that it can just disappear tmr and it's okay, will just have to find another angle of attack.

Find a skill you can tune more and take a large wealth producing decision that not everyone takes (leave your roots for a rich place needing your new skill, for instance). If possible, tame the jealousy, it's really toxic: have fun doing something special like I have living in China, and use that as your worth-comparator. And find a working partner.
Presumably, the people who were using desktop workstations pre-pandemic have started working from home with laptops - but their ways of working and tooling all center around doing things locally.
Does anyone have a solution to sync clipboards across:
1. The system (XServer)
2. A terminal text editor (Kakoune)
3. The same text editor on another system over ssh

I currently have 1 & 2 sync'd ok, but 3 is only one-way. I use the OSC 52 escape sequence (supported by my terminal) to sync a copy on 3 to 1. But I have not figured out how to sync from 1 to 3.
Airbnb's experiment in combatting rental bias means swapping names for initials
That's... very weird. What would that expose? If you can read the keys at all from the OS, directly or indirectly, that's a security flaw. AFAIK AMD GPUs have supported video decode on Linux across all generations, so what was unavailable?
Anonymized request means that the client's IP is not passed to the server. Since both search engine have a paid search results API, it is enough to simply proxy the API request to achieve this claim.

Kagi is both paying Google for API access and using Google infrastructure (GCP), helping Google make revenue that is not ad-supported.
Is filled with strong acids, for example.

But I agree that having to deal with high voltage is a totally new level of troubles.
Very naive question but is it even possible to do quantum experiments with code on a regular computer? Anyone knows if it's been tried?
so then I guess that should shut down the Maryland suggestion. No idea why it would be brought up as a possible solution for democratic representation when it goes against the wishes of the people seeking representation.
Nota: A Document Language for the Browser
That's what I think as well. It seems like there are mechanics and truck drivers commenting now when there used to be quants and physicists. The quality of expertise seems to be diluting and driving away subject-matter experts. I swear it's a feedback loop.
In my experience, sequential numeric IDs are usually absolutely fine. The problems identified in the article are either phantoms, or easily overcome. Let's go through them.

"When using a numeric primary key, you need to be sure the size of key you're using is big enough" - as the article itself notes, 64 bits should be enough for anyone.

"That number that you first pulled out and didn't use is lost forever. This is a common error with sequences — you can never assume that the highest number you see as an ID is implicitly the count of the number of items or rows." - true, so always treat numeric IDs as opaque, like UUIDs. The fact that they are actually sequential is an implementation detail.

"You can copy a table over to a new database and forget to copy over the sequence generator object and its state, setting yourself up for an unexpected blowup." - doing weird manual operations on your database offers a wide range of ways to screw up, far beyond this. Just don't do this? When you copy a database around, you need to copy the whole thing, to preserve its integrity. If you're creating a frankenbase, then of course you need to exercise caution. If you're really worried, on app startup, check that the sequence's next value is higher than any existing ID, and crash if it isn't.

"Having a single place where identifiers are generated means that you can add data only as fast as your sequence generator can reliably generate IDs." - this is a real problem, but it's easily overcome by batching. Rather than using hitting the database for a new ID every time you need one, the application can occasionally hit the database to acquire a range of IDs, keep that range in memory, and use them as needed. You might be able to build batching on top of the database's built-in sequence machinery, or you might not, or you might prefer not to even though you can. At worst, it means adding a table to the database to track sequence values. Scaling is then accommodated by tuning the batch size and scope (per instance, per thread, etc).

"On a scaling-related note, numeric IDs limit your sharding options" - the approach i have seen is to use batched sequences, and move the sequence machinery out of the database that is being sharded, and into a separate service, or its own database. Application instances can all pull batches of IDs from the shared service or database, which ensures that they are non-overlapping.

The nice thing about numeric IDs is that you can start with the simple and easy approach, a standard database sequence, and then migrate to more scalable generation strategies as your database grows, without having to change your data model. The problem of generation is nicely encapsulated.
iMessage, Apple Watch... iCloud?
This is only about chassis ground current, not earth leakage, which is strictly the domain of the charging circuitry.

Seriously: if you do not understand the difference please do no not start messing with the HV side of an electric vehicle. Below 48 V is considered a safe voltage but can already - under the right conditions - cause you plenty of hardship and I'm aware of one death from a 48 V system.

Anything higher than that with voltages between 200 and 600V pretty much the nastiest range because it is too low to arc and high enough to kill you needs special precautions, tools and ways of working to keep you safe.

You can't rely on technical measures to keep you safe when diagnosing and repairing those circuits because those technical measures could be the cause of the fault.
You may want to consider a Mac. Most of its software doesn't use any Fn+ combos, or Home/End/PgUp/PgDown/Insert/ContextMenu keys. They have other shortcuts. It's a pain to learn them in the beginning, but in the long term it gives you an idea that maybe having many single-purpose keys on a laptop keyboard is not a best idea, ergonomically.
200% is not fractional scaling, though?
>Why not? We kinda already did it for the flu every year. And if it is the only alternative to lockdowns [1], I think most of us would prefer that.

Because this is not a fatal illness for everybody, it should target the most vulnerable group of people willing to vaccinate/use boosters. The very same thing happening already for the flu shot every year.

"Pollard also stressed the "need to target the vulnerable" going forward, rather than administering doses to everyone age 12 and older. More data is needed to ascertain "whether, when and how often those who are vulnerable will need additional doses," he said."
Would you say its actually a good indicator that a candidate will succeed on the job? (no sarcasm intended)
Have you tried Sciter?
Google could be better, but they serve people who react to ads.

People who click ads like different search results than the rest.
Yum. Or even with fermented beets! Borscht is delicious
Where's the Talmud passages to support your claim?
If you choose to straddle ecosystems there really isn't that much that the likes of Obsidian can do to help though (especially when it comes to iPhone). I use Obsidian with Mac + Android (Synced via Dropbox, and backed up using git) and it works. Little bit of manual setup, but I can handle that.

At the end of the day Obsidian is just a directory structure of Markdown files. If needed, you can edit them with Obsidian (say using the Dropbox app).
Absolutely brilliantly put.
Why don't you ask or learn their habits? - The habits of the rich.

Is there a way to email you? I'll send a few articles which might be helpful for you. (They are not worthy of HN discussion, so not commenting here.)
As soon as you open up a legacy X application it looks blurry. The main offender was Chrome/Electron but I think this has been fixed last year.
Care to elaborate why that would be more problematic than any other app that hasn't been updated or maintained in that period of time?
When are we going to get back truly native apps?

Flutter Desktop works great, and there are a bunch of nice GUI libraries for Rust, also some new developments for the JRE.
> It's a repeat of the MS-IE escapades of a few decades ago but everyone's OK with it.

Is it though? Safari seems to be pretty close to the HTML standard and at least not implement any proprietary features. Sure there may be bugs or they may lag behind but they are making an effort to be compliant.

I'd say Google seems to be the one leading a lot of decisions regarding to standards and implement them the way they want before they are actually standardizes and because they have the biggest market share Apple and Firefox just have to follow their decision.

Ideally Apple would allow third party browsers on iOS, but I think it's beneficial for users that they don't. I do believe that without it Chrome would have a much bigger market share and developers wouldn't be forced to support browsers other than Chrome and Google would have even more power over web standards than today. I guess Chromium being open source would make it a bit better.
Not smart. It says right on the bottle that it's not made for skin contact. Check the ingredients (if they're all listed) and see if there's safety data for them all.
You misread that, they were saying that poor people have self-doubts about more serious matters than that.
The mind has such a hard time comprehending death that it tries to escape through other views of reality. This can happen regardless of your scientific knowledge or religious beliefs. That's the most interesting takeaway from this piece in my opinion, as I experienced the same while losing a parent to cancer.
Small study suggests pandemic may slow babies’ development
I completed Andrew Ng's Coursera course and one thing it did not do is make me understand neural nets from scratch. Probably, you and I have different interpretation of "from scratch".
Since I am currently working in an environment that resembles GP's premise, I have to say that I find this take to be way too optimistic.

I'd be exactly in the boat you describe (and actually: I've yet to see a situation where someone reviewing my code did not lead to improvements). But: If I want my code reviewed, I have to actually fight for it. Since everybody's workload is too high, even the willing often simply don't have the time.

From higher up, at our place, there's no one that actively opposes code review as a practice, but they don't seem to get that it requires investment (i.e. time), either. That means that if management refuses to change their ways of planning or explicitly enshrine reviews as priority tasks, it simply won't happen except for maybe the gnarliest cases.

And that's from a perspective of the change's author being willing and proactive. I work with individuals that produce very questionable code at times. And I'm not talking style here: Code in 2021 that still is prone to SQL injection at every turn. Methods that are hundreds of lines long with a gigantic cyclomatic complexity that no one (including the author) will ever really understand. Method names like "process" and "process2". And so on.

Needless to say, those programmers will never push for their changes to be reviewed. The rest of the team simply discovers them after they blow up (which they do regularly) and we're debugging.

Now, these people are luckily a tiny minority (which at least makes this somewhat bearable), but I over and over again would wish for someone with more authority to show that they're interested in the matter. Which a policy on code review would do -- if only as a signal. Yes, we want to check each other's code. Yes, we want collaboration. Yes, that's more important than some arbitrary deadline for minor feature X. Yes, we expect our programmers to be professionals.

Another symptom of such an environment also is the fact that everyone is the king of their particular hill. No one every familiarizes themselves with another person's code unless they really have to. By now, I've jumped to insisting that every change on a critical component I'll ever make will be done through pair programming, and so far, at least that seemed to stick. But again -- that only happens if both parties involved actively fight for it instead of everybody understanding that this is just an expected part of work.
You can simulate quantum dynamics but the number of bits required is exponential with respect to the number of qubits simulated. So basically you can simulate really simple quantum systems but it becomes pretty much intractable when the system you are simulating has many parts.
Gee. So much effort, for something so mundane. I'd never manage.
I just want to take a second to share that Next.js is the worst thing I've ever used in my life. I am a react dev. They somehow managed to make Next.js harder for me to use than Django, which is in Python, which I've barely ever touched!

Imagine that react is like an airplane dashboard. Next.js is like adding a faceplate to the dashboard, jumbling up the buttons, then hiding some buttons because "best practice" and "optimization".
Not to take away from your overall correct point, but...
Let me introduce you to focus modes....
Yeah, I practiced leetcode by spending about an hour a day for 2 months, but I had only done around 60 LC total (25 medium, 35 easy).

I didn't feel a need to do much more as they had very similar patterns. I did attempt the ones I had solved more than once though, but it was to really drill in the principles behind the problem rather than to try and "memorize" them.

Prior to my prep, I had almost 0 algorithm experience. I got an offer from every FAANG I applied for.
A few months ago, I was playing with msfvenom and wanted to experiment with making a payload designed to bypass the antivirus of both Windows Defender and an antivirus that my work uses(with my boss's permission). I worked on it all day, but I could not get around internet-connected Windows Defender. Any time a port was bound or web connection was attempted, it shut me down.

It made way more impressed with Defender. I was always told it's inferior, but its sandboxing and heuristics scanning are quite good.
"more" is a little mild, one can probably power tens of millions of CC transactions with the power a single BTC block wastes
Good point, wondering the same thing. I'm considering starting using a password manager, but my bigest concern is that malware can capture the passwords by listening to clipboard. The model in my head on Windows from programming using WIN32 API two decades ago is that any application can read clipboard contents as often as it wants to. Assuming the malware does that in a tight loop, how can password managers be secure at all? I imagine X Window System is no better in this respect. Has anyone given this any thought? Are my concerns unfounded?
I’m sure Apple’s world-renowned UX team can innovate a way to allow new search engines to be added w/o bricking your phone. I’d rather have that than lack if real, capital-laden competition in search.
Don’t fight the feelings, utilize them as a fuel to move forward.

The existence of the feeling indicates that this matters to you - then what stops you from pursuing same goals?
Honestly I think you should be able to test stuff in real world scenarios if possible.

I would never do iOS development seriously without native devices.

Virtualization brings you far, true, but it's still different.

I would even create a hardware lap if I would do end-user device Software development.

And the quote is still true. If you do iOS MacOS development it IS the obvious choice obviously.

Yours might be cheaper and might have other advantages but it is NOT obvious.
You're in luck, since a more frequently updated fork called Bypass Paywalls Clean is available at addons.mozilla.org:

- Add-on: https://addons.mozilla.org/en-US/firefox/addon/bypass-paywal...

- Source: https://gitlab.com/magnolia1234/bypass-paywalls-firefox-clea...

It's included in Iceraven's default add-on collection.
There must be a reason though why a lot of companies are actually using this stack these days with SPAs and it seems like front-end is kind of merging with back-end by using the server-side rendering and server-less DBs with Prisma for instance?

Its actually just interesting to observe.

I am a complete newbie but curious what are the seniors here think about this trend overall.

Meteor had to be sold in the end since they didn't get the adoption. But the "JAM-stack-ish" frameworks do get that adoption recently at least based on the funding rounds (kind of half serious here).
Also very useful, thank you!
They're in RC now. In terms of data loss: I'm not concerned with what I've seen. Some features are still missing, such as SED control. I think most of things I wish were there aren't present on core either, such as VM VNC clipboard and solutions to the web UI logging out often when 2FA is enabled and some mysterious directory locking issue when pulling dropbox.
Obsidian has a git plugin that I've been using for a while. It's pretty configurable for frequency of commits, and I've never had a problem with it.

It is at the end of the day a directory of Markdown files, so it's flexible with other tools. I have a bunch of things like Markdownload configured to write into various sub-directories.
None that I was aware of in 1990s Galway, Ireland.
Thanks, sdiepend! I definitely should have used “Tell HN”
I’ve been using Fedora 35 with Wayland and fractional scaling set to 150% on my Framework laptop and it works great for me.
Sure, remapping "belongs" to the input layer, but there are use-cases that aren't possible if you do this. I've had a few situations in the past where I had to do window-level button remapping. I had programs that had hard-coded keyboard shortcuts for keys that my keyboard simply didn't have and remapping them for the whole system would've screwed up every other program.

If you go further and expand input remapping to also inclue macros you'll also soon find the need to send input directly to a window. There are also many cases where a simple remap won't do since there isn't a single "originating" input event (like remapping joystick movement to WASD or faking inputs from non-input device events). This makes any such API fairly complex and you'd have to be implementing something like it in the compositor/window manager/DE anyways, so why bother also doing it at the input layer?

Where Wayland went wrong is ignoring these use cases and putting the burden of making APIs for them on compositors, which of course couldn't agree on anything, so now we have nothing. Evdev works at a very low level, so many things aren't possible, libinput doesn't expose its APIs externally anyways and the only compositor with even rudimentary input mapping support is KWin and that barely works.
The man with no shoes, sees in the man with no feet, his fate.
Personally, I've found fractional scaling on Gnome makes the window furniture too large for my taste. I've settled on boosting the default font size in gnome-tweaks to 125% instead, which makes font rendering match the DPI of my monitor but leaves window bars / tool bars etc at a more sensible size.
I cannot relate to the article. If I cut files and do nothing - they are not deleted from the origin. If I cut text - texts are versioned and backed up with git or similar alternative.

Even if I would lose something, it wouldn't take too much time to restore it. If its a password - 99% of them can be recovered
As a beginner, I can't really emphasize how frustrating learning React is... at least compared to Svelte which is really just easy to understand and learning curve is less steep.
One reason why so many developers have "power horse mobile workstation", is because that's whats handed out by employers. Desktop PCs for devs, management, etc. are a rarity in the office.

As to the question, it depends on your needs. If you do most work at home, and have the device powered on most of the time anyway, then yes, a beefy desktop machine paired with a relatively cheap (as in "not a big deal if accidentially destroyed by bad luck"-cheap) is a good idea.
How is it more flexible exactly?

I hate this idiom every time I come across it. I like to look at the header file to see the interface and important documentation, and this just obscures it. Depending on your compiler it can make debugging a huge pain as well.
Great questions, I struggled with this part the most when I was learning it.

`.grad` is set by `autograd` when calling `backward()`

Probably the easiest way to understand this is to play a bit with `.grad` and `backward()` on their own, with the first code sample in the `autograd` section [1].

[1]: https://sirupsen.com/napkin/neural-net#automagically-computi...