MurphyA/hacker-news huggingface dataset:
by twistslider | 2025-12-14 22:39:36+00:00
These integrations are lacking compared to Spotify. For example in Tidal you have to set it for each device where you install the app, and it doesn't work with things like casting. It's easy to forget to set it up which can cause gaps in your history.

The Plex integration gets pretty close to native, but it only scrobbles after a track is done, it doesn't have 'Now Playing' support.

As for Deezer and Quobuz I'm not sure. Afaik Spotify still stands alone by being set-and-forget, working on any device and having full feature support.
by tim333 | 2025-12-14 22:39:36+00:00
I don't have a problem with the headline but the article is kind of bad.

And the headline is vague enough that you could read many meanings into it.

My take would be going back to Turing, he could see AI in the future was likely and the output of a Turing complete system is kind of a mathematical function - we just need the algorithms and hardware to crank through it which he thought we might have 50 years on but it's taken nearer 75.

The "intelligence did not get installed. It condensed" stuff reads like LLM slop.
by nzoschke | 2025-12-14 22:39:55+00:00
A central service. Hosted, secure, frontier model is fine. I’m thinking this through it’s probably something GitHub or an addon should provide.

But maybe it starts local with an app like yours anyway. I do a lot of solo hacking I don’t want to share with the team too. Then there is some sort of way to push up subsets of data.
by didibus | 2025-12-14 22:40:05+00:00
A good read, but it reminds me that people see the programmer as being there to identify when the AI makes an error or a mistake.

But in my use of AI agents as a programmer and also for other work. I would say that, while yes, you also have to look for mistakes or errors, most of the time I spend is on programming the AI still.

The AI agent has no idea what it must produce, what it's meant to do, when it can alter something existing to enable something new, etc.

And this is true for both functional and non-functional requirements.

Unlike in traditional manufacturing, you've already built your manufacturing pipeline for a precise output, you've got your CAD designs done, you ran your simulations, you've calibrated everything already for what you want.

So most of the work remains that of programming the machine.
by epolanski | 2025-12-14 22:40:05+00:00
The list of things jsdoc cannot do is long but a simple example is overloading, you cannot express this[1] in jsdoc, and if you need to reference .d.ts files you're back at using TypeScript, so the point of JSDoc was...?

If you need precise return typing, conditional types, literal values, etc, you aren't going far if anywhere with JSDoc.

[1] https://shorturl.at/pg5dL
by Aurornis | 2025-12-14 22:40:21+00:00
> It's all full stack these days. It's often expected that you can handle both worlds (client and server)

Full stack is common for simple web apps, where the backend is almost a thin layer over the database.

But a lot of the products I’ve worked with have had backends that are far more complex than something you could expect the front end devs to just jump into and modify.
by vmbm | 2025-12-14 22:40:36+00:00
I have trouble sleeping, and it gets particularly bad in the winter. I have figured out that at least one of the triggers for poor sleep has been evening screen time. Redshift style apps help a little but barely. I can get away with some light usage of my phone on the dimmer settings, but if I sit down at my multi-monitor desk setup I will be wide awake all night and feel terrible in the morning. And this is with redshift and screens set to their lowest brightness levels.

So I spent a fair amount of time looking into e-ink options as a potential solution. I eventually settled on a refurbished Lenovo Thinkbook Plus G4, which has a flip-able screen with e-ink on one side. I paid around $800 which was less than a dedicated e-ink monitor, and only slightly more than some of the higher end large tablets/e-readers. So it was a hard deal to pass up.

I am happy to report that using the e-ink in the evenings has helped quite a bit on the sleep front. And while the laptop is pretty nice, e-ink in general requires a fair bit of compromise and the laptop in particular has some rough edges. You definitely need to spend some time on your display settings to make things work (high contrast, cursor and pointer visibility, font color in IDE and terminal apps, etc...), but for the most part I can make it work. And while I don't work in sunlight often, e-ink can really shine if you are outdoors (I have the sun shining on my screen right now as I type this and it is super readable.)

