Live data from Hacker News

The Rise and Fall of CORBA (2006)

queue.acm.org

101–110 of 156 posts

Re: The Rise and Fall of CORBA (2006)

#101
> SOAP had serious technical shortcomings, but, as a market strategy, it was a masterstroke.

Wrong. SOAP descended quickly into the "whatever happened to" category. Like CORBA. I'm happy to say I threw out SOAP and used REST instead at Google, in practically my first act there:

https://albertcory50.substack.com/p/working-at-google-enterp...

The Internet had no time for multi-company, political garbage like SOAP and CORBA.

Re: The Rise and Fall of CORBA (2006)

#102
CORBA is one of the first technologies that I came across and saw that it was kind of 'hot', but decided I'd learn it if I ended up really needing it. And I never did.

It's important to learn when to ignore things in this field. It's never possible to be 100% sure, but there are always going to be 'new! hot!' things.

Re: The Rise and Fall of CORBA (2006)

#103

> SOAP had serious technical shortcomings, but, as a market strategy, it was a masterstroke. Wrong. SOAP descended quickly into the "whatever happened to" category. Like CORBA. I'm happy to say I threw out SOAP and used REST instead at Google, in practically my first act there: https://albertcory50.substack.com/p/working-at-google-enterp... The Internet had no time for multi-company, political garbage like SOAP and C…

Why are you taking the sentence out of context to change its meaning? TFA says it was a good business move by Microsoft for Microsoft because it fragmented the competition which had been consolidating around CORBA. What happened to it afterwards is irrelevant.

Re: The Rise and Fall of CORBA (2006)

#104

The old adage: "the first rule of distributed objects: don't distribute your objects". DCOM and EJB also came unstuck by failing to observe this rule. It's impossible for young'uns to appreciate just how obsessed the software world was by 'objects', OO and the chimera of reusability in those days; I subscribed to 'Object' magazine, and still recall one article breathlessly predicting that in the future bespoke develo…

> " I subscribed to 'Object' magazine, and still recall one article breathlessly predicting that in the future bespoke development would become bunk as folks would just buy e.g. an Aircraft object off the peg and plug it into their application. " One drum I keep beating is that COM in Windows is amazing for scripting and interoperability between programs. Before PowerShell and "everything is an object [but you're stu…

If I could upvote you 100 times at the expense of not being able to vote for the rest of the year, I would do it right now.

Re: The Rise and Fall of CORBA (2006)

#105

> SOAP had serious technical shortcomings, but, as a market strategy, it was a masterstroke. Wrong. SOAP descended quickly into the "whatever happened to" category. Like CORBA. I'm happy to say I threw out SOAP and used REST instead at Google, in practically my first act there: https://albertcory50.substack.com/p/working-at-google-enterp... The Internet had no time for multi-company, political garbage like SOAP and C…

Why are you taking the sentence out of context to change its meaning? TFA says it was a good business move by Microsoft for Microsoft because it fragmented the competition which had been consolidating around CORBA. What happened to it afterwards is irrelevant.

Because what happened to it afterwards is NOT irrelevant.

Just like CORBA sounded great in the press releases, but went nowhere in practice. Which is what this article is about.

Re: The Rise and Fall of CORBA (2006)

#106

The old adage: "the first rule of distributed objects: don't distribute your objects". DCOM and EJB also came unstuck by failing to observe this rule. It's impossible for young'uns to appreciate just how obsessed the software world was by 'objects', OO and the chimera of reusability in those days; I subscribed to 'Object' magazine, and still recall one article breathlessly predicting that in the future bespoke develo…

NIH killed OOP. Nobody wants to use someone else's object, because that isn't FUN and programmers get paid in FUN.

Re: The Rise and Fall of CORBA (2006)

#107

Earlier quoted context omitted.

There was also a thread obsession. However, luckily, 'Threads' magazine is about sewing. I had an issue on my desk.

Ah yes apartment threading and all that. Read so much about that stuff, but will go to my grave having never understood it!

Apartment threading means that your component has a thread in, which doesn't call into other components. It receives the requests via messages, same if it were running in another process. I believe there is marshaling of arguments to an apartment thread, like in the out-of-process case. Thus you don't have to deal with the possibility that two or more calling threads are executing the component's code.

Re: The Rise and Fall of CORBA (2006)

#108
post #21

The old adage: "the first rule of distributed objects: don't distribute your objects". DCOM and EJB also came unstuck by failing to observe this rule. It's impossible for young'uns to appreciate just how obsessed the software world was by 'objects', OO and the chimera of reusability in those days; I subscribed to 'Object' magazine, and still recall one article breathlessly predicting that in the future bespoke develo…

> one article breathlessly predicting that in the future bespoke development would become bunk as folks would just buy e.g. an Aircraft object off the peg and plug it into their application Every time I consume a third-party’s REST API, I’m doing that, no? Albeit the article may have oversold the idea in the work ending there.

There's the idea, and then there's its execution.

You're saying someone else's successful (and partial) execution of an idea somehow validates the original failed execution.

Re: The Rise and Fall of CORBA (2006)

#109
post #7

Earlier quoted context omitted.

Why no type checking? Generate an Open API client for target languages. Done. Assuming you need an API. I'll never build an app that way again, it's not worth my hands. I'd rather use Hotwire, or LiveViews, or Django's Unicorn for the web part. Zod looks nice too.

The problem isn't so much with checking as it is with what kinds of things you can check. OpenAPI offers a very powerless type system. So bad, it's almost not worth using. Not only that, it's designed for JSON, which is an awfully bad format -- so, even if you could check that somehow, you'd still be very limited by what you can actually send. Also, yeah, all kind of hot garbage you listed will work on Web, because t…

Reactive UI development is hot garbage now? I think not :)

Re: The Rise and Fall of CORBA (2006)

#110

Earlier quoted context omitted.

Why are you taking the sentence out of context to change its meaning? TFA says it was a good business move by Microsoft for Microsoft because it fragmented the competition which had been consolidating around CORBA. What happened to it afterwards is irrelevant.

Because what happened to it afterwards is NOT irrelevant. Just like CORBA sounded great in the press releases, but went nowhere in practice. Which is what this article is about.

It's irrelevant to calling it a masterstroke market strategy, which is what the sentence you quoted is about.
Post reply on HN