skysight-inc/HackerNews huggingface dataset:
> here is how I do my backups. It takes me about ten seconds per day and five minutes per month to maintain

> rsync everything to each of them, bringing one down to a safe deposit box downtown, and taking out the one that was there from my last visit

Sounds like you are underestimating how much time you spend on backups. Sounds good though
PayPal patents new system to detect the theft of "super-cookies"
s/awesome/workable
1. Prep.

2. Bluster while I prep. A lot of quick thinkers are not actually quick thinkers. They are quick responders, using far more words to say just as much, with the filler works frontloaded to give them time. For example:

"Now, correct me if I am wrong, and I may be, and this is something to consider, what if we X?" buys you about 5 seconds of time to think. You can say those words in front of pretty much every argument.

3. Stop caring. Few quick decisions are actually needed. If my Product Owner is going to make me defend my approach, I just concede the argument and allow the other guy's approach, whether or not it has gaping security holes or will fail in prod. Haven't made a case for anything at work in two years and just make sure everyone whos who did make the screw up.
That’s so tragic, what’s the consequences of me still collecting and drinking the rain water? Cancer?
It can do it but not necessarily. I think in strict mode only actions can modify state and if you use reactivity only for rendering then it great
> The goal behind "hooks" was to make React simpler for beginners.

What makes you think this was the goal? React team has been trying to get rid of 'this' for a long time; I believe I saw someone say that it had some undesirable consequences for the fiber architecture and for the "concurrent mode" that eventually was transformed into a set of concurrent features. Alternatively, it is possible that they wanted a better reactivity model than the one based on component's lifecycle. Why does this necessarily have to be simpler for beginners?
I wondered what this new 'broccolini' was everyone's talking about here, turns out it's just another pan-Atlantic vegetable name variation; it's AmE for tenderstem broccoli.
They have (transitively) provided the company the original $125 to use in their operations.

In that example, you provided the money; I was just a middle-man.

Except as it pertains to employee/executive comp and future fund-raising, the company doesn't care about the secondary market liquidity. They care about the money they used over that 30 years to grow.
I can objectively prove that React devs themselves have at the very least changed how they understand hooks but more likely have been making it up as they’ve gone along. The best example is one of the more problematic hooks, useEffect.

Here’s how useEffect is described in the old documentation:

https://legacy.reactjs.org/docs/hooks-effect.html

> The Effect Hook lets you perform side effects in function components

Here’s how the new docs explain useEffect:

> useEffect is a React Hook that lets you synchronize a component with an external system.

These are dramatically different claims about what useEffect is supposed to be for. Dig a little deeper and Reaft developers will now explicitly tell you to not use useEffects for side effects, which again is the opposite of what they explained it to be.

The same change in how they’re actually supposed to be used has been true across all the books to a lesser or greater degree.

Maybe React has finally stabilized and it’s easier for new devs because they’re learning the more stabilized version. However, I suspect it’s easy because they just happen to be within the same cycle of understanding in React. Much like how React was easy for devs coming to it nearly a decade ago, until the devs changed everything about it. New devs may just not be deep enough into the new cycle to experience the pain of all your understanding being wrong.

Now, to be completely clear, I have no problem with the changes. I think change is good and I have successfully worked with languages where the change has been even more dramatic than React.

The difference with React, I’ve increasingly come to realize, is that the developers will make radical changes in how they understand it to work, while still gaslighting you that nothing really has changed.

Hence the massive effort they made to convince everyone that hooks were just a different approach as classes and they both would be first class citizens forever, when they first introduced hooks, only to subtly and quietly change the narrative to hooks being the future of Reaft and recommending hooks.

They make these shifts all over the place without ever announcing it and convincing you to believe that what they’re saying today has always been the case.

