exploring truth, post binary

[booellean]

On May 7th through May 9th, the non-profit I volunteer for, NoSchoolViolence.org had a Hack-a-thon with our most recent partner Microsoft. Because of this wonderful experience working with some fantastic senior architects, our organization is closer than ever to full development of the Lantern and LightKeeper, tools that utilize machine-learning and correlation to help curb school violence.

Thank you everyone who made that day so special! Looking forward to our continued efforts in this very needed project.

[booellean]

Me, in college

[booellean]

regex.test V.S. string.match to know if a string matches a regular expression

Many times I'm using the string match function to know if a string matches a regular expression. if(str.match(/{regex}/)) Is there any difference between this: if (/{regex}/.test(str)) They see...

I was researching the differences between str.match(regex) and regex.test(str) for they appear to do the same thing at first glance.

What I found is this: .match returns either an array or null while .test returns a boolean value. So, what does this mean to me as a developer?

If I want fast checks, .test is the way to go, for the check will end the moment a boolean returns true. .match should be reserved for the moments I need to find all or some of the values so a thorough check needs to be performed.

[booellean]

Beyond the Browser

Is the future of the mobile web in native applications?

The advent of the mobile web has completely redirected how we developers design and program for the user experience. Devices and programs are quickly becoming completely interconnected; even today, phones, televisions, cars, computers and even refrigerators can exchange data. This is in part thanks to JavaScript (js), the closest global programming language we have.

Even so, js has its limitations. First, js is run client side, so its execution is completely reliant on the device and their API. Second, it is a single threaded synchronous programming language, and as such execution of an operation can easily be blocked while js waits for a callback.

Thankfully, many of these issues are resolved when js moves from the browser and is programmed within a native application. Frameworks such as Electron, NativeScript, and React Native can create native applications using a combination of css, html, xml, and js. They resolve issues web applications have with js, such as blocking, cross platform user experience uniformity, and access to native modules. In other words, you can get the best of js by programming within a native interface.

To expand this further, the frameworks are asynchronous programming languages that prevent blocking whilst an operation is awaiting completion. Js is prone to blocking due to it being single threaded, limited by input/output (I/O) functions and callbacks. By taking advantage of the multi-threaded language of the framework, js execution can continue while a block of code is waiting for a callback.

Furthermore, cross platform user experience is essential to good coding and design. When js is in a web application, the execution is determined by the client side browser. Thus, the browser’s execution is determinant on the device, i.e. if the device a computer or a smartphone they may execute the js differently. In a native application, the device will run the js consistently, for it is the framework that is executing the js code. By using the aforementioned frameworks the code is going to be cross platform, functional and identical on every device, ensuring a smooth and seamless user experience.

Last, despite js supporting mobile devices, mobile applications have poor gesture recognition and limited native module access. This has more to do with frameworks keeping up to date and the web browser applications not. Because of this, js programmed within these frameworks has superior gesture recognition, such as tapping and swiping the screen. The frameworks offer full access to native modules such as camera and calendar applications. This allows your code to read inputs from other native applications as well as output data to them.

So the question becomes, is it better to program a web application or a native application? Although the argument strongly favors native applications, it is important to recognize that native applications have their own limits; such as client side data storage, lack of control due to the framework submitting to the user’s device, and all major updates requiring permission from the user before changes to the interface can be made.

In conclusion, although JavaScript was born in the web and it has advantages there, js in native applications allows for more seamless code execution and better cross platform user experience. Even if web applications resolve these issues, js will still have its place in native application development.