skysight-inc/HackerNews huggingface dataset:
Gopher, Gemini, and https://wiby.me and https://search.marginalia.nu are still alive.

Usenet, too.

gopher intro: gopher://magical.fish and gopher://sdf.org

gemini intro: gemini://gemini.geminispace.info

More sites:

gopher://1436.ninja

gopher://adamsgaard.dk

gopher://bay.parazy.de:666/7/q.dcgi?

gopher://bitreich.org

gopher://bitreich.org/9/radio/listen

gopher://box.matto.nl

gopher://gopher.erb.pw/1/roman

gopher://gopher.icu

gopher://gopher.viste.fr

gopher://i-logout.cz

gopher://i-logout.cz/1/bongusta

gopher://i-logout.cz:70/1/bongusta/

gopher://katolaz.net:70/1

gopher://magical.fish

gopher://medialab.freaknet.org

gopher://ozz.ddns.net/1/

gopher://republic.circumlunar.space

gopher://sdf.org

gopher://sdf.org/1/users/dbucklin

gopher://sdf.org:70/1/users/nm03

gopher://texto-plano.xyz

gopher://typed-hole.org

gopher://uninformativ.de

gopher://zaibatsu.circumlunar.space

Usenet newsgrousps:

alt.2600

alt.2600.hackers

alt.2600.hope

alt.2600.hope.announce

alt.anonymous

alt.ascii-art

alt.comp.linux

alt.comp.os.linux

alt.computer.workshop

alt.culture.usenet

alt.cybergoth

alt.cyberpunk

alt.cyberpunk.movement

alt.cypherpunks

alt.fan.usenet

alt.folklore.computers

alt.linux

alt.os.linux

alt.os.linux.slackware

alt.privacy

alt.privacy.anon-server

alt.startrek

alt.sys.pdp10

alt.usenet

comp.arch

comp.infosystems.gemini

comp.infosystems.gopher

comp.lang.c

comp.lang.c.moderated

comp.lang.misc

comp.lang.perl

comp.lang.perl.announce

comp.lang.perl.faq

comp.lang.perl.misc

comp.lang.perl.moderated

comp.lang.perl.modules

comp.lang.perl.tk

comp.lang.scheme

comp.misc

comp.mobile.android

comp.mobile.android.misc

comp.mobile.misc

comp.os.cpm

comp.os.linux.misc

comp.risks

comp.unix.admin

comp.unix.misc

comp.unix.programmer

comp.unix.questions

comp.unix.shell

es.comp.hackers

es.comp.os.linux.anuncios

es.comp.os.linux.instalacion

es.comp.os.linux.misc

es.comp.os.linux.programacion

es.comp.os.linux.redes

hispagatos.chat

hispagatos.comunicados

hispagatos.talk

news.admin.moderation

news.announce.important

news.announce.newgroups

news.announce.newsgroups

news.groups

news.groups.proposals

news.software.nntp

rec.ars.movies.current-films

rec.ars.sf.tv

rec.ars.sf.written

rec.arts.int-fiction

rec.games.int-fiction

rec.games.roguelike.nethack

rec.radio.amateur.antenna

rec.radio.amateur.boatanchors

rec.radio.amateur.equipment

rec.radio.amateur.homebrew

rec.radio.amateur.misc

rec.radio.amateur.moderated

rec.radio.amateur.policy

rec.radio.amateur.space

rec.radio.info

rec.radio.shortwave

rocksolid.feeds

rocksolid.shared.i2p

sci.anthropology.paleo

sci.astro

sci.electronics.design

sci.electronics.repair

sci.environment

sci.logic

sci.math

sci.physics.relativity

sci.physics.research

talk.environment

talk.origins
The React team is testing out a compiler time approach to useMemo instead.
this is IBM firing its guns straight at liberty minded software

here come the rent seekers: soon enough we will have to pay per character we type. this may seem exaggerated and I really really do hope it stays a gross exaggeration and never actually actually happens.

