S
StrandElectric
....continual Micro$oft changes. And is the C# that is part of the visual
studio 'vb2008Express' download, the 'real' C#?
studio 'vb2008Express' download, the 'real' C#?
...continual Micro$oft changes. And is the C# that is part of the visual
studio 'vb2008Express' download, the 'real' C#?
...continual Micro$oft changes. And is the C# that is part of the visual
studio 'vb2008Express' download, the 'real' C#?
Both languages continue to evolve, so it's not like your not going to
have changes from one version to the next...
Not sure where MSFT is with this today:
http://channel9.msdn.com/Blogs/Charles/Luca-Bolognese-C-and-VBNET-Co-
Evolution-The-Twain-Shall-Meet
http://blogs.msdn.com/b/scottwil/archive/2010/03/09/vb-and-c-
coevolution.aspx
Funnily enough Tom, vb6 was meeting my need! I am invetsigating changing toTom Shelton said:It happens that StrandElectric formulated :
Huh? There is nothing really wrong with VB.NET - I personally like
C-style languages better, so I use C#... It also has an advantage, IMHO,
because it is backed by an actual standards body (ECMA and ISO) - and the
most support on alternative runtimes such as Mono - which means easier
porting to OS's other then Windows. It also can be used more easily for
more MS platforms, such as Windows Phone 7, Zune, XBox 360, etc - but,
unless your wanting to target those devices it's not a big deal.
Both languages continue to evolve, so it's not like your not going to have
changes from one version to the next - though, MS has done a dang good job
in .NET so far of not breaking code as you move forward.
In other words, if VB.NET is meeting your needs - there's not a real
reason to switch. In most ways, especially after the current 2010
release - the languages are pretty much on par feature wise...
Funnily enough Tom, vb6 was meeting my need! I am invetsigating changing to
vb.net in case classic will not work in future versions of windows.
On another tack, have had look at some C# code, and no thanks! What tedium
with the non-intuitve curly brackets for example. And I note the use of the
term namespace and also the Catch Try structure. So no doubt a lot of the
development of vb.net is influenced by C proponents.
Actually I agree about that!Tom Shelton said:StrandElectric laid this down on his screen :
And, it most likely will not - at least on some version anyway.
Try/Catch is used in most modern lanugages - or some variation of such - C
based or not. Most modern OOP languages, support the idea of structured
exception handling, and those words seem to really capture that nature the
best
Hmm... My old cyncism is returning...Mayayana said:| On another tack, have had look at some C# code, and no thanks! What
tedium
| with the non-intuitve curly brackets for example. And I note the use of
the
| term namespace and also the Catch Try structure. So no doubt a lot of
the
| development of vb.net is influenced by C proponents.
|
The idea was to force everyone to move to managed
code. .Net was to copmete with Java. (Which it did
quite well.) Then it turned out to be just the thing
for the SaaS craze. And now it's a great way for MS
to pull an Apple, mediating between developers and
end-users, and taking a cut. (Today Phone 7, tomorrow
the world.)
With C*, many of the C/C++ people are somewhat
vain about their language and look down on Basic, so
their version of .Net always has to be just a little
better, else they wouldn't use .Net. If you look at the
MS pages for info. and download you'll see that C# is
for adults and VB.Net is marketed as "good enough for
hobbyists". Yet they both use the same basic framework.
The idea was to force everyone to move to managed
code. .Net was to copmete with Java. (Which it did
quite well.)
Then it turned out to be just the thing
for the SaaS craze.
And now it's a great way for MS
to pull an Apple, mediating between developers and
end-users, and taking a cut. (Today Phone 7, tomorrow
the world.)
With C*, many of the C/C++ people are somewhat
vain about their language and look down on Basic,
so
their version of .Net always has to be just a little
better, else they wouldn't use .Net. If you look at the
MS pages for info. and download you'll see that C# is
for adults and VB.Net is marketed as "good enough for
hobbyists". Yet they both use the same basic framework.
Yes. When .Net first started being successful I
asked a friend, who was a software project manager,
why that was. Without pause she said, "Tools.
There are much better tools for .Net." I'm not surprised.
Open source rarely produces convenience.
No. That's why it's a craze. But Microsoft is taking
it seriously with Azure.
You present your opinion as fact. There's nothing
to stop you from writing for Phone 7.
(Any sales
from your Angry Squirrels app yet?)
But people
have a right to know what they're getting into and
deciding for themselves. My own opinion is
that I don't care to write software if MS is going
to tell me what I can write, so the idea that .Net
can target Phone 7 is irrelevant to me.
I'll bet you like those new "pentalobular"
screws that Apple's started putting in their
products to prevent you, the consumer, from
carrying out risky repairs and maybe hurting
yourself.
http://www.cio.com/article/656322/The_Case_of_Apple_s_Mystery_Screw
I didn't see anyplace where you actually said
what you're doing in terms of projects. .Net is
sort of the only game in town at this point, in
many ways. VB is arguably the most widely
supported tool, running almost dependency-free
on Win95
to Win7, but it's really just for 32-bit
PC software. As Tom said, .Net is being adapted
to a lot of things. If you want to write phone
"apps" for Windows Phone 7 that would be .Net.
If you're writing server-side applets on a corporate
network that's probably .Net.
Silverlight? .Net.
And there's talk that Win8 may be "Desktop as
a Service":
http://www.zdnet.com/blog/microsoft/windows-8-to-showcase-desktop-as-a-service/7975
That would imply lots of web services that people
use from any machine they're on... and probably
some kind of MS App Store for that as well. That's
likely to be something where only .Net can be used.
Probably.
On the other hand, Desktop .Net is silly.
Silverlight is being scaled back.
The ARM chips
that Tom mentions are for phones.
Smart phones are a current gimmick that few make money at.
And Windows smart phones are notably unsuccessful so far.
So what's the
real value of all these places where .Net can be used? You're
looking at something like a replay of the shareware craze
on phones, but with MS controlling your connection to customers.
If they can pull off that kind of control on Win8 then no doubt
they will. Vista/7 is already a restrictive corporate workstation
with MS as SysAdmin. All MS needs to do now is to clamp
down on "unrecognized and potentially unsafe" software
installation and suddenly their PCs are just like gigantic
smart phones, with you having to rent software through safe,
official online stores. (I imagine that Mr. Ballmer must salivate
over the tight control Apple manages to keep over both Apple
developers and the customers... not to mention the 30% (?)
cut they get on software sales for the iPhone.)
To me all of that leads to much bigger questions: What
will computers be in 3-4 years? If you're writing software
for others to use, what do you want to write, will anyone
care, and will they be able to install it? Will you be able to
really write Windows software, or only nonsense like iPhone
apps for smart phone addicts to play with while crossing
busy city streets?
I saw a bit on Saturday Night Live recently that captured
the feverish and off-kilter quality of the current landscape.
I have to paraphrase. It was on the news segment and went
something like:
"The IRS is now making tax forms available for the iPhone.
Great. Now you can fill out those really confusing forms on
a much smaller screen."
Mayayana said:| >
| Hmm... My old cyncism is returning...
|
I didn't see anyplace where you actually said
what you're doing in terms of projects.
After this one, less than 3 months ago?
http://www.zdnet.com/blog/microsoft/microsoft-our-strategy-with-silverlight-has-shifted/7834
Even if they go back to SL for the Web, Silverlight
for Windows software is still as dead as Adobe's AIR.
They're both desperate attempts at control of the market,
with lots of ambition and little common sense.
Aren't we talking about .Net Windows development?
ARM for Windows, other than phone, is still in the
vaporware labs.
More opinion as fact. And more opinion that's being
colored by your own personal hopes.
Maybe real Windows
will get to ARM. (They can barely fit it onto a PC at
this point.) I haven't seen anything about ARM servers
and PCs. What I've read is an ongoing discussion about
whether Windows will ever get to ARM in the first place,
and that's only in the context of tablets. (Then of course
there's the question of who might be buying these
theoretical tablets, and whether they'll actually use software
or perhaps just twiddle their Facebook and send photos.)
So maybe there's a future for Windows programming on
ARM ... somewhere down the road. And maybe there isn't.
If you're going to market .Bloat for ARM then you really should
include the caveats.
Glimpses of the future? You're such a consumer.
The most successful app on iPhones is Angry Birds.
Then there's the Moron Test. And hundreds of thousands
of other fluff trinkets. It looks an awfully lot like
the shareware market of 2000 to me. A few people
hit it big. A lot more made pocket money. Then the
market evaporated. Everyone was talking about the
Internet, but it was just the latest fad.
I think you do have a point in one sense, though:
When people become addicted to sucking on a pacifier
on a nearly constant basis, you can't just take it
away. So for the phone addicts who survive crossing the
street, something will have to replace their phone apps.
But we don't know what that is. Yo yos? Sudoku on the
inside of their glasses? ...Let me guess, .Net is being
ported to glasses?
Or another way one could put it: I have a different
opinion.
After this one, less than 3 months ago?
http://www.zdnet.com/blog/microsoft/microsoft-our-strategy-with-silverlight-has-shifted/7834