skysight-inc/HackerNews huggingface dataset:
I have not adopted hooks and have argued against it for others on the team. My primary objection is that the paradigm is not clean.

Class based components are fairly straightforward. The entire render function is run on every change.

Solid/Svelte are fairly straightforward. The component is run once and then only the reactive parts change.

Hooks run the function on every change but there are islands of non-running code inside the constantly rendering body where only run when their dependencies change. This strikes me as an obviously intermediate solution and I don't want to spend time porting/developing something that's going to be obsoleted in a year or two.

The next framework generation is underway and the time for early adopters to move on is in the next year or so. The main reason to hold off is that the handling of SSR/hydration/etc is in flux and I believe the primary benefit of the upcoming generation is going to be ability to avoid shipping most component code over the wire.

I have a lot of respect/love for React. I've seen quite a bit of criticism that the vdom idea is inherently inefficient but the important thing about it was that it was reliable. Lots of JS used to do all sorts of crazy stuff with the dom underneath you but React has basically cleared the field of most of that which allows more fine grained approaches to work consistently.
Unconfirmed Reports of Russian Bomber Entering Polish Airspace
*for my gig as a software developer who does a bit of video

The extra width is key, and the density and brightness are acceptable. The qualities are a vector more than a scalar, and someone less presbyopic and more AV focused might give those different weights.

I recommend doing it as a side-by-side though, I did this with the monitor in question and the iPad Pro before choosing the former.
> It's not the same for me. I live in Europe, not the Middle East. Very simple.

That's the reason why Ukraine war happened. We don't care, unless it is happening in our neighborhood! Now it is too late.
It took you a few days to learn a new big & powerful React framework, and your experience apparently was bad, I'm ok with that.

But, sorry : what does that have anything to do with hooks ?
There is no "would" here; he couldn't prove anything and the money is safe.

But let's say we live in a magical universe in which juju is real and yet someone is foolish enough to offer a lot of money for a proof.

How would the prover lose social standing? He proved wrong that obnoxious nay-sayer. He'd be a juju hero, with stars in his eyes. Or maybe not. If juju were real, he would also have been trampled by a throng of others trying similarly to get the easy money.

What I suspect is that there might be an element in the juju mythology which stipulates that any wielder of juju power who tries to prove juju to nonbelievers will die.
Good luck accurately machine translating the infinitely growing idiom of jokey Twitter conversation, which most native speakers can pick up pretty quickly.
Well make sense to me to host your status page outside your main infrastructure.
OP greatly overestimates the knowledge of the average HN user!
That's just retroactive rewriting of history. These "local demands for autonomy" where a violent, foreign funded, uprising. It was about to be crushed by the legitimate Ukrainian military which was in turn crushed by the Russian army. The Neonazi militias occured afterwards and filled the power vacuum left by Ukrainian army.
I had to modify FFmpeg for a job and I found it surprisingly accessible and easy to read/modify: https://github.com/FFmpeg/FFmpeg
You can't use electricity to produce enough heat to melt steel thats why they use coal thats why that electricity is so cheap. If you could then why is the steel industry spending billions on coal when there is cheap renewables in massive abundance? Why is the electricity produced by solar so worthless if it has such imense value to this rich industry, and on the flip side why is the value of bitcoin through the roof if society don't benefit from it.

Banking the worlds unbanked offers little to you that doesn't mean it offers little to society think of those who have less than you.
My iCloud email is up and running.
TLDR; Divide-and-conquer heuristic.

When I was contracting, every few months I was looking at a new-to-me code base. First - if you don't know the language the code was written in, then you need to learn that at some basic level. Next, if there was some framework or set of libraries involved, see how many of those you can identify and how many you might already know. Start with trying to run through a build, as you'll either have success or it will throw errors and that will teach you something about both the health and the components of the project.

Once you actually get into the codebase, look for patterns. Often there will be pretty clear layers or types of components, identifiable either by name or organizational structure. Sometimes you'll see patterns that tell you "Oh, George must have written all this code, and Steve must have written all that code" because of personal idiosyncrasies. That's the worst case, but sometimes it's what you have to go on.

I spent a lot of years in application triage, where I was called in to fix serious problems in apps with which I had no experience. Like today's Apple outage - I used to parachute into situations like that and had to get things running, fix, post-mortem, etc. There are great tools out there where you can inject them into running code and watch real / test users execute code. Thats's a great way to very quickly learn how everything is assembled, IE: why did that piece of code get executed there, or why didn't that piece of code get executed.
Yep, white lies. The underlying rationale is that kids do throw up in pools and you don't want to get into a public argument with a kid about how they're not going to throw up, can they go in pretty please.