Anyways, I guess what I am trying to say is that I really hope more investment gets put into e-ink. I think it is a pretty awesome technology and would love to expand my usage of it. But at least for now it is mostly something that I am tolerating for the sake of sleep.
by idoubtit | 2025-12-14 22:41:03+00:00
1. Die Wand (1963, Germany). The Wall. Marlen Haushofer.

An excellent novel, simple, yet moving. Why do we live and what is our connection to nature?

2. Fifth Business (1970, Canada). Robertson Davies.

I've read thousands of novels, so I'm always glad to read something new and unpredictable, but still based on the best premise: interesting characters.

3. Sostiene Pereira (1994, Italy). Pereira Maintains. Antonio Tabucchi.

My favorite book this year. A deep and smart and tense plunge into the Portuguese life of a few decades ago. Italian literature has so many gems.
by general1465 | 2025-12-14 22:41:04+00:00
I would guess that it is because of stale line up. There is Model 3, Model Y (which is Model 3 Wagon if that would be a European car) and now they come with a light facelift of Model Y. Model S and X are abandoned.

Compare it to European and Chinese brands, which are offering much wider range of cars and in case of European brands you don't need to travel to a different country to get your car fixed if it breaks.
by panick21_ | 2025-12-14 22:41:16+00:00
There are already many of these. fd, httpie, rg, and so on.

There is of course RustTLS that already exists and is already very advanced.

