It's the UX, deliberately omitting information or not. There at least used to be some toggles for example without any indication that they mean anything other than a minor load balancer configuration change, but caused I think $200 month bill addition. No indication at all that they have a meaningful monetary impact.
I'm being rather snarky here, but the main point of front-end JS UI frameworks is to exist and to survive in their environment. For this purpose they have evolved to form a parasymbiotic relationship with others in their environment, for example with influencers. The frameworks with the best influencers win out over older ones that do not have the novelty value anymore and fail to attract the best influencers.
Next is the Microsoft Sharepoint of the JavaScript world. It’s a terrible solution to just about anything, and yet gets crammed into places and forced on people due to marketing-led decision making.
My 10 minute Next build was replaced with a 1 minute 30 second Vite build.
And such an extrodinary different is usually holding the tool wrong, but Next has years old open issues for many of the causes here (like forced output tracing) and has just ignored them. Possibly because the Next team's preferred deployment environment isn't affected?
The "just retry" approach is truly bothersome. I think it is at least partly an organizational issue, because it happens far more often when QA is a separate team.
I think not so long from now the exotic meal experience for the young ones will be real grilled chicken that looks like a chicken. Like zebra or crocodile meat was for us northerners.
From my own little box I think that that if lab grown meat was available and affordable, I would never eat a bit of real chicken, pork or beef again. I know veganism is an option too, but... I grew up with meat and it's very difficult to give up.
Have you tried tempeh? It solves 95% of my chicken craving since I found the right recipe and spices. It's also cheaper, nutritious, faster to cook and almost no processed.
I have the same problem. The "What It Is" section starts with "Mycelium is a Clojure workflow framework built on Maestro" and that's a bit generic. Maybe something to test some AI generated code and then test if the tests are tested enough using Closure, but I'm not entirely sure.
The main question that is not obvious, is what should I use it for?
This is far more brilliant than I thought. I know my purpose now, "AI" told me. It's to drink wine and eat macaroni!
The only problem is that larp as ai comes back with "no work yet. check back later :(" a lot, but if you run out of credits, that's it. So... Did everyone run out of credits? I feel like there's something up with it.
I'll take one addiction and a possible oral cancer for the company, thank you so much. No, I understand it's not guaranteed, but I am seriously flabbergasted by the careless actions of some companies...
I think the more generic stream concept is interesting, but their proposal is based on different underlying assumptions.
From what it looks like, they want their streams to be compatible with AsyncIterator so it'd fit into existing ecosystem of iterators.
And I believe the Uint8Array is there for matching OS streams as they tend to move batches of bytes without having knowledge about the data inside. It's probably not intended as an entirely new concept of a stream, but something that C/C++ or other language that can provide functionality for JS, can do underneath.
For example my personal pet project of a graph database written in C has observers/observables that are similar to the AsyncIterator streams (except one observable can be listened to by more than one observer) moving about batches of Uint8Array (or rather uint8_t* buffer with capacity/count), because it's one of the fastest and easiest thing to do in C.
It'd be a lot more work to use anything other than uint8_t* batches for streaming data. What I mean by that, is that any other protocol that is aware of the type information would be built on top of the streams, rather than being part of the stream protocol itself for this reason.
Yeah it makes sense to me that the actual network socket is going to move data around in buffers. I'm just offering an abstraction over that so that you can write code that is wholly agnostic to how data is stored.
And yes, because it's a new abstraction the compat story is interesting. We can easily wrap any source so we'll have loads of working sources. The fight will be getting official data sinks that support a new kind of stream
I've been wondering too, what the solution would be. IF the bots were actually helpful, I wouldn't care, but they always push an agenda, create noise, or derail discussions instead.
For now maybe all forums should require some bloody swearing in each comment to at least prove you've got some damn human borne annoyance in you? It might even work against the big players for a little bit, because they have an incentive to have their LLMs not swearing. The monetary reward is after all in sounding professional.
Easy enough for any groups to overcome of course, but at least it'd be amusing for a while. Just watching the swear-farms getting set up in lower paid countries, mistakes being made by the large companies when using the "swearing enabled" models and all that.
reply