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
The post on the USV blog about the challenge of creating native mobile apps (meaning ones that can on exist on the mobile platform) has created a lively discussion with by now over 60 comments. A good chunk of that discussion was about the relative merits of just sticking with the mobile browser versus developing apps. For instance, Fred observes:
I’m a big fan of the mobile browser too but it does seem like the prevailing delivery package today is the mobile app, not the browser.
That and a conversation yesterday at lunch got me thinking: Why doesn’t Android make the browser an equal citizen for app development? All that would be needed are some Javascript extensions to give access to the phone capabilities, in particular location, the camera, making calls and cross-app communication (including access to built-in apps such as the address book).
I have in the past written that this would be the best (possibly only) way to beat the iPhone and had been hopeful for the Palm Pre. But all along in those posts I missed the bigger question. Why isn’t Google pushing the HTML5/Javascript model for Android? After all, Google is demonstrating what can be done with Javascript in its mobile version of gmail and I even posted about how that was a good thing for the Pre. Google is also really showing off the capabilities of HTML5 with Wave.
So does anyone know why Google would not completely embrace Javascript/HTML5 as the app delivery model for Android and pioneer any missing capabilities (such as camera access)?
![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=82b2d4a7-600c-4ea5-bbd7-07c56aec812a)
The post on the USV blog about the challenge of creating native mobile apps (meaning ones that can on exist on the mobile platform) has created a lively discussion with by now over 60 comments. A good chunk of that discussion was about the relative merits of just sticking with the mobile browser versus developing apps. For instance, Fred observes:
I’m a big fan of the mobile browser too but it does seem like the prevailing delivery package today is the mobile app, not the browser.
That and a conversation yesterday at lunch got me thinking: Why doesn’t Android make the browser an equal citizen for app development? All that would be needed are some Javascript extensions to give access to the phone capabilities, in particular location, the camera, making calls and cross-app communication (including access to built-in apps such as the address book).
I have in the past written that this would be the best (possibly only) way to beat the iPhone and had been hopeful for the Palm Pre. But all along in those posts I missed the bigger question. Why isn’t Google pushing the HTML5/Javascript model for Android? After all, Google is demonstrating what can be done with Javascript in its mobile version of gmail and I even posted about how that was a good thing for the Pre. Google is also really showing off the capabilities of HTML5 with Wave.
So does anyone know why Google would not completely embrace Javascript/HTML5 as the app delivery model for Android and pioneer any missing capabilities (such as camera access)?
No comments yet