More honesty towards how they’re changing React and what those changes mean would have gone a long way to reduce the absolute confusion floating around the react world.
MobX is how you get spaghetti code and state changes everywhere. That is why we (our company) moved away from the observer pattern that MobX and RxJS use.
You can copy with Ctrl+Ins
Apple Vision Pro's components cost $1,542–but that's not the full story
I have made hard decisions to fully return to vuejs for a few months, much simpler.React has lost itself totally thanks to vercel/next.js who hijacked oss projects for its short gain with VC's money.
Maybe doing the harder thing feels more dignified, because for me it's the other way.
It’s not really a solution. You have only two players. It’s almost like a utility service.
>Write the simplest code first - get it right, if too slow or uses too much resource then set a measurable goal what a good speed or resource needs to be and then optimise until you reach that goal.

So you write the code with algorithm X. You potentially might not know the complexity, depending on how extreme you are with this philosophy, but let's say it's O(n^2). You run it on your test data. It's too slow because of some unneeded deep copies. You change that. Now it's fast enough. It gets merged.

3 years later, you're experiencing integration test failures, because scaling up your system has caused this algorithm to make things time out. No problem: you'll simply look into it and optimise it. Except you can't. Thanks to leaky abstractions, threading-models, or just an inherent quality of the code, changing this algorithm to something with a lower complexity becomes a major refactor. Pray you don't have external APIs or stakeholders depending on it.

So, not only have you wasted the time polishing the O(n^2) algorithm, you also now have a huge technical debt from what can simply be described as inadequate forethought.

The 'simple code now, polish later' process - which is really just 'move fast and break things' in a different shade of paint - means you never learn to internalise the easy wins. It also paradoxically portrays optimisation as both too complex to do initially but trivial to do later. It's not the latter. Having a good gut-feeling of algorithms or the Kafkaesque way memory works is not something that is learned over the course of a JIRA ticket - it's learned over the course of years, treated as any other code-quality concern. For comparison, you could close many tickets quickly by using a global variable to pass data around. But you don't. You make sensible, idiomatic changes to make sure things are stored and accessible where makes sense. Optimisation is the same: there is a lower bound below which it's unacceptable, even if it's not something that fails requirements.

StructuredProgrammingWithGoToStatements was written in 1974. It doesn't track well to modern computing models. I have more L1 cache than he had main memory. I do accept that the vast majority of bugs were from this, 50 years ago. I don't accept that's still true today. It's still a useful thing to teach new learners so they learn how to prioritise their development but as professionals creating novel things we need to have a certain level of planning ahead. And pride.

It's also a tautology. If the optimisation is worthwhile, it's not premature. If the optimisation is noncritical, it's premature.

My example above is not fanciful, by the way. Off the top of my head, Windows, Python and C++ all had/have trouble with some performance loss due to the fallout from earlier decisions and difficulty rectifying it once the world is built on top of it. I've run into similar problems at my own jobs, particularly anywhere that uses microservices. You can't avoid all of these but you should avoid those you can.
How do you determine that a gene variant is "Neanderthal", when most of the DNA is shared?

Sapiens are Neanderthals.
Unsafe for humans likely means unsafe for many other organisms too.
How can they even technically achieve that? You need to locate the exact location and drop some charges at presumably fairy deep depths Are these cables accessible by divers?
Such a headline surely suggests that the definition of 'unsafe' needs clarification, since we are not all dead.
There is debate whether Whiptail is better/lighter than Dialog. Certainly, Dialog has more features and works with the gpm mouse driver whereas (for me, anyway,) whiptail does not.
I'll add a tiny solutions:

If you do the audio captcha, you usually nail it the first time and it lets you in right away.

Check archive.ph for the articles.

On Brave, you can add dns block lists. One of the lists available through the GUI is for blocking scripts in news sites.

Instead of google, sometimes I use Yandex since it has more raw shitty results. Which, ironically, can be more useful than the AI-written textual diarrhoea on ever SEO-addicted site.

I use Brave + Ghostery + Privacy Badger and don't get that popup for YouTube.

