Some parts of this page may be machine-translated.

 

【Overseas Event Introduction】Bet You Didn't Think Your Browser Could do That by Monica Dinculescu

【Overseas Event Introduction】
Bet You Didn't Think Your Browser
Could do That
by Monica Dinculescu

This time, we will introduce the content of "Bet You Didn't Think Your Browser Could do That" from the presentation at "Jamstack Conference 2018"!

 

The "Jamstack Conference" with over 10 years of history is hosted by "Netlify", the creator of Jamstack. Developers from around the world gather to discuss the latest website design and development concepts based on Jamstack. The language used for presentations is English, but we will introduce it in Japanese on this blog.

 

Table of Contents

This time's speaker is Monica Dinculescu, the developer of Magenta, a platform that combines machine learning with music and art.

 

The "sloppiness" required by programmers, this is how it is utilized in Jamstack development.

 

Let's take a look right away.

Development Flow Bottleneck

 

The above figure is a representation of the service developed by Ms. Monica, until it reaches the user.

 

The pixels surrounded by pink represent the parts she directly develops, in her unique expression.

 

The yellow highlighted section represents the process that takes place on the server.

 

Development of pixels can be completed in as little as 1 day, depending on the item.

 

However, there may be issues with the process that takes place on the server in the yellow section, which can take more than 4 months to fix or maintain.

 

What is one of the causes of problems that occur in the processes performed on the server?

Complexity Issues

 

One of the causes of problems that occur in processes on the server.

 

That, complexity is emphasized by Ms. Monica.

 

An example of complexity is...

 

When using JavaScript libraries, there are times when you may want to import the library even if you do not actually use all of its features, just to have it available.

 

As a result, there will be a mix of different versions of libraries. So, what will happen?

 

Libraries cause conflicts due to version differences, resulting in frequent errors.

 

This is just one example, but when a single developer tries to handle even server-related errors like this...

 

Required skills cover a wide range. It also incurs costs.

 

In reality, it is not possible for one person to become an expert in all areas.

 

And yet, why is it that the belief that "static sites are no good!" is still ingrained in developers and the focus is placed on server-related tasks?

Why do you need a server?

The three main reasons often cited for the need for a self-hosted server are...

 

① Hosting

 

[Reason 1]

 

It is believed that a server is necessary to host the created service.

 

[Actually]

 

You can replace it with a cloud service like the one shown in the image above.

 

Setting up your own server, managing things like OS and patches, and monitoring the network... It is much more beneficial to allocate this cost to your original development tasks!

 

② Database

[Reason 2]

 

It is believed that a database is necessary.

 

[Actually]

 

Databases can also be used with cloud services!

 

You can use cloud services even with SQL or NoSQL, and even with local storage.

 

③ Interact

[Reason 3]

 

Have customers fill out the form and perform user authentication.

 

It is considered essential to have a server for this.

 

[Actually]

 

These can also be solved with services provided by third parties!

Current Dynamic Processing in Browser

The range of things that can be done simply by calling the browser and JavaScript libraries has greatly expanded. Four demos were introduced in the presentation.

 

Here, we will introduce one of them!

 

Tensorflow is a famous Python library for machine learning.

 

There are also increasing examples of using the JavaScript version of tensorflow.js.

 

These achieve high-speed processing at the same level as when executed on a local machine on the browser.

 

Summary

"Being lazy" is a fundamental concept that is conveyed to programmers.

 

In other words, the concept is to not repeat tasks that were originally unnecessary or tasks that are unnecessarily repeated.

 

Various libraries have evolved based on this philosophy.

 

Development processes have become more complex, and the knowledge that needs to be acquired has increased.

 

It is ironic that the result is moving further and further away from the desired "sloppiness".

 

"Jamstack" was a natural landing point for her, as she returned to "sloppiness" in the new generation.

 

It seems like we can expect more and more from now on!!

 

Thank you for reading until the end.

 

Human Science Co., Ltd. offers unique solutions for web content and platforms using the combination of "document creation know-how" and "the latest web development technology (Jamstack)" that other companies do not have.

If you are interested, please contact us here!

Human Science Co., Ltd.

https://www.science.co.jp/document/jamstack.html

 

Source of this document: https://www.youtube.com/watch?v=f5QYSdpMs6Y

[jamstack_blog_tag]

Related Blogs

Popular Article Ranking

For those who want to know more about manual creation and instruction manual creation

Tokyo: +81-3-5321-3111
Nagoya: +81-52-269-8016

Reception hours: 9:30 AM to 5:00 PM JST

Contact Us / Request for Materials