No I am not using Blazor yet, but...

My feeling is very negative towards the whole front end development
situation.
Silverlight was a great technology ten years ago.
After what Microsoft did to us I have huge trust issues with them now!

JavaScript is a whole different paradigm which in my arrogant opinion is
not a real language!
There are tools that make JavaScript slightly less bad.
But it is still JavaScript!

Maybe Angular is almost at the same level of functionality now that
Silverlight was ten years ago???
But it adds hundreds of open source code libraries to my solution which I
have no control over.
I see that as a DevOps / DevSecOps nightmare!
I am NOT recommending Angular to my clients!

My preference would be to do as little as possible on the front end, in the
real world that is not possible!

My current advice to my clients is...
Have HTML on your front end.
Call back to the server where you can run your favorite language in a
controlled environment.
Send back new chunks of HTML to update the display as needed.
Do as little as possible in JavaScript.

If your favorite language is C# Web Assembly and Blazer offers some real
promise.
My understanding is at the recent build conference there was not even any
discussion about Blazor.
Maybe Microsoft has learned not to talk about what they have not yet made a
firm commitment to????
They are trying to do a release every 14 days see
https://blogs.msdn.microsoft.com/webdev/
Last release was 2-May (V0.3, 22 days ago,
https://blogs.msdn.microsoft.com/webdev/2018/05/02/blazor-0-3-0-experimental-release-now-available/
)
Then 17-April (V0.2,
https://blogs.msdn.microsoft.com/webdev/2018/04/17/blazor-0-2-0-release-now-available/
)

If you look at https://github.com/aspnet/Blazor
You see the last commit was a day ago.

Also worthwhile to read: https://github.com/aspnet/Blazor/wiki/FAQ

I could not find the comment again about the 14 day release cycle.
Maybe that has gone away????

Opinion:
If Microsoft does this right (which they look to be doing)
If it remains open source
After it gets a little more mature.
After Microsoft (or other large company) makes a public commitment to the
technology
If it works as expected
I will change my attitude to the technology to full support

After Microsoft !@#$%^& us with Silverlight, I think they are being careful.
But also I will be very careful about picking any new technology.

My gut tells me that I should make the jump to Blazor.
But my head is still say wait and see...

All the best
Just another Greg in the room :-)



Greg Harris
[email protected]
phone: 0407 942 982
Baulkham Hills
NSW 2153



On Tue, May 22, 2018 at 8:57 AM, kirsten greed <[email protected]>
wrote:

> Hello
>
> Is anyone out there using Web Assembly and Blazer for real projects?
>
> I just spent a couple of days trying to get the code generated by Visual
> Studio's AutoRest add in  to work with Bearer token security.
>
> It turns out that the Autorest project on Github has moved on from that
> old code and done a big re-write
>
> Greg's blog at https://gfkeogh.blogspot.com.au/2018/02/im-in-future-
> of-web-and-it-doesnt-work.html
>
> back in February did sum up everything eloquently in my view.
>
> Is anything better out there yet?
>
> Thanks
> Kirsten
>
>
>
>

Reply via email to