nonetheless, the trends are here and this is part of them; and we all knew it was a merely matter of time before IBM started to destroy what redhat once was and turned it into more IBM

after a while of starving this project, some 'visionary business founder' is gonna come up with some sort of subscription service to use this software.
It's fine to work with higher layers of abstraction, but you should get some value out of it. What I think happened is that React just removed some work from lower layers and created even more work at a higher abstraction layer.

I would say that React gives you more work in terms of cognitive load and also in terms of development time if you look at it on a medium to long time-frame.
You don't need any of it. You can write vanilla JS, using ES6 classes, as web components and be done with the whole front-end framework game. All you need for data-binding is an Observable of some kind that can loop through listeners for events and call their handler. Component classes all have a render function so that React kids feel at home. Those components are registered using CustomElementRegistry.define [1]. Tools like vite help roll up all that code and styles into a minified bundle but doesn't include all the crap that these "modern" frameworks add. Take this from someone who has been writing web sites since 1996. You don't need any of those frameworks unless you're looking to give away control of your product to the roadmap of the framework or need to hire a bunch of people to accomplish something quickly and all they know is React.

[1] https://developer.mozilla.org/en-US/docs/Web/API/CustomEleme...
> to write is different from to rewrite

Only if you use dictionary meanings of words. Otherwise it really is not different. 99.99% of all meaningful code is not gotten right on the first try. As said above, you have to iterate on it.

> I'm referring to the fact that code can be made into libraries, or APIs if you're so keen on collecting rent

Name one library -- that is NOT just a network client for a paid SaaS service -- and then maybe I'll understand what point you're trying to make. And even if you find one, they are a vanishingly small, undetectable, minority.
In the 70s one family had one working member supporting the whole family, currently it's becoming increasingly common for one person to hold multiple jobs and their spouse too. Multiple states are voting back child labor, literally, so add those jobs too, to the count. Working children. The job count is a BS metric at this point and doesn't reflect the quality of the jobs, or the quality of life. It means nothing.

Also "9 months" is kinda ridiculous to expect to see the long-term effects of AI. AI may be evolving fast, and it is, but business, laws, healthcare, regulatory agencies and so on are held back by gigantic inertia and some real safety cocnerns. It is still humans who have to integrate AI in their human processes, so the first few iterations will be slow and cautious to occur (after that... eventually AIs will run systems made by AIs so change will accelerate). For example, a startup tried to offer an "AI lawyer app" for traffic tickets, and lawyers sued the startup. Hollywood is starting to use AI as well, and writers and actors went to strike.

Obviously things like that will hold AI back for a while. But not forever. AI is inevitable.
If I'd come here in when React was the new hotness and criticised it, I'm pretty sure I would have been shouted down.

In the meantime this one site I worked on, which used Java for server side rendering¹ with a bit of JQuery and custom scripts is still going strong.

1: It's ridiculous to hear JS people say how awesome server side rending is when basically every other language used for the web was server side, sometimes decades before it.
Microsoft Windows has all the pieces already to actually make this happen right now. AD, Group Policy, device lock down policies, "S Mode", etc.

To be honest, what I think they lack is straightforward licensing in order to run an organization with these tools with high availability.
> My experience with MobX and the greater observable-industrial-signal-complex is that accidental loopiness very much can and does still happen. I have seen codebases with complex MobX computed-changes-graphs that senior engineers were clever enough to write but not to debug. And I was not aware of tooling which helped keep these graphs in line.

My experience is completely the opposite. I've worked on large, complex interactive editors writtein in MobX and its been pleasently easy to reason about. Some tooling is built into the framework (cycle detection, strict mode). The design guides you towards making the right choices (prefer computed over autorun, etc) and makes those choices easy to use.

And unfortunately, with useState, useMemo and useEffect you can make the same cyclic dependency spaghetti (e.g. useEffect can easily setState). Unlike with MobX however, everything is harder.
The reason to prefer kotlin coroutines is exactly the reason to ditch reactive for virtual threads.

