skysight-inc/HackerNews huggingface dataset:
> It's designed to use the most democratic and ubiquitous commodity avalible.

Which is why Bitcoin mining is only feasible in the areas that have the lowest electricity rate?

> We produce about 160,000 TWh of power, ~50,000 TWh is wasted due to inefficiencies. Bitcoin using 120 TWh (0.25% of wasted power)

How much of those inefficiencies are caused by Bitcoin? My understanding is that a substantial fraction of that inefficiency is things like "there's power loss in running power from a power plant 100s of miles away" or "converting from AC to DC power induces power loss." In other words, Bitcoin isn't converting electrical waste into useful work, it's just creating more electrical waste on top of the power it directly uses.

> A lot of Power projects get scraped due to inconsistencies in demand. Random Ex: Texas power outages during summer peak AC usage. It's infeasible to spin up and spin down extra generators to meet spikes in demand. #Bitcoin fixes this by providing excess supply a discounted demand during normal hours that can be routed away during peak needs else where. Ditto for renewables.

Are you aware that the electrical grid already manages demand in large part by telling the smelters to stop smelting for a few hours? There's no need to invent new demand to manage existing demand.
They can't be used for proof of work.

Hashing for say, Bitcoin, works because you're finding a hash that has certain properties (e.g., having a certain number of leading zeroes). Anyone can take the input (to the hash function) you've found and trivially test that it does indeed produce a hash with those properties. Finding the hash is hard, but testing the hash is easy.

Doing SETI/Folding work doesn't work like that. Consider Folding: every unit of work produces useful output. Every input produces equally valuable output. Additionally, the cost of producing the output is high, but the cost of verifying that output is also high.

With hashing-based PoW, everyone in the network can verify that a hash with the correct properties was produced. There's no way to say "yes, this one Folding@home worker found something unique". The work needs to be checked, which means a majority of nodes in the network need to verify the output, which means >50% of the network needs to compute the same thing again (you can't rely on less than a majority, or anyone could cheat).
Exactly. Many times I've typed out a comment and at the last moment refrain from posting, because I feel it doesn't really add to the discussion. I'd rather there be less higher-quality comments, than many comments like mine justing adding +1. Ironically, I almost deleted this comment.
Video games serve as entertainment and for many people an escapist solution. Yes, I own a few Pocket Operators and owned an OP-1 previously. Playdate is an evolution of TE’s design aspirations. The OP-1 included video game like animation and influences in its music engines. Similar to the OP-1, I am concerned that its strict design POV may hinder creativity. Some artists prefer limitations. I would’ve loved an editable sequencer on the OP-1. Was a backlight that hard to include for the Playdate?
Apple paid woman millions after iPhone technicans posted explicit photos online
In this way react is choose your own adventure. There is no current signal that the way class components work will change and I don’t exactly expect that to happen any time soon if at all. Rather then new features are aimed at developers with more complex use cases and make heavy use of asynchronous data fetching in a way that lends itself to concurrency.

If this isn’t you I’m sure at least the general performance improvements will be nice otherwise I don’t see why you can’t just keep doing what you’re doing
How much more access can you possibly want on top of the previous FDA expanded access guidelines as well as the newer Right to Try Act?????
As someone who was initially resistant to hooks, I actually find that they're a more expressive API to how I was already thinking about my applications. There's footguns for sure, just like there are with class components, but I found that rewriting my class components with hooks instead actually made the code cleaner and easier to reason about. That being said, it's possible the benefit simply came from the rewrite, but even with newer components, I feel like hooks are a better API.
And watching news will somehow help?

Some genocides are happening right now, news are silent.

Men are already prevented from using anticonception and abortion. Some countries ban DNA paternity tests. I do not see any news about that.
Both you and OP are conflating the income and wealth question, which is what ProPublica's article specifically addresses.