For package manager see for example AerynOS (or its new name that I can't remember).

There are lots of rust editors, terminal and otherwise.

And of course the complete Cosmic Desktop is written in Rust, so you don't have to go 'non-graphical' at all.

So AerynOS, with uutils and Cosmic is very close I would say.
by danielhep | 2025-12-14 22:41:16+00:00
I work on an open source server project that is deployed in many different contexts and with many different clients and front ends. GraphQL has allowed us to not feel bad about adding extra properties and object to the response, because if a particular client doesn’t want them, they don’t request them and don’t get them. It has allowed us to be much more flexible with adding features that only few people will use.
by citizenpaul | 2025-12-14 22:41:26+00:00
Yes.

Today I asked it to make a short bit of code to query some info from an API. I needed it to not use the specific function X that is normally used. I added to its instructions "Never use function X" then asked it in the chat to confirm its rules. It then generated code using function X and a word soup explaining how it did not uses function X. Then I copy pasted the line and asked why it used function X and it said more word soup explaining how the function was not there. So yea not so good.
by cjohnsonpr | 2025-12-14 22:41:42+00:00
We open-sourced Rosetta, a lightweight protocol and CLI that helps AI coding agents build and retain institutional knowledge about a codebase across sessions.

The core idea is simple: instead of re-prompting agents with ad-hoc README excerpts or hoping they infer architecture from code alone, Rosetta introduces a standard file format (ROSETTA.md) that captures agent-relevant context explicitly: architecture, conventions, entry points, gotchas, and append-only agent learnings.

Key aspects:

A structured markdown protocol (ROSETTA.md) designed for machine parsing, not marketing

Append-only “Agent Notes” so agents can persist what they learn over time

Optional scoped modules (.rosetta/modules/*.md) for conditional context loading

A CLI for validation, scaffolding, and bootstrap prompts

A programmatic API for agent frameworks and IDE integrations

This is not another docs generator or LLM wrapper. It is closer to a memory boundary between humans, agents, and codebases.

Motivation: Most AI coding tools still treat every session as stateless. Humans accumulate institutional knowledge; agents currently do not. Rosetta is an attempt at a minimal, explicit standard for closing that gap.

Repository: https://github.com/metisos/Rosetta_Open_Source

Interested in feedback on:

Whether this should be a protocol vs just a convention

How agents should govern and curate learned notes

Failure modes you’ve seen with persistent agent context

Happy to answer technical questions or hear why this is a bad idea.
by JKCalhoun | 2025-12-14 22:42:39+00:00
I'm currently making a number of "breadboard-able" analog computing modules.

I've always loved electronics since I was a kid (still trying to learn). As I explore and learn I've begun to make these small "breadboard helpers" [1]. (Just one on Resistor Transistor Logic (RTL) right now.)

An obsession over a project in a 1970's hobbyist electronics magazine sent me down the rabbit hole that is (was) analog computing. So I have been bread-boarding and prototyping small analog computer modules.

I'm in the PCB-layout stage for the modules and hope to have them ready early next year.

[1] https://www.circuitpixies.com
by erkok | 2025-12-14 22:43:14+00:00
I tend to agree with the author. GraphQL has its use cases, but it is often times overused and simplicity is sacrificed for perceived elegance or efficiency that is often times not needed. "Pre-mature optimisation of root of all evil" comes to mind when GraphQL is picked for efficiency gains that may never become a problem in the first place.

Facebook invented GraphQL to solve a very specific problem back in 2012 for mobile devices. Having to make multiple queries to construct the data needed in FE in mobile clients is bandwidth constraining (back then over 3G networks) and harmful for battery life, so this technology solved this problem neatly. However, these days when server-to-server communication is needed over an API, none of the problems Facebook invented the protocol for are problems in the first place. If you really want maximum efficiency or speed you probably ought to ditch HTTP entirely and communicate over some lower level binary protocol.

REST is not perfect either, one thing I liked about SOAP was that it had a strong schema support and you got to name RPCs the way you liked, and didn't have to wrangle everything around the concept of a "resource" and CRUD operations, which often times becomes cumbersome to fit into the RESTful way of thinking if you need to support an RPC that "just does magic with multiple resources". These are the things I like about GraphQL, but on the other hand REST is just HTTP with some conventions, which you necessarily don't have to follow if things get in your way, and is generally simpler by design.

The only thing I wish with REST is having a stronger vendor support for Swagger/OpenAPI specs. One of the things my team supports is a concept of Managed APIs for our product: https://docs.adaptavist.com/src/latest/managed-apis and we support primarily RESTful APIs but also couple of GraphQL based ones and the issue we face is that REST API specs for many products are either missing, incomplete or simply outdated, so we have to fix them ourselves before we generate our Managed API clients, or write them by hand if the specs don't exist. It's becoming easier with AI these days, but one thing I personally regret when we transitioned from SOAP to REST as a community, is that the strong schema support became a secondary concern. We no longer could just throw API client generator at SOAP's WSDL and generate a client, we needed to start handcrafting the clients ourselves for REST, which is still an issue to this day, unless perfect specs exists, which in my experience is a rather rare occurrence.
by henvic | 2025-12-14 22:43:18+00:00
More wealth gives you more power in different ways, including political.

That doesn't mean that society stands where it stands now because of political power. If anything, we've evolved in spite of it.

And you assuming that I was born rich is hilarious. I come from the northeast from Brazil, and my parents weren't by any means rich growing up. Now, on their 70s, they're finally financially stable after a lot of hard-work, and despite the government doing their best to destroy their wealth. And to clarify: besides attending a really good private school, my childhood was quite poor (luckily, I always had a computer about 5-10 years older than the current models back then, at least; I could've newer, but your loved statism made it harder to have access to tech).

You're full of prejudice. You think someone who isn't on the same page as you politically is privileged lol

Wealth inequality doesn't cause people to die from preventable diseases. Your commie mindset does when they can't afford to have access to wealth, medications, leisure, access to good resources, etc.
by shadowgovt | 2025-12-14 22:43:26+00:00
Not standardized enough; I can't guarantee the format of an API is RESTful, I can't know apriori what the response format is (arbitrary servers on the internet can't be trusted to be setting content type headers properly) or How to crawl it given the response data, etc. we ultimately never solved the problem of universal self- describing APIs, so a general crawling service can't trust they work.

In contrast, I can always trust that whatever is returned to be consumed by the browser is in the format that is consumable by a browser, because if it isn't the site isn't a website. Html is pretty much the only format guaranteed to be working.
by exogen | 2025-12-14 22:43:51+00:00
A few years ago, I made a model skinner for Tribes 2, a ~25 year old game that still has a loyal following: https://exogen.github.io/t2-model-skinner/ (if you check out the Gallery link there, you'll notice this app resulted in a whole new wave of skins, and even a Halloween skin contest)

To satisfy the urge of doing something else ambitious in the browser, I'm now doing the same thing for Tribes 2 maps: trying to make a web-based map viewer and editor: https://exogen.github.io/t2-mapper/ (editing/creation part still in progress)

I got this working for most maps pretty quickly. It translates the mission object tree from the Torque .mis files into a Three.js scene graph. Eventually though, I noticed that some mission definitions were more dynamic – Torque .mis files are really just TorqueScript .cs files with a different extension and some pragma/magic comments. So, to actually handle every map would require not just a mission file parser, but a whole TorqueScript runtime. Implementing THAT part seemed really tedious and, frankly, uninteresting to me. So I had Claude Code get a whole TorqueScript transpiler and runtime working. Now, when you load a mission, it actually runs all the same scripts that Tribes 2 runs to load the mission, all the way from server.cs and its `CreateServer()` function.

Currently, I'm continuing to get its rendering matching Tribes 2 as closely as possible, and setting things up so that live editing of missions will work.

Source: https://github.com/exogen/t2-mapper
by czhu12 | 2025-12-14 22:44:55+00:00
Yeah it’s totally free to use and there are pricing tiers for support that portainer provides. Canine is 100% FOSS. No hidden features behind some payment plan or anything.

Portainer sponsors us, to keep us working full time on it.

Shoot me a note at chris @ canine<dot>sh

Would love to help in any way I can! Always looking for more adoption, esp at medium sized companies
by Aerroon | 2025-12-14 22:45:30+00:00
Ironically this wouldn't work for me because I do almost all of my reading on my phone these days. It has become the main use of my phone at this point.

It is a good idea though, as long as they can find things they want to read. I've been sucked into the "bleeding edge" of reading (web novels), so it can be a bit more challenging to find things I really want to read. They are still out there though. Eg The Martian and Project Hail Mary (the former actually started as a web novel) .
by qubex | 2025-12-14 22:45:39+00:00
Have it in print. Fondly remember BeOS in the second half of the nineties; still have second-generation BeBox. I was amongst those who were dismayed when Apple “didn’t choose Plan B” and instead acquired NeXT (that I also had experience with, and whose hardware and software I adored, but that just didn’t “feel right” for the whole “multimedia convergence” visible on the horizon ahead). Guess I was wrong, but I still dote on my Batmobile, and the interface is so perfectly “nineties zany grunge” in retrospect: as chiselled as Motif but with a define nod to Keith Haring.

Anyway, an awesome and prescient book.

Anathem, Cryptonomicon, The Baroque Cycle… Neal Stephenson is an absolute master of his craft, though he is famous for failing to stick the landings sometimes.
by lucasfdacunha | 2025-12-14 22:45:41+00:00
Working on https://greatreads.dev/ A place to aggregate and find articles from developers' blogs. Right now, I'm building a submission form for people to submit new sources.

There is also a way to search for articles using vectors, it's called "Semantic Search". So basically you can ask, for example, "Postgresql and how to best optimize it." and it would search for articles touching that subject, or at least related to it.

Wondering about the best way I can add a weekly newsletter built on top of the content currently being ingested, and still looking for more sources to add to the database (let me know if you have any good recommendations).
by andrewingram | 2025-12-14 22:45:52+00:00
For me it’s really about the component-level experience.

* Relatively fine-grained re-rendering out of the box because you don’t pass the entire query response down the tree. useFragment is akin to a redux selector

* Plays nicely with suspense and the defer fragment, deferring a component subtree is very intuitive

* mutation updaters defined inline rather than in centralised config. This ended up being more important than expected, but having lived the reality of global cache config with our existing urql setup at my current job, I’m convinced the Relay approach is better.

* Useful helpers for pagination, refetchable fragments, etc

* No massive up-front representation of the entire schema needed to make the cache work properly. Each query/fragment has its own codegenned file that contains all the information needed to write to the cache efficiently. But because they’re distributed across the codebase, it plays well with bundle size for individual screens.

* Guardrails against reuse of fragments thanks to the eslint plugin. Fragments are written to define the data contract for individual components or functions, so there’s no need to share them around. Our existing urql codebase has a lot of “god fragments” which are very incredibly painful to work with.

Recent versions of Apollo have some of these things, but only Relay has the full suite. It’s really about trying to get the exact data a component needs with as little performance overhead as possible. It’s not perfect — it has some quite esoteric advanced parts and the documentation still sucks, but I haven’t yet found anything better.

Did my only ever podcast appearance about it a few years ago. Haven’t watched it myself because yikes, but people say it was pretty good https://youtu.be/aX60SmygzhY?si=J8rQF6Pe5RGdX1r8
by orwin | 2025-12-14 22:45:53+00:00
Not me, but it's the first that for now didn't fail catastrophically on moderately difficult task. Not that the other models can't manage difficult tasks, but they sometimes generate stuff so wrong it's almost funny. For now (a week of usage), it never truly failed (the one time it couldn't find a working solution, it simply proposed solutions I could use and stopped, without generating bullshit code), and sometimes I don't have to change anything from the generated output.

It's definitely more useful than me the first 5 years of my professional career though, so for people who don't improve fast or for average new grades, this can be a problem.
by tptacek | 2025-12-14 22:46:13+00:00
You appear from your published CV to be much, much younger than 51. I'm not 51, but I'm much closer to it than you are, and at an age where many people in my social circle at past that. What on earth gives you the confidence to say something like "at 51 you don't have the energy to compete"?

Also, at 51, you probably have more time to compete than a 36 year old.

I think you're way off on this.
by victornomad | 2025-12-14 22:46:54+00:00
I've been working on LLMParty for some months. It is a collection of experiments that use LLM under the hood. For each experiment I tried to play with something different, such interaction, LLM knowledge, use, etc

https://llmparty.pixeletes.com

If you have to try one I recommend this

- A chatbot to control a car https://llmparty.pixeletes.com/experiments/universal_ui
by tharkun__ | 2025-12-14 22:47:41+00:00
Which one?

Like, I see the comment about the Keychain integration and all that. But in the end I fail to see (without further explanation but I'm eager to learn if there's something I am unaware of) where this isn't different from what I am saying.

Like yes, my ssh key has a passphrase of course. Which is different from my system one actually. As soon as I log into the system I add the key, which means entering the passphrase once, so I don't have to enter it all the time. That would get old real fast. But now ssh can just use my key to do stuff and the agent doesn't know if it's me or I got compromised by npm installing something. And if you add a hardware token you "just have to tap" each time that's a step back into more security but does add tedium. Depending on how often my workflow uses ssh (or something that uses the key) in the background this will become something most people just blindly "tap" on. And then we are back towards less security but with more setup steps, complications and tedium.

I saw the "or allow for a session", which is a step towards security again, because I may be able to allow a script that does several things with ssh with a single tap, which is great of course. Hopefully that cuts the taps down so much that I don't just blindly tap on every request for it. Like the 1password thing you mentioned. If I do lots of things that make it "ask again" often enough I get pushed into "yeah yeah, I know the drill, just tap" security hole.
by AutoAPI | 2025-12-14 22:47:52+00:00
https://PostalAgent.com – Send personalized postcards online.

Upload a CSV or circle neighborhoods on Google Maps to build your address list (consumers or businesses). Printing and postage included in one price.

In the last 30 days I've added an API plus integrations for Pipedrive, Zoho, and Follow Up Boss. If anyone wants to help test these new integrations, I'll set you up on a special plan and let you send mail at my cost (roughly the price of a stamp).