se6
Thanks to Brexit, UK will secure its tax havens, to the benefit of very few and to the detriment of many...
See https://www.taxjustice.net/2019/01/23/brexit-and-the-future-... for some more info.
[Edit: corrected the date]
sox -n soothingnoise-3mn.wav synth 3:0 pinknoise tremolo 0.5 30 fade q 5 3:0 30
Worked a treat to make my son sleep.Even today OpenCL is a viable solution for GPU. It works fine on both AMD and NVidia GPUs. It is also pushed a lot by Intel for FPGA, which probably scare even more NVidia.
OpenCL kernels are compiled at runtime, which is brilliant since you can change the kernels code at run time, use constants in the code at the last moment, unroll, etc.. which can gives better performances. (Nvidia only introduced the possibility of having runtime compilation as a preview in Cuda 7!)
The "single source" argument is completely overrated. Furthermore, you can have single source in OpenCL putting the code in strings.
Many people criticise OpenCL because when you come from C++ it seems a lot of work. It is true that OpenCL has an API influenced by OpenGL and is verbose. However it is not difficult to write a small framework specific to your needs and domain to factorise much of this verbosity.
NVidia does everything it can to hide the fact that their devices support OpenCL. People thinks that only ancients versions of OpenCL run on NVidia devices. That is not true: 1.2 is not ancient is still as of today the main version of OpenCL used. OpenCL 1.2 is fully supported and NVidia quietly say to its large customers who refuse to use CUDA, that they will starting to support soon some OpenCL 2.0 features.
To answer your question, I am not sure either will win, but they will both exist for a long time.
Could not be further from the truth there! OpenCL is an open standard, can be used to program GPU, CPU and even FPGA. It is definitively NOT proprietary in any sense! To target both AMD and NVidia GPU, you do not need any vendor specific flag at all. Yes, OpenCL, is like OpenGL pretty verbose and explicit. It can be a bit tedious but once you've factored this verbosity in a framework of some kind, it becomes pretty easy to use.
HIP seems interesting, but I am unwilling to invest on it yet. What will happen if for whatever reason AMD abandon it in 6 months? No such worries with OpenCL.
ip addr | grep "inet " | cut -f 3 -d " " ip addr show | grep inet
Edit: wrote back original command and replied below insteadFunny. I just find the opposite: Ubuntu is a superb desktop, polished, clean and powerful, very productive and easy to use for the experienced use with keyyboard shortcuts, but also to new users with mouse and no prior knowledge.
Anyway, being a long time Linux enthusiast and running Ubuntu as my main OS for many years, I bought the E4.5 to support the project and was not expecting an experience which would match Android.
Having said that, it has improved so much and I would venture to say that as of 2016, it is starting to be ready for general public.
It is my main phone, and everything pretty much works, the UX is great. The main annoyance is that it is a bit slow: starting an app takes a few seconds. But might be due to the not too potent hardware of a E4.5.
Ubuntu phone seems the only alternative we have to the smartphone OS duopoly and to feel and be in control of the device in our pocket. That is priceless to me.
It has come a long way already: the off the air (OTA) upgrades roughly every month make it better and better. It is more than usable. If not having Skype, WhatsApp etc.. is not a show stopper for you, then it can be a great phone for you. There are already many apps, but of course not comparable to Android. Can see an official app viewer here: https://uappexplorer.com/
Also the dev tools for it are great. The Ubuntu SDK, based on QtCreator is pretty slick. It is quite easy to write a native app. There are many guidelines and good docs for it: https://developer.ubuntu.com/en/