By considering income but not wealth as taxable, the system skews automatically to highly regressive, furthering wealth inequality.
4. You cannot make money off of the work being done because the saved money will then be spent on more mining until we hit a 100% non commercial computation equilibrium
React hooks might be the best feature ever, once you understand it, it provides you a way to write highly reusable code.
I personally fell in love with hooks after initially disliking them, you should give it a try, maybe in a toy personal project, to see if you like it. It is great for separation of concerns.

You basically stick to writing pure functional components focused only on how to render, and try to abstract reusable logic into hooks, and expose only what you need

For example, you could make a useApi() hook and inside your component just do const { data, loading, error } = useApi('/endpoint'), so you can hide everything you don't need away from the rendering logic
a) and b) just mean you’re relying on someone else who watches the news, so the same drawbacks apply…
Except that is not true at all by any objective measure. [1]

The Ultra Rich do not use Personal freedom to disable efforts, it uses Government Regulation to disable efforts, the Rich LOVE big government why do you think many billionaires vote Democrat, it enables them to control the economy to ensure the poor are kept poor and dependent on government. In the end we should look to Smash the State, Eat the Rich, and expand personal freedom [2]

[1]https://www.youtube.com/watch?v=4J5s6aZCPSg

[2]https://c4ss.org/content/30085
Right. Making students repeat and memorize sentences that are beyond their current ability is detrimental.

Think of it this way. If I gave you a paragraph in Turkish (or insert language X) to memorize and recite that's very different than giving you some greetings and responses to memorize and recite.

For the first there is no mental model for where the paragraph fits in or how it's constructed. In the second almost everyone has some experience learning greetings in a couple of languages just by exposure to pop culture, so even if you don't understand the specifics of how those phrases work you have some confidence in how to employ them and you'll generally feel somewhat confident in being able to break them down later if you need to because greetings done in short and simple language.
We do intend to ship a ES module build of React in the near future. Because that's a breaking change that could require significant changes to existing apps (i.e. to update the imports), we'll likely wait until the next major release cycle.

However, note that tree-shaking probably won't help much in the case of React. React isn't a library of independently useful features; it's a cohesive framework where features work together. We also have a really small API surface area. So there's no much to "shake" apart.

Arguably the main `react` package would benefit slightly from tree shaking, but those exports are already really small. The `react` package doesn't contain that much implementation; it mostly just calls into internal React DOM to schedule updates.
Great! So let's figure out a way to make this study happen so that the drug can be given effectively (if it does indeed work) rather than have a blanket approval of a drug that lacks any proof of efficacy at all.

That a drug hasn't been approved for a treatment in years is no reason to approve one that doesn't work.
So blockchains aren't fundamentally decentralized, permissionless, censorship resistant networks, and you've found a secret issue that will cause an unraveling of the protocol?

If not, then maybe just step back and observe the chain grow block by block, day by day, unfettered, for the rest of your life.
Really looking forward to new server side components and suspense.

Also, kudos the the React / facebook team for building such an exceptional framework. React has really enabled small teams like ours to build large applications and even a framework! It takes a lot of dedication and careful planning to create such a versatile lib for a broad audience. 8 years down the road and the team is still keeping it together while innovating web-dev to new frontiers.

Thanks again! And keep up the good work.
> will never allow my children to play that game

I can see not forcing them to play the game, but "will never allow my children to" always struck me as a weird tone.
Wow, thanks for that link.
For example, Analogue Pocket, the 200 USD Game Boy hardware emulator that sold out in minutes: https://www.analogue.co/pocket
Your facts are wrong. The global, yearly energy use of Christmas lights is ~2x Bitcoin's energy use.

People way overestimate how much energy Bitcoin uses and way underestimate how much simple things like christmas lights, video games, hockey rinks, etc. use.
That and hot hatches, pretty please.
> top^W^W

Is this an abbreviation or a reference to a command or what does it mean?
So you're saying you have no idea why they're making changes because you haven't been following along, despite using the library every day...?

