MurphyA/hacker-news huggingface dataset:
by Y_Y | 2025-09-02 09:45:30+00:00
> You'll need > Your legal name and address. These need to be verified by uploading official identity documents.

I don't have a "legal name". Sounds like some sovcit bullshit. I go by several names, none of which is canonical. Maybe other countries formalize this idea, but the countries where I am a citizen/resident do not.

> A private email address and phone number for Google to contact you. These will need to be verified using a one-time password

I love that email OTP is good enough for this, but apparently not for anything else, where I'll need an approved verified secure attested super official app.
by npteljes | 2025-09-02 09:45:55+00:00
That's a flawed premise, as games totally don't suck today. There are so many to choose from, and people create new ones all the time, experiences where you can clearly feel that they poured their hearts and sweat into it.

For me, the practicality of gaming doesn't get in the way of the same enjoyment that you described feeling. I love it that I can have my favorites and current ones loaded in a single console, which I hold exactly as dearly as you described with the game cartridge. To me, most games are experiences though, and therefore I have no use for the media, packaging etc after I have experienced it. When I want to refresh my memories, I rather look at the screenshots and videos I took of the game, rather than the box or cartridge, as the media I created is much more personal.
by kumarvvr | 2025-09-02 09:46:01+00:00
Recently started developing a client side web app using Angular v 20. The app is quite complex, with about 40 components many of them nested, about 7 to 8 "pages", data dashboards, multiple forms, continuously updating data from server, etc. There substantial amount of data flow in the application.

So far, the experience has been absolutely wonderful, particularly, given the context of myself as a developer in the whole process, which is,

1. I am a seasoned developer, mainly doing python stuff, back-end servers, desktop applications, data applications, etc. Very little exposure to front-end tech.

2. I keep myself updated with the concepts, patterns & architecture of front-end systems, because I am extremely into design and good UI.

3. I am at a stage where I can do basic web apps with Vue, React, Angular & vanilla HTML and JS.

With Angular Signals and concept of Stores, Services and Dependency Injection, I am able to handle data flow very easily, am able to add features to the app in a consistent manner, able to debug and trace errors with relative ease.

I have earlier read NextJS docs, Remix Docs and read tutorials about developing react apps using Vite. It has always been a confusing maze of stuff. Perhaps I am getting old (about to touch 40), but I have been programming for about 25 years now and I was able to carve out the architecture I want in an Angular app with ease.

Also, this app is going to be a production app, and is critical for my work, so its an impactful decision, which, thankfully, I have been happy and pleasantly surprised with.

It could be that I could have chosen React, and end up with the same thing, but, somehow, in the extensive tech stack selection process that I took up before committing to Angular (which involved testing out core mechanisms of the application in React, Vue & Angular), I felt very much at home with Angular way of things.
Show HN: Easy to use JavaScript interpreter for Python
by amol- | 2025-09-02 09:46:07+00:00
The project has been around for a while, but I never shared it here, so I thought it was fine to bring it up in case anyone was looking for something similar.

DukPy is a Javascript interpreter for Python that is primarily designed with ease of use and ease of install use cases. Most other Js interpreters might be faster or more feature complete, but are also harder to install. DukPy tries to avoid any external dependency so that compiling it is straightforward and provides prebuilt wheels for a lot of different system.

The project is designed with Web development in mind, so it also includes some convenient transpilers adapted to DukPy, so that you can transpile your JSXX or SCSS content without having to install nodejs at all.

In the future I hope to grow the NodeJS compatibility layer and switch the javascript engine at a certain point.

PS: The project is very close to the 512 stars badge, so if you feel it's interesting any extra github star would help me reach that goal! Thanks
by tempodox | 2025-09-02 09:46:32+00:00
> Google has announced that, starting in 2026/2027, all apps on certified Android devices will require the developer to submit personal identity details directly to Google. Since the developers of this app do not agree to this requirement, this app will no longer work on certified Android devices after that time.

