Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Macbook Pro offering in hardware list #310

Open
marnovo opened this issue Nov 27, 2018 · 8 comments · May be fixed by #313
Open

Update Macbook Pro offering in hardware list #310

marnovo opened this issue Nov 27, 2018 · 8 comments · May be fixed by #313
Assignees

Comments

@marnovo
Copy link
Member

marnovo commented Nov 27, 2018

The current Mac notebook model we offer in the hardware list, the 13-in non-touchbar MBP is by now already 1.5 years old (!).

Apple updated their MBP line a few months ago, but just the touchbar versions. With the recent launch of the new MB Air, it's becoming clear for months they're leaving the non-touchbar version to rot & discontinue. In the end, Apple is basically making this model a bad deal so that people move up or down the tiers.

The now updated touchbar version (w/the same 16GB RAM and 256GB SSD) is just ~10% more expensive than the non-touchbar yet vastly superior:

  • 4-core 8th gen CPU (vs 2-core 7th gen)
    • Multi-core benchmarks ~75% faster!
  • 10% faster GPU
  • 100% faster SSD, more reliable
  • 4 Thunderbolt 3 ports (vs 2)
  • Improved, more reliable and silent keyboard
  • Much better cooling (2 vs 1) means less noise and throttle
  • Better display (truetone), security features (touch ID), yadda yadda…

Generic model comparison article here.

Keeping the pretty inferior, objectively less reliable and likely to be discontinued non-touchbar version for a small price difference looks like a quite bad deal… even more so when considering the resale value in the future.

TL;DR: replace the current Mac offering, the MBP 13" 16GB / 256GB non-touchbar, with the newer & better MBP 13" 16GB / 256GB touchbar.

P.s.:

Also, I'd strongly encourage to set all the keyboard layouts in laptops to US. We're a fully international company for a while already, US English is our working language, so it becomes a mess when people inherit computers and have to adapt to languages with bizarre layouts.

@creachadair
Copy link
Contributor

#309 is also related. This makes sense to me.

@creachadair
Copy link
Contributor

I wrote the specs for the 15" model by finding a comparable relative spec to the 13" model. If we are going to bump up the specs for the latter, we should probably also do the former. Would you like me to prep a PR with those changes for your consideration?

@marnovo marnovo linked a pull request Dec 10, 2018 that will close this issue
@m09
Copy link

m09 commented Dec 18, 2018

Also, I'd strongly encourage to set all the keyboard layouts in laptops to US. We're a fully international company for a while already, US English is our working language, so it becomes a mess when people inherit computers and have to adapt to languages with bizarre layouts.

Just a note regarding the layouts: I type in azerty and on the laptop I got (which is not this model), there is no way for me to type < and >. As you can guess, this is rather annoying to do about anything related to programming. It might therefore be safer to make sure that the layout will be usable for the employee before deciding instead of setting hard guidelines.

I do believe that whenever the differences are small it's fine to opt for the most general layout, but still in some cases it hinders productivity for an unclear future benefit.

@marnovo
Copy link
Member Author

marnovo commented Dec 19, 2018

there is no way for me to type < and >

Whoa, how do you do? But how is this (im)possible with a US keyboard?

This proposal came from a general view a while ago, when a lot of the company had to either relearn how to type with the super quirky/inefficient Spanish layout or just literally ignore the key labels and map to a regular QWERTY layout (my case). So it's about choosing the "least" overall inefficiency/loss in resale value in the long run.

@smacker
Copy link
Contributor

smacker commented Dec 19, 2018

US keyboard just doesn't have that button:
https://upload.wikimedia.org/wikipedia/commons/thumb/b/b9/KB_France.svg/500px-KB_France.svg.png

@m09
Copy link

m09 commented Dec 19, 2018

Whoa, how do you do? But how is this (im)possible with a US keyboard?

I use X11 unicode input which means I type Ctrl+Shift+U 033E for > and Ctrl+Shift+U 033C for <. Which means I don't do HTML without an external keyboard. Overall it's not that big a deal but still obviously annoying. As to why it is impossible to type, it's because the standard US QWERTY layout has one less key than the standard AZERTY layout (between Shift and z, we have the key for > and <.

This proposal came from a general view a while ago, when a lot of the company had to either relearn how to type with the super quirky/inefficient Spanish layout or just literally ignore the key labels and map to a regular QWERTY layout (my case). So it's about choosing the "least" overall inefficiency/loss in resale value in the long run.

I completely agree that we should aim for the best tradeoff between comfort and resale/reuse value. It's just that we have to take care to correctly weight the comfort depending on the specific layouts involved.

@dpordomingo
Copy link
Contributor

I also wonder if inheriting laptops would be a priority for a company that is growing and is mostly remote, and there is no that much rotation, and the expected life of a laptop should be less than the expected for a developer in the company.

@smola
Copy link
Contributor

smola commented Mar 25, 2019

I think we can move on with the Macbook Pro offering update and move the keyboard layout discussion to a different issue? The layout issue affects all laptops as well as external keyboards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants