And if not for the rise of AI it's possible that WASM as a machine-level compilation target for all languages might have happened. As much as Gary predicted he didn't see AI coming.
Not really: ASM.js became WASM. What killed the possibility of WASM being The One Way to run everything is AI... the one wildcard that Gard Bernhardt didn't predict.
I re-watch that presentation two or three times a year because it's a great example of how to give a presentation, how to structure your slide deck to complement your presentation, and a surprisingly educational tour of the permission rings architecture of operating systems.
And at some point we're going to have a period or war and our psychological attachments to old programming paradigms will be released so that we can move on to a more advanced way of doing things (but that won't stop your bank from running YavaScript for at least another 85 years).
Interesting that Colombia is currently powering more than 70% of their electrical consumption on hydropower. They currently have about 65 TWh of hydropower capacity; the total feasible generation potential is around 200 TWh. Makes then an interesting country to host such talks.
The launch of Proton Meet officially eliminates the lazy excuse that securing real-time WebRTC media at scale is "too hard" for modern enterprise platforms. Hopefully this forces the hands of Slack, Teams, and Google to stop treating E2EE as a premium afterthought and start offering it as a standard option for the modern web.
Do they think so-called AI is capable of self-awareness or abstract thought, that it's not a human-programmed mountain of if statements and strict logic?
The best way to monitor the DLQ is by setting up CloudWatch alarms on the ApproximateNumberOfMessagesVisible metric. Set an alarm to trigger when the message count exceeds 0, paired with an SNS notification to alert developers via email, Slack, teams, Pager Duty, or whatever your preferred mode of being alerted is.
In my experience Claude is like a "good junior developer" -- can do some things really well, FUBARS other things, but on the whole something to which tasks can be delegated if things are well explained. If/when it gets to the ability level of a mid-level engineer it will be revolutionary. Typically a mid-level engineer can be relied upon to do the right thing with no/minimal oversight, can figure out incomplete instructions, and deliver quality results (and even train up the juniors on some things). At that point the only reason to have human junior engineers is so they can learn their way up the ladder to being an architect and responsible coordinating swarms of Claude Agents to develop whole applications and complete complex tasks and initiatives.
Beyond that what can Claude do... analyze the business and market as a whole and decide on product features, industry inefficiencies, gap analysis, and then define projects to address those and coordinate fleets of agents to change or even radically pivot an entire business?
I don't think we'll get to the point where all you have is a CEO and a massive Claude account but it's not completely science fiction the more I think about it.