I don’t have any hope that this will sway Google, but at least the users are being warned.
by lucas_membrane | 2025-09-02 09:46:39+00:00
Teddy Roosevelt, a man anxious to do good things, probably gave the idea that people who know things should control things a big boost by promoting science, public health, and reasonable regulation of businesses. This succeeded so well that it seemed like a reasonable approach to government and was extended with the founding of the Federal Reserve to manage the money, by Wilson during WWI when the government took over the economy, by Herbert Hoover when he was a leading problem solver for US presidents during the decade or so before he became president. FDR and most of his successors have continued the trend, with many obvious successes. But the unseen problem was that people felt disenfranchised by the reliance on experts, and our social system, which requires shared wisdom and a balancing of interests and powers did not have appropriate checks and balances to arrange things so that either the technical intelligentsia would somehow be self-correcting or that there would be some other intelligentsia that could check and balance.
by ggm | 2025-09-02 09:46:43+00:00
Seems like a compelling case. The charts are great.

From the vantage of my expensive flat in Brisbane, I would kill for a Greggs steak bake right now. Alas, we're gentrified. We have "Harris Farm" near by which is officially posh. No hot pies for me (Banh Mi on the other hand.. good ones with paté...we have a plenty.)
by rvz | 2025-09-02 09:46:59+00:00
> You basically need to keep them in check constantly, even for a pet project like mine.

Once you do that, then it is not "vibe coding".

> But I do believe we'll get to the point they will replace more and more engineers.

Well some software engineers will get replaced. However, your claim was "all engineers", which isn't realistic.

Given the amount of safety mission critical software that runs the internet, air traffic control for planes, cars and embedded devices, etc they will always need human software engineers to review, test and maintain all of that, including the Linux kernel itself which runs almost everywhere.

Fully replacing all of them with LLMs would be outright irresponsible.

> But eventually, all that money in research will get somewhere I believe.

Of course, LLM security researchers and consultants breaking vibe-coded apps.
by Doxin | 2025-09-02 09:47:45+00:00
I don't think that's true actually. Not only do you get fewer parts in total, you also very quickly get to a scale where tracking part wear in detail becomes sensible. Slightly bigger scale and you get essentially 24/7 engineering coverage.

Yes a failure will affect a larger group of people, but it's also much less likely to occur, and much more likely to be fixed quickly.

As a thought experiment imagine everyone running their own privately owned diesel generator. Would that be more reliable than what we have now?
by bestest | 2025-09-02 09:48:14+00:00
Since you're here — I'll just pipe in.

Here in this article, the author, failing to comprehend the domain differences, is applying the same approach to call a function everywhere. Of course it won't work.

The fallacy of nextjs is attempting to blend function domains that are inherently different. Stop doing that and you will be fine. Documentation won't work, it will be just more confusing. Blending edge and ssr and node and client-side into one is a mess, and the attempt to achieve that only results in layers upon layers of redundant framework complexity.
by tialaramex | 2025-09-02 09:49:01+00:00
What "renewable energy market" ? Are you mistaking "green" consumer electricity tariffs for actually renewable energy ? It's all the same electrons, and if you don't pay for the gas then those gas turbines don't run, which means there's no electricity.

