(Disclaimer: I was the lead architect for the initial release of Streamwork, but have since left SAP.)
411 karma · joined March 28, 2008
(Disclaimer: I was the lead architect for the initial release of Streamwork, but have since left SAP.)
But yes, they do have a plugin version of Fabric. I have similar misgivings about that.
"The high-performance parts of the application are written using a performance-specific extension to JavaScript, called KL (Kernel Language). This language is similar in scope and syntax to JavaScript, but has some key differences that optimize it for writing high-performance code.
Fabric applications are described as a dependency graph (think of a flow chart). The dependency graph describes data, and the transformations that must happen to that data. Fabric analyses the graph to discover where it is possible to perform tasks in parallel. (task-based decomposition) Fabric analyses the graph to discover where it is possible to perform the same instruction on lots of data at the same time.
All of this is possible because Fabric has the LLVM compiler embedded within it. This means that applications are dynamically compiled on target. The Fabric plug-in has to be written for each platform, but Fabric applications only have to be written once.
Fabric handles CPU multi-threading automatically, but the developer must explicitly write code for the GPU using OpenCL."
If you did take advantage of the runtime's support for multiple global objects, what would those global objects correspond to? The most natural scope would be "user session" - but if you go that route, now you support stateful user sessions. And before you know it you have developers storing loads of user session state in the server's RAM and wondering why they keep running out - and lose the ability to easily fail over to another server process.
So I imagine Node's author decided it was better to just keep things simple and discourage use of globals.
In the CS code, the association between the object and it's type of motion (galloping/slithering) is made at construction time (via the implementation of "move" associated with the object), and in the "pure javascript" code it is made at the call site for "move".
This seems like such a fundamental difference that it becomes a little difficult to take the rest of the argument seriously.
"The JSPrime effort was begun to unify and be a (single!) successor to GWT and Closure/JSCompiler"
"What is the future of the JSCompiler and GWT? JSCompiler and GWT were already on a merger path. This effort gives us a direction for that unification around the Dash language. We will actively support teams for a long time on the current generation of JSCompiler and GWT and provide fantastic co-existence and migration tools to Dash."
See: http://markmail.org/message/uro3jtoitlmq6x7t
(My emphasis added. I read that as "maintenance mode".)
(Edit: thanks for the heads-up on the FF6 version of the plugin - but I guess I have now missed the two-week window where both FF6 and the compatible version of the plugin where available to download!)
(Grrr... yet more evidence of G's gradual sunsetting of GWT.)
Sorry, I mean "support teams for a long time on the current generation".
Gruber's a great writer for the most part, but this particular instance of his work is pretty trite and hardly a unique observation. His lack of knowledge about the players in the space should give a clue to readers about how much weight to give the rest of his insights about this subject.
Autonomy & SAP have similar customers, true. But the suggestion in Gruber's post is that the purchase of Autonomy is a substitute for a purchase of SAP. Which is a bit like saying the purchase of a front drivers side door mirror is a substitute for the purchase of a car.
(Downvotes too, jeez.)
(Yeah, I know, if they wanted a good experience why would they use IE7? But I think we have to live with IE8 for a good while.)
Stay classy, IV.
And your problem with this is? Just that they are saying it now? Don't understand the concern, honestly.
It seems more likely to me that Apple is very much aware of the contradiction but has plans to change this, but no intention of telling us about it yet.
Gotta wonder what that huge data centre they are building is for, eh?
A timeline:
iTunes store opens: April 26 2003
Steve Jobs DRM letter: Feb 6 2007 (4 years ago)
EMI content available DRM free: May 29 2007
80% of iTunes music DRM free: Jan 6th 2009
All US iTunes music DRM free: April 7th 2009
So I think you are stretching the meaning of "only recently", especially when considered in terms of the pace of technology development (as opposed to, say, geological time.)
You couldn't even buy an iPhone when they started removing it. The period over which they were exclusively selling DRM content is actually shorter than the period since they stopped.
(Update: that last part is not quite right - I was counting from the DRM letter date, not the EMI date. But it's close.)
(Update: amused by the accusations of blasphemy.)
(And makes me sound a bit uncharitable too. Merry Xmas!)
"I have written production level code in Erlang, namely a BitTorrent client good enough for everyday use"
...seems to be going some way towards proving the Acharya's point #4 for the following reasons:
1) No reference to any actual users of the code apart from the author himself.
2) No link to where the code is available.
3) Code is a single-user client, when Erlang's strength is usually considered to be in multi-user servers.
It's not obvious that the author understands what is meant by "production level", since the project mentioned does not even appear to meet the most liberal possible interpretation of this term, which would be "shipped".
90Degrees was founded by a former colleague of mine, and they definitely hired a lot more than just sales from BOBJ, actually I'd have said it was the opposite - they took a lot of tech guys from my old team at a time when morale got pretty low a year or so after BOBJ took over. Most of those guys relocated to Redmond after MS took over, a few are back at SAP.
Being acquired by a larger company will affect the culture. Most people who date from the days of Crystal look back fondly on that time. Things definitely took a hit after BOBJ took over but if you look back the site thrived under BOBJ. It may have helped that BOBJ was really only 50% bigger than Crystal at the time. SAP is a different story, they were about 10x the size of BOBJ. I left, which tells you something about my morale there.
There has been a bit of turnover at Indicee - there was a period (prior to my arrival) when they were using more contractors etc - but we have a pretty solid full-time team now. We just pushed out a 2.0 of the product which is a substantial reworking.
Crystal/BOBJ/SAP has acted as an academy company for enterprise BI software in the same way that EA has for gaming. There are a few BI companies started by ex-Crystal people and rumour has it that some companies have opened sites here to soak up some of the post-SAP diaspora (Qliktech for example.)
Don't expect those kind of businesses to get much love here on HN, but there is still plenty of tech employment in this town and I'd say the prospects were getting better not worse.
(FWIW I am a former Crystal/BOBJ/SAP employee and now work at Indicee, a SaaS BI startup.)