History has some strange twists and turns for those willing to see them. Blazor is one of the oddest. Take .NET compile it to Web Assembly and run it in the browser. Sounds like fun? Now we can all try it out as it reaches version 0.3.
Blazor isn't a completely silly idea, but it almost is.
The crazy idea is compiling the Mono runtime to WebAssembly. Why it's Mono that is used rather than .NET Core is a good question, but I suppose if the Mono team has done the work why not? Given you have essentially .NET running in the browser, you can now write C#, or any .NET langauge, programs in the browser.
The only question that remains is: "How are the languages going to interact with the browser?"
There are two possible answers.
You could add some code to make the environment look like Windows. This would give you something like Silverlight used to be.
You could build an interface to the DOM and all things HTML.
The latter is what the Blazor team has decided to do and as a result it is difficult to see the use case for it.
Nevertheless the Microsoft team is pressing on.
Blazor lets you write .NET code and run the result in a browser. At the moment there is no plan for a native mobile app. Technically it isn't ruled out, but it would go up against Microsoft's other mobile solution, Xamarin.
The new elements in Blazor 0.3 are:
- Project templates updated to use Bootstrap 4
- Async event handlers
- New component lifecycle events:
- Component and element refs
- Better encapsulation of component parameters
- Simplified layouts
Now that we can all try it out we can find out if it is a good idea.
After all how many Microsoft ways are there now to create web pages?
I know I keep saying it, but how could Microsoft have left a revolutionary technology like Silverlight just die...
Amazon has launched a service for querying streaming data using standard SQL to help developers create apps that analyze real-time data without the need to use specialist languages and techniques such as those in Apache Storm.
Ceylon was Redhat's Java killer. Of course, it didn't kill anything much and now it has been "donated" to the Eclipse foundation. You can view this as a positive or a negative step depending on your outlook. What you can't avoid is the simple fact that building a Java killer is too easy and there are too many of them.
- March MOOCs
- Master Phase Of IARPA Mapping Challenge
- OpenStreetView Launches
- Hand Tracking With Nothing But A Webcam
- Get Up To Speed With iOS 10 with Udemy
- Nanodegree Plus Offers Guaranteed Jobs
- 10 Million Raspberry Pis
- RethinkDB Closure Analysis
- Low Cost Robot Wins Amazon Robotics Challenge
- EdgeX Foundry - Open Source Framework For Industrial IoT
- Developer Pay Satisfaction According To Stack Overflow
- Alexa Skills Contest Winners