HN user

Dockson

235 karma
Posts3
Comments28
View on HN

This doesn't really follow the usual battery scam pattern, does it?

Like, EEStor or Nikola with big claims, timelines pushed years out, raise a ton of money, delay forever. Donut announced at CES and said bikes ship Q1 2026 which is weeks from now. They've raised ~€25M total (QuantumScape has burned through $1.5B+). And apparently they're not doing a big fundraise right now either.

If it's a scam it seems like a really bad strategy? You're basically setting a timer on your own credibility.

I've been reading around and the thing I keep landing on is the Nordic Nano connection. They're a Finnish nanotech company Donut invested in, and they published specs for a "bipolar electrostatic capacitor" with basically identical numbers - 400 Wh/kg, 100k cycles, fireproof. Does anyone with more battery knowledge know if this could be some kind of supercapacitor hybrid being marketed as a solid-state battery? The VTT report confirms fast charging works but doesn't say anything about energy density, cycle life, or what this thing actually is.

Seems like the energy density and cycle life reports (supposedly coming in the next few weeks) are going to be way more interesting than this one.

Just want to heap on with the praise here and say that this was definitely the best experience I've had with any tool trying to add monitoring for a Next.js full-stack application. The Client Sessions tab where I, out of the box, can correlate front-end actions and back-end operations for a particular user is especially nice.

Great job!

Hmm, then I must have come off wrong. That being my final goal does not mean that I care less for what I do. I try to find meaning in my every day work by optimizing for the value I create for the end user and can not be less motivated than when I only work on something because "I have to" or it "being the only way".

Thank you for your insight, it is great to get to hear from someone in the trenches and an "average SAAS Joe" as you call it. The keyword in my opening statement is "eventually" as I do understand the need to hustle initially, potentially for a long time. When work is fun it is no longer work, as someone smart once said. What is hard to motivate for me is doing all that work for (mostly) someones else gain and for a product that I personally wouldn't work on on my own time, like I do now in my day to day. Thanks again!

Honestly, as long as the wages before tips are fair, then there's nothing wrong with tipping as a concept.

Do you wish tipping as a concept would spread to all customer-facing industries?

Fundamentally, it cannot work well because the whole premise of GraphQL is to allow clients to request as many different permutations of the data as they want.

What kind of client are we talking about here? If you run a web app then all your queries will be predefined in the code which means that the only variables are just that, variables. If you are talking about other apps consuming your GraphQL API then yes, they can request whatever permutation they want. But realistically, what client that consumes your API would keep changing the shape of their request all the time? And if they do then just revoke their access. Abusive clients is not a problem exclusive to GraphQL.

We do not rebuild the tower of abstractions for every site that uses them. I do not personally implement React from scratch when I use it for any of my sites. I get all of the benefits for none of the effort. You do not seem to acknowledge factors other than straight up performance, as is evident by what you are picking and choosing from my comments, so obviously it is not attractive to you.

Real life is not code golf. We do not build things entirely for ourselves. We build things for our employers, for our co-workers, for our family members and for our friends. We build to create value for someone and value is not a one-to-one correlation with the weight of a site in KB.

If I can make it easier for me and anyone working with my site in the future by sacrificing 50-150 KB then I will take that deal any day of the week. That is what abstractions are for. That is why we do not work in byte-code. We pay for convenience in clock-cycles and disk space.

You put "improve" in quotes as if instant page navigation without flickering is somehow worse than the alternative. Browse around this [1] website and tell me it is not a better experience than your bog-standard html + vanilla js concoction. Also every time this is brought up the developer/content editor experience is entirely neglected, when in reality it is a big consideration when creating something other than your own dev-blog that you update once a year.

[1] https://reactjs.org