What is important is to teach how to create the algorithm, the logical steps, in the first place. Not the actual language that was used (C was just starting to get rolling when I was learning languages, and Pascal was huge). Teach algebra and geometry. Teach trig. Use word problems. Have the student learn how to take a stated problem, break it down to steps needed to solve, and then implement the solution in any language - even pseudocode.
It is this process that enables all programming; learning a specific language or toolset is irrelevant. Learn how to think logically, to analyze a problem, and how to create a flow for the problem is what matters. And that can be done with simple high school algebra, geometry, and trig.
Or Apple could take a look at something like the Note 5. Mine works with normal gloves, like my motorcycle gloves that are nothing special, not "special silver thread" imbued. Just a good screen design.
My Note 5 works great with my Joe Rocket Flexium TX motorcycle gloves - and they are standard gauntlet gloves, not "special cap touch" models. Perfect when I want to add fuel-up information at the gas station, no need to pull off my gloves!
There's a bit of a difference between a campaign server for a political party and a data/e-mail server for a sitting member of the Administration, don't you think? As far as I know, there's no requirement that a private organization keep all its notes and records (beyond Federally required financials for taxation purposes) related to its organizational goals. But we do know there are multiple laws and regulations related to preserving all Federal on-the-job communications...
Engineers tend to be conservative; scientists tend to be liberal. The latter are the dreamers, the theoreticals, the former are the ones who have to make it work in the real world, the implementers. Maybe that's the breakdown? In theory versus practice? Dreamer versus doer? Tends to fit the "liberal versus conservative" positions in the US rather well...
I mean, it's bad enough that the stereotype of techies is we're all fat, slovenly weenies who can't pick up a thick book (let alone a lady). But when we're so freaking lazy we can't even turn the AP to face AWAY from us? Well - we just confirmed the stereotype...
See you don't follow. Android isn't Java based. Sure, it can be PROGRAMMED with the Java language, but the executables - and the OS itself - are native machine code. It's no more a Java-based system than a desktop PC is Java-based because someone wrote a program in Java then compiled it into a platform-specific executable.
See the other response to my post. The other poster says you're full of crap and provides a link backing up the whole old-version-apps-not-working thing. I think your Apple Colored Glasses are too firmly in-place!
Yep, it's simply stunning what many people consider as "normal" for music. I work in the CE space, designing and making audio products. The standards have drifted immensely, but I do see glimmers of hope! At the recent high end audio shows I've been at, there is a marked uptick in the number of under-30 attendees. I think the open access of music via streaming has brought more interest to all things music related, and as people consume more and more music they want to experience new systems as well - and gain an appreciation of quality reproduction.
Personally, I hope Tidal.com and other services like it succeed, because CD+ quality streamed audio will change the perceptions that 128k MP3 is "good"...
Huh. So when updating the OS (which is when the binaries are recompiled), that's the "delay" you're complaining about? It's done when you update the OS; when you can RUN the OS (it's rebooted) everything is nice and native. I know you're a huge Apple fanboy, but you really, REALLY should educate yourself a bit about the competition. Or you come off looking like a fool for the ignorance you display!
PS: because of the way Android runs, apps written back for Android 2.0 still work. Do apps written for the 3GS still run without issue? Or does the author have to recompile first?
The Samsung S7 and S7 Edge have 2560x1440 screens. The iPhone 7 has 1334 x 750 and the 7 Plus has 1920 x 1080. So you get a LOT more pixels and - in the case of the iPhone 7 - much bigger screens as well (the two Samsung models and the iPhone 7 Plus are 5.5" units). Considering that's the main UI, adding the thickness of a fingernail to the package is pretty insubstantial. Of course, if you REALLY want thin, you can go with the Gionee Elife 5.1 that has about the same resolution as the iPhone 7, but packs it into a package just 5.2mm thick (about 2mm thinner). Oh - and it keeps the 3.5mm jack as well...:)
iOS requires less memory than Android because its applications are native. iPhones have always had less processor and memory but outrun Andoid anyway.
Android runs native as well, and when you update the OS it goes through and recompiles all apps to use the latest SDKs and OS features on your phone - all optimized for your hardware platform.
Right now, there is only one way to get that high fidelity out of Bluetooth: AptX Wireless. Most Android phones support it. OSX supports it. iOS does not. So you're not getting that good quality. And let's not even get started on 100-200 ms of latency, making watching movies/videos on your phone look like bad 1970s overdubbed kung fu movies..
It's not surprising that an iPhone can get by with less RAM and runs faster with a given ARM core architecture - they push a lot fewer pixels than most of their competitors. For example, the iPhone 7 Plus is 1920x1080; the Samsung S7 Edge is 2560x1440. The Samsung device is pushing 78% more pixels. When you factor that into the equation - it's surprising how efficient the non-iPhone devices are.
What we found when measuring those (and the Momentum 2.0 - got lucky, got them both before they were recalled) was that you could get about 18-19 hours of ANC on-time when wired (you turn the unit on, and ANC is always on). When paired with Bluetooth and streaming audio, it was closer to 8-10 hours.
IIRC, the Momentum uses a CSR8670 main module (Bluetooth, charging, control) that pulls around 22 mA when running (13 mA with no streaming or playing of audio, just on and connected). It uses a separate AMS 3435 for ANC purposes, but that's a really low power device, using about 8 mA not including what's needed to power the speakers. Audio was sourced from line-in or Bluetooth, through the 8670, then into the 3435 to use its amplifiers.
With everything running, you were pulling around 50 mA (LEDs, amplifier overhead, other functions consuming power) and it would shut down when you got down to 3.4V - which would take around 8-10 hours depending upon how loud you played it.
Add in things like cap sense, extra LEDs, remote control via BLE, discrete amplifiers, and the MFi/interface circuitry itself (which isn't minimal - the Lightning Audio Module typically pulls 10 mA for that processing alone) and you quickly ramp up to 100 mA - or more. And those kinds of features are found on things like the Parrot Zik, Samsung LevelOver, Beats Studio Wireless, etc.
What's even better architecturally is to NOT use lossy compression on the stream (or do so a second time, in the case of already compressed audio). And even better, architecturally, for those who watch videos on the phone is to NOT use a connection scheme that has 100 to 200 msec of latency. Unless you like having all your videos look like poorly dubbed Hong Kong kung fu movies from the 1970s...
Having half an ohm of impedance between your amp and a 32-50 Ohm driver is pretty irrelevant, comparatively... Oh - and EQ can still be applied, as the effect of that cable impedance is essentially the same as higher amplifier output impedance - it's a completely predictable "filter" on the system and can easily be dialed out as needed (not that it is needed, in 99% of all cases).
Lastly, a typical headphone transducer consumes less than 1mW of power (they are typically 95-105 dB SPL @ 1 mW output). A Bluetooth radio typically consumes 30-40 mW when operating - quite a bit MORE power is consumed by a Bluetooth radio than a headphone amplifier. So using a Bluetooth headphone will dramatically increase power consumption relative to a wired headphone.
If you really care about audio quality, you should be pretty excited about headphones that can draw power from the lightning connecter... that allows for better processing, better noise cancellation, and so on all for headphones that never need a battery.
Hi there! Having participated in the design (and continuing to do so) of more than a few VERY high-end powered headphones, I can tell you that a 1500-1800 mAhr battery is pretty standard these days. And that's needed for a 12-15 hour run time. That translates to about 125-150 mA draw from the battery. The Lightning connector only allows 100 mA. So something will have to give (hopefully it's the god-awful capsense and LED indicators people love to load up on their headphones). You only get so much power from that connector...
There are much thinner phones on the market today that use a full-size 3.5mm jack (Vivo X3S is 6mm, Huawei Ascend P3 is around 6.18mm, and the Gionee ELife S7 at 5.5mm, for example). And the volume occupied by the jack MIGHT allow something around 50-70 mAhr of more battery - about enough to run that Bluetooth radio for an hour or so - meaning if you listen to Bluetooth headphones for more than an hour you're down on total operational time as you continue to consume more power than if you just had a wired headphone.
Slashdot Mirror
What is important is to teach how to create the algorithm, the logical steps, in the first place. Not the actual language that was used (C was just starting to get rolling when I was learning languages, and Pascal was huge). Teach algebra and geometry. Teach trig. Use word problems. Have the student learn how to take a stated problem, break it down to steps needed to solve, and then implement the solution in any language - even pseudocode.
It is this process that enables all programming; learning a specific language or toolset is irrelevant. Learn how to think logically, to analyze a problem, and how to create a flow for the problem is what matters. And that can be done with simple high school algebra, geometry, and trig.
Or Apple could take a look at something like the Note 5. Mine works with normal gloves, like my motorcycle gloves that are nothing special, not "special silver thread" imbued. Just a good screen design.
My Note 5 works great with my Joe Rocket Flexium TX motorcycle gloves - and they are standard gauntlet gloves, not "special cap touch" models. Perfect when I want to add fuel-up information at the gas station, no need to pull off my gloves!
There's a bit of a difference between a campaign server for a political party and a data/e-mail server for a sitting member of the Administration, don't you think? As far as I know, there's no requirement that a private organization keep all its notes and records (beyond Federally required financials for taxation purposes) related to its organizational goals. But we do know there are multiple laws and regulations related to preserving all Federal on-the-job communications...
Engineers tend to be conservative; scientists tend to be liberal. The latter are the dreamers, the theoreticals, the former are the ones who have to make it work in the real world, the implementers. Maybe that's the breakdown? In theory versus practice? Dreamer versus doer? Tends to fit the "liberal versus conservative" positions in the US rather well...
Wait, what? Compiled programs are as memory intensive as interpreted programs? Seriously - you want to claim that?
I mean, it's bad enough that the stereotype of techies is we're all fat, slovenly weenies who can't pick up a thick book (let alone a lady). But when we're so freaking lazy we can't even turn the AP to face AWAY from us? Well - we just confirmed the stereotype...
See you don't follow. Android isn't Java based. Sure, it can be PROGRAMMED with the Java language, but the executables - and the OS itself - are native machine code. It's no more a Java-based system than a desktop PC is Java-based because someone wrote a program in Java then compiled it into a platform-specific executable.
See the other response to my post. The other poster says you're full of crap and provides a link backing up the whole old-version-apps-not-working thing. I think your Apple Colored Glasses are too firmly in-place!
Huh. SuperKendall just claimed otherwise! But then, he's a known Apple Fanboi so...
Duh - with a flashlight!
Challenge accepted! Let us see if you can stop my Raekwon strike followed with my Ghostface Killah kick!
Yep, it's simply stunning what many people consider as "normal" for music. I work in the CE space, designing and making audio products. The standards have drifted immensely, but I do see glimmers of hope! At the recent high end audio shows I've been at, there is a marked uptick in the number of under-30 attendees. I think the open access of music via streaming has brought more interest to all things music related, and as people consume more and more music they want to experience new systems as well - and gain an appreciation of quality reproduction.
Personally, I hope Tidal.com and other services like it succeed, because CD+ quality streamed audio will change the perceptions that 128k MP3 is "good"...
Huh. So when updating the OS (which is when the binaries are recompiled), that's the "delay" you're complaining about? It's done when you update the OS; when you can RUN the OS (it's rebooted) everything is nice and native. I know you're a huge Apple fanboy, but you really, REALLY should educate yourself a bit about the competition. Or you come off looking like a fool for the ignorance you display!
PS: because of the way Android runs, apps written back for Android 2.0 still work. Do apps written for the 3GS still run without issue? Or does the author have to recompile first?
Educate yourself. Android runs native machine code.
Hi there, perhaps you're not aware of the fact that Android runs native machine code, and has for the last 2 years.
The Samsung S7 and S7 Edge have 2560x1440 screens. The iPhone 7 has 1334 x 750 and the 7 Plus has 1920 x 1080. So you get a LOT more pixels and - in the case of the iPhone 7 - much bigger screens as well (the two Samsung models and the iPhone 7 Plus are 5.5" units). Considering that's the main UI, adding the thickness of a fingernail to the package is pretty insubstantial. Of course, if you REALLY want thin, you can go with the Gionee Elife 5.1 that has about the same resolution as the iPhone 7, but packs it into a package just 5.2mm thick (about 2mm thinner). Oh - and it keeps the 3.5mm jack as well... :)
iOS requires less memory than Android because its applications are native. iPhones have always had less processor and memory but outrun Andoid anyway.
Android runs native as well, and when you update the OS it goes through and recompiles all apps to use the latest SDKs and OS features on your phone - all optimized for your hardware platform.
You are a moron with an agenda.
That's OK - you're just ignorant... ;)
Right now, there is only one way to get that high fidelity out of Bluetooth: AptX Wireless. Most Android phones support it. OSX supports it. iOS does not. So you're not getting that good quality. And let's not even get started on 100-200 ms of latency, making watching movies/videos on your phone look like bad 1970s overdubbed kung fu movies..
It's not surprising that an iPhone can get by with less RAM and runs faster with a given ARM core architecture - they push a lot fewer pixels than most of their competitors. For example, the iPhone 7 Plus is 1920x1080; the Samsung S7 Edge is 2560x1440. The Samsung device is pushing 78% more pixels. When you factor that into the equation - it's surprising how efficient the non-iPhone devices are.
What we found when measuring those (and the Momentum 2.0 - got lucky, got them both before they were recalled) was that you could get about 18-19 hours of ANC on-time when wired (you turn the unit on, and ANC is always on). When paired with Bluetooth and streaming audio, it was closer to 8-10 hours.
IIRC, the Momentum uses a CSR8670 main module (Bluetooth, charging, control) that pulls around 22 mA when running (13 mA with no streaming or playing of audio, just on and connected). It uses a separate AMS 3435 for ANC purposes, but that's a really low power device, using about 8 mA not including what's needed to power the speakers. Audio was sourced from line-in or Bluetooth, through the 8670, then into the 3435 to use its amplifiers.
With everything running, you were pulling around 50 mA (LEDs, amplifier overhead, other functions consuming power) and it would shut down when you got down to 3.4V - which would take around 8-10 hours depending upon how loud you played it.
Add in things like cap sense, extra LEDs, remote control via BLE, discrete amplifiers, and the MFi/interface circuitry itself (which isn't minimal - the Lightning Audio Module typically pulls 10 mA for that processing alone) and you quickly ramp up to 100 mA - or more. And those kinds of features are found on things like the Parrot Zik, Samsung LevelOver, Beats Studio Wireless, etc.
What's even better architecturally is to NOT use lossy compression on the stream (or do so a second time, in the case of already compressed audio). And even better, architecturally, for those who watch videos on the phone is to NOT use a connection scheme that has 100 to 200 msec of latency. Unless you like having all your videos look like poorly dubbed Hong Kong kung fu movies from the 1970s...
Having half an ohm of impedance between your amp and a 32-50 Ohm driver is pretty irrelevant, comparatively... Oh - and EQ can still be applied, as the effect of that cable impedance is essentially the same as higher amplifier output impedance - it's a completely predictable "filter" on the system and can easily be dialed out as needed (not that it is needed, in 99% of all cases).
Lastly, a typical headphone transducer consumes less than 1mW of power (they are typically 95-105 dB SPL @ 1 mW output). A Bluetooth radio typically consumes 30-40 mW when operating - quite a bit MORE power is consumed by a Bluetooth radio than a headphone amplifier. So using a Bluetooth headphone will dramatically increase power consumption relative to a wired headphone.
If you really care about audio quality, you should be pretty excited about headphones that can draw power from the lightning connecter... that allows for better processing, better noise cancellation, and so on all for headphones that never need a battery.
Hi there! Having participated in the design (and continuing to do so) of more than a few VERY high-end powered headphones, I can tell you that a 1500-1800 mAhr battery is pretty standard these days. And that's needed for a 12-15 hour run time. That translates to about 125-150 mA draw from the battery. The Lightning connector only allows 100 mA. So something will have to give (hopefully it's the god-awful capsense and LED indicators people love to load up on their headphones). You only get so much power from that connector...
There are much thinner phones on the market today that use a full-size 3.5mm jack (Vivo X3S is 6mm, Huawei Ascend P3 is around 6.18mm, and the Gionee ELife S7 at 5.5mm, for example). And the volume occupied by the jack MIGHT allow something around 50-70 mAhr of more battery - about enough to run that Bluetooth radio for an hour or so - meaning if you listen to Bluetooth headphones for more than an hour you're down on total operational time as you continue to consume more power than if you just had a wired headphone.
So from that we can assume you're a millionaire pantsuit wearing 70 year old grandmom who likes to attack women who have been raped by her husband?