That said, I miss the internet of the early 2000s.
Safari is really the Internet Explorer of this era.
I haven’t done serious front end work since years, so I’m not up to date with recent solutions. The current project I contribute to has a Next.js app for its front end. The web app has maybe 4-5 pages, only one is pretty heavy (a sort of IDE like web UI). I’ve never experienced such a sluggish tool. next dev consumes a massive amount of memory and is really slow, next build takes minutes to compile pages… I’m pretty happy I’m not touching the front end regularly, I’ve mostly noticed the slow build times when creating a docker image (it takes ~10min to build in a CI context, most of that time is waiting for pnpm install and next build to finish) and setting up some continuous deployment pipelines.

I really feel bad for anyone who decided to go with that stack.
My absolute final resort "solution" for data loss of keepsakes:

Accept the impermanence of data, memories and memorabilia.

Ideally I'll strive to keep that data backed up as long as I can, and will mourn its loss, but mentally I prepare myself that one day I might lose access in some way. Most importantly, that data is also 99% irrelevant to the next generation, maybe save for a handful of photos or videos ("what did grandpa look like?"). So in the grand scheme of things it's not like I have to be an epic archivist of my own life.

I suppose it helps that this was done for me in the past - toxic family members threw out all my childhood family photos a decade ago.
The first Borderlands movie has an idendity crisis
Another cool addition would be if we could autoplay the frames in order, at a rate of 24 odd frames per second. Perhaps if it’s not too much to ask can we also add the soundtrack? This way we can really appreciate the movie the way the director intended the medium to be experienced!
>I have never heard of an example in earlier human history when two groups of humans have blended peacefully after their territories became in contact.

Mexicans are roughly half Native American, half European.

>The majority of the Neanderthals have disappeared during a relatively short time span, of a few thousand years.

People did something that killed off the megafauna, and made people deformed at the same time. Genetically we are one species.
Is React no longer a Facebook/Meta project?
You might be interested in learning the reason hooks were invented [0]. I also use hooks in Flutter via a separate package and its creator made a great GitHub issue talking about exactly why class components cannot replicate the hook model [1], simply due to the limitations of how classes work. The code is in Dart but it's simple enough to grasp if you know JS and class concepts in general like overrides and mixins.

[0] https://medium.com/@dan_abramov/making-sense-of-react-hooks-...

[1] https://github.com/flutter/flutter/issues/51752
The "right way" isn't always the same way - in fact I'd go as far as saying that you should beware of anyone who tells you there is only one "right way".

There's no point committing the effort and resources into a full CI/CD pipeline for a simple script admin script that'll be running on just one VM you've got - but if that script is going to need to run on 100 servers then you don't want to be having to run git pull on every one of them manually.
Using eBPF based tools (like bcc) to debug the issues
https://github.com/iovisor/bcc
Everything that matters is checked into fossil. Box hosting that uses zfs. That rules out most failure modes other than gross incompetence, partially mitigated by a periodic backup to external drives.

In the before times I put everything in Dropbox. Dropbox synced with an empty directory by mistake and deleted everything. Not going to use Dropbox again.
Good work! One thing - when comparing Debian, please indicate a distro (bookworm?)
Why make it complicated. You pull an anchor along the bottom of the ocean and cut the cable.

It was commonplace where I grew up on an island, that our telephone line were cut by accident. Happened like 2 times in 15 years.
Well, Open source is NOT a business model (and your business will fail if you think that it is)

https://anonymoushash.vmbrasseur.com/2018/08/24/open-source-...

Previous HN discussion: https://news.ycombinator.com/item?id=26602316
Japan births hit record low, population down by largest margin in 2023
Unsafe doesn’t have to mean immediately fatal. The dangers of PFAS are pretty well known - hormone disruption, cancers, reduced vaccine efficacy.
>The EPA recently lowered its PFAS guidelines significantly after discovering that the chemicals may affect the immune response in children to vaccines, Cousins noted.
Sure there's a road there ... it's just your typical northern Australian, specifically Cape York type road .. they can get a bit extreme for the unwary.

https://youtu.be/l_sY-gp_pqg?t=228

