Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...
Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...
Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
>400 subscribers
>400 subscribers
Share Dialog
Share Dialog
Of course the big news yesterday was the (one day premature) announcement of Google Chrome, Google’s much rumored browser. I am looking forward to trying it out today. Based on the comic strip Google used to describe it, Chrome has some nice innovations in it. First and foremost are the use of processes to isolate tabs and significant improvements to Javascript execution. The fact that Google released Chrome as open source is positive, but I wonder whether it would not have been healthier if this innovation had come through the Mozilla Foundation and Firefox. Would be interesting to know if there was any attempt by Google to get Mozilla to incorporate these things that were rebuffed. That would shed some light on Google’s motives in releasing their own. The most likely sticking point for Google could be around Gears, which is crucial for making the Browser a real application execution environment with offline capabilities. While Gears itself is opensource, I believe that Google controls the API and its evolution. This has the biggest potential impact on other companies (and not just Microsoft) that deliver web apps. Google’s willingness to have the Gears API be subject to some kind of community or standards process will be fairly important.
![Reblog this post [with Zemanta]](https://img.paragraph.com/cdn-cgi/image/format=auto,width=3840,quality=85/http://img.zemanta.com/reblog_e.png?x-id=090daa41-64a3-4a14-a1d8-1e84db222fe6)
Of course the big news yesterday was the (one day premature) announcement of Google Chrome, Google’s much rumored browser. I am looking forward to trying it out today. Based on the comic strip Google used to describe it, Chrome has some nice innovations in it. First and foremost are the use of processes to isolate tabs and significant improvements to Javascript execution. The fact that Google released Chrome as open source is positive, but I wonder whether it would not have been healthier if this innovation had come through the Mozilla Foundation and Firefox. Would be interesting to know if there was any attempt by Google to get Mozilla to incorporate these things that were rebuffed. That would shed some light on Google’s motives in releasing their own. The most likely sticking point for Google could be around Gears, which is crucial for making the Browser a real application execution environment with offline capabilities. While Gears itself is opensource, I believe that Google controls the API and its evolution. This has the biggest potential impact on other companies (and not just Microsoft) that deliver web apps. Google’s willingness to have the Gears API be subject to some kind of community or standards process will be fairly important.
No comments yet