Hacker Newsnew | past | comments | ask | show | jobs | submit | SysArchitect's commentslogin

> He stresses that you should focus on building a community, with the code and platform as happy side-effects of that community.

Exactly, so license shouldn't matter that much. I'd probably be a lot more interested in it were it BSD licensed, as it is now I have no real desire to play with this new OS.


Can you explain why you prefer BSD as a contributer (I'm assuming you're not running an OS company) so much that you won't help a GPL project?


Seconded on the BSD license being the way forward.


Only the currently selected foreground application gets to use the TouchBar and display content on it.

Which means apps distributed outside of the app store when they have focus are allowed to put whatever they want on the TouchBar and you are allowed to close and delete the app.

Problem solved.


$10 Billion worth of debt that is tax deductible as losses.

"Tax credits" :P


Friend of mine who worked at Qwest in the early days and worked with Level3:

"Interestingly enough, Level3 started out by building out the Qwest network as a contractor building out the fiber. Level3 in exchange for some of the work L3 was given long-term IRUs on the fiber and heavily discounted conduit leases.

Level3 to this day still leases a lot of fiber from CenturyLink (ala Qwest)..."

CenturyLink buying Level3 means that they are basically leasing to themselves :P


This still has the issue of not being able to use your car controls to control the music, but:

https://www.amazon.com/Antec-Portable-Bluetooth-Receiver-Hea...

Pair this with your phone, and plug it into power. When your car turns on, it powers on, pairs with your phone, and spits audio out over 3.5mm to the car stereo.

Comes with a 3.5mm male -> 3.5mm male plug for this purpose.


Why are there threats of DRM with the DAC moved to the cable instead of the DAC sitting inside the phone (where arguably it has more control over the DAC than if it is sitting in-line on a cable)?


Because you remove the "analogue hole" in the DRM scheme of the 3.5mm jack.


They could upgrade lightning to support USB-3... Lightning doesn't specify the USB protocol.


30 pin was introduced in 2003, it was finally replaced with Lightning in 2014 and thereby deprecated from use.

That's a 11 year run.

I bet those treadmills are not even that old yet.


Well, Micro-USB was announced in 2007. So by the time USB-C really takes over, it will have had maybe a 10-year run. So that's no better for compatibility life.


I completely agree with you. Micro-USB has already shown that it is not the best standard moving forward, it is already at it's end as manufacturers are replacing the port on devices with a USB-C port instead.

So let's call it. Micro-USB, 2007 -> 2016 (9 years). It had less of a run than the 30 pin dock connector!

---

I still have USB-B, USB-Mini and USB-Micro, and USB3-Micro-B devices... some were built even after USB-Micro was available, yet they still use USB Mini (which in most cases is a lot more sturdy than Micro). I have a ton of different cables for different devices because there was no real standardization until USB-C very very recently.

Why was the same vocal crowd not out when manufacturers switched from Mini to Micro and everyone had to buy all new cables?

With USB3 there is also a USB3-TypeB connector, which is not even backwards compatible with USB-TypeB...

http://www.datapro.net/techinfo/usb_3_explained.html


There's no reason they couldn't add a full secure enclave on a USB based keyboard with TouchID.

Register your fingerprints into TouchID, they are stored securely on the keyboard, with some secure communication between keyboard/computer... now you can easily log in and or do Apple pay.


I agree. However I think they'd lean towards devices that already have such tech rather than creating another one.


Now when happens when I unplug the keyboard and plug it into something else?


Nothing. Since there is no relationship between the secure enclave on the keyboard and the laptop, TouchID won't function.


They tend to tick-tock between Nvidia and AMD. Although this update is once again an AMD (Mid 2015 is AMD as well).

My late 2013 was Nvidia.


> They tend to tick-tock between Nvidia and AMD

I'm not sure "tick tock" is the right word. The MBP used AMD in 2006, NVidia from 2007 to 2010, AMD in 2011, NVidia from 2012 to 2014, and 2015 is AMD. It's actually a break in the pattern for them to use AMD chips two years in a row.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: