Live data from Hacker News

Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

ifixit.org

811–820 of 927 posts

Re: Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

#811
post #207

Earlier quoted context omitted.

I just set a "visited" bit in the data structure while the code walks it. There's a cycle if the bit is already set. It's the same algorithm as yours, but a lot cheaper.

Perhaps cheaper in space, but you will have to do an initial pass over the entire structure to zero your visited bits first, so it may not be cheaper in time.

Just ensure the bits are always zero on allocation, use DFS, and ensure you re-zero the bits on the way out.

Re: Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

#812
post #804

Earlier quoted context omitted.

They no longer have Steve Jobs Quality Control? He was the type of person to play with something for 5 minutes and say "yeah... no" or to eagerly take something he liked and abuse the hell out of it for 24 hours then come back with a laundry list of improvements. He was a jerk and he cared deeply about user experience. In his absence you have what exactly? Tim Cook lacks vision, if you want your mountain moved to Plu…

I am still confounded how people continue to say that Tim Cook has no vision, as if he's simply some sort of bean counter with green shades who just lucked into become the CEO of one of the world's largest companies. Tim Cook's vision is much larger than computers if you haven't been paying attention. Look, from what I can observe, ever smaller devices, lifestyle devices, the focus on privacy, their take on the cloud…

And yet Apple is eroding trust by pushing buggy software and poor quality hardware. Maybe his focus is just elsewhere but Apple is who they are today because of an attention to their products that other companies lack.

Maybe he's trying to position Apple as a privacy minded trustworthy company when it comes to your data but he's ignoring or entrusting the crown jewels to someone else while he does it. If people stop buying Apple products because they're unreliable and support sucks then it won't matter.

Re: Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

#813

Earlier quoted context omitted.

Maybe this is a market opportunity for somebody to build a laptop with high end components (monitor, keyboard, touchpad) running a super-duper-well-integrated linux.

I certainly agree. System76 [1] is probably your best option there. They're attempting to do just that. 1. https://system76.com/laptops

Nice, thanks for the link. That seems really promising! But it sounds like they still need to fix the trackpad (a decently working trackpad has been my main struggle with Linux laptops): https://arstechnica.com/gadgets/2017/08/review-system76s-gal....

Re: Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

#814
post #293

Earlier quoted context omitted.

I had someone in an interview in Berlin ask me to write a garbage collector. In CSC 202, our professor talked about using reference counts. Jeez. I think my profs covered ref counting as an introduction, then also went on to cover mark/sweep and generational collectors. We also covered compaction, copying and bump allocation. I don't think it took that long. If I were running a shop that focused on, say Java, I would…

I had someone ask me the cycle detection question once, and I didn't care for how they phrased it. Specifically, should I find it immediately upon entering the first cycle (at a higher memory/time cost) or should I just eventually detect it (e.g. turtle/rabbit)? It was on me to clarify, but as a newb to the industry, I felt like I should just know which was expected. And either way, if I were to ask this question, I…

Here's how I asked the question. I would present the data for a 2 node cycle and ask what would happen to this routine. Here's a response I would get far too often: A conditional clause detecting a 2 node cycle. Then I would present a 3 node cycle, then ask how to detect an n node cycle, period.

Lots of 3.5+ GPA grads can't make that logical leap!

Re: Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

#815
post #194

Earlier quoted context omitted.

Those things aren't taught in CS programs as the majority of companies don't need those skills. Most want application development such-as a web or iOS app developer. This sort of thing is very relevant for someone writing an application or a server process. Programmers who can write their own compiler are much better C and C++ programmers, because they have relevant background. Programmers who understand the low leve…

>Programmers who can write their own compiler are much better C and C++ programmers, because they have relevant background. Sure, sure. But how many companies care about that sort of thing? C is rather my best language, and as far as I can tell, that helps me out as a sysadmin, but I need to be good at some EMCAscript based framework if I want a higher-paying Software Engineering job, at least outside of the embedded…

> but I need to be good at some EMCAscript based framework if I want a higher-paying Software Engineering job

Then I should hope you know enough VM-fu to be able to optimize a JavaScript application.

Re: Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

#816

Earlier quoted context omitted.

When Jony Ive became more important than (the now defunct) Steve Jobs, form rose over functionality.

> (the now defunct) Steve Jobs That's one way to refer to a dead guy.

This is my new favorite euphemism for death. "Deceased" just sounds boring. "Defunct" has a certain weight to it.

Re: Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

#817
post #780

Earlier quoted context omitted.

>But it doesn't compose with shift for selection. Yes it does. Ctrl+Shift+E selects the text up to the end of the line.

As an interesting note, it doesn't work with MS Office.

Well, that's one problem you wouldn't have on Linux I guess.

Re: Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

#818
post #655

Earlier quoted context omitted.

So true. Earlier in meetings we can go about silently browsing or replying to emails. But now the keyboard is so loud that we have to apologize to the speaker!

Or the alternative, paying attention.

If the meeting was worthwhile, we wouldn't feel the need to check emails during said meeting ;)

Re: Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

#819
post #665

Earlier quoted context omitted.

> Every single Apple's competitor delivers laptops with 32+ GB of RAM, and MacBooks are stuck at 16GB and there's no one to blame for it but Apple. This is only partially correct: those are separate models which are bigger and have worse power and heat characteristics. Every laptop which is similar to Apple's shares the 16GB limit for the same reason; the difference is that Apple has decided not to offer that second…

> Apple has decided not to offer that second tier MacBook Pro, a first-tier plaything. If they do finally release a "second tier", what the hell are they going to call it? MacBook Super Pro?

I'd imagine they'd call it Macbook Pro 17"

Re: Apple Engineers Its Own Downfall with the Macbook Pro Keyboard

#820
post #772

Earlier quoted context omitted.

Both linux and Windows seems to get basic text selection right, yes. Of modern desktop os-es, Mac OS X was the only one who has ever consistently surprised me on this . It might not be a big deal to everyone but for me who - deal with text day out and day - and prefer to keep my hands at the keyboard (even when I have a nice trackpad) small thing like this matters. Just like details like a good trackpad matters to ot…

The text selection shortcuts are completely consistent on modern OS X, in my experience. At least, I can't find an app where shift+alt+right_arrow doesn't select a word.

I've also yet to find an instance in macOS where Emacs-style text navigation shortcuts didn't Just Work™ automatically. One of the few things about macOS that I actually like relative to the average Unix/Linux desktop.
Post reply on HN