If you haven’t heard yet, Apple (Jobs) just announced that Safari will be available to Windows users. This is important for 2 main reasons.
First of all, web developers will be able to test their applications in Safari now, which means they can assure a consistent design across browsers. People won’t have to have a mac to test how their sites look in one.
Second reason is related to the first one. Safari is the browser for the iPhone, which means that Steve Jobs has opened a way for developers to reach it. Not only Apple developers, but any web developer, and they can test their applications in Windows or Mac, they won’t need to buy an iPhone for development purposes.
There are a few “bad” things to take in consideration. Since Safari is now available in any platform, it will get the atttention of hackers, malware, spyware, etc. It is a start point for Mac holes to be exploited. This is also re-ignite the old “IE is unsafe just because it has more users” discussion. Let’s not forget Safari is in the iPhone too, why can’t it be a target? A omnipresent web browser sounds like a nice juice pray for hackers.
Now, on a user level, I don’t think Safari will become a leader, I don’t think it will take a lot of market share from IE o FF. I think it will remain a browser to enable developers to access several platforms, unless you are a mac fanboy trapped in a windows shell.
Update: A person from Dekoh just replied to this post explaining all these doubts.
Today the Dekoh guys have a post on their blog with a comparison of their product and Adobe Apollo. Some of the points are not completely clear to me:
- RSS Support: Dekoh Yes, Apollo No. What does this mean? What kinda of RSS support will Dekoh have? For what I know you can easily build a RSS reader, or even a routine to parse XML (RSS feeds).
- Broswer supported: Apollo None. I don’t really think so, is not that they don’t support any web browser, they just use a diferent webkit. What does this exactly mean? Beats me. What I do know is that this webkit has been used in Safari and KHTML. So “none” seems a bit innacurate to me.
- Reusable Widgets: Dekoh Yes, Apollo No. What are these widgets Dekoh mentions? Prebuild out-of-the-box widgets? Isn’t it a platform? Can’t developers make some for the Apollo platform? What does “reusable” exactly mean to Dekoh? Can I use them on Netvibes?
- Bundled Database: Dekoh yes, Apollo No. Other Databse support: Dekoh though JDBC, Apollo No. Now, can Dekoh connect to SQL o MySQL? By reading this I would say yes. Can Apollo? It could. From the Apollo FAQ:
- “Will Apollo Applications be able to communicate directly with databases?
Apollo 1.0 will not have built in support for communicating directly with databases. However, it will be possible to write Database drivers in ActionScript (leveraging binary or XML sockets), which would allow Apollo applications to communicate directly with a database (both local and remote). “
- Web 2.0 features like sharing, tagging, commenting; Share from desktop, applications or content with personal friend network: Dekoh Yes, Apollo No. Mmm… Ok, I don’t understand this. Tagging, sharing, commenting? Aren’t those feautres that could be built in any platform? Again is this out-of-the-box support for these?
Like these, there are other unclear points in the comparison. You should probably see for yourself and decide. And then comment here 🙂
PS: I first read about Dekoh here.
Netvibes has opened the registration for the preview (soon as ready) of their Universal Widget API (UWA) announced last week at FOWA (Future of Web Apps).
This API is aimed to help delopers write widgets once for all platforms (Netvibes, Google, OSX, Vista -¿?, etc.)
I hope it supports webtops too.
Today I read a post in Pearsonified about how to modify your wordpress CSS stylesheet. I would like to talk about it with a much wider approach, based on my experience with Sharepoint Portal Server 2003.
Sometimes, as a web developer you have to work with CSS stylesheets handed by some other web developer, or the guy that was previously in your seat doing what you are doing now. Sometimes they have done an amazing job, sometimes you just thank god you never met the poor devolved b*st*rd.
This is how the post I mentioned above says you should work, which is also how I’ve been working with Sharepoint: Don’t modify the current stylesheet, add a new one with the modified styles. If you can’t add a new reference (say you don’t have access to modify html code) add the new styles at the bottom of the current stylesheet with a HUGE comment indicating that it is your modification.
What I do is: Find what you want to chnge in the HTML code. Look into it and find out what styles are applied to it. Find the style in the stylesheet and copy it. Paste it along with all the modifications and start messing with it.
- Say you need to keep track of these changes, having all of them in one place is the best way to do so.
- If you make a change and all of the sudden everything goes upside down, you can always just remove the last change, or remove all your changes with one press of *delete*.
- If there is no “template” for the pages then you will *only* have to add the references to each page to make them all look the same.
Today I read a post on Scobleizer about Microsoft vs Adobe . I agree and disagree.
He points out two important things. The first one is that Microsoft is facing a lot of competition when it comes to development tools, languages and all. That is true. I like Microsoft, but I can see them loosing a lot of mindshare.
The second thing he points out is that Adobe is the one gaining terrain from Microsoft. That is also true, but I think here is where he misses one point. I have always thought (and found that my developer peers agree) that Microsoft has a maturity level that Adobe (or Macromedia when it was) hasn’t reached yet. I think Microsoft has a better understanding of the developers, has better IDEs and it is easier for a newcomer to get started with VB than Actionscript I’m sure. And while Adobe might be more innovative and have more momentum, you cannot ignore the years Microsoft has developing and perfectioning Visual Studio and their Framework.
I remember when I tried Flex how HARD it was to find solutions on the internet. I gave up on it. With Microsoft you can trust the “I’m feeling lucky today” button when it comes to solution. And the VS2005 IDE is YEARS ahead any IDE Adobe has (Dreamweaver included).
This might (will – I think) change with time. What I would’ve loved seen is Microsoft embracing Flash instead of competing with it (just like Borland did with their .Net Edition od Delphi), using VB instead of ActionScript would’ve been great for both sides.