|
I've been under the impression over the past 4-5 years that Javascript is the new Silverlight. The perception I've always gotten is that their NodeJS investment and efforts are their way of placating the OSS community. What's really lousy is that there is no migration strategy to go from SL into something else.
For those of us that despise Javascript, WebAssembly is our great compiled hope for the future. All the client-side acrobatics JS frameworks have done to bastardize HTML in the browser (looking at you, React framework) can be drastically minimized using...Razor pages. How sweet it is!
WebAssembly is the future - at least it is for me whenever I need to build client-side web app functionality.
Javascript frameworks (especially React) are quickly becoming the Web Services of HTML.
|
|
|
|
|
Though I have never been a fan of ASP.NET MVC, I believe the new Blazor software is a step in the right direction as it is beginning to return to some of the ease-of-use that made WebForms so successful while allowing developers to conform to the C# language on both the client and server sides of the equation.
Like many developers, I have found JavaScript to be a complete headache to work with and the prevalence of the JavaScript Frameworks now available has made web development a nightmare. As a result, I stopped developing my projects for the web when I retired from corporate development in 2014.
As WebForms drifts into obscurity, I don't see Microsoft suddenly dropping the Blazor Platform once it has been released for commercial development. If they did this, the company would have no web development standard to rely on.
That being said, I see Blazor being refined into a more WebForms like environment that will return web development to the same ease-of-use paradigm that made such Microsoft tools so popular...
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
MS can revive Silverlight by reimplementing it in Blazor/Webassembly without use of plugin
|
|
|
|
|
|
|
R.I.P. anther good one gone.
Everyone has a photographic memory; some just don't have film. Steven Wright
|
|
|
|
|
It sucks.
He suffered much, nevertheless, he persisted and put country above all.
![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
I'd rather be phishing!
|
|
|
|
|
I encourage you to go back and read what the MSM wrote about him when he ran against Obama the first time. His "Bomb, Bomb Iran" comment. And the fact that amazingly, HE TOO has a "Foundation" that takes money from the likes of George Soros (a Devout Globalist, who has a stated goal of destroying America, and Capitalism, and a shameless Nazi supporter who said he lost no sleep over what he did).
Funny how the theme changes when he dies. My opinion of him will never change. As a libertarian, I view him as a war monger who profited from big military contractors.
I am glad he is no longer suffering.
|
|
|
|
|
The enemy of my enemy is my friend
Arthasastra: Book VI
The king who is situated anywhere immediately on the circumference of the conqueror's territory is termed the enemy.
The king who is likewise situated close to the enemy, but separated from the conqueror only by the enemy, is termed the friend.
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
That's the most honest thing I've read in this thread, and reflects the reality as I see it, and tried to state it. If he was Pro-Trump he would be demonized as a Nazi, Baby-Killer, SongBird, WarMonger. But like a TYPICAL Politician, he wanted good press in his dying days, so he went the other way. And "Look, all is forgotten!" LOL!
|
|
|
|
|
RIP .
August has claimed many a good man.
|
|
|
|
|
> "good man"
> "John McCain"
Error: incompatible constraints on node 1
|
|
|
|
|
A soldier never dies but becomes imortal.
Thanks & Regards
Puneet Goel
Save Paper >> Save Tree >> Save Humanity
|
|
|
|
|
He was a decent politician.
There are to few of his kind.
|
|
|
|
|
So much for cross-aisle cooperation. Now partisanship will become the standard.
|
|
|
|
|
I didn't care for the man.
When the borders of [fill in the blank]-istan are more important than those of the USA then you're a bad Senator.
|
|
|
|
|
I wonder what are your strategies for learning a new technology. Do you read one or more books first to get a grasp of what a certain technology is capable for, or do you start developing or practicing creating apps after reading some articles and then googling the missing pieces along the way as you code? I know people who never read books cover to cover and just learn on the go.
I like to have a better grasp of the technology first before starting a project, so I try to read a beginner book first, then some intermediate to advanced books, sometimes before even trying to create an app. Sometimes I just try to have a big picture of all the capabilities of a certain technology before starting to code and just go back to a certain topic when I am about to code. It is sometimes a problem of learning to much firsts before starting coding.
If you try to go and immediately code after reading a few tutorials, you may be able to create a full app without entirely knowing the full capabilities of the technology, and so you may try to do certain things the wrong way when there are a more official way on doing it.
Let's put React.js for example. I can simply learn react by looking at the "Getting Started" and some basic concepts, and then start coding immediately. But then I will miss concepts like redux and other patterns if I don't read an entire book.
What are your thoughts? What is the better way to learn and be comfortable with a certain technology?
|
|
|
|
|
First, there must be a need.
|
|
|
|
|
|
Or are you a nerd for speed?
|
|
|
|
|
Shouldn't that be a nerd for sperd?
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Better a nerd than a hunk.
|
|
|
|
|
Unless you are feeling hunky-dory 
|
|
|
|
|
|
I always read first, go through a few tutorials then usually dive in. But always go back and read more to pick up advanced concepts. The stuff I'm trying to learn now I've read/reading 3 books, one of them 1600+ pages before writing any code.
Everyone has a photographic memory; some just don't have film. Steven Wright
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
