skysight-inc/HackerNews huggingface dataset:
But that's precisely where I strongly disagree. Redux's problems do not come from a poor implementation of a state machine, but rather the interactions between state machines and stateful, non-state machine representations.

Again, Redux is the purest expression of a state machine possible in a general-purpose programming language (as opposed to a specialized one like TLA+). It maps one-to-one with the usual textbook definition (technically textbooks don't have a rigorous definition for state machines, but rather finite state machines, but usually by "state machine" we just mean you take a normal FSM and just relax the finite bit by introducing some infinite component into the overall state such as an arbitrarily long list). The store is the state, the actions are transitions, and the reducer is the state transition table.

Redux's infelicities come precisely from the fact that it needs to interact with things that are not modeled as state machines! Namely, interacting with black box children and the outside world (mostly sending stuff to the outside world, Redux comes with stuff out of the box to deal with just one-way inputs from the world). And Redux doesn't come with ways out of the box to deal with those so you need to layer more stuff to make it all play nicely together. But you need at some point to interact with them to work with the JS ecosystem so you need that stuff.

If you had state machines all the way down you don't need any particular patterns other than the fundamental state machine description! Especially with Typescript's structural types, everything just works (you just pull out chunks of your store into little stores and pull chunks of your big reducer out into little reducers, it's literally just cut-and-pasting chunks of your code and giving it a new name and making new state machines all the way down).

The friction comes from interacting with React, dealing with the outside world, and figuring out various decisions of what to do about data structures that the JS stdlib doesn't decide for you out of the box (e.g. what immutable library should one use). Even the choice of mutable vs immutable is something that is decoupled from Redux proper (it turns out for incidental reasons it's easier for type systems to properly scope local effects with immutable data structures than mutable ones, but that's more an artifact of Typescript than Redux, see e.g. Rust's type system for a counterexample).

If all of that was just more state machines (and the stdlib issues were taken care of) then Redux would be absolutely lovely.

And that's not just a pie-in-the-sky hypothetical. E.g. Elm is basically what Redux would be if everything was state machines and works great in all the places Redux doesn't (Elm's infelicities in turn are of a different variety that stem from some limitations of its type system to properly express some of the structural types you'd like state machines to have, in particular a lack of structural union types that often requires duplicating the state transition table in certain ways as you break a larger state machine down into smaller state machines).
>Only area where this whould be relevant i think is online multiplayer games.

That's the issue with augmented reality games like Pokemon Go.
People driving to see sights is really not the issue with cars that we have.
I'd call that at least fairly optimistic. We're working on technology, but it hasn't materialized yet. Even if it does materialize sooner rather than later, we have no particular guarantee the political will to utilize the technology will exist.

I'm still confused about the bear. How is a human not existing a danger to others? A human not existing is really only dangerous to the human race once it reaches some critical mass that will essentially prevent any new humans from existing. I don't see how this is at all analogous to unleashing a bear in a populated street. Each instance is inherently not dangerous by itself. You can't say that for the bear.

By that reasoning, why should we do anything to reduce green house gas production or any kind of pollution? We'll figure out how to remove it from the environment or make it otherwise non-harmful eventually. May as well go full steam ahead now in that case, right?

I also highly contest the notion that preventing a human from coming into existence is anything like removing an existing one. If you were forced to chose between killing somebody or destroying a viable embryo scheduled for implantation, would you seriously have all that much trouble deciding?
It's "just javascript" because if you want to modify anything and have it re-render, it's `let counter = 0; counter++`, not `const [counter, setCounter] = useState(0); setCounter(counter + 1); `. Of course there's template and all, but for regular logic, you don't have to fiddle around abstractions.
(Jornalista is Portuguese, you're looking for periodista)
yes. and to add to this, the fitness for use in some safety critical system, and we talk about functional safety here, is strictly regulated. functional safety requires process discipline at the system level, evidence based engineering and evidences for soundness of scrutiny, at the system level and then down to the components.

in that light it is a moral obligation to remind consumers of the technology about their obligations. The legalese may sound just evasive, and motivated by the us environment of litigations by stupid people, but seriously: fitness for use is am obligation of the systems engineer, not the provider of FOSS.

elisa.tech is a community to enable Linux in safety applications. even there, the responsibility is with the consumer of their work, they also just seek methods and inputs for system safety engineering, which, when used by a system safety engineer may lead to a certifiable, and then liability covered device. like an adas system powered by Linux.
Certainly, the FBI in the '60s and '70s would have been unlikely to be expanding much effort towards this situation. Though I think everyone here is assuming that intelligence agencies treat all of these public puzzles with the same degree of utmost seriousness.

Take the Taman Shud mystery- only one death, completely without context. Yet it's mentioned that military analysts took a shot at unravelling the mystery:

> In 1978, following a request from ABC-TV journalist Stuart Littlemore, Department of Defence cryptographers analysed the handwritten text. The cryptographers reported that it would be impossible to provide "a satisfactory answer": if the text were an encrypted message, its brevity meant that it had "insufficient symbols" from which a clear meaning could be extracted, and the text could be the "meaningless" product of a "disturbed mind".

https://en.wikipedia.org/wiki/Tamam_Shud_case

I don't think spies are any less interested in perplexing mysteries than the rest of the public. While I don't expect that an agency would throw all of their manpower at a case such as this, I could imagine individual analysts taking a stab at it on their own time. Maybe the organizations themselves might sponsor side projects as a means to test codebreaking techniques and glean lessons along in the process. I mean, why else does the NSA have a page on the Voynich Manuscript:

https://www.nsa.gov/news-features/declassified-documents/voy...

They even did an entire study on it:

https://archive.org/details/VoynichManuscriptAnElegantEnigma...

Serious agencies dive into less-than-serious studies into exotic or sensationalist topics all of the time. Sometimes for general interest, sometimes for good PR, sometimes simply because of bureaucratic waste. Why else do we hear about military studies of UFOs, from Project Blue Book to recent news stories? Given the enduring mystery of the Zodiac Killer, I can't imagine why some of these professionals- beyond the FBI even- might not have tried to crack it, themselves. And perhaps some have already succeeded.

Edit:

> There's no reason to believe that he'd write a message that would give himself up. Real life is not like the fable of Rumpelstiltskin where solving a riddle makes someone honor-bound to give themselves up.

Despite this, perhaps figuring out the message would've given some sort of psychological insight or contextual clues that could have helped investigators determine the identity of the killer.

Not to mention, your point is refuted retroactively by the case of the BTK Killer, whose taunting anonymous puzzles were his downfall. Though admittedly investigators identified him not by actually solving his puzzles, but by analyzing the medium they were conveyed in.
Oh man I'm glad I wasn't the only one!
> Relative to an absolute viewpoint [...]

Any yet this "absolute" viewpoint is never really absolute, but always relative to the authors current position in time – as if by coincidence.

EDIT: To clarify, when an author uses an exponential curve to make the "runaway" argument, they almost never justify why the current absolute value of the curve should have special significance over the absolute values at other points in time. For example, in forgotmypw17's original post, there's no explanation why the current status of free software is at a special threshold – or what "exponential curve" they're even talking about.
> Spotify is a big ask because google would have to port widevine (the web DRM.)

Spotify shouldn't be a problem [0][1] using librespot [2]. As for banking, I can't speak for all of Europe, but web apps are generally optimized for desktop use, apps have some convinient features, like scanning the QR code of a bill and pay it with one tap, instead of having to type in everything manually when it's on paper, or copy paste it from a PDF.

Additionally some banks require an app for 2FA for the web interface on PC too.

[0] https://github.com/kraxarn/spotify-qt
[1] https://github.com/xou816/spot
[2] https://github.com/librespot-org/librespot
Ask HN: Anti-vaccine statement by Geert Vanden Bossche?
What is your take on Dr. Geert Vanden Bossche's statement https://37b32f5a-6ed9-4d6d-b3e1-5ec648ad9ed9.filesusr.com/ugd/28d8fe_266039aeb27a4465988c37adec9cd1dc.pdf ?
The temperature effect on atmospheric circulation is called an inversion. Basically, air near the ground is normally warmer than that above it so rises buoyantly, mixing the atmosphere through convection. When the air near the ground is colder than the air above it (the gradient is "inverted") the air no longer rises, causing polluted air generated at the surface to linger. There are several circumstances that can lead to colder air at the surface than above it, including cold, cloud-free nights.
Gasoline doesn't just magically appear at the pump. Oil extraction has huge environmental costs too.
> 2. Defend your product against large organizations with the resources to take your software and improve and operate it cutting you out of the equation.

You don't/can't. That's what the megacorps want. They want the GPL, FSF and RMS gone so they can exploit all of the work done for free in open source communities.
What are the downsides or criticisms of Svelte? This whole thread is like a giant bandwagon. Typical of JS crowd. 3 years later, everyone is going to jump on the next one.
I don't think that's the case here, though - it has been reported that this may well be the first time it has happened in the canal's 150 year history.
Svelte gives us a host of possibilities because of it being compile time. Its the perfect UI language.

Think about it. You can write anything in the script part. Lets say you have a Go UI framework. Write Go code inside script tag and use the template to produce UI elements for TUI apps, for desktop apps without even working hard to manage state, manage UI element paradigms. The simple reactive style of programming can be used. Of course a different compiler can be used. But the possibilities are open. With React and stuff that's kind of difficult. You will eventually end up writing original Go code.

And currently you can compile Svelte components into React/Preact etc. Its not production quality. But its possible. (Svelte2TSX makes it possible)
This is nothing more than a continuation on the attach that FSF and RMS is getting these days.

How this thing got on the front page is amazing.

The techno-maoists like nothing more than destroy institutions and reputations.
I don't know about Chrome adblocking because I'm using Firefox on all my Android devices. I installed uBlock Origin and I'm using it to block elements with CSS rules (lots of annoying sticky headers and useless navigation bars.) Sometimes I use it to block scripts. My primary adblocker is Blockada which is a local VPN and blocks all ads in all apps. This means that usually no ads make their way to Firefox and I remove their empty spaces from pages with uBlock.

The shortcoming of using Blockada is that I can't use another VPN. I don't really need it yet, but if I would that could be a big problem.

I don't know why Google doesn't allow chaining VPNs. Maybe the UX would be too difficult on a phone, maybe it's a real edge case not worth spending money on, maybe it would be used only to block ads.
Gödel's Loophole
Perhaps I missed something, but if we are using brake pads even less because of regenerative braking in EVs, why do we need a new material for them?
So freedom respecting software is for people who can program or pay someone else to program for them. That's why there will never be widespread use of it?
When I had come to USA I had only heard about bald eagle and never seen one. San Diego Safari park had one caged bald eagle which had hurt its beak and wings so badly that it could only survive in Captivity.

It was a holy F** moment for me as the bird was damn majestic and lot larger and intimidating than what I would expect from a bird.

Garuda - the hindi word for Eagle, is often described as the vehicle of Lord Vishnu, one of the powerful Hindu Gods. Bald Eagle would be perfect match for that job.
Do you know Rockin1000 [0]?

In 2015, a thousand of (mostly italian) musicians played simultaneously "Learn to Flight" as a way to ask the Foo Fighters to visit the town of Cesena, Italy. Dave Grohl then agreed to have their last tour date in Cesena :)

[0] https://youtu.be/JozAmXo2bDE
> A developer can absolutely make an agreement in which he takes on the liability. He's going to need to be paid to take that liability on, to both spend the time to eliminate defects, but also to purchase insurance so that he isn't bankrupted when a defect inevitably gets through and causes harm.

Hmm... I hadn't though about the implications of this before. Is this a solution to the mythical funding balance the industry is failing to achieve? Enterprise software already operates like this. What if e.g. github reframed its project sponsorship model as something that involved getting maintainers setup with liability insurance and the ability to offer sponsors warranty and liability for their software.

My concern with the rust ecosystem right now is that it goes the way of node and projects just get littered with endless libraries that were fresh and hot at one point in time. Often times you open issues and it takes days or weeks to get a response if at all because the maintainers have moved on.

I'd be super interested in only using dependencies where I could subscribe to liability and warranty service after I've tried them out and they're want I'm going to roll with. And you would even potentially see interesting things like "pure" chains where all software used is covered by somebody.

This model would also have the interesting effect of promoting software design and language selection that results in "easier to warrant" not just "does the job" and maintainers that do a better job at writing good software would bubble to the top since their liability insurance premiums would stay cheap. If you write too much crappy software, at some point it becomes unaffordable and you go work for Facebook (it's a joke! you get the point).
CorelDRAW Graphics Suite Crack v23.0.0.363 and Key (2021)
A lot of Bach (and "classical" music in general) may feel slow, but is actually quite fast if you measure the amount of notes played per minute. But this is something I only realized when I started to learn guitar and tried playing some pieces.

Anyway, what I really like about Bach is how much many of his compositions just swing. He was a big fan of the canon, where a melody is played simultaneously by several voices/instruments, but with an offset and counterpoints. He uses this to create what to me are beautiful textures and great rhythm.
The “relativeness” comes from time, not from us. Judging the curve today, the past looks flat and the future looks steep. In 5 years the same will be true: today will seem flat and the future will seem steep — that’s the point of OP showing both of those ranges. It is this relative perspective that precisely creates the illusion of a runaway point, an “absolute” perspective gives you the fractal understanding that the graph is the same at every dimension.
I’m sorry. I really like coffee.
What Adobe isn’t telling you about Photoshop for M1 Macs
> During spraying process, high-aspect-ratio carbon nanotubes are interweaved into lithium vanadium phosphate

As soon as you read 'nanotubes' you know its not a relevant competitive chemistry.

This is a non-commercial chemistry that is not anywhere close to being able to be used in the incredibly high volume car market. VW was talking about chemistry that are already produced at scale and already being validated in batteries, so they could be in mass-market cars in this decade.

But it sounds nice to write research paper.

This is honestly the first time I have heard of Vanadium lithium phosphate batteries, usually you hear of Vanadium in flow batteries. As far as I know, most people consider these vanadium flow batteries as basically non-competitive already.
I'm not a fan of this piece, which seems sloppy and superficial. Here is an example:

"Every debt product — sovereign, emerging markets, financial and non-financial corporate, housing, consumer, student, and health care — is at or near all-time highs. Total debt measured 150% of US GDP in 1980; today it hovers at 400%. During the worst stages of the Great Depression it was 300%."

The first warning sign is that the source is a seekingAlpha blog. But the second big red flag are the words "total debt", which is a meaningless statement. Consider two scenarios:

Scenario A: I borrow from a bank to buy a house. I now have an asset (house) and a liability (mortgage debt). The bank that lent me the money now has an asset (my note) and a liability (the deposit it created for me). Whoever I bought the house from with the deposit given to me by the bank now holds the bank deposit as an asset.

Scenario B: I borrow from the credit markets by selling a bond (or alternately, I borrow from a bank and the bank sells off my note as a mortgage bond). I have the same asset (house), but a different liability (the bond). Someone else in the credit markets has my bond.

Now if the amount borrowed was X, according to the calculations of "total debt", In scenario A, the total debt is 2X, because they are double counting the liability of the bank as well as my liability. In scenario B, the total debt is just X because the bank is no longer involved and it's a credit relationship between two members of the non-financial sector.

So whenever you want to count all debt, you need to count all debt of the non-financial sector, or count all debt in the financial sector, but you can't add these together to get some fantastical "total debt", as that is double counting.
People who talk about "total debt" do not know this and their opinions about Z.1 data should be treated with great skepticism.

Another thing to look at is interest rates. The idea that you would only compare debt and income without taking interest rates into account is the third red flag. As the ability to service debt is not just a function of your total income but also of the rate you are paying. Again, people who have even a basic awareness of what debt is know that you can't just look at debt/income. When someone makes a comparison of debt/income in which there are two very different interest rate regimes, well you shouldn't subscribe to their newsletter either.
> Are you insinuating that all Muslims support child marriage? Because it certainly seems like you are.

Yes I am. For a Muslim to not support what is in the Koran is apostasy, as the Koran is the perfect word according to them.

Mohammed married a 6 yo, and consummated the marriage at 9 yo. As the "perfect example of a man", Muslims today still copy that. When laws are passed against that, those lawmakers can expect a much-shortened lifespan.

You are part of the problem for commenting without knowing that.
I'd be quite afraid to go in many US places. And many US places experience some poverty that's the stuff of nightmares.

I think it's about time to stop calling the #1 world economy, #1 world manufacturer, a country that's expanding it's sphere of influence across the globe (see Africa) plus having a growing in well equipped military as 'underdeveloped'.
> I know I, and most developers I know, dropped Backbone/Knockout/whatever instantly to use React because it was so obviously better.

You skipped a huge step. There was angular before react. Which was horribly bloated and over complicated. People wanted something simpler. React, with it's facebook clout won in the end.
You are talking about React here, not Frontend in general. Angular has different concepts. Steep at the beginning, but in my point of view easier in the long term with a stable API.

I agree. Frontend is tough, but so is development. ;)
"The Palace of Westminster, the medieval royal palace used as the home of the British parliament, was largely destroyed by fire on 16 October 1834.

The blaze was caused by the burning of small wooden tally sticks which had been used as part of the accounting procedures of the Exchequer until 1826. The sticks were disposed of carelessly in the two furnaces under the House of Lords, which caused a chimney fire in the two flues that ran under the floor of the Lords' chamber and up through the walls."

Since medieval times the Exchequer had used tally sticks, pieces of carved, notched wood, normally willow, as part of their accounting procedures.

The parliamentary historian Caroline Shenton has described the tally sticks as "roughly as long as the span of an index finger and thumb".

These sticks were split in two so that the two sides to an agreement had a record of the situation. Once the purpose of each tally had come to an end, they were routinely destroyed.By the end of the eighteenth century the usefulness of the tally system had likewise come to an end, and a 1782 Act of Parliament stated that all records should be on paper, not tallies.

The novelist Charles Dickens, in a speech to the Administrative Reform Association, described the retention of the tallies for so long as an "obstinate adherence to an obsolete custom"; he also mocked the bureaucratic steps needed to implement change from wood to paper. He said that "all the red tape in the country grew redder at the bare mention of this bold and original conception."

By the time the replacement process had finished there were two cart-loads of old tally sticks awaiting disposal"

Burning of Parliament

https://en.wikipedia.org/wiki/Burning_of_Parliament
That's quiet an extremist statement. There's quiet a few ticks on the continium from nuclear fallout bunker to a few months of food and water.
Coin could be one the Biggest ICO of 2021
Whats even better than planning for costly buffers that are unused most of the time is having a system that can adapt to unplanned changes in circumstances. So far I don't see that this isn't the case, but time will tell.
I use the code-server project just fine, and it has worked great for me.

Seems like the white screen issue is a common problem. Have you tried something like this? https://github.com/cdr/code-server/issues/1223#issuecomment-...
Would be interesting to also see top causes of those deaths