Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Oh, come on! (Score 5, Insightful) 436

by salgiza (#32664052) Attached to: Developers Expect iOS and MacOS To Merge
The article is about how some of the APIs (UIKit, mainly) in iOS are probably going to be included in future versions of MacOSX, and suddenly the summary is about MacOSX becoming a big iPhone full of DRM! Slashdot: where not even the editors bother to read the articles! (Either that, or someone hates Apple too much...)

Comment: Re:User Inertia (Score 1) 139

by salgiza (#29342593) Attached to: Google Apps Not the DC Success Many Believe?

Although it's Firefox are Safari are supported in the latest version of SharePoint, you can't edit documents directly from the portal (and probably Excel Services won't work either, but I haven't tried it). Taking into account that document libraries are the most useful part of SharePoint, and they only work in IE, well, yeah, it works, but you wouldn't use any other browser unless in an emergency.

Moreover, I pity the poor programmers currently involved in SharePoint. Have you seen the HTML that it generates? It was written for IE6, in quirks-mode, and it continues that way. That means that everything having to do with HTML and CSS has to be written at least twice, because padding, :hover events (on non-A elements) and many other things we now take for granted are either not available in quirks-mode, or work differently across browsers.

And if you develop anything on top of SharePoint, well, you don't have the option to use valid HTML, so welcome back to the year 2000! In the end, the overhead cost of developing for multiple browsers in this mode means that most customers are quite fine if their custom apps (that work on top of SharePoint) only work on IE. In fact, many useful third-party addons (ej. Nintex) only work in IE.

Hopefully, SharePoint 2010 will fix this, and I'm quite sure that SharePoint is going to be a great product some day. But just right now, it sucks in too many areas, and it has a major handicap to overcome: shared folders are easier and faster to use.

Nothing happens.