It's like the thing about getting arrested for turning on the lights inside a moving car. No, you won't get arrested, but the reflection on the windshield can be annoying, and getting distracted by kids going ham on flicking the lights on and off is obviously dangerous.

See also, school "permanent records".
There's a big difference between low-impact, low-evidence beliefs like fan death, and easily verifiable, high impact things like "sacrifice a cat person".

The problem isn't that people have momentary false beliefs (fan death can be disproven with a bit of evidence gathering) but that there appears to be no correction mechanism. If you never see a dude turn into a cat, and if sacrificing people doesn't make you rich (worked for Jeff! ... Sorry couldn't help myself) then why do you think it works?

I'm not sure the answer is intellectual. It's quite possible people have some sort of psychological desire to believe things they know deep inside aren't true. Perhaps it's some sort of group belonging that must be satisfied ("yes, he walked on water!") by professing belief in what everyone can see is false.
We use a thing called Relay (https://relay.dev/) to manage our querying, mutating, and state management.

When you query data, it is cached locally in a shared data store that will automatically trigger re-renders of components that take in the data types as a dependency.

You don’t have to write an update to the data, you query it and Relay updates all the underlying models in the local state cache.

The data types are correlated to your components via GraphQL fragments which allows Relay to know what and when to update.

Because most of the values you are using in your component are already stateful, you end up using A LOT less hooks since most state updates will trigger and happen for you.

It’s incredibly powerful once you get going with it.

The downside is getting it to work properly with the type generation. It can be rather finicky and Facebook likes to rewrite the API out from under you every couple years.
yeah, 'bruh' has been a thing for the past... 7-8 years now? hit its peak around 2016 but is still going strong.
Is it hard to imagine there are people who want Putin to win as fast as possible so that fewer lives are lost and nuclear war is prevented? Ukraine should have stayed neutral wrt NATO, and at any time Zelensky can end his war, but he won't.
> unsure of the legality of this.

I always have a laugh when I see this logic.

A product costing more than $200 and not available in the consumer market without some hoops to jump? Of course someone would resell it for $20 (including their profit) totally legally.
Drinking a lot of water can be helpful - if you expect to perspire heavily from temperature and/or physical exertion but that is a different kettle of fish.
> I trust Apple more than Google personally

Curious as to what the basis for this is? As I understood it much if not most of Apple's OS and software is a pandoras box so we have no real idea as to what it tracks and/or sends back to Apple.
Yeah I get that. Just saying that negotiation requires both sides to think that that risk discount is fair. We're pretty much in agreement. ;)
root@freebsd13-aa64:~ # fortio load -c 100 -n 1000000 -qps 0 http://127.0.0.1:8080/
Fortio dev running at 0 queries per second, --> 4->4 procs, <-- for 1000000 calls: http://127.0.0.1:8080/
10:23:40 I httprunner.go:87> Starting http test for http://127.0.0.1:8080/ with 100 threads at -1.0 qps and parallel warmup
Starting at max qps with 100 thread(s) --> [gomax 4] <-- for exactly 1000000 calls (10000 per thread + 0)

caishu@ubuntu21-arm64:~$ fortio load -c 100 -n 1000000 -qps 0 http://localhost:8080/
Fortio 1.22.0 running at 0 queries per second, --> 2->2 procs <--, for 1000000 calls: http://localhost:8080/
13:07:55 I httprunner.go:87> Starting http test for http://localhost:8080/ with 100 threads at -1.0 qps and parallel warmup
Starting at max qps with 100 thread(s) --> [gomax 2] <-- for exactly 1000000 calls (10000 per thread + 0)

Why half the GOMAXPROCS for the Linux example?
I'm a researcher in the field, and the amount of new research coming out each day is just way too big to handle. Which means I have to rely on heuristics like this to judge what is worth my time. Otherwise I'd be spending 25 hours/day reading papers, and waste brain capacity digesting worthless findings. Not everything that passes peer review is read-worthy, far from it. It just means there aren't any gaping holes in it. Don't get me wrong, the heuristic is far from perfect. But a random paper on HN (which is not known for its abundance of researchers) that was posted without any context explaining why I should care is not a good signal.
Counterpoint - encouraging the average Ukrainian to "kill Russian soldiers" puts their lives at risk as well since the Russian soldiers are better armed. And lets say they get geeked up and start firing into the street form an apartment building, to which the Russians respond by launching a missile into and killing others who weren't trying to engage the soldiers.

The sane response would be to consistently call for non-violent posts only on the platform.
If you want hours of battery storage sure, not if you want seasonal storage. That makes solar+battery a niche, not something you base your energy economy on. Besides, even if you did there's not enough minerals being mined to do battery grid storage at scale to move entire economies over to it.
Why do you think it’s ugly? What makes it so?

I’ve bridged several UIKit components into SwiftUI and it’s been fine. You have to be careful with Auto Layout, my approach was to divide into separate UIView and then wrap those in UIViewRepresentable, thus leaving the layout to SwiftUI. But that was the main thing to keep in mind.
That is the great question. We have a similar situation in United States see

https://www.thedailybeast.com/stella-immanuel-trumps-new-cov...

I think part of this is political, they want people to believe in crazy things and not look for the rational truth because that might expose those who are trying to hoodwink the public in other ways. Like giving huge tax-cuts to billionaires. Give huge tax-cuts to billionaires and money will appear in your clay-pot.
Michael: My father’s no different from any other powerful man. Any man who’s responsible for other people. Like a senator or president.

Kay: You know how naïve you sound? Senators and presidents don’t have men killed.

Michael: Oh. Who’s being naïve, Kay?
Oh yeah, sure, FBI never ever infiltrated and also never ever did anything bad to any anti-war movement in USA.
For me it seems React has made some unfortunate choices in an attempt to go FP in a language that does not afford it very well. Instead of embracing JS and working in alignment with its limitations/offerings, the React team has introduced elaborate workarounds that gives a whiff of FP but introduces indirection and verbosity and does not solve basic problems of state (i.e. the example from the blog post with classes vs. closures).

I prefer frameworks like e.g. Svelte that works with what JS affords. If you want to go full FP Elm or ClojureScript will give you more value for your money than React imo.
> I know this isn't the point you were going for, but this _is_ a heuristic that is deployed in some companies/institutions (at least the UK variant certainly is).

Which companies/institutions are you thinking of?
Or a science too complex to be proven?
That's over-commented code written by a junior developer from my quick look. The first random thing I looked at in grbl/eeprom.c:

...
char old_value; // Old EEPROM value.
char diff_mask; // Difference mask, i.e. old value XOR new value.

cli(); // Ensure atomic operation for the write operation.
...

You can remove the need for the first comment by calling the variable old_eeprom_value. Boom, simple and obvious. Commenting cli() is similarly ridiculous: call the function disable_interrupts() and it's completely obvious what it's doing. Later on:

sei(); // Restore interrupt flag state.

This is incorrect. It's enabling interrupts, not restoring them. If the intent was actually to restore the interrupt disable flag to its original state then this function is buggy and will unintentionally enable them. It would be far better to document the expected sematics in the documentation for the function above, but instead of documenting the expected semantics of the eeprom_put_char() function, you have to read the code to figure out what the semantics are. What would be better is to have a comment in the function description saying "this function can only be called with interrupts enabled" or "this function is atomic and can be safely called from an interrupt handler or with interrupts enabled". Then it's obvious when reading the code which semantics are guaranteed / expected.

So, sure, overly commented code makes it easy to figure things out, but this is a sign of a junior developer that is focused too much on the code and not enough on the overall system. This isn't something I'd like to see a developer pointed at that is looking to learn good habits. Good habits are telling other developer what they can expect from a function. Bad habits are making them read the code to figure that out.
Sorry, but you interjected a lot of assumptions, biases and opinions and are passing them as fact.

> oligarchs, who will only be further advantaged by unregulated markets.

No one is saying about "unregulated markets". The idea is about having regulations being localized and based on the principles of much smaller communities. Take the principles from Localism applied to "virtual city-states", if you will.

> wealthy family (...) is comfortable with inefficient plantation-based farming.

Because they have a monopsony on the labor. On a world where you can decouple "where you live" from "where you work", this goes right out of the window. And it goes both ways: it can be either because the locals leave the place because they can find better opportunities, but also because people from other, wealthier places might look at these places as an opportunity for a low-cost of life and cheap labor. Go checkout /r/digitalnomad and you will see how many people are already doing or planning to do such a thing.

For a more cynical person, this means "gentrification". For someone looking at things at a wider-scale, it means that people could eventually be able to do something that was only possible for the elites controlling multinational corporations.
Compliance is easy and manageable, for the most part. It's just that companies want to still do the things the law is trying to disincentivize, and want to put as many dark patterns as they can in the way of users avoiding it. So the "unmanageable" part is trying to figure out how close you can come to breaking the law without being blatant.
Yeah but what do you use it for apart from receiving verification codes?
Fatigue can be a symptom of depression.
To me, it feels kind of like the poster is agitated that the article focuses another country's problems, which elicited the kneejerk response about "Americans", "Christians" and "lazy journalism", as if to say "focus on your own problems." This response is confusing I never stated this was a problem specific to Nigeria, but instead I asked a general question about magical thinking in academia.
I would be focused on trying to simply run your workloads on your own.

It can be with EC2 or on your own physical/virtual Linux machine, but it should involve the required databases, the various components (e.g. your front & backends,) and some way of providing access (it could just be the option address and a port at the start.)

Lastly, figure out what it looks like to update code safely.

Afterwards, you should have a pretty good idea of how you can leverage cloud services to enhance or replace aspects of this, but will be dependent on none of them.

I can’t imagine that you’ll get this valuable perspective from any available course.
I picked a terrific time to lose my temper and do a `rm -rf /Library/Developer/CommandLineTools ; xcode-select --install` /facepalm
Apple Maps is down, and so is installing other map apps via the App Store
Pretty much the title. Had to go for a drive and Apple Maps couldn't find anything. Odd, so I rebooted and it persisted. Looks like there's a major outage. No big deal, I'll just install waze... and the App Store is totally down too.

I felt like I was teleported back to the map quest era. It just goes to show how having everything locked to a single provider is asking for trouble!

Protip: Keep another maps app installed just in case!
Source? Looking at this report[1], battery storage methods are 2x-3x the cost of "combustion turbine" (natural gas?). Presumably the kW and kWh costs for storage costs don't factor in the underlying of the energy they're storing, so the actual cost is likely higher.

[1] https://www.energy.gov/sites/prod/files/2019/07/f65/Storage%... (figures 5.5 and 5.6)
I think this is what sets this technology apart. The human element. We don't take photos to look at in awe of the quality and crispness. We take them to share with others. Usually DSLRs force you to get to a computer, insert the memory card, process the photos in Lightroom, then share from your computer.

Phones make this process seamless because the designers realized that the key to a good photo experience is the human experience of sharing.
If you're a researcher in the field is it not a fundamental skill to be able to make these judgement calls yourself? And if wasted time is a concern to you, what makes you think others would be willing to put in the time to try and convince a random academic that they should or shouldn't read a paper where they've not even specified what they'd want to get out of it?
Naturally, and I think Putin will stay clear of that red line.

But there are many other means to be tough with Russia without triggering an all-out war. Not giving him money or trading with him is a start. Providing an unlimited supply of weapons, intelligence and humanitarian aid to Ukraine is another.

We should also be mindful that staying clear of a direct confrontation with Russia doesn't mean Russia should be allowed to set up all sorts of arbitrary red lines in term of what they claim constitutes an act of war. Providing planes to Ukraine for instance isn't an act of war by any standard. Biden's veto on the transfer of the Migs was really an act of weakness that will call for Putin to define more red lines. I heard general McMaster recently mentioning Russian pilots were shooting at US troops in Korea and Vietnam.
You can buy the chips from them for a sufficient price.

The price is probably something unreasonable, with a high minimum order quantity or high lead time - because that's typically what happens when you see "Ask for Price" or "Request a Quote" (folks who do that often want to reduce your ability to comparison shop easily).
Hmm, maybe you could. I haven't tried it. You'd need to make sure that both sides of the via are un-tented (no green solder mask) so that the solder would flow through. The via would need to end up flat so the solder ball on the part would stick. And you still might get solder bleeding through when you reflow.

For high-ball-count FPGAs, it sounds super tedious to prep. And obviously it's a no-go for machine assembly. But for smaller stuff it sounds feasible!
I work on a large, complex, well-respected iOS app. Some of our main competition is desktop apps, and we've often been asked for a macOS version. M1 Macs can run our app natively now, and we've done some work to make that a better experience than it would be by default. We've also spend some time seeing about using Catalyst to bring the app to the Mac for real.

As a longtime Mac developer, I'm not super impressed. It's cool to get a build going for macOS quickly, but the effort required to make a non-trivial Catalyst app not suck turns out to be very significant.

I would definitely not even dream of using it to build a Mac-first/Mac-only app. The (debatable) advantages of UIKit over AppKit are just not even close to enough to outweigh the difficulty involved in making a good Catalyst app. The benefit of Catalyst is bringing an existing iOS codebase over and/or sharing code between platforms. It is not a better way to make a Mac app on its own merits.