Earlier quoted context omitted.
1) You could also create some wrapper scripts setting the path, or have someting inspired by virtualenv handle it, or maybe different terminal profiles. Those breakings really are edge cases. 2) Don't put them in the PATH. They're prefixed with 'g' so you can make an non-prefixed alias for your interactive shell, and use the prefixed variant in your scripts if need be. If you write portable scripts you're either usin…
3) g++? that's not in homebrew... He probably meant GCC, which does have recipes in Homebrew. Homebrew started taking off, and in my case Just Works This is the first time I ever heard anyone saying it. In general Homebrew did a good job for me, but it did break on me a couple of times. And when it did, fixing it caused me a lot of stress, because in the end it's really not much better than " ./configure && make && s…
Back on Linux (after one year of Apple and OS X)
191–200 of 334 posts
Re: Back on Linux (after one year of Apple and OS X)
#192Earlier quoted context omitted.
Do they still ship with unusable trackpads (that requires you to carry a mouse everywhere if you ever going to use your ThinkPad) or has that improved in recent years? It's the only pain point against ThinkPad for me.
If you're a programmer using Emacs/Vim you really don't care for trackpad or mouse for the great majority of your computer needs.
Re: Back on Linux (after one year of Apple and OS X)
#193Earlier quoted context omitted.
That being said, if debian can do it for around 30,000 packages on almost as many architectures as OSX has mere hardware models, why can't OSX do it? With all the app stores and cloud services, Apple is big on 'quite a bit of infrastructure'.
Because Apple don't provide these package management tools, volunteering third-parties do. Apple are never going to provide Linux-style package management tools because the market for them is minuscule compared to Apple's real market: normal people. For normal people, there's the App Store.
It seems like the OP's point is pretty valid to me. I use an OS that gives me what I need to do my job.
Re: Back on Linux (after one year of Apple and OS X)
#194Earlier quoted context omitted.
You are missing the point. The idea is not to determine exactly what's going on, because that doesn't matter. You mentioned the casual user before, but all these details are only important to specialists trying to debug an issue with a specific application. When you run out of RAM, it is completely irrelevant which application is thrashing, because the problem is that you run out of RAM . It doesn't matter if the rea…
Fantastic argument, user is having a problem, but it doesn't matter what's going on, let the user try arbitrary things which I already explained that are folklore and why they make no sense, maybe it works. If that's you advocate, let's stop here with this discussion, as there's no common ground. When you're having a problem, first you try to understand it in order to try to solve the root cause. Applying rules of th…
As professionals we often forget what it is to be a casual user. Asking a casual user to learn what you explained as folklore is simply too much to ask. Everyone who uses a computer should at least be technically literate to a degree but that means understanding the basics. To a casual user the basics are: my computer has a processor that executes tasks, it has RAM that stores data for quick retrieval, and a hard disk for long term storage. Each application uses a percentage of my finite RAM and when it runs out my system slows down. Therefore logic dictates that if I kill the app taking the up the most RAM my computer will go faster.
That's all they usually know. We understand that Activity Monitor lies to us and killing random processes is voodoo but we also have to take into account how we use our machines. The casual user will be able to solve their problem by killing processes more often than people like us will because of the way they use their systems plus there is a placebo effect for them. When they kill a process they often feel like the system just got faster regardless of whether it really did.
I liken it to driving a car. Ask some random person about fuel economy. Their thinking is "high octane fuel has more energy per gallon therefore if I use it I'll get better fuel economy". They might even know the relationship between tire inflation and fuel economy too if you're lucky. Ask a professional driver about those things and they'll look down at the average person like they're crazy. They know all how octane, oil, air filtration, shocks, struts, aerodynamics, etc, etc. all contribute to better fuel economy. "If only the average driver knew what I knew, then they'd save a ton on gas" theyd think. But alas, that's too much to expect so we just have to make sure they get the basics and it's up to the professionals to provide the average person with something that just works and do our best to be one step ahead of users by anticipating their usage patterns. This applies to hardware/software engineering, car manufacturing, and anything else. You just can't expect the user to learn or even take an interest in even a quarter of what we know.
Re: Back on Linux (after one year of Apple and OS X)
#195Earlier quoted context omitted.
You're not really fair. Yes, it's true that osx has 3rd-party-package-manager. But it's also true that they can be very complicated, or simply broken. The easy'ness of a good linux-distribution is just not possibly with osx. The days where you need to hack yourself something togehter, just to get some basic applications, are gone...at least on linux.
As someone who uses both Linux(most familiar with Fedora and Ubuntu) and OS X regularly I have to say I completely disagree with you. My Linux systems are always a headache. Last week I pulled a recommended patch from the system updater and it broke Xorg. I had to remove it by hand and reinstall it.
Re: Back on Linux (after one year of Apple and OS X)
#196Regarding hardware quality: "...why there's no PC manufacturers that would have the same overall quality of the hardware." In my experience, business ThinkPads beat MacBooks by a mile for working (e.g. programming). I am surprised to see so many coders use MacBooks. Thinkpads have better ergonomics, are more robust and better performance/configurable hardware (e.g. RAM).
I can think of a few reasons: 1) MacBooks are pleasing to the eye. ThinkPads are well-designed functionally but ugly. Aesthetics don't matter to everyone, but to those for whom they do matter, they are not a frivolous concern. Working in an elegant environment (including hardware) can have a positive effect on one's state of mind. 2) A lot of people are interested in developing iOS apps. This is much easier on a Mac.…
Re: Back on Linux (after one year of Apple and OS X)
#197Re: Back on Linux (after one year of Apple and OS X)
#198Re: Back on Linux (after one year of Apple and OS X)
#199Re: Back on Linux (after one year of Apple and OS X)
#200Earlier quoted context omitted.
(I'm the author of the original post) You bring up good points and my article would need some clarification on some parts, I agree on that. I'll just write quick replies back to you, and try to format something on the article itself later. Purge really did free memory and quite a lot. I'm not too expert (as you probably can tell) how the OS X memory management works, but I mostly settled with solutions that seemed to…
I do happen to have an 8 GB machine, and almost never reboot (only reboot for OS updates). I run half a menu-bar full of resident helper apps, like Dropbox (a big one), Fantastical, ScanSnap, Xmarks (another big one), Transmit (another big one), Evernote, and more. I also keep Apple Mail running, mapped to a half dozen Gmail IMAP accounts. I have "geek tool" updating my desktop with iCal appointments and various ps o…
Here's what I don't understand - why would anyone in their right mind purchase a $2000 laptop and then not spend the 20 minutes and 100 bucks to max out the memory on the thing? It's the easiest thing in the world to do, and basically means you never have to worry about memory usage again.