The communication about the "why" of new features has been extremely clear. E.g. for hooks: https://reactjs.org/docs/hooks-intro.html
> the times when the stock falls

Remind me when that's ever been allowed to happen in the past 10 years. At the first sign of any market trouble, the default Fed response is OMO and cutting interest rates to shore up the markets. Stock prices can never fall even if the actual economy is in the shitter.
Agreed that having React available as native ES Modules would be good. There's an open issue on that:

https://github.com/facebook/react/issues/11503

However, there really isn't anything to tree-shake in React. The renderer implementation is effectively a single consolidated set of logic that handles all work for all types of components. So, there's no unused functions to get shaken out.
Congrats on the release folks!

I'm always impressed by how far the library has come while remaining _so stable_, and it's always the thing I point to when talking about backwards compatible and stable JavaScript API's.

I bet you're all happy to be finally dropping that polar chart!
> I thought white-collar crime was usually a person scamming a company.

That's not my understanding of the term "white-collar crime",
nor is it the definition used here, for example: https://en.wikipedia.org/wiki/White-collar_crime

The interest calculation problem you describe would fall under what I think is the usual definition of "white-collar crime".
While we’re comparing anecdotal evidence, here’s mine:

Have a liberal arts degree from a small liberal arts college (<2000 students), had no
problem at all breaking into tech or FAANG tech internships, anecdotally I think it helped me get my foot in the door.

Most of my peers also have degrees in liberal arts, and most of them are living successful and fulfilling lives, both professionally, socially, and even monetarily; some went into tech and finance, many are not.

I think something important to realize is there’s many paths to success — even the same idea of success that many in tech seem to have (financial security) — and someone who is passionate and talented will find one; following a pre-set college curriculum churning out STEM majors is just one way to get there.
And unless I've misunderstood Fastmail's service, on a cursory glance of the service they offer, isn't something they offer.
The speech utterances are not transgressions of rights; it is the physical actions: assaults, lynchings, unequal imprisonment for identical crimes, etc. So riling up a bunch of people about how "Trump is a Nazi" ought not be a crime, but if someone immediately punched Trump after hearing that speech, then it was that punch that was the crime (violation of right to physical security / life of victim).

I'm assuming that you're not claiming anything like a natural right against exposure to offensive speech ("speech acts").
> it's also unfair to call them aggressors for the couple of times they've resisted this continual inward push from NATO.

My country was occupied by USSR (aggressors). Now is free and it is not their business anymore. Complayning about that is bullying.
It's not an actual apology when you not only justify the bad behavior, but then go on to repeat the accusation.

"I'm sorry I slugged you but you made me really mad. I won't do it again if you don't" is wholesale failure.
If running a Bitcoin heater costs half as much as running a regular Bitcoin miner then you can spend the savings on twice as many miners to get more Bitcoin. If everyone does then the effect is net zero. However, your miner can't be a heat pump so in practice it would be net negative.
I will also never allow my children to gang up on and beat homeless people in the streets.

Sounds like a weird tone?
You can program Roblox... and Minecraft pretty much _is_ a programming UI.
Terraform CDK is a thing too, if you want to go beyond AWS.
https://en.wikipedia.org/wiki/Wealth_tax#Past_repeals

There are two studies cited. One on the repeals is by "Institut de l'Entreprise" which seems to be a wealthy people's think tank [1] and the other is about why the wealth tax wasn't introduced in the UK [2]. I'm not convinced by the evidence here.

[1] https://fr.wikipedia.org/wiki/Institut_de_l%27Entreprise

[2] http://eprints.lse.ac.uk/42582/1/Why_was_a_wealth_tax_for_th...
I love when news like this penetrates through the HN echo chamber where people legit believe that static site generators are going to take over WP any day now. It's a reminder that we all have blind spots.
And yet that haven for the rich, Switzerland, has a wealth tax. Explain please?
The biggest issue with Pulumi is that Pulumi doesn't support adding custom API providers. Part of the power of Terraform is in provisioning infrastructure, orchestration, deployment, and application configuration all in one tool. For example:

