I don't know when the sharks will move in, but this final sentence of the article points to a broader problem with climate change induced migrations: species don't move at the same pace. Plants move much slower than insects, and insects faster then their predators. This will create imbalances, which will lead to big problems with new diseases and pests.
Eventually things will re-calibrate, but a lot of species may go extinct and we could see a very long period of reduced biodiversity. It takes a long time to adapt.
Even remembering alters the memory being recalled, entirely unlike how computers work.
IE has been dead and buried for ages. Edge doesn't have even close to the same market share and is based on Chromium.
They build more and more of their own UIs on Electron.
I honestly don't remember when they tried to snare someone to use proprietary extensions to something open. I probably have missed a few instances.
Long story short: MS isn't a saint. They are a business. And they have behaved relatively nice for so long that some young adults don't know any other side of MS now.
You can make a product that pleases its users, or just cater to the interests of the ones with the buying decision, for enterprise users they are almost never the same. Microsoft, like Oracle, leans heavily on the second strategy. Their developer tools are often (not always) an exception to this principle. I think this is the true reason Microsoft is so disliked as a brand.
Just define your API interface as a collection of types that pull from your API route function definitions. Have the API functions pull types from your model layer. Transform those types into their post-JSON deserialization form and now you're trickling up schema from the database right into the client. No client to compile. No watcher to run. It's always in sync and fast to evaluate.
Plus, openapi can be useful for other things as well: generating api documentation for example, mock servers or clients in multiple programming languages.
I'm not disagreeing with you, what is best always depends on context and also on the professional judgement of the one who is making the trade-offs. A certain perspective or even taste always slips into these judgement calls as well, which isn't invalid.
I agree with the commenters above that it makes the critique fall flat. The author is saying “This thing is so frustrating and harmful it makes me want to stop working in a field because of it. Oh, by the way, I use this tool myself for other things, and will indeed pivot to contribute directly to them”.
Instead, I see it as a deeply personal rant about the state of affairs which he considers inevitable himself. That is why he leaves the ship.
Before AI slop, there has always been just the agile slop of the bare(ly) minimum product, good enough to woo the ones making a buying decision, or at least until the career sharks have moved on to the next thing. That kind of slop has always been there and everywhere actually. Its called capitalism, or consumerism. The trick is to work for a place that isn't squeezed too hard, because its still in the investment phase or because it just earns money on its own merit.
AI will certainly transform things, just like higher level languages and frameworks have done so. Maybe programming without AI will be the 'micro optimization' of the future: something that is still there and valuable, but only sometimes and only in a certain niche. Slop is eternal, it just has a new face and a new name.
This blog to me is a nice personal rant about a smart young developer coming of age, trying to find his way and guard his ideals or standards against the onslaught of consumerism, just as ambitious young developers always have tried to do.
The maintenance burden shifts from hand syncing types, to setting up and maintaining the often quite complex codegen steps. Once you have it configured and working smoothly, it is a nice system and often worth it in my experience.
The biggest benefit is not the productivity increase when creating new types, but the overall reliability and ease of changing stuff around that already exists.
I would be torn if I had to write intro documentation like this. On the one hand, people demand code examples, but on the other hand, the majority of people reading code examples will nitpick minor pet peeves in the syntax and completely detract from the actual new ideas and concepts that go way beyond just the syntax.
I found the descriptions of the concepts very enlightening and I honestly think they gave me a better idea of what the language would “feel like” to program in than a code example (or a description of the syntax) would have.
In theory, syntax should be interchangeable. It's conceivable to parse a syntax into an AST and reexpress it in another syntax without changing the AST. In practice, this is not done for many reasons (incl. tooling like diffs) but a big reason is that individual bits and bobs of the syntax are tied to the new concepts in subtle ways. There could absolutely be multiple syntaxes for the same concept, but if the concept is new, even in small and unobvious ways, then no prior existing language’s syntax will map it exactly. For this reason, a code example can't really express the new concept, especially if the syntax is superficially similar to another language that doesn't actually have that concept.
We are several years in now. These statements are actually pretty hurtful for people who have been through a lot. It's like saying you could beat cancer if you only wanted to, or if you didn't think all those negatives thoughts, you wouldn't be so ill now.
Not only is it suggesting that this misery is in some way 'your own fault', but it also implies that it isn't real, or serious, at least not in the same way other diseases are.
And yes, psychological problems are real too, indeed. But it is not the same. The origin narrative around a disease does in fact matter for people trying to cope with it, and how others see you, for insurance, for politics and medical care. Please be more respectful about it.
It would be like saying, "Don't use Laplace transforms because he did some unsavory thing at some point in time."
Maybe it's more like: Laplace created awesome things, but let's be fair and also put in his wikipedia page a bit about his political shenanigans.
A lot of of so-called geniuses, especially the self-styled ones with some narcissistic traits, get away with being an asshole. Their admirers have different norms for regular, boring people. I don't think that is fair or healthy for a community.