1 year agoWebAssembly is a new binary format in which web applications can be compiled. It is projected and implemented directly while you read these lines and developers of all main browsers move it forward. Everything changes very quickly! We will show a current status of the project with rather deep immersion in tools on work with WebAssembly in this article.
In order that WebAssembly earned, we need two main components: the code assembly tooling in a binarnik of the WebAssembly format and the browsers capable this binarnik to load and execute. Both that, and another is not completely created and very strongly depends on completion of work on the WebAssembly specification, but in general it is separate components and their development goes in parallel. This separation — a good thing, it will allow compilers to create the WebAssembly-applications capable to work in any browser, and to browsers — to start WebAssembly-programs is not dependent on by what compiler they were created. In other words — we receive an open competition of building tools and browsers that all this will continuously move forward, bringing to the ultimate user the excellent choice. Besides, such separation allows design teams of tools and browsers to work in parallel and independently.
The new project on the party the WebAssembly tools about which I want to tell today is called Binaryen. Binaryen is the library for support of WebAssembly in compilers written on With ++. If you personally do not work on the compiler WebAssembly, then you probably do not need to know something about Binaryen directly. If you use some compiler WebAssembly, then it, perhaps, under a cowl uses Binaryen — we will review examples below.
1 year ago I begin to publish a series of articles about web development on the Erlang. Many want to try the Erlang, but face a problem that introduction courses generally concern the Erlang as functional language and are far from real projects (Learn You Some Erlang for great good! — good and detailed book). On the other hand all training materials on web development mean that the reader already well knows the Erlang.
This series of articles is calculated for developers who have an experience in web development (PHP, Ruby, Java), but have no experience of development on the Erlang.
At the heart of the project feymvork n2o. The choice is quite subjective, but from live the Erlang of frameworks, n2o me seemed to most "erlangopodobny", in too time of ChicagoBoss is more similar to MVC frameworks in other languages.
1 year ago
Somehow I was asked to hold a small seminar in lyceum where I once studied, on creation of the website. In the course of writing of the speech I thought that it can pour out in material which, perhaps, will be useful to many beginners in the field of web-design, imposition of web pages and so forth. I do not apply for truth in the first instance and everything stated carries purely personal view of work with design and a code. Article gives a superficial glance on concepts and means which, in my opinion, can become quite good start for this purpose who is ready to go further.
The idea of this article was born after several painful weeks of studying of WebGL. On a personal example it became clear that the people who are not facing before with 3D - graphics, have generally wrong ideas of work of this technology. Besides there was a problem with information search on the Internet.
This article there is a wish to facilitate a threshold of entry in pure WebGL, to give an initial idea and to prompt, where to move further.
1 year ago
I as much as possible will try to write without "water". A minimum of the excess distracting information and verbalizations. Maximum of useful information and working code. I will not bring up a question why to someone own torrent search engine based on RuTracker. And I do not consider myself the guru of programming. We will just make this website together. Let's use Apache+PHP, MySQL and Sphinx. At once I will warn that the website will work at the minimum virtual hosting absolutely not quickly.
On Codepen many good solutions from different specialists appear, and I consider that the best of them need to be collected in one place. Therefore began to save at itself on the computer interesting scripts on different subjects 2 years ago.
Earlier I spread them in group of a product of cloudy IDE mr. Gefest, it were assemblies from 5-8 solutions. But now at me began to accumulate till 15-30 scripts in different subjects (buttons, the menu, hints and so on).
Such big sets should be shown to bigger number of specialists. Therefore I spread them on Habr. They hope to you will be useful.
1 year ago
Transfer of a post how Windows Azure API was developed is offered to your attention: about difficulties, successful and unsuccessful solutions, the drawn conclusions. Further — the text of the author.
After conversation with my fellow worker on REST API the idea to tell about the experience the organizations and works of command which created Windows Azure Service Management API came to my mind. On writing of this post I was inspired by such magnificent articles in a genre "to what I learned" as this behind authorship of Foursquare and this from Daniel Dzhakobs from Netflix.
Warning: Everything told under a cat — my personal opinion. I am not sure even that other participants of command agree with me. And I precisely know that some of the introduced ideas are quite inconsistent.
This article is transfer ASP.NET of 5 — A Deep Dive into the ASP.NET 5 Runtime — introductions to architecture of DNX and ASP.NET 5 constructed on it. As original article was written in March, 2015, to time when ASP.NET 5 was in a stage of active development (approximately beta 3), a lot of things in it became outdated. Therefore at transfer all information was staticized to the current ASP.NET 5 version (RC1), references to the connected resources (generally on docs.asp.net) and the source code on GitHub were also added (you look only in cases if implementation is interesting to you). Pleasant immersion!
.NET Runtime Environment (DNX)
ASP.NET 5 is based on flexible, cross-platform runtime which can work with different .NET CLR (.NET Core CLR, Mono CLR, CLR. net Framework). You can start ASP.NET 5 using a complete. net Framework or can start using new .NET Core docswhich just allows you to copy all necessary libraries together with the application in the existing environment, without change something else by your machine. Using .NET Core you can also start ASP.NET 5 krossplatformenno on Linux docsand Mac OS docs.
The infrastructure allowing to start and perform the ASP.NET 5 applications is called .NET Runtime Environment docsor DNX is short. DNX provides everything that is necessary for work of .NET of applications: host process, CLR hosting logic, detection of the managed Entry Point, etc.
Logically the architecture of DNX has five layers. I will describe each of these layers together with their duties. The image is taken from the article DNX-structure wiki