(aforementioned GitHub provider)

https://registry.terraform.io/providers/terraform-provider-c... for Concourse (CI/CD)

https://registry.terraform.io/providers/coralogix/coralogix/... (full disclosure: I work for Coralogix)

This would be completely impossible with Pulumi. If Pulumi didn't bless it, it doesn't exist in Pulumi's world. In the meantime, Terraform allows you to separate all the network calls to a custom provider and allow you to just focus on the configuration. The number of paid external APIs is only expanding exponentially, Pulumi can't possibly build and support them all in-house. Sounds like a current limitation of Pulumi's "use any programming language you want" design and something that really needs to be addressed; it's not that writing a custom Terraform provider is easy, but it is quite simple to get started by following any of the bajillion open-source providers as a sample template to get started from.
Good news, everyone!

https://github.com/FiloSottile/age/commit/d164fef036a2d19280...

It will be in the next release candidate.
Anvil | Software Developer | Cambridge, UK | On-site/Semi-Remote | Full-time or Part-time | https://anvil.works/jobs

Anvil | Junior Software Developer | Cambridge, UK | On-site/Semi-Remote | Full-time or Part-time | https://anvil.works/jobs

Anvil | Developer Advocate | Cambridge, UK | On-site/Semi-Remote | Full-time or Part-time | https://anvil.works/jobs

