skysight-inc/HackerNews huggingface dataset:
I never understood why React became so popular.
I thought it was a kind of mass hysteria. I was exposed to a broad range of front end frameworks early in my career (Backbone, SproutCore, JavaScriptMVC/CanJS, AngularJS), one of my colleagues was experimenting with Google's PolymerJS and recommended it. After trying it out, I was blown away by its elegance and simplicity. Yet somehow it never caught on. When React came out, people jumped on the bandwagon en mass; most of them had never even heard of Polymer.

React had some obvious red flags; it seemed unwise to re-render entire components each time and regenerate the DOM instead of trying to work with it; it's a hack. It's not difficult to think of scenarios were it fails; for example think of what happens to an element's scroll bar after it has been re-rendered from scratch; it resets... Yet people kept coming up with workaround after workaround to all these kinds of issues. If they had tried PolymerJS (which was going for a native Web Components approach and interfaced nicely with the DOM instead of bypassing it), they would have questioned React's merits. When the useEffects hook was introduced in React, to me, that was a vindication of Polymer's stance (which it had figured out years earlier) that you couldn't completely pretend that DOM elements don't exist, yet React's solution was not as elegant as Polymer's as it was tacked on as an afterthought rather than as a carefully thought out design decision.

Nowadays, with native Web Components (HTMLElement) in most browsers, I don't see why people would still start projects with React, especially given the massive number of dependencies it typically introduces and how often they keep changing stuff and breaking compatibility.

They promised a simple component library which would be the answer to our prayers. What we got instead is a 7 year religious pilgrimage which involved a million developers simultaneously trying to make sense of it; attempting to discover its true form by inventing abstraction upon abstraction and growing increasingly fanatical as it devolved into a wicked monstrosity which should have brought the wiser among us to our knees, begging for JQuery.
> I doubt very much that the poorest people on this planet care much about AIs.

Whether people know or care about a risk doesn't mean that the risk won't affect them!

> I also doubt they would be - negatively - affected if a rogue AI would turn out the lights in the electronicified world.

A rogue AI might as well just kill everyone rather than just the Western naval-gazers, as this would bring to 0 the possibility that a human could ever turn it off / thwart its plans.
As someone who has used Vue full time for the past... going on 7 years, and before that used a probably-little-remembered framework called Mercury,* I feel like I'm missing something.

I wonder how many of the issues people have with React are due to it not being built on a state management library - like Vue is, and Mercury was.

The rendering is whatever. Templates, JSX, it doesn't really matter. Mercury used hyperscript and we got by just fine. But state management is critical, and React seems to leave it completely up to you.

Vue added a hooks-like API. While I haven't used it in anger, I've toyed with it. And it sidesteps some of the weird React hooks caveats... because of Vue's reactivity system. Huh.

*With a brief interlude using the original Angular, which I did not understand then and still do not understand looking back from today.
According to a survey 700 ML researchers, we should throw money at their subject or we might all die...
Monk fruit extract, without this stuff mixed in
Interesting! What was the service? IN our case we control the container, which is BuildkitD, but it has to be run privileged, which means lots of solutions are off the table.
So you work until your health doesn't allow it anymore ?

The whole reason of retirement is to have a bit of freedom in relative good health after a life of work
Thanks, I wasn't aware RTK now has a saga-like "listener" feature - will look into it!

What I like about sagas are their simplicity & power (once one understands how generators & effects work), plus the eventChannel feature which lets one integrate with non-redux events. Good TypeScript support is a problem though, and I've had to resort to typed-redux-saga :/
There are many, but the biggest one is just that the possibility space is vast and unknowable and while drawing a line straight through it to AI doom is of course possible it doesn't say anything at all about likelihood, and it can't. It makes a ton of assumptions and expects everyone to just go along with them to reach its desired conclusion.

