Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Comment Fall Of The Empire (Score 1) 196

Between the best minds in the US being sucked up by the parasites in Wall Street and massive numbers increase in the number of law students (*) it really does look like the Empire is in the middle of its last greed-fuelled explosion, close to the point of spectacularly imploding in upon itself. Only the decay will likely be slower more insidious than that.

Time to move to Brazil.

(*) http://blueprintprep.com/lsatblog/law-school-admissions/big-law-we-have-a-problem/

Comment Better to focus on the big fish (Score 1) 190

This just sounds like another game where they're focussing on the little guys whilst ignoring the big tax avoiders.

Like this guy, who's a member of the House of Lords (comparable to the Senate, except half of the members get inn through birthright): http://www.guardian.co.uk/politics/2010/mar/04/lord-ashcroft-vat-conservative-polls

Comment Re:Writing one model for ObjC++ and .NET platforms (Score 1) 580

The article you posted is suffering from semantic leak. The words "layered" and "tiered" have many, subtly different meanings depending on who you're talking to. I, personally use a broad definition: a layer or tier says nothing about where the code is running.

The main benefit is that by having your state, interface and actions split up it becomes simple to change the way each of those are executed or handled. Data could be read directly from a database, with the actions running on a remote machine communicating with the client via RPC. Plus when separated it's generally easier to use codegen for each part targeting various platforms (ideal for implementing client-side validation!).

For LOB or data-driven applications (which I'm assuming is the standard use-case for Silverlight compare to JS/HTML) you would be advised to implement a service layer over your domain-entities. That gives you platform-level separation. Or at least it should, as that's kind of the whole point :)

With a service-layer in place, you have some kind of translation on the boundaries. For example you access your domain via a webservice, which serializes to XML, JSON, whatever, which is then reconstituted on the frontend.

These conversions should be totally automated and preferably nicely wrapped on the platforms supporting each layer.

Depending on your exact problem, you could even approach something such as Modal Driven Architecture. There you define an application as a model (usually UML), and then use that as input to your multiple, target-platform-specific compilers. This is particularly suitable to for CRUD systems: from one UML model you can generate a complete database, object model, winforms and web frontends. Though, to be honest, I'm not sure if there are many examples where the resulting interface can be described as "high quality". Oh, and from what I've seen the motivation for using such an architecture has been more to do with technical deficiencies of the modellers than any benefit over other methods. Though, as with everything, that's far from a rule. If your problem is easier to user-stand when it's modelled visually, and it's worth trading potential UI quality for it, then that's great.

Comment Re:I am a Silverlight Developer (Score 2) 580

It's also exactly the reason why you should choose a layered architecture, and preferably MVC/MVP or MVVM. They all make platform switching much easier as the frontend is a very think layer.

Silverlight in particular has a really nice MVVM framework called Caliburn (http://caliburn.codeplex.com/). If you've built your app using that, then it shouldn't be a huge amount of work to switch to html5/js for the frontend.

Hey, you might even be able to use a.net to js compiler to do the body of the work: http://jsc.sourceforge.net/

Comment Re:I'm bombarded.... (Score 1) 408

> What are you talking about?

Basically, because a German has a choice between a number of parties which have very different agendas, he/she can vote for a party better matching his/her own political views. Sure, these parties then make compromises to form a coalition.

An American has a choice between one of two parties, who differ only slightly.

You use the Tea Party as an example. Americans can't vote for the Tea Party. They have to vote for the Republicans. At the same time, someone who believes in Conservative values, but sees the Tea Party as a bunch of right-wing loonies also has to vote... Republican.

So yeah, you do see a broad range of differing political ideologies in (western) Europe when compared to the USA.

Comment Re:I'm bombarded.... (Score 4, Interesting) 408

A couple of points:

1) You can't really group "Europe" together like that. Sure, in countries such as Germany, Italy and The Netherlands you see parties which are closer to their idiologic roots than in the US. But in the UK that's not the case: there are but two real parties (the liberals have in the last year proven themselves pointless), and they're fairly similar policy wise.

2) A lot of Western Europe (Germany, Italy, Netherlands etc) have many differing political parties getting together to form coalition governments. This is why you see media targeting specific niches. Here in Netherlands we've got free-market, socialist, communist, pseudo-fascist, green & animal parties.

3) "Europe" (the EU) is similar in size to "America". If we compare them politically at that level (i.e. EU vs US) then they're not really that different. Except the average European has less of a say in who, exactly gets to represent them, and the EU has a lot less power over the member countries than Washington does over the States.

Comment Re:Only a few left.... (Score 1) 426

Well, as long America is a British Empire Colony, no way to explain them the beautiful simplicity of the Metric system.

It always makes me smile that the UK runs on the metric system. I'm 30 and I only know the imperial measurements from road signs and the British Pint (~568ml).

One thing that everyone (except programmers) does wrong is dates in the Gregorian system. It would be much easier if we just went small endian: 2005-12-31 or 2005/12/31 is much better than 6/4/2005 because it sorts logically and can't be confused as dd/mm/yy and mm/ddy/y are.

Comment Android is safer than iPhone.. (Score 5, Insightful) 177

Angy Birds, for example, collects a heck of a lot of personal information on the iPhone. Why? Because the user isn't warned about it. Their Android application has so far been much cleaner, mostly because Android asks the user to give the app permission to access certain data.

Link: http://www.observer.com/2010/media/angry-birds-and-other-must-have-apps-collect-more-personal-data-you-think

Slashdot Top Deals

It is easier to write an incorrect program than understand a correct one.

Working...