|
|
I liked Silverlight. It was like WPF, but for the web.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
It worked for both desktop and web, and I found that extremely innovative. That's something I haven't seen before or since. Too bad they didn't continue down that road...
Anything that is unrelated to elephants is irrelephant Anonymous
- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944
- Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain
|
|
|
|
|
The reason Silverlight deceased is that it needed a browser plugin to run. Most browser developers would not want to add that (they still trembling when ActiveX mentioned), and .NET wasn't supported on platforms other than Microsoft. So it made Silverlight a Microsoft/IE only thing...
Microsoft's decision (with others) was to push forward the HTML5 initiative instead...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
I think there was a Firefox plugin as well. I think the bigger problem was that there wasn't a Linux browser plugin.
|
|
|
|
|
Actually, Microsoft likes to get people enthused about a technology stack, and then completely abandon it once acceptance and use has become significant. To be honest, I'm surprised that Microslop is still supporting .Net...
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Silverlight is about more than playing videos.
|
|
|
|
|
|
Cutting Edge!
... such stuff as dreams are made on
|
|
|
|
|
Cool. I'm afraid I may get to be good at this toolkit.
|
|
|
|
|
HTML5 squeezed out the technically superior Silverlight.
VHS squeezed out the technically superior Umatic.
TCP/IP squeezed out the technically superior OSI protocol stack (USA: prevented OSI from entering).
XML squeezed out the technically superior ASN.1.
The x86 architecture squeezed out the technically superior PowerPC (you could even count 68K).
K&R C squeezed out the technically superior Pascal, and prevented other well designed languages from entering the scene.
I guess we could keep on for quite a while.
Engineers have some romantic ideas about competition causing the best candidate to win, pretending that by 'best' they mean the technical superiority. When it doesn't turn out to be true, we treat is as an exeption: VHS won because of the availablitly of porn movies on VHS; everybody knows that. But there are practically always exceptions: Usually, when a technologially superior solution wins, it is not due to competition, but rather to a cooperative joint effort. (If you ask for examples: The comittee-designed GSM kicked out the competing cellular phone technologies, even in the USA. The comittee-designed DAB digital audio brodacast is way superior to all those proprietary competitors - even the US winner, HD radio, is far behind from a technical viewpoint.)
Technical superiority is not significant for being the winner in a competitive market. Often it is a great disadvantage, because it won't allow making those shortcuts to cheapen it. The reason why TCP/IP protocols won was that any fourteen year old hacker can put together something that sort of works on his home PC. The OSI protocols required a professional, with professional competence to build high quality solutions, not a pile of random hacks. I always argued that the names are wrong: It should be TSMTP, TSFTP, TSNM...: TOO simple mail transfer protocol, TOO simple file transfer protocol, TOO simple network management. But the TOO-simple is what made these protocols win the battle.
|
|
|
|
|
|
Wasn't it a Microsoft flash in the pan?
|
|
|
|
|
Hi All,
Thing I need for operation cluster is a piece of software to monitor packets of data (video?) really a version of Wireshark that will let you look at the packets. I did offer to put one together for use (in C#) but was denied the chance...
One the major task is to create the IP packets loaded with test data...(#FF#01#FF#01) I'm guessing I should have lead with that...
modified 19-Jun-18 5:38am.
|
|
|
|
|
Maybe WireShark can help you...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
Maybe I should re-word the question...thanks.
|
|
|
|
|
Sorry, I just can't resist: Anyone's wife in paranoid surveilance mode? The downside is that she is only interested in your traffic and ignores everything else.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
|
I hope that was not just bitter sarcasm.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Oh very bitter!
|
|
|
|
|
This is a pretty common feature in most current Network Security Monitoring software, but it requires a bit more of an investment than just firing up WireShark.
Two that I've worked with off hand are Security Onion and ROCK NSM. Security Onion is a bit more popular and better developed, and if you haven't done network security work before will provide the best bang for your buck. They will require their own physical machine to be effective, in general (you'll lose packets in most virtualization scenarios).
Neither of those will be useful for generating test data packets, though.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
tcpdump
|
|
|
|
|
The 3D printer was producing only cobwebs and it looked like the muzzle was not muzzling enough molten plastic anymore. So I got myself a new muzzle and installed it. Now the printer is like new.
The only complication: I had to heat the printer up to operating temperature (= 240 C) to remove the muzzle and install the new one, preferrably without burning myself too much. It went well, even with having to insert the new muzzle by hand before it heating up too much.
Maybe I can even save the old muzzle and reuse it next time. I know that ABS could be cleaned with acetone. Unfortunately it's slightly baked PLA that's closing up the muzzle. Does the chemistry set have anything to solve away that?
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
CodeWraith wrote: Does the chemistry set have anything to solve away that? Wikipedia says Quote: PLA is soluble in chlorinated solvents, hot benzene, tetrahydrofuran, and dioxane. which all sound rather nasty.
Cheers,
Peter
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Peter_in_2780 wrote: all sound rather nasty.
You're not kidding!
Benzene is carcinogenic, and can destroy your bone marrow, leading to anemia (I remember this from Chemistry lessons, over 40 years ago: it was firmly impressed into us that you don't touch it outside a fume cupboard).
Wikipedia doesn't like dioxane either: This compound is irritating to the eyes and respiratory tract. Exposure may cause damage to the central nervous system, liver and kidneys.
Me? I'd probably just buy a new one...
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|