The only difference is virtual threads have platform support which means even better stack traces and no need to decorate your method.

So yup, agree.
This was the part that intrigued me. After years of silent begging to PyTorch to support ROCm, suddenly models in general supporting so many different platforms feels overwhelming, and really good.

I'm crediting llama.cpp of all things for being the boost to really up the ante on open source model compilation.

Whatever it is, at least, many of these open source things feel like they just 'happen', as an eventuality, but in order for that to happen it takes a lot of work from a lot of people! Really happy to see the dream of this particular kind of democratization opening widely! :)
What makes scrolling on this page so sluggish? (FF mobile)
I’d read the author’s argument as being, at least narrowly defined for data workers, that this will _not_ happen. Which I think is probably actually generally correct; if data work is cheaper you will do more of it, so, say, a 50% efficiency gain for data workers will not generally mean that you want half the data workers.

This has arguably _already happened_; I’d be reasonably confident that there are more people working with data now than there were 100 years ago when the business was rather more filing-cabinet-oriented, say.
The problem that hooks solve really nicely is when you want per-component state, but you duplicated versions of that state (and surrounding logic) in different components. With class-based React components you had to use things like higher order components, or manually add the state properties into each component. With hooks this is all neatly abstracted away.

You don't always need this. Sometimes your business logic can just be a pure function. But where you do (and IME this is quite common), hooks are super nice.
Based on reviews I've seen, the Reolink doorbell camera seems to be the only commercial option that fits the author's requirements. It works locally and can be integrated into Home Assistant. It does however require a separate app for the intercom but the author's homegrown solution does not seem to provide any audio communication and there doesn't seem to be a way to have two-way audio in Home Assistant directly, at least not via the camera protocol.
On mobile, a quick test didn't even look at where the link pointed..... Because all links on twitter are t.co aren't they? Weird you think any links aren't t.co. It's how they track analytics on everything

No buzzwords there, just suspicion there's something else underlying with various technologies that are in play even on a 'simple' link click
It's interesting that this pretty much codifies the 'rich people have it easier in court' phenomenon, if 'being rich' is something that you can use in your defense no matter what the crime then that's an end run around justice. The discrepancy when dealing with rich vs poor in court is already tremendous, this acts like a force multiplier. I'd like to see that same judge looking at someone who is poor to give poverty as a defense being equally lenient. But I'm not too optimistic about that happening.
As it turns out, Moser’s research is a result of motivated reasoning and is flawed.

https://link.springer.com/article/10.1007/s10508-022-02359-8
Thank you for digging up the quote and summarizing the sentiment. I've never been able to put my finger on this aspect of Dickens.

I personally share the same philosophy that morality swings above its weight in the grand scheme of society. It's fully within our control as individuals and therefore a worthy target for literary influence.
The userland is quite GNU. Think bash, gawk and coreutils (ls, etc.) as well as the libraries the userland depends on -- including the C and C++ standard libraries, pthreads, readline, etc.

Very little of it is irreplaceable these days. You could use a different shell. You can even run a BSD userland under a Linux kernel, in theory. The Linux kernel itself is replaceable with e.g. the open sourced Solaris kernel. There's many alternatives to just about any major UNIX component these days. But the standard (and often the only fully supported) set of tools and libraries on Linux is heavily GNU.
To be fair, unlike a monopoly controlled product, Ferraris are fungible in that I can equally not be able to afford a Lamborghini, Bugatti, Koenigsegg and numerous others. We have many options for cars we can't afford. The Honda will have to do. :-)
Show HN: I am building a low code tool in VS Code for fun
The Finite-State Machine we walk on during the generation process does not suffer from this problem so we can still output correct JSON, if that’s what you’re asking.
Why EVs specifically, and not simply all vehicles? We have an EV that weighs 1200kg, and a normal ICE car that weighs 2200kg - if anything the latter should be paying more tax due to its weight.
> No one ever got fired for choosing react, as some other commenter said.

