Sanjiva Weerawarana is pretty angry at Tim Bray. Read if you're in the mood for a little useless war …
One thing I'd note - Sanjiva writes:
REST is now beyond the peak of the hype curve and is sliding down. Waay down.
REST is now being seriously hyped, and it will eventually follow the inevitable curve – no objections (even though I saw things differently little over half a year ago). But I disagree it's beyond the peak already, on the contrary: it's still going way, way up.
For the record, I don't think the hype has got much to do with actual technical facts, positive or negative. Also for the record, I don't think users in general accept REST has won and the SOAP stack is a failure – in fact, most of them still don't know there are any doubts about how great WS-* is.
Still, I can't resist to respond to Sanjiva again:
Oh yeah we support both WS-* and RESTful services. However, they won't meet the RESTafarian fanatics like Tim Bray's coolaid drunkenness level of REST ..
You mean you don't like people to point out that Axis2's "REST support" has got nothing to do with REST? ;-)
Here's a very good summary of the problems when trying to align the WS-* and REST models:
IMO the real underlying problem is that as long as programmers expect to write a class and flip a switch to get a service or one or more RESTful resources then we have nothing really but RPC masquerading as something else. Both resource and service advocates would be well-off in trying to move the developer community to get past the “class is all I need” stage. If REST is successful in getting developers to get their hands dirty more power to it.
In einem umfangreichen Bericht an das Bundesverfassungsgericht (BVerfG) hat der Chaos Computer Club (CCC) die Auswirkungen der Strafrechtsänderung des sog. Hackerparagraphen untersucht. Der CCC kommt zu dem Ergebnis, dass der § 202c StGB ungeeignet ist und sogar dem geplanten Ziel des Gesetzgebers zuwiderläuft.
Eine wirklich fundierte Stellungnahme, so weit ich das nach einem schnellen Darüberlesen beurteilen kann. Jetzt müsste man nur noch jeden Politiker und jeden Jurist, der zu diesem Thema eine Entscheidung trifft, einer Wissensprüfung unterziehen, und schon könnte nichts mehr passieren … aber wahrscheinlich wird Wissen, wie so oft, mal wieder eher als hinderlich empfunden.
Don't know how I missed these: two excellent talks by MuleSource's Dan Diephouse, one on Dos and Don’ts of RESTful services, the other on The Rise of AtomPub in the Enterprise.
Since the announcement by IBM and Linden Lab that OpenSim can talk to Second Life, I've been thinking again about RESTful Virtual Reality. [...] Ultimately, how to use the same techniques as the Web to link Virtual Worlds together into a single, massive 'Virtual Universe'.
Here's how I would architect the Universe Web...
The appstore is easily the most interesting part of the iPhone, much more than 3G.
I agree whole-heartedly. I believe the AppStore is a great thing from a commercial point of view, both for Apple (obviously), but also for the developers who all have (almost) the same chance to have their app noticed and make a ton of money from it. I understand concerns with regards to the openness of the whole thing – but hey, this is a free market and it's not as if anybody forces you to buy into this particular walled garden.
The best quote on scalability I’ve seen all year long comes from Ted Dziuba, via Jeff Atwood:
Scalability is not your problem, getting people to give a shit is.
Be sure to read the whole thing.
After iterating through a couple of releases over the last two weeks, the Ruby libxml community is happy to announce the availability of version 0.8.0, which we believe is ready for prime time. It offers a great combination of speed, functionality and conformance (libxml passes all 1800+ tests in the OASIS XML Tests Suite).
libxml is great for XML processing; very fast, correct and stable. Having working Ruby bindings for it is superb. Interesting comment from Charles Oliver Nutter:
Since so many people seem to be interested in a good XML library these days, and since XML libraries by and large look pretty much the same on the surface, I’m pretty sure we could map the libxml APIs onto JAXP for JRuby. That would allow people even more confidence to move to libxml for all XML purposes, since they wouldn’t be tied to the C impls.
Excellent idea.
In a new presentation, recorded at QCon San Francisco, CORBA guru Steve Vinoski introduces REST with a focus on those with a more "traditional" SOA background.
Steve explains the goals of the various constraints REST imposes, and the desirable properties one can gain from adhering to them. In a hypothetical discussion with a "SOA guy", Steve addresses various frequent doubts people express when they first look at REST. He explains many of the constraints of REST and the reason behind them.
The video only captures the very lively discussion during the session, but Steve put in an effort to repeat most, of not all, of the questions by the audience, which included industry luminaries such as Sanjiva Weerawarana, Glen Daniels (both from WSO2) and REST expert Stu Charlton (then BEA).
Steve Vinoski, who has also written an article for InfoQ about using Erlang to develop RESTful services and was interviewed on his views on REST, middleware, and programming languages before, is a very well-known expert on middleware, mostly known for his long-time involvement with CORBA. He is a member of technical staff at Verivue and was previously chief architect and Fellow at IONA Technologies for a decade. Over the past 15 years, Steve has authored or co-authored over 80 highly-regarded publications on distributed computing and enterprise integration. Since he has left IONA, he has become a very vocal proponent of the REST style.
Check out Steve’s presentation (57 minutes).
Excellent presentation by someone who really knows his stuff; check it out on InfoQ.
I'm looking for an authoring tool (for a book project - don't ask for more details just yet). It needs to work on a Mac.
The end goal is to create a Word document that makes use of styles only. No manual formatting, font changing etc.
Surely Word itself (and similar monstrosities, such as OpenOffice) can't be the only option?
I took a look at Scrivener, which seems nice, but exports really bad Word docs. I would love to use Pages, but it doesn't do outlines (WTF?). MultiMarkdown sounds perfect, but doesn't export to (real) Word docs. Mellel seems nice, too - but again, the Word export just creates formatted text (no styles).
John Bergmayer's comment on 43folders sums up my requirements perfectly:
The dream program for me would be a standard word processor, but one that REQUIRES the use of styles for all text. No free-form. No manually applying and formatting, ever. Add a mode for easier drafting/rearranging/outlining and good full-screen, and I’d be very happy.
If someone tells you "technology X doesn't scale" without qualifying that statement, it often means the person either doesn't know what he is talking about or is trying to sell you something. Technologies don't scale, services do.
+1.
These are the most current entries; check out the archives for more.
