|
The age of exploration in the cloud is passing. Now it's time to get down to business. "I am serious. And don't call me Shirley."
|
|
|
|
|
I think this is evident with Adobe's move to CC.
|
|
|
|
|
Internet phone company said it is developing the technology in the lab but it could be several years before it reaches the market For those video calls with depth
{scratches head} Does anyone actually want this? (Outside of maybe the porn industry).
|
|
|
|
|
|
|
Obi-wan, you're our only hope! (to fix Skype)
--------------
TTFN - Kent
|
|
|
|
|
The Tor (The Onion Router) network has witnessed over 100 per cent rise in the number of users connecting to it for the month of August and has reached record levels for the first time since the project has been collecting usage statistics. I can not (en) possibly think (ess) of a reason (eh) why.
|
|
|
|
|
Kent Sharkey wrote: eh
Aren't you in Canada, aye?
|
|
|
|
|
That I am. Although 'eh' isn't as common as Bob and Doug make it seem.
--------------
TTFN - Kent
|
|
|
|
|
Microsoft tried, but it couldn't win the hearts and minds of developers who weren't already indoctrinated -- and it alienated others along the way "You keep using that word. I do not think it means what you think."
Your friendly neighbourhood link bait du jour.
|
|
|
|
|
Infoworld wrote: People coded to .Net because they were coding for SharePoint or BizTalk. [sigh] Is it a requirement that people who write for technical rags must smoke crack?
/ravi
|
|
|
|
|
Sometimes I wonder if it's the crack, or they are just putting something crazy out to just try to get attention.
--------------
TTFN - Kent
|
|
|
|
|
Online journalism - can't get paid if nobody clicks your link. Gotta have a rediculous assertation to get any attention in the tabloids today.
|
|
|
|
|
I hope the next Microsoft failure keeps me gainfully employed for 15 years.
(I assume I'll be writing .NET code for another few years)
|
|
|
|
|
|
Collin Jasnoch wrote: I see a lot of manufacturing jobs that have a need for employees that know PLCs and have a lot of C# experience.
The PLCs themselves don't need to be programmed in their own archaic language anymore.
At least, not if you are using products like the one from Steeplechase System (sold to someone else so it has a different name; Google for it if you need to know).
You just draw the flowchart for the control network and that is treated as the program and compiled into code. Runs on PCs.
|
|
|
|
|
|
I looked at Steeplechase software in 1995.
I think at that time 120 MHz Pentiums were top of the line.
The claim was made that such a PC could replace 2700 PLCs.
Steeplechase software was located in Ann Arbor, Michigan and sold its software to the likes of GM, Chrysler and Ford.
One would think those companies would have evaluated the stability and reliability of the product before installing it in their assembly lines.
But I have no first-hand experience with its use in any manufacturing facility I worked in.
|
|
|
|
|
|
Collin Jasnoch wrote: Really the only the the PC offers in replacement is a bigger pool of software developers. But that is not necessarily a good thing. A company wants to hire a talented software engineer and has to filter out the numerous candidates. If
their tools are so common that people in high school understand them enough to be dangerous they have difficulty filtering. Where as if some of the tools are simple while some are complex they are assured the candidate is good simply by having the skill set.
Interestingly, Steeplechase used a flowchart to describe the logic and its code generator would generate code from the flowchart! Talk about eliminating programmers altogether!
By your logic, we should ban not just VB but all frameworks too and force people to code in assembler. That should severely restrict the number of people willing to do the drudge work of writing programs!
PS. I see your viewpoint but I think we have seen orders of magnitude improvement in reliability and performance of PCs.
By the way, as early as the early 1990s, companies were offering small form-factor boards with an Intel microprocessor and memory and I/O (slightly larger than credit cards) for industrial purposes.
|
|
|
|
|
Not to say that MS might of handled VB6 backward compatibility better - there were oh-soo many projects that instead of being ported to .Net got ported to Java just because VB.Net and VB6 compatibility issues.
|
|
|
|
|
Yep, zero information there, no number no nothing.
Wout
|
|
|
|
|
"It was supposed to destroy Java, extend the Windows platform, and secure the Microsoft monopoly for another decade or two."
The deuce you say.
"Microsoft did many things right. It hired the smartest experts on language design, compilers, and virtual machines. But it also did some things terribly wrong."
Yes, like hire the smartest experts on language design, compilers, and virtual machines.
As for me, .net came around at exactly the right time -- when my OpenVMS career ended.
Yes, I now have a Java for Android book, but C# is just so much fun I've barely started it.
|
|
|
|
|
A unaddressed bug in Apple's Mac OS X discovered five months ago allows nefarious hackers to bypass the usual authentication measures by tweaking specific clock and user timestamp settings, granting near unlimited access to a computer's files. That feeling you're experiencing? That would be schadenfreude.
|
|
|
|
|
An ambitious project means anyone can now track the movements of almost 50 sharks in realtime. "The calls are coming from the house!"
|
|
|
|