If you hit such roads in the wet you're going to get bogged - and extracting yourself from wheel deep mud is an arcane artform.

Fishing & 4WDing in West Cape York: https://www.youtube.com/watch?v=sB3ia158GOI
I am not surprised. There are a handful of competitors but I believe the ship has sailed. I am a complete AWS dunce but it's too easy for me to spin up an ECS with spot machines and run my python app on it. When Heroku hit the scene and for many years, there was no easy alternative. You had to go and provision your own machines to then setup.
It’s interesting how no real evidence was cited and how they state that levels in humans have dropped precipitously even though levels in the environment have not.

They attribute this to knowing that PFAS exist but that doesn’t really explain anything.

Maybe I’m missing something but this article (as written) seems like pseudo science.
I remember the jalapenos from a local farm, which I haven't had for too long. They were all spicy, but it was well known that about 1:4 were wicked, very comparable to a conventional habanero.

I ferment habaneros and when I do, it's usually several pounds. I process by hand without gloves and evidence of this persists for days. It's only painful when exposed to heat, eg shower, handwash, etc. But as an avid capsaicin reservoir, I can attest that proper jalapenos can be surprisingly 'hot', while the typical store bought versions often can barely look a poblano in the eye without breaking a sweat.
This really makes China look weak.
A common model for chemical intake is based on the person's weight. I.e. if it's unsafe for the average human it's likely even worse for children, smaller animals, etc.
What sort of billing platform do people use for this sort of stuff?
> VSCode and WSL makes Windows awesome for web development

it is, MS care about keeping people on windows, even through it sometimes doesn't look like it

That was the idea of WSL after Microsoft realized they kind had lost the server wars (if you want to call them that) and people in science degrees frequently ended up using Linux, too (not just STEM but also others, e.g. Linguistics):

make it so that people which normally might have tried out Linux because they use tools which are Linux first don't have to try it out and in turn might never notice that it has become fairly usable for a lot of use-cases even for non tech enthusiasts

but they love Linux sure, and they surely didn't do anything to make it harder to install Linux on new system in recent times like trying to convince vendors to not ship the 3rd party certificate needed to install linux with secure boot enabled

similar for VSCode, MS realized there are huge groups of people they will never convince to use VisualStudio so they made a IDE just for them, even open source

and then increasingly adds more and more MS proprietary extensions they believe are long term essential for productive using it

but sure MS has changed and definitely isn't having any bad idea like Embrace, extend, and extinguish anymore ... or maybe they just realized they need to be a bit more soft with their approach and care a bit more about image

anyway I'm (actually, not sarcastically) sure a lot MS Dev, including such involved in this projects, acted only with best intention not having EEE or anything like that in mind

problem is huge companies like MS are in the end committed to abuse their power as much as they can get away with

which currently means playing somewhat nicely and embracing competition ... for now
Proportional – Integral regulator in Verilog. Implementation and verification
I think this might be the cleanest-looking, fastest news site I've ever seen.

It's Israeli obviously, but shame that despite the name implying it might have a wider outlook it does seem to be Israel/Israeli business focussed.
Ah yes, HN's automatic title editorializing strikes again, removing 33% of the title's wordcount and changing it from "click here to see my backup method" to "hey, I do backups".
I don’t care what he built if he justifies his arguments with distorted facts and complains about lack of things that have been around for a decade.
So, 'unsafe' here means 'unsafe for children'.

That... still seems like an issue, to be honest. Not that you were saying it weren't, but... hmm. I wonder how much of a problem we're making for ourselves.
Possibly. Plus hormone disruption, reduced vaccine efficacy, and other problems.

But, as the article noted, PFAS levels in humans are steady for now. So, the damage is probably already done.
What are the legal and technical requirements for e-book distribution?
I’m exploring Adobe ACS as part of our quest to understand the prerequisites for distributing e-books within our organization. My company specializes in live online courses and we currently send physical textbooks to our students.

