It would be reasonable to include in the letter how much the debt is and the date of that perhaps. And with good intentions, an alternative way of resolving the issue. This letter is not friendly. I get letters with the same spirit and those bug me a lot.
While the introduction section was informative somewhat, this is really written to promote a commercial service at the end. And it's badly out of place.
A question, I was wondering if you happen to know whether there is a long term commitment from these orgs/companies to support WebGPU, say for at least 10 years?
Thank you for the insightful comment. I'm not sure you're not my target audience. In summary I gather you find the extremely rigid system of these builder inconvenient. I guess you had to consult the docs to figure our how to create that link for your son, and a good chunk of that 10 minutes was spent on this. Am I correct?
I'm thinking if my builder can make a software engineer build website quicker with a high level of abstraction that's exclusively mutual with others being able to do so. I've been researching intuitive interfaces, as my hypothesis is that the interface is the bottleneck. Thank you again for your comment, it is helpful!
I have heard this opinion from some other people as well. I'm wondering what are the particular needs that call for a custom website vs. staying with wix/squarespace or another similar service?
Re your last question, I don't think so. It's just an attractive application, hidding neural network weights is valuable in some settings, for instance.
The author appears to forcefully prove his theory about reddit in order to sell a website he's an advisor at. I wish the disclaimer was at the top of the text.
I work at a startup that uses edge AI. There are many factors that edge is preferred over cloud. Security is one. Latency is important in many cases. If the internet connection is another dependency for a critical system, it can be a big headache. Once you start working on a real-world project you run into these issues. In return you give up monitoring the data and model that can be done with cloud deployment.
Let's go one step higher, keeping track of the state by a state machine. When designing/coding with the correctness on mind, I try to stay focused, and not think of edge cases. Or I will end up spending more time coming up with edge cases and what can go wrong. I'm not lazy, I'm almost certain of that. But I do feel time is a limited resource and want to add more value per hour spent working. Maybe, this is more the case of if it can be automated then automate it.
My summary of this blog post: plenty of random input data can reveal code bugs. The kind of bugs that would take probably a lot of time of think of and write unit tests for, in advance.