andix

23 ms·

481.
by andix 1y ago
It suggests a way more ridiculous fix. As mentioned by other comments in detail (security patches for transient dependencies, multiple references to the same transient dependency).
482.
by andix 1y ago
Sure, without package managers. It's also not about fully reproducible builds, it's about a tradeoff to get modern package manger (npm, cargo, ...) experience and also somewhat reproducible builds.
483.
by andix 1y ago
Lockfiles are essential for somewhat reproducible builds. If a transient dependency (not directly referenced) updates, this might introduce different behavior. if you test a piece of software and fix some bugs, the next build shouldn'
484.
by andix 1y ago
The old asp.net was not only horrible in regard of deployment (iis/windows). The whole thing was a mess. It might've been innovative around 2005, but it was completely scrapped in ~2016 for a good reason.
485.
by andix 1y ago
It used to be much more modular back in dotnet core 2.x. It was just too complex for most people to wire up everything themselves. You needed to install a lot of nuget packages, add a lot of middlewares. In the end 95% of the projects added
486.
by andix 1y ago
Yes, in my opinion. But also objectively it's really good for many things. That's the reason I asked the question "why?". It's probably much slower (asp.net got performance/memory optimized to a ridiculous exte
487.
by andix 1y ago
I think you can just pick the components you really need via nuget reference. And start/stop the web server as you like. The full asp.net out-of-the-box experience is tailored to the most common use case, which is a plain web service.
488.
by andix 1y ago
This really depends on the prompting. I experienced it multiple times that claude code couldn't figure out how to fix a bug and just gave up. Instead of getting stuck in an infinite loop.
489.
by andix 1y ago
There used to be Nancy, but it got pointless to compete with asp.net core.
490.
by andix 1y ago
In total. Just compare different web frameworks by performance, flexibility, features and so on. Whatever you compare, ASP.NET Core will probably end up in the top 20%.
491.
by andix 1y ago
No modern dotnet web framework requires nginx or iis.
492.
by andix 1y ago
But why? ASP.NET Core is one of the best web frameworks, extremely modular and flexible. It's low level components (http server, routing) can be used as a foundation for new web frameworks.
493.
by andix 1y ago
Coding with AI agents is very similar to working with junior developers (or even other developers) in a team. Someone needs to give the project direction, keep the code organized, suggest refactorings, and many more things. I guess it'
494.
by andix 1y ago
Probably both. I think ChatGPT wouldn't have found the issue by itself. But I noticed some specific things, asked for some tutoring and then it helped my to find the issues. It was a team effort, either of "us" alone wouldn&#
495.
by andix 1y ago
Many humans tell you bullshit, because they think it's the truth and factually correct. Not so different to LLMs.
496.
by andix 1y ago
Absolutely. I used to have a lot of weird IPv6 issues in my home network I didn't understand. ChatGPT helped me to dump some traffic with tcpdump and explained what was happening on the network. In the process it helped me to learn man
497.
by andix 1y ago
I don't really get how those 24/7 agents should work. Claude code is the first tool that gives me really good LLM code, but it needs A LOT of guidance. I even interrupt it often, to stop it following through on bad ideas.
498.
by andix 1y ago
Some people claim we already reached peak-LLM. It's cheap and powerful right now, in the future it might just get more expensive, or worse quality for the same price.
499.
by andix 1y ago
Yes, but for most things it's not significant. For example Stack Overflow used to handle all their traffic from 9 on-prem servers (not sure if this is still the case). Millions of daily users. Power consumption and hardware cost is com
500.
by andix 1y ago
Let's hope that's true, and not some statistics trick.
501.
by andix 1y ago
I guess you need to get used to it. LLM token usage directly translates to energy consumption. There are also no flat fee electricity plans, it doesn't make any sense.
502.
by andix 1y ago
This is a very common usage pattern, I don't think they will restrict that. The daily limits are probably there to fix the account sharing issue. For example I wanted to ask a friend who uses the most expensive subscription for work, i
503.
by andix 1y ago
Using the DOM APIs directly? Please do that. Have fun!
504.
by andix 1y ago
Not reloading the document via HTTP while updating the content is the definition of a SPA.
505.
by andix 1y ago
Latency might even be more relevant than bandwidth. Especially if it's a good SPA, that uses optimistic updates (or sync), and some kind of caching for fetching data (tanstack query or similar).
506.
by andix 1y ago
I guess you never worked on a complicated web app that was 100% jQuery, because web frameworks were not a thing yet.
507.
by andix 1y ago
Imagine Gmail, ChatGPT, Slack, and so on as server side rendered websites, but with smooth transitions. This wouldn't work at all. Let's take slack as an example. We had those chat websites 20 years ago. The thread was in it'
508.
by andix 1y ago
Exactly. I remember the times when webmail clients were SSR applications. Roundcube and Gmail were game changers. Webmail finally felt smooth and usable. Web shops are somewhere in the middle, they need a little bit of interactivity for the
509.
by andix 1y ago
This reads more like "ditch Next.js" for traditional SSR. A good SPA has a lot of benefits. Because it can be interactive like a native app. It can only use those benefits, if it is interactive to some extent (like gmail or google
510.
by andix 1y ago
Journals could fix that. They could create a category null results and dedicate it a fixed amount of pages (like 20%). Researchers want to be in journals, if this category doesn’t have a lot of submissions it would be much easier to get pub

More ›