We are in the process of creating a bespoke PDF reader that will allow students to read, highlight, and write notes. I’m keen to grasp the necessary legal and technical requirements for hosting and giving access to ebooks through our LMS PDF reader.

I’m wondering if I need to establish individual licensing agreements with publishers… Any insights on this matter will be greatly appreciated.

Thanks!!!
I live in Europe, I browse TikTok regularly I have yet to see a political post. It's mostly gardening and cycling content on my feed. Maybe this is a "search and it will find you" type of situation?
This contributed in a big way to the culture at Google, culture that can now be seen flowing in their products.
Sintel is worth watching. I believe it's also the longest one at about 15 minutes.
Every time the technological paradigm shifts, it's used to offer an explanation for the rest of the universe. In the 19th century it was all about clocks and other mechanical systems.
Later it was nuclear this or that. Now its singularity, simulation.
Thirty years from now, what? Maybe it'll be all biological, like everything is a giant womb. Or perhaps the brain interfaces will unlock some kind of psuedo-ESP.
Best estimates I've found is that Starlink v2 sats have an aggregate capacity of 80Gbps each.

AAE-1 alone has a capacity of 40Tbps (the article says terabytes - that's wrong; EIG is <4Tbps, TGN Atlantic is ~5Tbps), and so assuming the numbers I found are right, you'd need to be able to aggregate bandwidth across 500 Starlink sats for uplink, 500 more for the downlinks, and whatever number you need for laser links between the endpoints.

There are at lot of submarine cables[1], though, so while I don't doubt that there will be people looking for contracts to use Starlink for some degree of extra redundancy and worst-case offload, the primary redundancy for these cables will be other cables, along other routes at least until Starlink gets a couple of generations further.

[1] https://www.submarinecablemap.com/
By the time you forgive the bill you may have caused significant psychological distress, maybe even irreparable. This doesn't feel like a responsible approach.
You don't see both sides, that's pretty clear from your descrition.

And the original event is about an IT/devops engineer for the air force not wanting to be even this remotely part of Israeli mass attrocities/genocide/whatever you want to call starvation to death/murder/massacring of millions of people so that he demonstratively killed himself.

So one side is this man and his moral compass, and the other is US air foce and US gov. supplying Israel with a huge amount of weapons and support for the massacres.

This website netizens tend to blab sometimes about morality and taking a stand against bad/marginally illegal managerial decisions. Well this one IT engineer made an ultimate stand, and nobody here even upvotes to give visibility to his story. Instead there's more of the same "I got billed too much for using service without fixed rates/billing cap, please help" bullshit getting hundreds of upvotes.
> Open-source software doesn't stop being so just because access to the source code is paywalled, as long as it has an OSI-approved license.

Whilst this is true, all OSI-licenses give others the ability to redistribute that code, and that doesn't appear to be the case here.
Because we don't drink rainwater.
In neal stephensons 1996 classic wired article Mother Earth Mother Board theres a bit in there about why cables are not attacked.

"There is also the obvious threat of sabotage by a hostile government, but, surprisingly, this almost never happens. When cypherpunk Doug Barnes was researching his Caribbean project, he spent some time looking into this, because it was exactly the kind of threat he was worried about in the case of a data haven. Somewhat to his own surprise and relief, he concluded that it simply wasn’t going to happen. “Cutting a submarine cable,” Barnes says, “is like starting a nuclear war. It’s easy to do, the results are devastating, and as soon as one country does it, all of the others will retaliate."

This rule was broken last year and it will happen again with more and more frequency.
What bugs me on a daily basis is how unusable/finicky certain webpages are (due to ads, prompts to login/subscribe, or the sheer link density). If my cursor is even slightly in the wrong place, I end up clicking on a different link. Or because my cursor accidentally hovered in the wrong place, it opened a dynamic menu which blocked me.

Or something even newer is the emphasis on "recommendations" being included in your searches (youtube, quora, etc).

https://www.youtube.com/watch?v=31g0YE61PLQ