That's supposed to be a pejorative, to describe how what management wants is rarely correlated with what's good or useful. 'Ignore shiny stuff' is the rallying cry when the shiny stuff is less performant and harder to use; as TFA illustrates, the thing about React is everything is more performant and easier to use than it. Where is the value in using React instead of Svelte for new development? If it is just that you already know it, what do you think of TFA's assertions about learnability?

The difference between React and Rails is, well, pretty much every mentioned negative attribute of React - Rails neither is terrible for performance, nor is full of hidden pitfalls, nor requires lots of boilerplate for simple actions, nor is incompatible with most Ruby libraries, etc.

I really think 'new stuff bad' rhetoric here is being divorced from every real reason usually backing it. 'React is good enough' is like someone saying 'MongoDB is good enough' - no it isn't, it was a huge step in the wrong direction and everything invented since it is moving towards more streamlined versions of the old ways of doing things. You explicitly reference the resurgence of old-school stuff, without noticing that it the thing it is specifically a rejection of is React.
I hope they all go to jail, though, and the ones that were first to to turn don't escape jail.
Their argument was in favor of keeping the tipping culture, as in not paying them the real wage because you'd lOsE ThAt sMiLe (as forced as it might be). Yes, I find this terrible as well.
Note sure about your second point there. An LED can be brighter if the diode is driven harder, right? But that can shorten its lifespan. Also, LEDs degrade over time, maybe it's better they just die before they get too dim. There's a tradeoff here between lifespan and user experience, and perhaps between lifespan and energy efficiency.
Why?
Sitting in desk for long periods and commuting by car/train in cycling-hostile countries is very bad for your health.
Second the Supernote. After having looked at the Scribe and Remarkable 2, I went with it. Actually feels like a proper notepad, the pens look and feel like expensive fountain pens and the whole experience is uncluttered and clean. The A6X is small enough to fit in any of my bags, and in a jacket pocket, which isn't something you can say about all the other 10 inches devices. It never leaves me.
The redirect has always been a bit annoying and I found on mobile if you click a link, see it load the t.co URL, then quickly go back and click again, it instead loads the actual linked URL. So I just instinctively do this now.
That means massive black holes have a much lower density that small black holes. So they are more likely to form than small black holes.

No, it doesn't, because you're ignoring all the physics required to get the mass into a small enough region so that it will collapse to form a black hole. The only way to make that happen that we know works is to form massive stars, where a fraction of the star's mass, in the center of the star, will eventually form a black hole. But the largest stars we know of have masses of ~ 200 times the Sun, and so can't form black holes more than a fraction of that.

If you imagine a more massive gas cloud collapsing under its own gravity, it will fragment into subclumps before getting very dense; these subclumps will themselves fragment or go on to form stars directly, but with an upper limit of, say, ~ 200 solar masses.

