開発スタッフがアプリ関連の最新技術やニュースをご紹介します。

Today I will give you an abstraction about how programming works.

The computer only understands the instructions in machine language code.

But it is more difficult to write a program in machine language code.

So, we have to write programs in higher level languages such as Java, PHP, Python and etc. But we cannot execute this source code (high level language code) directly on the computer.

Therefore, we must convert them into machine language code to be able to understand for computers. We need some special translators that are programs written basically in machine language code.

And these translators are called language processors.

There are 3 types of language processors.

Compiler

It is used for higher level language.

Read and run the entire program at once and then throw errors if one occurs.

The top-level languages that compilers use is: C, C ++, C #, Java etc.

Assembler

It is used for assembly level language (mnemonic codes).

Read the assembly level language instructions for the given entry.

Interpreter

It is used for higher level language.

Read and execute the source code line by line and throw an error after each line if one occurs.

The top-level languages that use interpreters are VB Script, Python, Perl etc.

Now you will have a general understanding of how programming works.

By Yuuma.

Tweet

今回は、CakePHPとデータベースの接続について説明をおこないます。

Tweet

Today I will talk about a trendy browser called brave. Lets check it out.

Barve ?

Brave is a more-or-less standard browser that lets users navigate to websites, run web apps and display or play online content. Like other browsers, it is free to download and use, remembers site authentication information and can block online ads from appearing on sites.

Its maker, Brave Software, is a relatively new entry in the browser battles, having first previewed the browser in January 2016. The firm was co-founded by Brendan Eich, the creator of JavaScript and a co-founder of Mozilla.

Any Differences ?

What sets Brave apart is its aggressive anti-ad attitude. The browser was built to strip online ads from websites and its maker’s business model relies not only on ad blocking, but on replacing the scratched-out ads with advertisements from its own network. It’s as if a new TV network announced it would use technology to remove ads from other networks’ programs, then rebroadcast those programs with ads of its own devising, ads that it sold.

Interesting Fact

Brave is built upon Chromium, the open-source project Google and others maintain. (Google uses Chromium to provide the source code for its Chrome browser.) The back-end technologies that power Chrome – including the Blink rendering engine and the V8 JavaScript engine – also power Brave.

Brave boasts of two things: Its speed and the privacy it provides users. Both result from its ad-stripping strategy.

On the desktop, Brave loads pages twice as fast as Chrome and Firefox. On a smartphone, Brave loads pages up to eight times faster than Chrome (Android) or Safari (iOS).

The speed increases are not surprising. By eliminating ads and ad trackers, Brave downloads much less content from a website than any browser sans an ad blocking extension. There’s nothing technological about Brave’s performance; it’s simply retrieving less data than other browsers. (If that weren’t the case, Chrome and other Chromium-based browsers would be just as fast.)

Economy

The foundation of the Brave economy will be “Basic Attention Tokens” or BATs, which have a value derived from a cyber-currency. Those tokens will be awarded based on user attention, or more plainly, time spent viewing ads and content. Brave users who agree to receive ads will be rewarded with BATs. Brave envisions users trading their tokens for premium content or advanced site features.

Download brave here.
https://brave.com/download/

By Yuuma.

Tweet

Today, I would like to share about PSR called PHP Standards Recommendation which are also known as coding standards of PHP. Actually, PHP does not have coding rules and standards itself. Developers tend to create their code to be more maintainable & safer by using naming conventions and various coding styles. Some use frameworks like PEAR, Zend to standardize their code.

Just In Case If you don’t know about `coding standards`

Coding rules and guidelines ensure that software is:

• Safe: It can be used without causing harm.
• Secure: It can’t be hacked.
• Reliable: It functions as it should, every time.
• Testable: It can be tested at the code level.
• Maintainable: It can be maintained, even as your codebase grows.
• Portable: It works the same in every environment.

Standards are important for safety, security, and reliability.

Every development team should use a standard. Even the most experienced developer could introduce a coding defect — without realizing it. And that one defect could lead to a minor glitch. Or worse, a serious security breach.

There are four main drivers for using one:

1. Compliance with industry standards (e.g., ISO).
2. Consistent code quality – no matter who writes the code.
3. Software security from the start.
4. Reduced development costs and accelerated time to market.

In 2009, There was a conference about PHP (https://tek.phparch.com/). At that conference, developers discussed about their opinions on working PHP projects and their complexities upon them. Finally, they decided to create coding standards to follow. The name of that association was PHP Standards Group. They updated their name as Framework Interoperability Group(FIG) later.  You can see more detail about FIG here (https://www.php-fig.org/).

Currently there are 13 approved standards.

1  Basic Coding Standard

2  Coding Style Guide

3  Logger Interface

4  Autoloading Standard

6  Caching Interface

7  HTTP Message Interface

11  Container Interface

13  Hypermedia Links

14  Event Dispatcher

15  HTTP Handlers

16  Simple Cache

17  HTTP Factories

18  HTTP Client

If you are still curious to know about other standards that are currently reviewed, draft, abandoned. Check out this official link (https://www.php-fig.org/psr/).

By Yuuma.

Tweet

本記事は前回の「CakePHP フォームヘルパー(1)」の続きです。
前回はCakePHPの「フォームヘルパー」という機能を使用して、入力フォーム用のHTMLを作成しました。
今回はそのフォームを使用して送信(Submit)された値をコントローラー側で受け取る方法を説明いたします。

Tweet