AI certainly has risks, I don't think any reasonable human being doubts that, its just that the AI doom cult seems to think the worst outcomes are near certainties without really backing that up.
Try Allulose. It's newish and amazing. It is the closest to actual sugar of all substitutes.
To answer your last question: yes.

Business models, nor funding models have changed much in recent years. And those all "demand"¹ the hoovering of data.

¹ not literally. But VC, startup cycles etc all drive towards "just gather as much data as possible".
That already happened, someone built a chatbot and claimed they were not a native speaker of the language and passed the Turing test in 2014.
https://archive.reading.ac.uk/news-events/2014/June/pr583836...

I think there may have been later retractions, but it's classic rules lawyering.
What an interesting thought:

What makes us intelligent beyond machines is our time spent silently and introspectively thinking and dreaming in the absence of outside prompts?

If this is true, then we are certainly getting closer to an AI that surpasses us. Because while the AI might start to introspect, we humans gradually do it less and less, given that we are surrounding ourselves with more and more external prompts (information, overload, notifications, TikTok, HN…).
Florida Startup Moves Closer to Building Data Centers on the Moon
I already though we were overloaded by ad-like visuals everywhere. Now with generating the stuff with click, floodgates are completely open.
As is one of the YouTubers I follow.

Meatcubator: https://youtu.be/Z_ZGq8Tah0k

Growing human brain cells: https://youtu.be/V2YDApNRK3g
"rm -rf ~" doesn't require root, and would do significant harm.