(It's possible that if you start with a cloud of pristine gas in the early universe -- nothing but hydrogen and helium -- that it might collapse to form a single supermassive star, or even a black hole directly. That might give you something like a 1000-solar-mass black hole. But that's still fairly speculative, and requires unusual conditions that don't exist generally.)
Attention: a little bit loud music
Virtual JavaScript worlds at planetary scales for threejs or react-three-fiber
The problem with that theory is that parties still hold primaries. Primaries have the most extremist representation since those are the people who are most motivated to vote. This is a problem when voter turnout for primaries is something like 15-20%
You can use a “meta” framework like Astro if you want, but micro front ends sound like hell. Nobody has really achieved portable non trivial components in a way that doesn’t come with a steep price tag, and web components have never taken off.
My opinion, which is shared by many other AI researchers, is that sensitivity to the exact phrasing of the prompt is a deficiency in current approaches to LLMs and many are trying to fix that issue. If they succeed, then I think the need for prompt engineering will be mostly negated. Hard to know when that line of research will yield success, though.
I see this as a problem to be solved in the software-education space
Show HN: Lottielab – Create product animations in the browser easily
Hi HN! Today we are releasing Lottielab, a web-based animation tool, to the public as an open beta. The main tool for editing and exporting Lottie animations today is Adobe After Effects, a 30-year-old visual effects tool that’s not fit for this purpose, has a steep learning curve, and requires a patchwork of error-prone plugins. With Lottielab, we are aiming to reduce the friction of creating and editing product animations by providing an easy-to-use editor with out-of-the-box support for import and export of the Lottie format and many others. Feel free to play around with the tool and let me know what you think - I'm here to answer your questions. Happy animating!
Maybe its not an argument at all and someone is just pointing out statistical facts? Any inference from that statistic is entirely in your own brain, with your own thoughts, interpretations, biases, etc.

I program computer chips and have a high school level of earth science under my belt so I have a hard time understanding how we extrapolate out things like 1 degree increase in temp means we're cooking the planet and there's no turning back. What I would like someone to explain is how our 200-300 years of measuring things can be extrapolated out to have any certainty around future or past events.

I (and I assume others) aren't asking to "smokebomb a conversation". I genuinely see headlines and understand we haven't been taking measurements for very long in comparison to Earth being here, and actually wonder these things. I would love to read thru something that presents it all in layman's terms (with references) that can describe how we arrive at any conclusions. I'm not denying that the temperature is increasing or that humans have a detrimental effect on the atmosphere. When I read mainstream media "reporting" on things I am knowledgeable about they get lots of details wrong and often come to wrong conclusions. Knowing that, I'm more like a 5 year old that keeps asking "how do you know that? / why?" Thanks for reading thru my brain dump.
While JSX is very well suited for programmatically defining your UI, it's about all that React is worth these days. You know about string literals right? You don't need JSX and in-fact can get away with:

render(props) {
return(
`<div>
{props.value}
</div>`
);
}
That's the thing, it's not just online. IRL there are reputations.
> The idea that tolerance 101 is about who you are able to discriminate is quite amusing. Especially in a thread about Orwell, doublethink and all that.

"discrimination" in the literal sense isn't bad, it's just making choices. The amusement stems from the very different things people mean when they say "discrimination". And being clear about what people mean with these terms is part of the 101.

But more relevantly, I didn't use that word, which is a very easy way to avoid any possible doublethink related to it!

> That in this scenario, since the KKK has terrible ideas and yours are better, you benefit from both being out in the open, since yours should surely win over.

I didn't say I want them to hide their ideas. I don't.

> Either way, yes, if you actually care for freedom of speech you ought to respect that which you find abhorrent.

Respect what, specifically? I respect their ability to speak. Do I need to go beyond that?
Praise the church of experts and their sanctioned interpretations of divine esoteric measurements
> Then go ahead and explain why West Virginia is consistently and historically among the poorest, least educated, unhealthiest, and unhappiest states in the US.

Can you really not imagine that some people don't care about money or education and instead care about other things that are seemingly unimportant to you?
One thing that became apparent to me after evaluating amount of complexity/work/team needed to maintain React projects compared even to Vue (but the difference is even more striking with more backend backed projects) is that - it is very often way cheaper to not to use React.
>>Heavier vehicles wear on the road more than lower weight vehicles, so it's a bit regressive at the moment.

The thing is - even if everyone in the world replaced their cars with Rivians, they won't do a fraction of a damage that trucks are doing to our roads. It doesn't matter in the slightest to your roads if you drive a 1 or 2 tonne vehicle - but that 40-tonne truck going over it absolutely does.

>>Tangentially, there was a 60 Minutes or similar report recently on how the extra weight of the vehicles also makes them more dangerous to vehicles of similar sizes that are much less weight.

That is very true.
That’s a good way to put it
All I want for these IoT things is being non-cloud dependent and PoE. I will run a billion wires before dealing with stupid batteries that keep dying, and they’re getting so expensive, too.
For one, built-in global state management like zustand. Context is too clumsy and iirc, causes unnecessary renders.
Isn't that a bit of a holy grail though? If your software can fact check the output of LLMs and prevent hallucinations then why not use that as the AI to get the answers in the first place?