I'd like him to make a more firm next step. He sometimes brings up some of the difficulties he has expressing things that would be simple in another language. I point this out. He understands that but still prefers to work in Scratch. One factor may be that he has a social network on Scratch.
Congrats on the launch! As an iOS dev who dabbles in ML, I'm having trouble understanding what you mean by "data applications" and who this is for. I'm guessing it's targeted at teams that crank out lots of small apps and therefore investment in learning your platform would make sense? It would be helpful if you gave clearer explanation of the use case(s), beyond the generic "customer data platforms, fintech companies building lending and risk engines, and AI companies building prompt engineering pipelines" (which, tbh, means nothing to me).
Our target audience are data engineers and scientists who are stitching together business apps like CRMs/email marketing tools etc, and building proprietary automations and analytics in between them like generating a customer health score and actioning on it.
One of the problems we’ve intended to solve is the separation of analytical systems (like all your pipelines for counting customers and revenue) and your automations (like do something on customer signup event).
I don't think it meshes well with Spanish wildfire stats [1]. I can't see any serious trend there, definitely nothing like California. The main difference is that they manage their forests and do prescribed burning.
Lambda’s deferred tuition model is life-changing for the people who can make it through. Many of their students come from backgrounds and life situations where no other option is really possible. That alone makes me want to root for the whole approach.
It’s true that the teaching and curriculum are uneven, and i wish they were less so, but you could say the same about many colleges.
There is a moral hazard here, but the reality is that we’ve passed the point where emissions reductions alone can get us where we want to be. We will need both reductions and removal.
Unlike many commenters here, I came to praise Swift. Of course there will be regrets -- nothing's perfect -- but on the whole I think the designers (and community) did an amazing job with Swift. I say that after having written multiple apps in Objective C -- I would never consider going back.
Optionals and null safety, first class enums, first class functions are just lovely in swift, all in a language that is super readable when well-written.
