Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bloomberg Terminals Suffer Widespread Failures

nytimes.com

Post reply on HN
Print view View original

41–50 of 69 posts

Re: Bloomberg Terminals Suffer Widespread Failures

#41

Post by PhantomGremlin »

noir_lord wrote: post #37
kokey wrote: post #34

Earlier quoted context omitted.

The issue was probably something like a broadcast storm because of defective fault detection on some redundant network kit. That won't stop people blaming it on the fact that the stack isn't built on the latest hipster frameworks.

While I see your point do we have to throw the word "hipster" at everything new?. I'm not a huge fan of Javascript and it's proliferation of frameworks but some of that stuff is objectively both good and useful.

It's human nature to want to label things. IIRC a while ago I was watching one of those "house hunter" type shows and a husband on there was really annoying. I found a discussion online and people were calling him a "hipster douche". So, perhaps hipster by itself isn't so bad. :)

Back a long time ago the applicable pejorative was "yuppie". I haven't heard that one recently. I suspect that many people reading here would have to look it up in Wikipedia.

Edit: BTW at the time I was partial to calling people "yuppie scum". Sigh. It's so hard to keep up with the changing putdowns! :)

Re: Bloomberg Terminals Suffer Widespread Failures

#42

Post by mahyarm »

marbletiles wrote: post #36
tacostakohashi wrote: post #31

Earlier quoted context omitted.

Only 700mb? Maybe back in the perkin elmer days, these days they're up to 4gb, constrained only by the various linkers, file size and address spaces available...

Server-side is very big - in fact, a long time ago the part called simply "the Big" got too big and now there are multiple Bigs.

And this is one reason why I don't like C++. I only hear about executables getting too big in C++ projects.

Re: Bloomberg Terminals Suffer Widespread Failures

#44

Post by hackuser »

chollida1 wrote: post #4

The outage isn't that bad. I've talked to 5 other firms in Canada this morning and haven't heard of a single one that is down. Bloomberg's tickering plant is still working and their emsx(trading system) is up and running, albeit a bit slow right now. I think it was on a stackoverflow podcast that Joel or Jeff said that it makes you wonder about people who complain about down time if they've ever built something of th…

> Google's been down, ditto for facebook, twitter and Azure

The first three, at least, are free services and availability isn't a priority for many of their customers. Bloomberg users have different requirements.

Boeing 747's are complex systems; it's not acceptable if one fails occasionally.

Re: Bloomberg Terminals Suffer Widespread Failures

#45

Post by keithpeter »

“What I miss is the instant Bloomberg chats, which I rate higher than trading or data feeds. The fact is, Bloomberg connects 100 percent of the Street, and all that human intelligence is what makes markets hum.”

I enjoyed the article and I have squirrelled this quote from a trader away for future use - the need to meet and exchange information is why we used to have stock exchanges of course.

Re: Bloomberg Terminals Suffer Widespread Failures

#46

Post by cheriot »

hackuser wrote: post #44
chollida1 wrote: post #4

The outage isn't that bad. I've talked to 5 other firms in Canada this morning and haven't heard of a single one that is down. Bloomberg's tickering plant is still working and their emsx(trading system) is up and running, albeit a bit slow right now. I think it was on a stackoverflow podcast that Joel or Jeff said that it makes you wonder about people who complain about down time if they've ever built something of th…

> Google's been down, ditto for facebook, twitter and Azure The first three, at least, are free services and availability isn't a priority for many of their customers. Bloomberg users have different requirements. Boeing 747's are complex systems; it's not acceptable if one fails occasionally.

> Boeing 747's are complex systems; it's not acceptable if one fails occasionally.

Yet they have failed. Reality isn't always acceptable.

Re: Bloomberg Terminals Suffer Widespread Failures

#47

Post by easytiger »

Karunamon wrote: post #24
anmilo wrote: post #9

Earlier quoted context omitted.

one of the reasons i'm generally Ok with Slack's valuation is that there is a ton of room for a messaging service to offer a service that is secure and auditable at the level that the SEC/FINRA and Banks require. Like the article mentions, if you talk to the people using BBG, it's really the chat functionality that provides the main value for literally everyone, at least in my experience (former front office dev)

I'm unfamiliar with these terminals (have kind of always wanted to play with one), but at first blush, a "secure and auditable" messaging system does not seem that difficult to build. Is it a legitimate compliance or practical implementation problem, or is it just the network effect?

its also easy to keep it secure when it doesnt use the internet

Re: Bloomberg Terminals Suffer Widespread Failures

#49

Post by santaclaus »

noir_lord wrote: post #37
kokey wrote: post #34

Earlier quoted context omitted.

The issue was probably something like a broadcast storm because of defective fault detection on some redundant network kit. That won't stop people blaming it on the fact that the stack isn't built on the latest hipster frameworks.

While I see your point do we have to throw the word "hipster" at everything new?. I'm not a huge fan of Javascript and it's proliferation of frameworks but some of that stuff is objectively both good and useful.

Using the term 'hipster' to refer to the newest and shiniest web framework always felt like a bit of a misnomer to me. A solid portion of hipsterdom is rooted in recycling of the obscure and of the vintage (vinyl, the popularity of the lumber sexual look, etc). It seems like the 'hipster' thing to do would be to write a web framework in PL/I or cobol or something.
Post reply on HN