What we have is a single electricity market because electricity consumers do not care how this electricity was made. Their motors spin, their lamps light, it's the same whether we burned peat (which is very, very bad for the environment) or strung together a lot of photovoltaics and made the sun's light into electricity directly.
by sensanaty | 2025-09-02 09:49:42+00:00
I have a monstrosity of a Vue 3 project at work and I far prefer it to any "elegant" React codebase I've ever had the displeasure of working with. Boggles the mind that React still has any mindshare to me, Vue and Svelte are both superior to it in pretty much every way except for availability of component libraries (which isn't so relevant in my line of work), and a slight edge in terms of TypeScript support (mostly a problem with Vue's props).
by npteljes | 2025-09-02 09:49:43+00:00
Because it's not understanding, which would imply an objective truth, but a subjective experience. I personally have great appreciation to music and games, but really dislike physical media at the same time. The way I like to experience them is much better supported by the digital solutions, than the analogue.

Although, to be honest, if the digital world didn't exist at all, I'm sure I'd manage to have a good time all the time. It's just that now that it exists, I prefer it more - streaming over physical media for example.
by Nevermark | 2025-09-02 09:49:44+00:00
That was very well said.

One quibble, and really mean only one:

> a high-dimensional probabilistic causal framework

Deep learning models aka neural network type models, are not probabilistic frameworks. While we can measure on the outside a probability of correct answers across the whole training set, or any data set, there is no probabilistic model.

Like a Pachinko game, you can measure statistics about it, but the game itself is topological. As you point out very clearly, these models perform topological transforms, not probabilistic estimations.

This becomes clear when you test them with different subsets of data. It quickly becomes apparent that the probabilities of the training set are only that. Probabilities of the exact training set only. There is no probabilistic carry over to any subset, or for generalization to any new values.

They are estimators, approximators, function/relationship fitters, etc. In contrast to symbolic, hard numerical or logical models. But they are not probabilistic models.

Even when trained to minimize a probabilistic performance function, their internal need to represent things topologically creates a profoundly "opinionated" form of solution, as apposed to being unbiased with respect to the probability measure. The measure never gets internalized.
by lwhi | 2025-09-02 09:49:45+00:00
Without open standards, we would likely choose _one browser_, due to the economic cost of development.

One manufacturer would call all the shots for the _one browser_.

There would be zero competition until something calamitous happened to the manufacturer and the pendulum swung to a new monopolist.

We even have an example of how this plays out to fall back on; Macromedia Flash.
by adwn | 2025-09-02 09:51:23+00:00
I think that would be of little help if the faster, less-secure cores have access to the same memory system as the secure cores. If the JavaScript engine of your browser runs on the fast cores, and you're visiting a malicious website, then vulnerabilities due to speculative execution on the fast cores could still leak information that was written by the slow cores. And you really wouldn't want to run the JS engine on cores without caches and speculative execution, at least not for everyday browsing.
by account42 | 2025-09-02 09:51:42+00:00
> As far as I understand it, the stance of the 'Open Source' crowd is that if Amazon can't make it one of their AWS offerings then it isn't true open source, and they'll get very upset at you if you claim it is.

You don't get to just redefine terms if you find them inconvenient and people are right to push back against such attempts. If you want something else, put in the work to get mind share for your model instead of trying to catch a free ride by taking over an established one.
by qsort | 2025-09-02 09:52:03+00:00
Veritas used to represent abstract truth is not out of place. Obviously it assumes a different connotation in a Christian context ("Veritas vos liberabit" from the gospel of John being the obvious example), but it's not the only usage. See examples here: https://latinitium.com/latin-dictionaries/?t=lsn50557

Data is the past participle of the verb "do". It doesn't necessarily imply that usage.

I do agree that the construction is weird though, in particular the infinitive.
by drodgers | 2025-09-02 09:52:45+00:00
Stile Education | Melbourne, Australia | Hybrid/Onsite | Full-Time https://stileeducation.com/au/who-we-are/engineering-at-stil...

We're high-performing, diverse, tight-knit team with a mission to radically improve mainstream science and maths education at schools. By creating the best lessons in the world, coupled with intuitive tools that allow teachers to take advantage of the latest pedagogies, we’ve already helped millions of students in Australia get excited about science and maths.

45% of Australian science students in years 7-10 use Stile. Help us scale from 500k to more than 5 million students across Australia and the US over the next two years!

We now have offices in Melbourne, Boston, Portland and more! We're primarily hiring in Melbourne (relocation assistance and visa sponsorship available), but there will be lots of travel opportunities.

We're looking for a bunch of new roles right now (not all on our jobs site yet; please reach out if you're interested even if you don't seem to fit a specific role!):

- Engineering manager - Full Stack Staff Engineer - Platform engineer - ML/AI engineer - Automation engineer - Principal+ engineer - Frontend engineer
by inglor_cz | 2025-09-02 09:52:48+00:00
Now try non-rigid land ownership, where land and buildings can be expropriated in the name of nebulous greater good.

Been there, done that, it is worse than the alternative. People will stop cultivating anything, because why bother if a random officer can just take things from you at will.

Western regulations about land appropriation are strict for a reason, and they always require just compensation for a reason. That is the only way to prevent powerful people from just grabbing what they want, cloaking the thieving act in word bubbles about common prosperity.
by globnomulous | 2025-09-02 09:53:11+00:00
Beats me.

The very idea of a "user" is, in every phase of Latin that I know, gobbledygook. There's no translation for it. It makes as much sense as "haver" would make to us ("haver of what?"). Maybe "emptores" (buyers)? Sort of?

"Data," in our sense, too, sounds wrong to me as a concept in Classical Latin -- too disembodied for effective, accurate translation. Maybe 'cognoscenda,' "that which is to be known/understood," would come close to the intended sense and still be somewhat idiomatic.

"Vera" or "verita" sounds, to me, like the right language for the idea of "something true."

And like I said, "defendo" sounds like the right verb.

The omission of conjunctions sounds as abrupt, curt, and pompous in Latin as it does in English: "guard the user, the data, the truth." Only Sallust and Tacitus get to write this way.

So maybe we could correct it to something like "defende emptoresque cognoscendaque veraque?" No, actually, I take it back. That sounds deranged and wrong, kind of like the raving you might hear from one of the street-corner prophets in Life of Brian. Protecting those things makes no sense, and even the grouping of those three concepts in a single list makes no sense. It sounds like the product of a disordered, unhealthy mind.
by w3news | 2025-09-02 09:53:35+00:00
Next.js is indeed not very open for feedback. Next.js is also opinionated. So if you are using Next.js, you can use what they have and do it their way. If there is something, just wait...

For me, it isn't a framework I want to use in any production environment. Your system is too much depending on something you have no influence on. Like in your own code, it is good to decouple, don't make things depend too much on something, not in your own code, but also on external code like frameworks and libraries.

That is why I prefer to build things like I can (kind of) easy drop my dependencies, for what reason, and use something else, or build it in my own codebase. If some framework doesn't allow it, and you have to work it their way, and is the base of everything, that should be a big red flag.
by viktorcode | 2025-09-02 09:53:55+00:00
That would be a valid argument if Apple mislead you into buying iPhone under the false premise of „you can install everything you want“. Instead, you either chose to blame Apple for making your phone work exactly as it was intended, or, as customary on the internet, you are blaming Apple for designing device you don’t even own against your expectations of how they should do it.
by thw_9a83c | 2025-09-02 09:54:03+00:00
Yes, LLM is a lossy encyclopedia with a human-language answering interface. This has some benefits, mostly in terms of convenience. You don't have to browse or read through so many pages of a real encyclopedia to get a quick answer. However, there is also a clear downside. Currently, LLM is unable to judge if your question is formulated incorrectly or if your question opens up more questions that should be answered first. It always jumps to answering something. A real human would assess the questioner first and usually ask for more details before answering. I feel this is the predominant reason why LLM answers feel so dumb at times. It never asks for clarification.
by muragekibicho | 2025-09-02 09:54:06+00:00
some people just mastered their domain. i pray i get this good in my area of expertise: elliptic curves. lol im researching curves on random math sites, and learning different implementation tricks (like the subtle diff in MSB and LSB implementations of the double and add algorithm* or that sometimes you can find the weirdest endomorphisms on non-binary Koblitz curves (they're not documented AFAIK and Koblitz the OG is too old to be chasing 1-bit, 2-bit endomorphisms)

This was me in awe of the pokemon card CSS lol. It appears to have been done before AI and this makes it even more impressive tbh.

*The diff is in MSB->LSB the generator remains constant while in LSB->MSB to the generator doubles. Either way, you always know the value of the generator at every bit. I think this is a vulnerability but I just can't find out how.
by rollcat | 2025-09-02 09:54:15+00:00
> Anyway, this whole library should have been a copy-pastable snippet for a dialog or toast

People under-value copy-pasting. I'd rather copy/vendor a thousand lines of code (with license+credit intact) than add it as a dependency.

I'm working on a side project, and needed a CPIO library for Go. CPIO is a fixed thing, a good implementation is "done". U-root[1] has a really decent implementation, so I've vendored 2500+ lines of code, as otherwise I'd have to (indirectly) depend on almost 700.000. Great value.

[1]: https://github.com/u-root/u-root
by pjc50 | 2025-09-02 09:54:36+00:00
The trouble with "use free electricity" schemes is that the capital cost never sleeps: you have built a fixed plant, on a piece of land, and paid for that, regardless of whether it runs or not. So there's usually a fairly high minimum duty cycle to make it economically viable.

You could make the argument in the other direction: the AI training datacenters could run for 23/24 hours, saving electricity at the peak time when it's most expensive and when they're pushing up the cost of electricity for everyone else the most .. but of course all those GPUs are too expensive to leave idle.
by athosblade | 2025-09-02 09:55:06+00:00
SEEKING WORK Location: Europe

Remote:Yes

Willing to relocate: no

Technologies:Vue, React, Next.js, Tailwind, Node.js, Django, PostgreSQL, Prisma, Redis, Celery, FFmpeg, HLS.js, SendGrid, Stripe, AWS, Linux, DigitalOcean, Heroku, Docker, PostGIS, Metabase, Greenhouse, Vanta, Google Workspace, Twilio

Résumé/CV: ademhodzic.com

Email: contact@ademhodzic.com

Github: https://github.com/AdemHodzic

I'm a full-stack developer with 7+ years of experience in startups trenches.

Here are the biggest projects I've worked on + a single feature that demonstrates my impact on product and/or technical chops :

Fanfest – fanfest.vip - Community engagement platform for soccer fans. Built a browser-based live streaming engine that lets streamers broadcast directly from their browsers in both 16:9 and 9:16 at 1080p (and lower resolutions), with simultaneous streaming to YouTube, Twitch, Facebook, Instagram, and X.com.

Pequity – pequity.com - Compensation management platform for mid-to-large organizations. Built V2 for offer approval chains, reducing complexity and fixing HUGE performance issues. For example, in the worst case scenarion in V1 for a single request it would take 2 minutes to finish. In V2 it's 970ms.

Haekka – haekka.com - Security and compliance training integrated with workplace tools. Developed a system for automatically assigning users training based on non-compliant events like exporting sensitive keys they did in AWS/Slack/Gmail.

Flox – flox.app - App facilitating social connections by helping friend groups meet. Used Postgis to build an algorithm for auto check-in system for event attendance.
by rossant | 2025-09-02 09:55:14+00:00
I was exploring the OpenAlex database [1] when I discovered that paper abstracts were not stored in plain text but as an inverted index, e.g.:

"abstract_inverted_index": { "To": [ 0 ], "determine": [ 1 ], "whether": [ 2, 154 ], "certain": [ 3 ], "computed": [ 4, 44 ], ... }

At first I thought this was for compression or something similar, but it turns out it is for legal reasons, to avoid copyright infringement on abstract plain text. Of course, it only takes a few lines of code to reconstruct the plain text from this inverted index, so I was surprised this would hold up in court.

I couldn’t find a definitive answer, but I believe the closest one is this comment on StackExchange: [2]

> It's possible that they could include the plain text abstracts legally, but some publication disagrees and they don't want to fight it in court. It's also possible that the publisher believes that the inverted index is indeed infringing their copyright, but they're not sufficiently confident that they would prevail in court to actually bring a suit. The ultimate answer to this question is that it's a close call, and until a court rules on it, nobody knows for sure whether it's illegal in any given jurisdiction. I don't know whether a court has ruled on it.

[1] https://en.wikipedia.org/wiki/OpenAlex

[2] https://law.stackexchange.com/questions/110313/how-does-inve...