Kind of a bit "too little too late" when they're still open-sourcing it but by bit in 2025 after promising to open-source it during the acquisition in 2017. I'm not very impressed.
It wasn't started in 2025, it's a process that's been going on for years. (Presumably, but I don't actually have more information here, the pre-acquisition codebase couldn't easily be open sourced without rewriting for legal reasons, e.g. copyright residing with someone else.)
Nothing about the communication at the time indicated that publishing the source code would happen gradually over a decade. For all intents and purposes, what was promised was that it would be open source within some reasonably short time frame.
Having worked on a similar endeavor, I doubt they intentionally dragged their feet on it. They likely had a smorgasbord of legal bullshit and technical challenges resulting from code omissions mandated by said legal bullshit that they had to muddle through.
I don't care. Don't promise to do something like that if you can't follow through. Nobody forced them to promise to open source Pocket (although that promise certainly helped the bad PR of integrating a closed source service into Firefox!).
How common is it for a SaaS company that isn't an old-enterprisey type to use third-party proprietary code in their business logic? I associated that phenomenon much more with standard installable PC software, especially the type to use specialized workflows for non-standard stuff, not a web service, much less something like this.
In the process of trying to update, Spotify on NixOS will likely display some big error message about how it's unable to install updates, which results in a pretty bad user experience when everything is actually working as intended. It seems fair to patch software to remove such error messages.
I don't think you can "fear" something you consider a gimmick. Also good fucking luck arguing smartphones don't have massive negative effects.
If LLMs were even 50% as good as they're pretending to be we'd see huge productivity increase across the board, we simply don't, and it's been almost 3 years since chatgpt was released now. Where is the productivity increase ? Where is the extra wealth generated ?
> If LLMs were even 50% as good as they're pretending to be we'd see huge productivity increase across the board, we simply don't, and it's been almost 3 years since chatgpt was released now. Where is the productivity increase ? Where is the extra wealth generated ?
I certainly did. You won’t see any of it, because I use it to work less, not more.
> I think most people in here know at least a few ways they can use AI that is genuinely useful to them
The only thing that really comes to mind is making something in a domain where I have almost no prior expertise.
But then ChatGPT is so frequently wrong, and so frequently repeatedly wrong when it tries to "correct" problems when pointed out, that even then I always have to go and read relevant documentation and re-write the thing regardless. Maybe there's some slight usefulness here in giving me a starting point, but it's marginal.
- Turning a lot of data into a small amount of data, such as extracting facts from a text, translating and querying a PDF, cleaning up a data dump such as getting a clean Markdown table from a copy/pasted HTML source of a web page etc (IMO it often goes wrong when you go the other way and try to turn a small prompt into a lot of data)
- Creating illustrations representing ephemeral data (eg my daily weather report illustration which I enjoy looking at every day even if the data it produces is not super useful: https://github.com/blixt/sol-mate-eink)
- Using Cursor to perform coding tasks that are tedious but I know what the end result should look like (so I can spend low effort verifying it) -- it has an 80% success rate and I deem it to save time but it's not perfect
- Exploration of a topic I'm not familiar with (I've used o3 extensively while double checking facts, learning about laws, answering random questions that would be too difficult to Google, etc etc) -- o3 is good at giving sources so I can double check important things
Beyond this, AI is also a form of entertainment for me, like using realtime voice chat, or video/image generation to explore random ideas and seeing what comes out. Or turning my ugly sketches into nicer drawings, and so forth.
You need very little for software development. Linters, IDEs, debuggers, and even programming languages are all optional, but they sure help shorten deadlines!
When I complain about HDR it's because I've intentionally set the brightness of pure white to a comfortable level, and then suddenly parts of my screen are brighter than that. You fundamentally can't solve that problem with just better tone mapping, can you?
Well yeah. I considered adding that caveat but elected not to because it's obvious and doesn't add anything to the conversation, since that's obviously not what's meant when the industry talks about "HDR". Should've remembered this is HN.
"Web server" is, more or less, about converting a database into JSON and/or HTML. There are complexities there, sure, but it's not like it's some uniquely monumental undertaking compared to other fields.
Not all web servers deal in HTML or JSON, many don't have databases outside of managing their internal state.
Even ignoring that, those are just common formats. They don't tell you what a particular web server is doing.
Take a few examples of some Go projects that either are web servers or have them as major components like Caddy or Tailscale. Wildly different types of projects.
I guess one has to expand "web server" to include general networking as well, which is definitely a well supported use case or rather category for the Go std lib, which was my original point.
Just to explain this confusion, the term “web server” typically refers specifically to software that is listening for HTTP requests, such as apache or nginx. I would use the term “application server” to refer to the process that is processing requests that the web server sends to it. I read “web server” in their comment as “application server” and it makes sense.
Yes. That's the same distinction I would expect. Although I'm not sure that the database stuff is the role I'd usually look for in the application server itself.
I don't think Anukari is in the Mac App Store, nor do I think a plug-in like it will ever be appropriate for the App Store, so I don't know what exactly you're worried about.
I mean the CPU can't prepare a job for samples which don't exist yet. If it takes 0.5 milliseconds to process 1 millisecond's worth of audio, you'll necessarily be stopping and starting constantly. You can't keep the GPU fed continuously.
reply