@PAKA well if anything goes wrong (and that can always be the case for whatever reason), then I would rather fix it during my normal working hours than on friday evening or on saturday/sunday.

@electrineer we will probably introduce maximum number of retrys and we will not contact all devices at the same time again

@dontbeevil the newest and normal version of VS. As Im only working on a private project to learn c++, I now switched to clion (for c/c++) which is basically the same as intellij (for java).

If you compare this with german companies, Slack is almost as much worth as Lufthansa, Deutsche Bank and thyssenkrupp together.

I used awk for that and also got confused with comparing numbers with <, > instead of - lt and - gt. Some stuff is not so intuitive.

No spoilers please, Im just at episode 4 😄

The site doesn't really work on mobile. Selectbox is really hard to open by touch.

I dont see any devrant stickers 🙄

You should add some client side Javascript checking, I just sent an empty form an now I'm already registered.

React native or titanium apps can be quite fast, but the main problem is, that there are often situations where you need hacky workarounds.

But the most important point is: dont use cordova/ionic for anything else than prototyping. React native, titanium or nativescript might work for production apps depending on the requirements.

@-vim- well the language would not be the problem, there are already transpiler. The problem is the binding to the native system functions and UI widgets. There are a lot of them and they all have a different interface / name on each platform.

The performamce of ionic is quite bad because the code is interpreted at runtime and the UI is rendered in a webview. React native, titanium and nativescript are also interpreted at runtime but they use native UI elements. Xamarin, Flutter or CodenameOne compile the code into native code. The performance is therfore much better, but the development effort is normally higher.

Is the programm running on the command line or did you create a user interface?

At least you get a match..

@HIGHphen exactly, with four for loops :-) and with two functions that dont even exist

Still it is important to distinguish the native and javascript thread:

"Another example is responding to touches: if you are doing work across multiple frames on the JavaScript thread, you might notice a delay in responding to TouchableOpacity, for example. This is because the JavaScript thread is busy and cannot process the raw touch events sent over from the main thread. As a result, TouchableOpacity cannot react to the touch events and command the native view to adjust its opacity."

More information on this:

https://facebook.github.io/react-na...

@justsomeguy of course it has something to do with JavaScript. Because parts run in a native thread and some parts in a js thread. Thats why there are sometimes performance issues. For a smooth experience everything has to run native.

@justsomeguy well this argument does not really hold as RN is not really usable without packages like react navigation. And some parts of react navigation run in a JavaScript environment, thats why it is laggy sometimes.

Titanium by Appcelerator, which is used by devRant, seems to work even better than RN. But dont forget, RN is still in version 0.5.

@justsomeguy Well thats simply not correct. You cant see the difference directly, but the app is slower than a native app. Best example is the tabNavigator from react navigation. When you compare switching tabs in a RN app to an app like whatsapp for example you directly see what I mean.

No you dont get the same performance, but still RN is much better than ionic. If you want a perfect app, you have to go native.

I dont want to go to bed without pushing my commit, I have a strange feeling about this :p

They should invest in their servers, everytime I want to push I figure out that github is down, same problem couple of days ago.

@3141 but what happens when you check a variable in JavaScript with the value 0. Null, 0,undefined all convert to false, this can easily cause bugs, thats why you should use if(x === false) in JavaScript.

var x = 5 - 5;
If(x) {} would not be executed for example.

@Kickflip I tried it once but I got the notification after a few days again. So I guess it's just a joke and maybe for advertising purposes

I guess the difficult part is to decide which things should be in an own directive and which should not. But when the project becomes big enough it's propably hard to understand either way.

Can someone explain why python is always used for machine learning?

Imagine you had a bug in the code and you actually won a million but you will never know :O

And 1000+ on devRant :)

Tbh the second is painfull to look at. How can you find this good? All the wasted lines...