Although interesting, because I'm now exposed to the NDepend tool, how is this News? It just begs the slashdot elite to post yet again how much.NET sucks cause it's made by MS, ripped off from Java, etc etc.
Alot of people have been waiting to see what 2.0 looks like before jumping on board. 1.0 had many limitations and deficiencies that most didn't want to deal with. The entire programming model has changed from Javascript in v1.0 to C# (or any.NET language, with assemblies, debugger support, etc) in 2.0. It is also possible to use IronPython, IronRuby, and VB, but I haven't yet experimented with any of those.
Silverlight 2.0 draws many parallels to.NET as it contains a fully fledged.NET CLR while running on both Windows and MacOS X, sporting an API similar to WPF (Xaml visuals, Storyboards and Animations, Templated and Styled Controls, databinding, etc) and yet is still a nimble 4.3 meg download to end users.
Based on the demand for MIX tickets and Sessions, and on conversations I've had with various people, I think there will be a substantial increase of interest in the 2.0 beta compared to 1.0. Anyone that has produced a site in SL1 knew 2.0 was coming, it was just a matter of the form and function details.
Lastly, Miguel de Icaza was at MIX showing Moonlight on linux running a few SL1.0 samples. Just as with any major Mono project, expect a lag time of up to a full product cycle behind MS's releases.
Insightful, ha. As Bender once said, "Thats using your ass".
As MS iterates on the implementation,.Net may evolve a bit, but I can still run old.Net 1.1 samples I wrote in 2002 on Vista without modification. The major reason.Net 2.0 was adopted en mass over 1.1 is because 2.0 was much better. Generics are a major boon to productivity. In general, each major release improves developer productivity by a randomly large factor. A Recent example: WPF beats the pants off of the old Winforms way of doing things; There are so many shortcuts and patterned ways of doing things in WPF (two way databinding a verified Xml document to a custom UI, with some added glitz for fun), yet it keeps Winforms intact, allowing WPF and Winforms content to be interopable.
If you're really that worried about MS somehow pulling the rug out from under your awesome app, implement it using mono.Cecil. It's an IL read/write layer with independent generic support, so you can load any version of mscorlib.dll you want under any runtime version, which frees you to use whichever your application requires.
Very few scenarios actually require this level of independence; most legitimate uses are things like dev tools that need to run across versions, but if you're so paranoid about it, you can make damn sure that your app will run on any version of.Net.
Another good point is: silverlight 2 is coming. The beta will likely be released at MIX next month, and that is a nimble version of the CLR and associated libraries, with a download footprint of 4 megs that runs on macos and windows (hopefully linux with the help of the mono guys). The silverlight clr core is from the same branch as.Net 3.5 (C# 3).
Dr. Stantz: You know, it just occurred to me that we really haven't had a successful test of this equipment. Dr. Spengler: I blame myself. Dr. Peter Venkman: So do I. Dr. Stantz: Well, no sense in worrying about it now. Dr. Peter Venkman: Why worry? Each one of us is carrying an unlicensed nuclear accelerator on his back.
Although I do think people should have a reasonable expectation of privacy when marking/tagging pictures as private though services like MySpace, I think it's a risk anytime you upload a picture or document or anything else to any computer that isn't physically your own property.
If anyone was actually exposed by this, it's their own fault.
I think Schlosser was right. The crux of the matter is about having an intimate connection with the animal you kill for food. Imo, most americans would refuse if asked to kill and butcher a cow or a pig in order to cook and eat it, yet they wouldn't hesitate to order up some baby back ribs or a burger, not thinking twice about where the food came from.
People should ask of themselves what exactly they are capable of and comfortable with, and accept responsibility for what they eat. In doing so, I've become more mindful of where my money goes and what I put in my body, and I'm all better for it.
Cloned or not, as long as the animal in question lived a happy, healthy life prior to being slaughtered, I'll eat it. If I can't source it to a responsible supplier, I won't./opinion
You will likely get both good and bad opinions in response to this question here on slashdot, but my best advice would be to ask this question of employers that you might be interested in working for.
It's true there's some parallels, but Xaml is much more flexible.
Xaml at it's core is essentially an object instantiation language. It allows developers to declaratively create objects, describe their members, and relate them to other objects. As long as the objects referenced follow some simple rules, said Xaml is compiled down and loaded, either while building an application or on the fly, as may be the case with Silverlight.
It's handy when the UI and Codebehind for a Window or Canvas can be worked on independently by the designer and developer, and have both parts compile down to the same class. It also makes for some interesting solutions if you want to alter look or behavior after shipping.
There is no EULA, or atleast, there isn't one that is displayed in an annoying install process. They explicitly designed it to be installed on new system in 20 seconds.
A web portal with a very tightly integrated, extensible "smart client".
The following scenario sounded interesting: Plugging in your camera and having pictures automatically copied, sorted, ready to organize on your "local server", automatically publishing once you're connected to the website.
The bit about developing "applications" using JUL sounded interesting too. I wonder how much cross-over functionality this and Google Gears has.
I recently (within the last year) deployed an application that end users use for downloading and viewing custom content, and are intended to install the app onto laptops, tablets, and other portable devices allowing them view said content both on and off-line.
When prototyping our "offline mode", we ran into this exact same problem because the Xml APIs we used wanted to validate xml against online dtds. We ammended the validator's resolver to use locally embedded or cached dtds for all our doctypes, problem solved.
In in my app it was an obvious problem to solve because offline usage was a big scenario, but I could imagine that being "out of scope" for a less-than-robust website.
Slashdot Mirror
I call it a Hawking Hole
Although interesting, because I'm now exposed to the NDepend tool, how is this News? It just begs the slashdot elite to post yet again how much .NET sucks cause it's made by MS, ripped off from Java, etc etc.
Alot of people have been waiting to see what 2.0 looks like before jumping on board. 1.0 had many limitations and deficiencies that most didn't want to deal with. The entire programming model has changed from Javascript in v1.0 to C# (or any .NET language, with assemblies, debugger support, etc) in 2.0. It is also possible to use IronPython, IronRuby, and VB, but I haven't yet experimented with any of those.
.NET as it contains a fully fledged .NET CLR while running on both Windows and MacOS X, sporting an API similar to WPF (Xaml visuals, Storyboards and Animations, Templated and Styled Controls, databinding, etc) and yet is still a nimble 4.3 meg download to end users.
Silverlight 2.0 draws many parallels to
Based on the demand for MIX tickets and Sessions, and on conversations I've had with various people, I think there will be a substantial increase of interest in the 2.0 beta compared to 1.0. Anyone that has produced a site in SL1 knew 2.0 was coming, it was just a matter of the form and function details.
Lastly, Miguel de Icaza was at MIX showing Moonlight on linux running a few SL1.0 samples. Just as with any major Mono project, expect a lag time of up to a full product cycle behind MS's releases.
"You reek of death, human" - Illidan
Insightful, ha. As Bender once said, "Thats using your ass".
.Net may evolve a bit, but I can still run old .Net 1.1 samples I wrote in 2002 on Vista without modification. The major reason .Net 2.0 was adopted en mass over 1.1 is because 2.0 was much better. Generics are a major boon to productivity. In general, each major release improves developer productivity by a randomly large factor. A Recent example: WPF beats the pants off of the old Winforms way of doing things; There are so many shortcuts and patterned ways of doing things in WPF (two way databinding a verified Xml document to a custom UI, with some added glitz for fun), yet it keeps Winforms intact, allowing WPF and Winforms content to be interopable.
.Net.
.Net 3.5 (C# 3).
:p
As MS iterates on the implementation,
If you're really that worried about MS somehow pulling the rug out from under your awesome app, implement it using mono.Cecil. It's an IL read/write layer with independent generic support, so you can load any version of mscorlib.dll you want under any runtime version, which frees you to use whichever your application requires.
Very few scenarios actually require this level of independence; most legitimate uses are things like dev tools that need to run across versions, but if you're so paranoid about it, you can make damn sure that your app will run on any version of
Another good point is: silverlight 2 is coming. The beta will likely be released at MIX next month, and that is a nimble version of the CLR and associated libraries, with a download footprint of 4 megs that runs on macos and windows (hopefully linux with the help of the mono guys). The silverlight clr core is from the same branch as
DotNet isn't going to disappear anytime soon.
Dr. Stantz: You know, it just occurred to me that we really haven't had a successful test of this equipment.
Dr. Spengler: I blame myself.
Dr. Peter Venkman: So do I.
Dr. Stantz: Well, no sense in worrying about it now.
Dr. Peter Venkman: Why worry? Each one of us is carrying an unlicensed nuclear accelerator on his back.
Have you ever defragmented a harddrive after copying around 1 million small files?
Although I do think people should have a reasonable expectation of privacy when marking/tagging pictures as private though services like MySpace, I think it's a risk anytime you upload a picture or document or anything else to any computer that isn't physically your own property.
If anyone was actually exposed by this, it's their own fault.
I think Schlosser was right. The crux of the matter is about having an intimate connection with the animal you kill for food. Imo, most americans would refuse if asked to kill and butcher a cow or a pig in order to cook and eat it, yet they wouldn't hesitate to order up some baby back ribs or a burger, not thinking twice about where the food came from.
People should ask of themselves what exactly they are capable of and comfortable with, and accept responsibility for what they eat. In doing so, I've become more mindful of where my money goes and what I put in my body, and I'm all better for it.
You mean like the Cavendish Banana?
Cloned or not, as long as the animal in question lived a happy, healthy life prior to being slaughtered, I'll eat it. If I can't source it to a responsible supplier, I won't. /opinion
You will likely get both good and bad opinions in response to this question here on slashdot, but my best advice would be to ask this question of employers that you might be interested in working for.
Reread the summary and article, replacing "nanorobots" with "nanoprobes"...
>I feel sorry for the canned individuals
I pity the ones that didn't see this coming.
Fascinating captain, and logical too.
It's true there's some parallels, but Xaml is much more flexible.
Xaml at it's core is essentially an object instantiation language. It allows developers to declaratively create objects, describe their members, and relate them to other objects. As long as the objects referenced follow some simple rules, said Xaml is compiled down and loaded, either while building an application or on the fly, as may be the case with Silverlight.
It's handy when the UI and Codebehind for a Window or Canvas can be worked on independently by the designer and developer, and have both parts compile down to the same class. It also makes for some interesting solutions if you want to alter look or behavior after shipping.
There is no EULA, or atleast, there isn't one that is displayed in an annoying install process. They explicitly designed it to be installed on new system in 20 seconds.
"Waiting for thesneeze.com"
Zomg, I already have to wait for my real sneezes...
So IBM sanctions playing Secondlife while on the clock?
This, I have to see for myself.
A web portal with a very tightly integrated, extensible "smart client".
The following scenario sounded interesting: Plugging in your camera and having pictures automatically copied, sorted, ready to organize on your "local server", automatically publishing once you're connected to the website.
The bit about developing "applications" using JUL sounded interesting too. I wonder how much cross-over functionality this and Google Gears has.
-ds
'its what we call a "LASER"'
Mod +1 Horrible Joke
I recently (within the last year) deployed an application that end users use for downloading and viewing custom content, and are intended to install the app onto laptops, tablets, and other portable devices allowing them view said content both on and off-line.
When prototyping our "offline mode", we ran into this exact same problem because the Xml APIs we used wanted to validate xml against online dtds. We ammended the validator's resolver to use locally embedded or cached dtds for all our doctypes, problem solved.
In in my app it was an obvious problem to solve because offline usage was a big scenario, but I could imagine that being "out of scope" for a less-than-robust website.
Coca Cola. Welcome to the coke side of life.
http://wow.blupp.net/item.php?id=339344
Only on slashdot would the parent be funny.
Much like an orgasm..