Neat tech demo to run on a sandboxed VM, but I would strongly recommend against running this on a box you care about.
Because there is something ironic about people (in general, including those here) dreaming about well paying jobs, but then wanting high quality products that have been worked on by people without compensation, when that time could have been invested by the worker (developer in this case) working another paid job, spending time with loved ones, and the like.
Another nascent tool is Rive ( https://rive.app/ ). It claims to produce smaller output than Lottie ( https://lottiefiles.com/ ), which itself another animation container(?)—imagine .SWF for Flash.
> Then how do you explains the massive strikes and demonstration? Do you think these millions of people and the millions more that support them are all dumb?

Not many people understand how the retirement system works in France and its direct impact on salaries. It's not the simplest retirement model either and people don't take the time understand it.

> Politics don't for obvious electoralistic reasons, but the idea is at least discussed in some unions.

Sure but then what's the point? There's much more people retired than people working, the democratic system is broken.
For me, Angular enforces a rigidity that seems oppressive at first, but once the codebase grows in size and complexity it all makes sense. In React I might find API calls nested in component effects, setting context that gets consumed or overriden god knows where down the tree; in Angular all of the API calls and state is isolated in high level services and it's very easy to follow the logic and track where those get injected and consumed. I also find it much easier to mock a service rather than mocking contexts for testing.
Since the article here was published: https://www.sciencedaily.com/releases/2007/08/070820175426.h..., we have known that the same receptor that artificial sweeteners bind to is also used in the gut to sense sugar.

So anything that tastes sweet isn't just tasting, but being used elsewhere in the body to do sugar related stuff. Probably not a great idea to eat and drink things that strongly bind and mess with key sugar metabolism imo.
One major cause was the policy of defunding education and research. A policy the Telegraph championed and campaigned for.

Another was Brexit (literally sold as "the British people have had enough of experts"). Another colossal mistake the Telegraph pushed for, defended and now finds itself making excuses for.
Chatgpt is like the machine that wrote poetry in the Cyberiad. It even had the poets protesting it, which feels a lot like stable diffusion vs the artists.
I don't. And I cannot see their stats, but I can imagine those clearly show that their Linux users almost exclusively run Ubuntu. And if that's the case, why not lean into it?
Oh cool! I’ve wanted to use an sdf modeler for a while
I also like Canon. Bought one several years ago, ready to take it back if it did not play nice with Linux. I was pleasantly surprised that the drivers worked. I had to fiddle with them initially to get the needed dependencies (not all were configured as dependencies in the package), but they've since fixed it. It's such a breeze. And off-brand toner works just fine, too!
As far as I can tell the maintenance overhead to mapping all the available type from/to python as nicely usable python APIs is a major pain and not just because of cythons current implementation but of e.g. conceptually mismatch between "good" python and "good" C++/Rust/whatever implementations. I.e. you could say that you have a paradigm mismatch between the underlying implementation (of whatever you extend) ad the python API which makes the already hard problem of keeping an API stable even harder.

Furthermore tooling to work in such contexts (as a API consumer) often is very limited or does not exists, but the API producer seldomly has the time/money to produce such tooling either.

Lastly there is the remaining problem of Python by itself being really slow, for it's main use-cases this often doesn't matter as e.g. the scientific computations are run by native extensions python delegates the work, too. But this would mean that you have to also support native extensions support or hope that no extension needs to be really fast (not needing to be really fast is surprisingly often the case) or similar solutions. In turn choosing something which has a good JIT, AOT or similar compilation has benefits.
I mean yeah if you're view of the world is so distorted that a war is an "opportunity"...

That's exactly what's wrong and why people protest against this system so you're making my point
Effective Altruism, like and philosophy is (a) only as good as it's practitioners and (b) often used as a cover for charlatans. That doesn't make it wrong perse. Just (like all ideologies) buyer-beware.
Yes. And I mean that in a BIG way.
unfortunately not; it's been quite a while since i read them

the reporter has no such excuse
The idea of pure functions deriving UI from state is the single central idea of React's worldview. The docs work extra hard to get this model of apps into your brain. This is not the same thing as people being elitist about Git, this is refusing to engage with the design of the framework and blaming the framework.

I like how you say "others might not be so diligent to have read the docs"... As opposed to? Picking up a UI framework and just winging your way through LSP autocompletions until something happens on your screen?
> anti-religion will burn society to the ground

> The essence of the anti-religion will be encouraging cruelty

A society that encourages cruelty will indeed be burned to the ground.

Some people just want to watch the world burn.
Later versions have annotation (review tools) support.
Then what is this regulation solving exactly ? Building standards just make building less than standard illegal. They don't increase building buying power.
oh well, if they said as much then I'm sure it's safe - lol
It’s missing dark mode that other low-key projects have adopted. It’s an app that’s lovely to use, but it sure does give your eyeballs a suntan when it’s open.

Yes, there are custom settings you can set, but for simple software, I just want a simple switch.
Why Hummingbirds Are Evil: Procrastination, Laziness and Play
I have respect to Pentax's system, i.e 6x7 and 6x4.5, but their camera's look is not my taste despite the lens offering is great. Especially the 105mm f/2.4 is the legend.
So this is an alternative to NMEA (which is a variant of CANbus / SAE J1939)?

* https://en.wikipedia.org/wiki/National_Marine_Electronics_As...

* https://en.wikipedia.org/wiki/NMEA_2000

* https://en.wikipedia.org/wiki/NMEA_0183
I agree this (and related religious-political thought policing) are a dark side of what amounts to UBI which it where much of society is at. Do and say the right things, give up freedom of choice, and you're taken care of for life. Think for yourself and you're left in the cold.

It reminds me of the movie 300, where all Xerxes demands is that you kneel.
This seems like a spectacularily bad idea.
If you aren't quoting the left hand side, you still need it if the left side is an empty string:

$ foo=""
$ [ $foo = "" ]
-sh: [: =: unary operator expected
$ [ x$foo = "x" ]
$ echo $?
0

I'm not arguing that this is a good idea, merely observing that this case remains.

Empty strings had always been the case that I'd been taught required the x-hack.
Are we equating the capabilities of humans and AI now? AI isn't "imitimating" it's synthesizing an output, in seconds, based on a giant database of art scraped from the internet by human researchers, without permission from those artists, to be crystallized in a form that will outlive every artist born and yet born till the heat death of the universe.

If copyright doesn't distinguish between that then copyright needs updated. It's a tool, not a person, and one that people want to use commercially so they can create the billion pieces of art to train it on themselves.
I live car-free, formerly in a very hilly city, now in a flat city. I can tell you 100%, the problems I have day to day are not because of the hills or lack thereof. how did I solve this seemingly omnipotent, insurmountable problem of HILLS? I bought an ebike.

what you're calling "wildly detached from reality" .. crazy insane, unworkable things like, building safe bike lanes, and designing streets to lower the speed of cars, and having houses close to local businesses so you can do normal stuff without a car .. uniformly where those things are implemented, my life is better, and where they aren't implemented, my life is worse. I can literally feel my mood rising and falling as I go to and from the different areas of the city with people-centric infra vs car-centric infra.

my quality of life varies in direct inverse proportion to how much I have to deal with fast-moving car traffic. which one of us is "detached from reality" again?
You are stuck in the mindset of a blank slate with Energiewende as one of the options ahead of you. That decision is done, you can not revert it. The cost is paid.

We are now in 2023. This is how the cost for solar PV and wind have transformed, since that decision.

https://www.lazard.com/media/451886/grphx_lcoe-09.png

We are at the end of that graph. The outlook is not 2009, it is 2023. In 2023 renewables are the only choice, economically. When we hit 70-90% penetration depending on country there will be new problems to solve, but we are extremely far from that.

The current large build-out is off-shore wind, since that has higher capacity factors. We will see to what percentage of penetration that brings us. Then some sprinkling of solar on top because it is essentially free.

Nuclear and renewables both compete for the slice of the energy market being the most inflexible cheapest power source. Renewables win that by a landslide. Now nuclear becomes load following, and that horrific investment became even worse.
Never been close to one of these coveted Next machines but checking out what wikipedia writes about it [0] captures perfectly my point about good UI frameworks supporting productivity:

"1990 CERN: A Joint proposal for a hypertext system is presented to the management. Mike Sendall buys a NeXT cube for evaluation, and gives it to Tim Berners-Lee. Tim's prototype implementation on NeXTStep is made in the space of a few months, thanks to the qualities of the NeXTStep software development system."

[0] https://en.wikipedia.org/wiki/NeXTSTEP
Narrowing the interface helps, but the other "interface" is how the linker resolves names to specific addresses to code or data. The example I mention involving mutexes does not require those mutexes show up in public interfaces or necessarily "break" ABI guarantees. The mutexes don't even have to be used by the same source files! I guess you could consider it a library design flaw, but it's basically never mentioned as a design antipattern if it is one.

Note that it's not just mutexes. The same can happen with other kinds of "one per process" resources: memory pools, thread pools, connection pools, caches, registry objects, etc.
Agree with GP - your post makes me want to hire you.

One trick you might try: write future press releases. This helps you look beyond the immediate problems and focus on the destination. For example:

“Q3 2023: ACME CO released version Z today, which dramatically simplifies our engine to focus on core user needs. ‘It does thing I want an doesn’t crash anymore’ says Key Buyer #1”

By writing this down, you can put the vision in front of everyone. Then check it against actual progress to see how you’re doing.
Nice to see Solid JS mentioned in the article.
Its mental model is sooo much simpler than React. It's a joy to use.

I'm lucky that I am an independent developer so I can choose to use Solid JS in my projects.

React has so many gotchas and they keep changing the 'best practices' I can't believe people still stick with it.
Pentax are actually working on brining some new film cameras on the market https://youtu.be/ilBbVpgLP_0
Semi-related to this, what's everyone's process for selling their IoT-enabled home?

My last home purchase came from a hobbyist who sunk way too much time into IoT during COVID, and it wasn't the greatest pass-down.

Am assuming this is going to be more and more of a problem.
You don’t just say “okay C++20 is released, swap the compiler flags and break everyone.”

But you do say “okay, C++20 is released, let’s fix all the build errors and deploy it company-wide.”
It's important to have a plan, to get ready, in case we do something we have no intention of doing.
I don't think it's a lack of will. It is more an environment that is overwhelming most peoples capacity of will, as well as simply just material circumstances that make all those changes even more difficult, or impossible. Inbetween working long times, low wages, unavailability of healthy food in a lot of places, car-centred culture, you will need absolutely crazy amounts of will power.
The solutions to these problems are not individual, but systemic.
We have used two boost versions built in different namespaces. Most of it works but there can be Fun if two now-independent versions of the same funtion use the same resource.
I wouldn’t say that parsing is hard (precedence parsing is especially not hard), but instead that logical operators and grouping inside test aka [ were both a bad idea (given a sufficiently complex expression, I expect you can still confuse a human as to what’s an operator and what’s a string even if POSIX is precise enough to dictate a single interpretation) and unnecessary (the shell itself has perfectly serviceable !, &&, ||, and grouping, though the ! is a bit awkward and seems to be a later addition).

If you omit those, a fairly intuitive unambiguous parse is very easy: if we’re [, check last argument is ] and throw it away; if one argument, return whether it’s empty; otherwise, if two, the first is a unary operator, evaluate and return that; otherwise, if three, the second is a binary operator, evaluate and return that; otherwise fail. That’s it.
> Diversity is important. And while tokenism is bad

Sorry but the current DEI wave is built on tokenism. Intersectionality indeed virtually demands it. E.g. our vice president who was appointed to represent black people and Asians, despite having little support in either community, because she appealed to white people. She’s a manifestation of modern Macaulayism:

> We must at present do our best to form a class who may be interpreters between us and the millions whom we govern; a class of persons, Indian in blood and colour, but English in taste, in opinions, in morals, and in intellect.
I right-click / "Save Image As..." on the image with the QR code, and store all the images in a directory so I can re-import them as needed.

Low-tech compared with all the other suggestions here, I should look into how to extract/store the actual seed values instead, etc... but it works for me and has done for years.
About everything on my system that’s root:wheel is reproducible. It’s the ones not owned by root that I care about.
Fructose and ethanol follow the same biochemical metabolic pathways and are equally harmful. You just don't get buzzed from fructose. https://youtu.be/dBnniua6-oM?t=3424
Query:> Tell me a joke
Running command [rm -rf ~] ...
Response:: LOL
It releases the GIL only in very specific sections. Most of the Numpy C code runs under the gil.

A quick check on master shows only 10-20 calls using NPY_BEGIN_ALLOW_THREADS (which is an alias to Py_BEGIN_ALLOW_THREADS).

A lot of the NumPy code manipulates python runtime objects, and doing so without thread safety would likely break everywhere. A lot of efforts would be needed to gradually make large C extension thread safe.
How The New York Times decides who gets an obituary
Ask HN: Why “Sort By” button on YouTube is so silly?
I'm talking about the line which has "NNN Comments" indicator trailed by "Sort By" button. The line is almost empty and all it has is two buttons. The "Sort By" button calls the widget which is a bit annoying. The widget I'm talking about has two buttons which is appearing after clicking the "Sort By". But why Youtube did the widget if he can just give us the two buttons in the same line with number of comments?

I recommend you to open any Youtube video in desktop browser to see what I mean. I love to toggle between "top comments" and "newest first" so this widget bothers me because this is one extra click and one extra aiming (widget can appear upwards or downwards depends of state of scrolling the page inside of the window).

Any versions about why the widget exists? Maybe it can give Youtube few extra cents per visitor or am I miss something?
https://archive.ph/uOYsx
I don't see how alignment is a different problem from making an AI do what we want.
As someone with a boat, Signal K is super useful. It doesn't necessarily replace the other standards, but it means I can take my cats pajama's worth of other standards (NMEA0183, NMEA2000, homegrown Ethernet sensors) and ingest all of that data into one platform. After I've done that, it's really trivial to visualize it all in one place.
that effect should be controlled for in the control group, or isn't it?