3,280 karma · joined July 8, 2016
1. Growth is not a must have for an economy, as long as it is sustainable, so even if it is a problem, which is highly arguable, it’s not really a problem like you’re positing.
2. Can you be more specific about what the next Eurozone crisis will be? It’s not useful to be vague and to scaremonger.
There is a distinction between getting data from an ISP and getting it via your use of their portal, but I’d argue it’s without much of a difference in reality.
I'll believe it when I see it. Making hardware is much more complex than making software, and 2 years is a long time given the iffy market circumstances right now, so let's see if it's materializes, and if it does...
> but it’s rumored to be screen-free and “roughly the size of a smartphone.”
Let's see if it turns out to be another Humane situation.
So on the language level it doesn’t directly change the behavior, but it is possible to use the types to affect the way code works, which is unintuitive. I think it was a bad decision to allow this, and Python should have opted for a TypeScript style approach.
I do wonder if all of the kinks will be smoothed out in time. Not a lawyer too, but the timeline to create the longer list is a bit tight, and generally feels like we could see an actual rejection or at least a stretched out process here that goes on for a few more months at least before approval.
So it doesn’t matter if Spotify passes on 70%, most artists aren’t going to see any substantial portion of that, label or not.
The biggest issue is that the complexity is self-inflicted. The term middleware has a pretty well understood meaning if you've worked with basically any other framework in any language: it's a function or list of functions that are called at runtime before the request handler, and it is assumed those functions run in the same process. The fact that Next.js puts it on the edge and only allows one is breaking that assumption, and further, most applications do not need the additional complexity. To go back to your toolbox analogy, more tools mean more complexity (and money), so you wouldn't get a new tool simply because you might need it, you get it because you do need it, and the same applies to edge functionality. If Next.js wants to allow you to run code on the edge before your app is called, that's fine, but it should be opt-in, so you don't need to worry about it when you don't need it, and it shouldn't be called "middleware".
Is there a reason they spelled out 1630s, like a style guide?
> Perhaps it's time to go with another method entirely.
What method would you suggest here?