News for hackers. Stuff that matters.
Re:Going native by JustSomeNobody on Friday March 24, 2017 @07:54AM (#13948278)
Words have meaning.

Native doesn't mean browser in a window. Same as realtime doesn't mean "it'll get there faster. Maybe"

Re:Going native by Touche on Friday March 24, 2017 @08:52AM (#13948541)
Words do have meaning but "native" has pretty unclear meaning.

Is JavaScript native? JavaScript is interpreted when it first starts, but eventually turns into machine code through JIT by most JS engines. So is JavaScript native because it gets converted to machine code, just as C++ does?

If you say no, then you're saying only AOT compiled languages are "native". So that eliminates Python, Erlang, Java. Even C#, the "native" language on Windows is not AOT (in most cases).

So that doesn't work, AOT has nothing to do with native. JavaScript is just as native as any other language.

So maybe the problem is the UI, right? That's where most people seem to have a problem. So as long as you are using Cocoa on OSX, GTK on Gnome, Metro on Windows, you're native, right? Oh, wait, Metro apps can be written using HTML, JS, and CSS. They are essentially identical to Electron apps. In fact, Microsoft supports (and encourages) you to create .appx packages from Electron apps [1].

Oh, and all of those Qt apps out there (like Calibre, by far the best ebook management software), not native (despite being C++ in a lot of cases).

So yeah, "native" has meaning, but the meaning is as clear as mud.

[1]https://github.com/felixrieseberg/electron-windows-store

Re:Going native by logicallee on Thursday March 30, 2017 @12:14AM (#13992837)
Just commenting that that is a very good definition of what realtime isn't! :)