As a C/C++ veteran of > 20 years, one angle is Android.
That Java mantra got carried into Google at the time and it's locked in now.
Benefits, portably recompiling (not Java) byte code on demand for 32-bit or 64-bit architectures with improved simd optimizations.
Backwards compatibility is kept at the in the runtime-compiler, API level instead of depending on the CPU for legacy compatibility (see Intel).
This predates.NET and only slightly suffers from progressing through the language tweaks from Java 6 through Java 8. It's much more mature than.NET so the changes aren't as drastic.
You're talking about connecting the dots and plumbing. That's IT.
Good coding is also a hard science. You only know where your goal is (and maybe not). Finding the dots to connect is then 90% sweating it out empirically.
The real world is full of different hardware, interfaces, paradigms. At certain points you can't gloss over it with generalized code, but have to engineer something more focused.
Sometimes, it's also time-intensive testing and hacking to glean out undocumented bits.
Of course this is all against a set schedule. You can't get there punching in and out 4 - 5 hours a day.
Linux is a kernel, OSX is a Mach kernel, mostly FreeBSD userland with other BSDs thrown in, NextStep, ObjC.
BSDs are always holistic experiences and so is OSX, Windows, etc.. Linux is Bazaar, *BSD has always been Cathedral (take it slow, engineer well).
At the end of the day, people rather live in a Cathedral/hotel where everything stays in known places than the 'vibrant' flea-market with fuzzy pseudo-RPM treadmill hell.
pre-JellyBean: swipe animation queues all 30 frames of the swipe animation, does NOT drop any, and struggles to complete them all, taking 4 seconds to walk the queue with as many skips and pops as expected. Video Player fail.
JellyBean: swipe animation probably does not queue 30 frames of animation, but ALSO gets PRIORITY to COMPLETE them first in the allotted 1 second. Video Player success
Real-world example, keyboard response -- which is more responsive?: the console that reacts instantly to your key-presses even under a load of 24.00 on a single-processor, or a console that gets back to you after it's done processing some background tasks. The former is "actually" and "feels" more responsive, while the later will run the bg-tasks slightly faster.
Ah, young idealism, trying to be the Debian. I was there, once. It is true that it's better to have open-source drivers, but you need a stable, open, documented hardware platform. PCs are, Android is neither.
You will spend your entire life rebuilding "plumbing" after which the hardware you've built it for is long dead while its descendents -- you cannot support. A life where you didn't actually build anything useful, the next iPhone nor next game-changing piece of software-engineering, but just ran in a mouse-wheel.
Reality is we just have to bend-over a little and suck up buying new hardware; accept the respective new binary blobs. Just try to stay above it. CyanogenMod is doing a good job there.
Their rendering and window subsystem has already proven to be laggy and inefficient unless you throw overwhelming hardware at it. Why even continue do it in Java and on Mobile!? There's neither memory, cpu/gpu, nor battery, to feed that mess properly.
Even Windows Phone moved their rendering engine to native. Why not a proper port of Wayland (or just switch to Qt) instead?
Potential? Demonstrated lifetime air pollution reduction (that's 10 years at least), reduced lifetime petro consumption, lower lifetime maintenance costs, is only POTENTIAL?
So you argue against the $5K premium vs a Corolla (there's a hybrid in Corolla's class for interior room, amenities, etc?), but a $15K premium for a Volt -- well that's just fine.
I'm sure you know more about this than anybody. Then you know about differentials and their huge longevity. Btw, Toyota hybrid transmissions are differentials.
People conveniently forget the air-quality benefits of hybrids. There's a huge lifetime difference that can be quantified in health improvement (healthcare cost reductions), lifestyle improvement, etc.
Slashdot Mirror
Meantime, nobody is complaining about the smaller Pixel 2, made by HTC with AMOLED screen by Samsung.
Small screen OLED is only hard for LG.
http://mashable.com/2017/10/23...
Meantime, nobody is complaining about the smaller Pixel 2, made by HTC with AMOLED screen by Samsung.
Small screen OLED is only hard for LG.
http://mashable.com/2017/10/23...
As a C/C++ veteran of > 20 years, one angle is Android.
That Java mantra got carried into Google at the time and it's locked in now.
Benefits, portably recompiling (not Java) byte code on demand for 32-bit or 64-bit architectures with improved simd optimizations.
Backwards compatibility is kept at the in the runtime-compiler, API level instead of depending on the CPU for legacy compatibility (see Intel).
This predates .NET and only slightly suffers from progressing through the language tweaks from Java 6 through Java 8. It's much more mature than .NET so the changes aren't as drastic.
Library of third-party libraries is vast.
Is this why all the cool Millennials are now pushing NPM, Node.js? :-P *facepalm*
Well, very little of the Chinese workers could afford to buy those iPhones they're making.
Foxconn is now just making it an absolute rule.
Cut the CEO's pay. That sure hasn't grown in a direct relationship to inflation while the worker's pay stayed flat.
http://www.triplepundit.com/20...
If you've seen In-n-out, always crowded, very cheap food, a lot of workers.
You're talking about connecting the dots and plumbing. That's IT.
Good coding is also a hard science. You only know where your goal is (and maybe not). Finding the dots to connect is then 90% sweating it out empirically.
The real world is full of different hardware, interfaces, paradigms. At certain points you can't gloss over it with generalized code, but have to engineer something more focused.
Sometimes, it's also time-intensive testing and hacking to glean out undocumented bits.
Of course this is all against a set schedule. You can't get there punching in and out 4 - 5 hours a day.
Just more BS cop-out from those who can't. It's too bad Google is now full of this NIH thinking.
They obviously forgot to study the entire class such as pull-to-refresh.
And then they rediscover pull-to-refresh is still there.
Or don't let you back out of a form without confirmation, as many sites already do.
How about ALSO disabling pull-to-refresh when you're on a form, which is the SAME problem.
Maybe they'll get to this in 20 years.
Vivaldi browser. Brings back the old school Opera with preferences for everything.
So do petro, ethanol, hydrogen, etc vehicles.
Chrome's tab-model is a literal Fork-Bomb. If I have to explain it to you, you need to get off /.
Unlike Firefox where it JIT loads tabs as you need them. Try restoring a 30+ multi-tab session with Chrome, good-luck.
Linux is a kernel, OSX is a Mach kernel, mostly FreeBSD userland with other BSDs thrown in, NextStep, ObjC.
BSDs are always holistic experiences and so is OSX, Windows, etc..
Linux is Bazaar, *BSD has always been Cathedral (take it slow, engineer well).
At the end of the day, people rather live in a Cathedral/hotel where everything stays in known places than the 'vibrant' flea-market with fuzzy pseudo-RPM treadmill hell.
Except you're nowhere close to reality.
pre-JellyBean:
swipe animation queues all 30 frames of the swipe animation, does NOT drop any, and struggles to complete them all, taking 4 seconds to walk the queue with as many skips and pops as expected. Video Player fail.
JellyBean:
swipe animation probably does not queue 30 frames of animation, but ALSO gets PRIORITY to COMPLETE them first in the allotted 1 second. Video Player success
Real-world example, keyboard response -- which is more responsive?: the console that reacts instantly to your key-presses even under a load of 24.00 on a single-processor, or a console that gets back to you after it's done processing some background tasks. The former is "actually" and "feels" more responsive, while the later will run the bg-tasks slightly faster.
Ah, young idealism, trying to be the Debian. I was there, once. It is true that it's better to have open-source drivers, but you need a stable, open, documented hardware platform. PCs are, Android is neither.
You will spend your entire life rebuilding "plumbing" after which the hardware you've built it for is long dead while its descendents -- you cannot support. A life where you didn't actually build anything useful, the next iPhone nor next game-changing piece of software-engineering, but just ran in a mouse-wheel.
Reality is we just have to bend-over a little and suck up buying new hardware; accept the respective new binary blobs. Just try to stay above it. CyanogenMod is doing a good job there.
Works fine on Ubuntu for Android.
Their rendering and window subsystem has already proven to be laggy and inefficient unless you throw overwhelming hardware at it. Why even continue do it in Java and on Mobile!? There's neither memory, cpu/gpu, nor battery, to feed that mess properly.
Even Windows Phone moved their rendering engine to native. Why not a proper port of Wayland (or just switch to Qt) instead?
Hybrids are modern engines. Heard of Atkinson?
Potential? Demonstrated lifetime air pollution reduction (that's 10 years at least), reduced lifetime petro consumption, lower lifetime maintenance costs, is only POTENTIAL?
So you argue against the $5K premium vs a Corolla (there's a hybrid in Corolla's class for interior room, amenities, etc?), but a $15K premium for a Volt -- well that's just fine.
I'm sure you know more about this than anybody. Then you know about differentials and their huge longevity. Btw, Toyota hybrid transmissions are differentials.
People conveniently forget the air-quality benefits of hybrids. There's a huge lifetime difference that can be quantified in health improvement (healthcare cost reductions), lifestyle improvement, etc.
It's not all about the MPG.
I'm sure it costs "much less" to rebuild the transmission, or engine, in any other TEN YEARS old, GEN ONE car.
Which of you have gone 10 years with a laptop, or cellphone battery?