I am having this issue on my 6S since the update to iOS 11. Have to charge the phone two times per day instead of one before updating. A friend of mine also has the same problem with his 6S.
Same, for my 6S+, watch 0, and iPad Air 2. All of them!
The watch is especially problematic as I am using it to track various activities and it is harder to charge (who has a watch charger in their car?) and can’t be used while charging.
The object/component system looks like a Unity3D ripoff. Even component names ("MeshRenderer") are unchanged from Unity.
Also it is interesting that it's written in JS without any higher-level technology like TypeScript or Dart.
A little bit off topic, but every time I try any kind of similar application (this, a CAD, a PCB editor) that is implemented to work in web browser, I lack feeling of "stability" of a desktop app with all the files stored locally - I would rather use a desktop app with inferior functionality.
Component based applications have existed for a long time but obviously there are choices made in webglstudio that tried to appeal to unity users, just because unity is the defacto standard.
About the stability of desktop apps I agree with you, but sooner or later that will have to change, so thats what we are pushing.
As a professional software developer I would say a multi-monitor setup indeed brings not much extra into my workflow (except maybe for VS Stack Trace and Output panes on a side monitor).
However, as a hobbyist 3D Artist, I would say multiple monitors are a must. When you are modeling you need beauty drawing/different projections side-by-side. You are unwrapping - you need UV window. You are working in Photoshop - you bring all the brush/layer/properties panes to the second monitor, etc, etc.
So this really depends on your task. When your primary UI is a text editor with shortcuts is one case, but if your environment is a mix of an art studio and a Boeing control panel, that's a different situation.
Two months ago I ordered an original ZX Spectrum 48K, on board series 3B for about $200. It is the same I had as my first computer when I was a kid. I knew I could have it all on the emulator, and, I didn't expect how much excitement and inspiration I had after loading several games from a cassette recorder and playing on a pixel-crawly TV. In fact, had to take sleeping pills after the first time. Now I am thinking to buy myself a C64, a separate small TV, and an Apple ][ with a monitor... will have to buy a separate table for that.
C++ is a programming language that is used in modern applications primarily for low level tasks like hardware interaction/embedded, games etc. This involves much dedication while learning, and a proper coverage of computer architecture aspects. This is why I do not see much point in learning C++ in a "For Rookies" way "in 21 days". If you want to be a C++ programmer, go find a good introductory C book which properly covers the aspects of memory management and pointers (like the Deitel's "C How to Program"). Then, gradually start C++ with something like Shildt, or again the Deitels. Then, maybe, one day you will want to look at the Stroustrup's book.
Otherwise, learn C# or Java or whatever quacks like a duck.
That is really bad advice. C style memory management is useless in the presence of exceptions, and a nightmare to get right even in C. Choose a book that teaches RAII from the beginning, and leaves C style memory management to a late, advanced chapter.
Accelerated C++ used to be that book, don't know if there is a newer and better replacement.
I agree that in modern C++ you need to avoid all the bare-C ways. Actually, my C++ is almost C# if you look at it, especially with the new c++11 standard.
But I still believe that to learn C++ the best way is to start with C, pointer arithmetic, and classic strings. Otherwise you will just miss the point and join the hordes of script kiddies who "once started C++".
I agree that understanding of pointer is essential to use C++, but the problem is many learning materials force learners to believe the have to use pointer everywhere - which is opposite in reality…
So there should be a good guidance of avoiding pointers as much as possible when learner is stepping to C++ from C.
If you want/need to learn C++, learn C++. Learning C to learn C++ is a really poor idea.
There are plenty of people in my office who are like that and they can't see the wood for the tree. Writing out their own for loops instead of using whatever std algorithm would do the job better. Holding their own owning pointers in the presence of exceptions.
The problem is people tend to not to actually learn C++ properly, cover to cover. They just learn the bits they need as an when they need them missing out all sorts of details in the middle.
Buk, you are great when you are a farmer's son. But then, when you take your first job, then second, and then you start to think about art of yours, and then you drink more, and then you found a firm with the best friends of yours, and then you quit because one of them start to bully you in a pursuit of power, and then you go to Shanghai to earn your salary in response to a generous proposition - you realize - one thing to do is to work hard, another is to rest; it's up to you to choose. I am choosing hard work, no matter for what's purpose. And that is why I love you, Buk.
Forgot to mention - touchscreen on notebook laptops is useless - your arms get tired and your screen gets dirty very quickly.
Also: google are regular copycats.
Let's spill bit of hatred on the rooster's nest:
"...box2D physics integration,..."
Why not make 2D physics engine by yourself? The answer: just because it involves real research and development to make it. Do it well, and you will be praised, and nobody will call you insane. And what the author really does is a poor cock-a-doodle-doo with a custom string class.
As for 90 - devyanosto - I think it comes from “9 to 100”. Its strange though its 9 and not 10.