Yep, if I use street name it attaches to wrong part of the street, if I use a place next to the street it attaches to the place, not the street. Couldn't figure out how to drag the origin point of the arrow
Feels quite clear Donut doesn't have much - no meaningful new tests released for many weeks already and some executive of Nordic Nano sued Donut Lab and said their claims were misleading.
I haven't really followed that closely myself, but I've noticed the people who I saw defending Donut before have gone really quiet about it lately.
I find the talk around Donut so weird. At CES we were told they had nothing because they hadn’t shared third party test. They then shared third party tests remarkably fast. From the dating of VTT reports it’s clear they shared it as soon as VTT finalised their reports. Now they have nothing because they haven’t released enough tests fast enough?
It’s clear they have something very interesting.
We’re mainly missing low temp and energy density test. If they have something real, obviously they’re saving density for last (near the time real customers get their hand on the bike), since it will give them huge amount of attention. Can’t fault them for milking what they’ve got (if they got it) for all the marketing hype it’s worth.
We’re also missing cycle life test but the claims can’t really be fully tested in a reasonable time. So even if their tests show projections that indicate high cycle life, people will doubt it, or shift the focus to ageing effects. So personally I don’t care much, we just have to see how it works out in real life.
The lawsuit incidentally reveal their connection to partners which does reveal that there’s something real there. Another criticism was that the couldn’t have developed all the tech from scratch themselves in such a short time, and now it’s clear they didn’t, they’re using tech licensed by other companies with real competence in the field.
If it’s as good as they say with zero caveats and can be manufactured at scale is another matter
I think by this point they demonstrated basically all the characteristics of their battery well enough, except for the density, but then that was a pretty damn important and big claim. I'm not sure they can afford to delay that much longer. Or the actual shipment of products.
They didn't share third party tests. They shared tests done by a party they contracted, and whose test reports don't back up the claims to the extent that they claimed.
Do they have something interesting? Maybe! But it could also be yet another Theranos. Extraordinary claims require extraordinary evidence, and they haven't exactly been forthcoming with it.
Donut's website claims that they will release the next test result in 7 days, so you can check next week whether those people will have something new to talk about: https://idonutbelieve.com
I sincerely hope Donut really has an ace up their sleeve, we could really use some domestic competition against China here in the EU. I sincerely hope that the next update from them is something solid (pun intended), and not 'what color is the battery'.
Tried it again few days ago. I kinda get that currently you can only use AI on Helix through LSP, but on top of that it does not have auto-refreshing files when changed outside - makes it really hard to work with external AIs, as I'm just constantly worrying if I'm editing a stale file.
GitHub Copilot, Claude Code and Codex provide fairly good IDE integrations. They don't just edit files behind your back. They actually edit the files you have in the IDEs using editor APIs and even show you a nice diff view. This way you never have content that is out of sync. I find this approach very usable and appealing.
On the other hand, many of the AI tools and their companies think that you should completely ditch IDEs for CLIs only, because "nobody needs to write code anymore". Some of them even stopped maintaining IDE extensions and go all-in in CLIs.
I've noticed that Codex usually uses the native editing tools and shows me a diff, but sometimes it just sidesteps that and does a cat > file << EOF, so I need to rely on Git diffs to tell what it did.
> This way you never have content that is out of sync.
They can definitely go out of sync, particularly if something that isn't the editor or the AI changes the code (e.g. running shell commands or opening the file in a different editor and making changes there). I've had a whole load of issues with VSCode where there's been spurious edits all over the place that show up again even if I try and revert them, because every time the AI makes an unrelated edit, VSCode tries to reset the file to the version it thinks exists and then play the AI's edits on top.
I don’t even open a text editor anymore 90% of the time. Seems clear to me that IDEs, in the traditional sense, don’t really have a place in the future of software creation. They might morph into something that does, but definitely not in their current form, imo.
I think this statement is misguided, and potentially comes from a lack of experience in getting AI coders to produce quality.
Proper engineering does not come about from the tools you use or how you use them. Proper engineering has always come from thought, and reasoning, it never was about the act of coding. It always was about the systems thinking and expressing the goals and desires that matched the requirements.
IDEs were never needed to properly engineer and in the days of AI will become increasingly less important.
Tools for planning, reviewing, and commenting on code are the future. The necessity to edit actual code is coming to an end.
Yes, that's what I said, I'm contrasting properly engineered AI code to vibe coded slop AI code, not that human written code is inherently better engineered.
I was feeling this pain also; so I switched my workflow to watching file changes with lazygit, and then switching to helix to make small tweaks.
Another option you may want to try is mux (github.com/coder/mux). It wraps the LLM in a nice interface which has the ability to do line/block comments on changes by the LLM that then goes goes into your next prompt. It’s very early stage though: v0.19.0.
How do other editors do this, if they don't use LSPs? Helix specifically choses LSP as the integration mechanism (in combination with TreeSitter) for supporting different programming languages, because it is a language-agnostic protocol and therefore only needs to be implemented once. Is there some established AI-agnostic protocol/interface? I don't think MCP would work here?
This is a distinctly Zed solution - trying to move the agent experience into the editor, rather than just giving the agent an interface with which to control and read from the editor.
Not only do the most popular editors have little-to-no incentive to implement it (they’re more interested in pushing their own first-class implementations, rather than integrating those of others), it’s much more work to integrate the evolving agent experience into the IDE than it would be to provide IDE integration points for the agents themselves.
So, I think this project would have been much more successful if it had been more focussed on keeping the agent and IDE experiences separated but united by the protocol, instead of trying to deeply marry them. But that’s not in line with Zed’s vision and monetization strategy.
It won’t be long before the big players start to release their own cloud-based editors. They’ll be cloud-based because the moat is wider, and they’ll try to move coding to the cloud in the way that Google Workspaces moved docs to the cloud. Probably with huge token discounts to capture people. If you squint, you can already see this starting to happen with Claude Desktop, which runs its agent loop on the cloud (you can tell because skills appear to need to be uploaded).
Notably, Microsoft, with VSCode and GitHub have a web-based editor advantage in this space, but no models.
It's not just Zed, Emacs has has a thriving ACP implementation in agent-shell[0], and allows for some very cool integrations[1]. There are a fair number of other clients[2] as well.
The second half of this is spot on. The now is making IDEs that can integrate with agents, not the other way around. Soon the Claude and Codex will do that for us on their hosts and the argument is it will save sending the context up.
Just watching filesystem for file changes and updating the in-memory view of the file on any change? This isn’t really relevant to MCP, though one option is to provide a different tool to the AI agent for file modifications, which would make modifications through the file editor itself.
This is non-trivial, if you want to do it efficiently. On Linux you can set up an inotify listener for individual files, but not for entire directories. This also breaks down if you are working with data on non-local drives.
Just as FYI, for people currently using firefox or want to use firefox but found its keyboard control (or plugins like Vimperator) lacking, I really recommend glide[0] highly.
I've used qutebrowser for years as I feel the keyboard controlled web is much more convenient, and there hasn't been any reasonable competition to qutebrowser. The vim keyboard control plugins for chrome or firefox don't fit the bill for me, they feel slow, are often out of focus, and quite limited.
glide fixes all of those problems, supports firefox extensions and has a really powerful and approachable scripting API. It's alpha but feels quite ready, I've been running it a few weeks full time and loved the experience.
> The MR60BHA2 is a 60GHz wave sensor that detects breathing and heartbeat patterns. Using its radar technology, it can monitor vital signs without direct contact, even through materials like clothing or bedding. You can use it for sleep monitoring, health assessments, and presence detection.
This is kind of crazy, I had no idea this was a thing. And here I have PIR sensors all over the place and hacks around those, that definitively sounds much better. Besides being more expensive and weaker range, any drawbacks for using it for motion sensing?
I agree with the article and I hold 0 crypto right now. But I still think it's amazing that I can hold something limited, something I can exchange for real money, in my head, just based on math. Sure it is extremely inefficient database, and pretty much all the real value needs to be linked with real world banking, but it does have some really unique features that makes me sad that it (predictably) turned to just scams and speculation.
Edit: and the other feature I like is that I could just attach my code to the raw banking backend. People say that anyways everybody just uses exchanges, and that's true, but if you'd ever want to connect to banking backend, you'd get buried in paperwork. With crypto, you'd just run or connect to a node.
The "currency" part is actually the only one that is not a scam, as long as you understand what it is and the trade-offs it makes.
If you do actually have a legitimate reason to use it (because conventional payment rails are not available, or you're doing crime, or need pseudonymity), it is a perfectly fine tool.
At the same time, the CO2 increase measured at Mauna Loa for 2024 was over 3.5ppm/yr, way up from the ~2.5ppm/yr seen previously this decade[0]
2025 State of the Climate report[1] said (on top of other horrible things)
> A dangerous hothouse Earth trajectory may now be more likely due to accelerated warming, self-reinforcing feedbacks, and tipping points.
I haven't seen hothouse earth mentioned in mainstream papers for a long time (decade+?), as it was deemed unlikely before.
Also The German Physics Society and the German Meteorological Society issued a joint statement warning about the possibility of 3 °C warming by the 2050s[2]
I am actually angry to people that they're irresponsible enough to vote for this without caring about others, but it feels like it was such a horrible timing for all this stupidity as well.
"In coordination with the requested terminations for Weather Laboratories and Cooperative Institutes (see OAR-10) and Ocean Laboratories and Cooperative Institutes (see OAR-19), NOAA will close...Mauna Loa"
Re: likelyness of hothouse earth scenario: I don't think that the clathrate gun hypothesis [0] was ever really off the table. It's the thing that has me the most worried about the long-term future, both for myself and my children.
> Also The German Physics Society and the German Meteorological Society issued a joint statement warning about the possibility of 3 °C warming by the 2050s[2]
All the glaciers will have disappeared too by then. Pinky promise.
I feel like democrats should make it clear that if there's still a fair election and they regain power, they'll go after both the corrupt people in this admin and entities buying favors. The current state can't be too good for the society, at least there should be a clear possible downside for being a part of it.
- Terminal search and focus (you can list kitty tabs and windows and get the window content from the socket, implementing a BM25 based search is quite easy)
- Giving the current terminal content for AI, so I can do things like run `ls` and then write "Rename the files (in some way)", and push the whole thing to LLM that replaces the command line without me having to write the full context
I even have a Codex session finder that uses codex session files to list and select the session I want, and then uses the kitty socket to find and focus the window which matches the session content
I have thought of things to do with kitty remote but have always been lazy to actually write the code. Do you have it open source by any chance for me to steal?
reply