You are approaching the issue but from the other direction :)
It is indeed subtle.
It could be solvable though if someone wanted to change the current behavior, in a forward compatible way.
Hint: "Don't use pointers at all" is the requirement that you would have to relax.
That means that you cannot know whether a pointer is safe or not to be used from within an interface.
Conservatively, that means that every nil pointer in interfaces are unsafe.
Which means we should either have a way to check for nil pointers (typed or untyped) in interfaces or assert that an interface value cannot contain a nil pointer. (requires definite assignment analysis)
Actually have implemented the nil checking migration part as a POC but seems that it requires the assertion part to be tractable... That is a bit more work.
I was making the difference between engineering and development too actually.
Building react and using react being an illustration of the difference between an engineer and a dev.
It is a spectrum however, that's true.
That is not my claim.
And to be fair the claim about fsd wasn't completely wrong. It is still has failure modes but you can't argue that the tech works.
Mercedes even had demos.
That is still irrelevant to my initial point.
Not convinced. That is a very static view. You would think that the output of AI will be better AI, better energy sources and that will make AI way cheaper in the long run...
It will end up a cheap commodity that is basically free to produce.
Over the long run it is absolutely one of the best investments in projections.
I feel like crap when taking creatine...
Actually most of these purported supplements are a no go. Preworkouts would work first session then make me ultra tired, caffeine is fine as long as I 'cycle' it...
Wondering strongly if those studies are not just to sell more cheap supplements... As long as for some reason we find that it has some level of effect on most people.
It has some effect for sure but not sure it is that positive...
Besides, I don't know if it helped jump start the process or not but I build muscle either way, on little protein, no creatine... Carbs seem to be more important actually.
Anyway, let me take a scoop of creatine to try again, even though I am unconvinced... Hope sells... :s
(I think hydration levels are more important and that is not solved by drinking low mineralized water although I find it has better taste, it gets rid of tiredness)
That's the thing, a programming language is not something static, it evolves.
For instance, people are working on adding generic methods for the next release cycles.
And what the article complains about is by design, not a bug. It is a tradeoff made to avoid bloat.
In any case, given the future possibilities, I'd bet on Go.
If anything, the language is just slower to evolve because every language change means the tooling needs to catch up. And now llms would have to catch up.
ChatGPT is still using Go 1.23 for instance...
We are speaking about incidental complexity vs. essential/inherent complexity.
Inherent complexity is dealing with an XML format that is prone to vulnerabilities because people don't know how to parse properly or the protocol was badly spec'd back in the day in the case SAML for instance.
Or ill-defined scopes, etc...
Having had the chance to try and implement libraries to interface with those systems a couple times, most people agree that implementations are far from perfect or streamlined. We call this incidental/accidental complexity.
I wonder if it is not people being notoriously lazy or clueless at an astonishing degree. How often do you hear that password were saved in plaintext? Surprisingly high in this day and age.
People not knowing what salt and pepper is... Vulnerabilities almost as if on purpose...
Perhaps it is actually not THAT hard but just like error handling, people don't want to do the unsexy parts and want to delegate those tasks to someone else perhaps.
There must be a behavioral pattern there...