Help us fix web development at Anvil (https://anvil.works)!

Web development is way too hard – Javascript, HTML, CSS, SQL, and frameworks coming out of your ears. So we built Anvil: a simpler way for anyone to build full-stack web apps, entirely in Python. Anvil is a web framework; it’s an online code editor; it’s a GUI builder; and it’s a hosting platform. And you’ll be helping us with all of it.

We're looking for:

SOFTWARE DEVELOPERS:

Build the platform that's fixing web development for everyone. You’ll be working on the Anvil editor (that’s the development environment, code editor, drag-and-drop designer, version control, and so on) and the Anvil runtime (that’s the Python-to-JS compiler, UI toolkit, database, integrations, and the hosting engine that makes it so easy to deploy).

Our stack is mostly Javascript, Clojure and Python (in descending order of line count). We don’t need you to be an expert in all of these already, and for the junior role we don't require any, just talent and an eagerness to learn. Otherwise, we’ll want to see evidence that you can hit the ground running with at least one of them – or that you’re a great all-rounder who won’t have a problem with any of it.

Much (or most) of your work will be open source: https://anvil.works/open-source

DEVELOPER ADVOCATES:

We need developers with great communication skills, to show people how to build awesome things with Anvil. You’ll be writing how-to guides, blog posts and tutorials, building example apps, presenting Anvil at conferences (when those resume), and helping our users – from individual developers to huge tech companies – build their applications. And then you’ll help us work out how to improve Anvil for them.

It's rewarding work – developers love being introduced to Anvil (our stand is always crowded[0] at conferences!). Plus, there are all the advantages of an early-stage startup: lots of autonomy, and huge impact.

We're bootstrapped and profitable, and a diverse team, with customers ranging from tiny startups to household names. Find out more: https://anvil.works/jobs
Sure, that's in a sense a movement to discourage this.

But my point was that it is still a niche movement, in the sense that when you're acting as part of an internet mob or a cancel mob or any kind of social mob, you don't get much of a backlash for it (even if you're not just a cog, but a prominent part of one).

Whereas if you were being a jerk in some other way, you'd immediately be called on that.
Billionaires are largely majority shareholders in corporations. I'd say that's a fine place to look. Maybe the IRS can look at the assets of anyone who's suspected to be worth 750M or more. Again, as I said, you could fund better enforcement of this by funding an IRS task force who's job it is to find and tax them. I can't believe something so simple as 'billionaires should pay more than 23% (or whatever it is) taxes are controversial, but here we are.

I especially love how the Koch brothers effectively funded an astroturf campaign that hijacked the republican party, to get blue collar folks to argue against taxes on the 1%. That is some rich irony.
cperciva's spiped is, at least, deliberately old-fashioned; and I'd be inclined to trust it over most newer designs. (Wireguard does appear to be pretty awesome.)

I do agree that lots of legacy cryptosystems just aren't very good.
To clarify, I am not talking about the React 18 feature. I have this problem in React 17. On Pagedown key, I throttle the setState calls because calling it too fast causes React to batch the updates. I'll try to make an standalone repro and open an issue in the React repo.
Patch-perfect commits are an idealistic goal. The truth is that, as already mentioned, many of those typos and “dirty” commits can be the source of bugs that you’re looking for. Hiding them hides the history.
If the tax is on the gains it's still a single whammy.
> but for sure you have to take in account the amount of buildings, air-conditioning, commuters, datacenters, branches, ATMs, bad written code, exchanges.

You also have to do the same thing for Bitcoin if you want the comparison to remain fair. Bitcoin doesn't magically replace the entire financial industry, so you don't want to accidentally include the costs of the things it doesn't replace (such as the bank manager who's deciding whether or not to authorize a mortgage).
Have you seen Terraform CDK? https://github.com/hashicorp/terraform-cdk
Yes! Absolutely I am rewriting history. I don't care about my messy history, and nor should anyone else. I routinely force-push to my branches because, again, it's my mess. Tools like mailing lists obviously handle this fine because every revision of my patches is published there, so who cares. Tools like Gerrit handle this well because it stores patch sets regardless of branch state -- as they are unrelated -- which feels like the right model. Tools like Github just suck at this in general and fall apart when you start force-pushing PR branches, but whatever.

The problem with squashing at review time is that it is incompatible with my model. I'd rather teach engineers to not push shitty "fix the thing" or "oops" commits that are ultimately useless for me, the reviewer or reader. Just use git commit --fixup and git rebase --autosquash as $DEITY intended and force push away. It's your world, you'll be deleting the branch after you land it anyways.

The tool works so well when used as intended: a distributed version control system. The centralized model adds so much pain and suffering.
This was written in 2012. It does not appear that this idea went anywhere - not sure why.

It could be the fact that it's not trivially easy to verify the work completed, unlike a hash.
Ahh, interesting! Missed this news. Makes sense.
Neat! Looks like a great release tool.

I'm wondering whether there is a specific reason to mobile apps?

Would be nice if all releases (web, mobile, etc) can be going through the same pipeline. After all, those "people-centric" tasks are generally applicable to other projects as well.
I find the function-based components much more elegant than class-based components. The semantics of Javascript classes are confusing, and the new notation is very concise. (Especially with an IDE, such that "refactor this pile of tags into a function" is a one-click process.)

The useState hooks are a tiny bit clearer than the setState semantics. The effect hooks are less clear, but all told, the new mechanisms for handle global state and side effects better without Redux. (Redux is neat, but after working with it for years, I just have to conclude that in most cases it's just too much mental overhead compared to a more idiomatically Javascript solution.)

There's nothing wrong with continuing to use class-based components, but I think you'll find that everybody else is going to gradually deprecate it. The key facts about the work flow -- state to render function to surprisingly efficient DOM reconciliation -- remains the same.
Scaling Kapwing to 100k+ Projects a day
From my perspective it does apply. Please see my comment upthread: https://news.ycombinator.com/item?id=27439301. If there's something there you feel I haven't addressed, I'd be happy to hear what it is.
Given that Amjad seems particularly worried about people encroaching in this space, let me again say that nothing about Replit is unique, the use of Nix for Replit is literally an idea years past its prime. Nothing remotely unique.

Amjad, if your securing your moat via threats, you better look out.

To anyone else, go grab Theia. In about an hour you can get something better than Replit going, and if you combine with Nix/Guix, there's just no reason to deal with people that behave like Amjad.
Come Work at YC