|
Nope. That was just such a silly option anyway.
|
#
¿
Jul 20, 2011 14:56
|
|
|
|
| # ¿ May 2, 2024 09:19 |
|
|
FCKGW posted:Holy poo poo this owns. If you replace the drive on your new MBA or Mac Mini, you just boot up to Internet Recovery mode, connect to wifi, authenticate your App Store ID and it re-installs Lion for you over the internet. The tech has been around forever, I was network booting and remote deploying OS9 in like 2000. The rest of the world infrastructure just hasn't caught up until now.
|
|
#
¿
Jul 20, 2011 20:28
|
|
|
carry on then posted:Aww, the new version of Safari got changed the behavior of the back button. It used to do something (always rerun scripts?) that meant unread post counts were accurate when backing into thread lists. Now, it shows the old count like Firefox does, meaning to get the updated counts, I have to hit refresh. The new features are nice otherwise, but that one feature made browsing the forums even nicer. Is there a reason for the new behavior? Webkit 2 aggressive caching. Chrome has the same problem.
|
|
#
¿
Jul 20, 2011 20:35
|
|
|
Mac OSX 10.7 Lion Edition: Chrome's UI is loving busted, use Safari edition
|
|
#
¿
Jul 20, 2011 21:03
|
|
|
Carbn posted:I spent a good hour or so having a play after work. I'm mostly very "meh" on the experience. Major gripes: Sweet crap the entire animation takes about 250ms, faster than Win7's fade in. That's Siracusa spergin' right there. quote:Mission Control. Can I just have expose+spaces back? quote:Gestures. Why am I being forced to relearn new gestures for things? quote:Waking from sleep. Why do I have to click the trackpad now? I liked just moving the mouse around. Because it was overly sensitive. Cat jumping on a desk or a light breeze can cause things to wake up. Also the ambiguous case of having a mouse plugged in and moving it around could cause it to wake up while closed and then opening the lid left the laptop screen blank, so Apple just made it so you actually have to click. It was like this way back in 10.2 or 10.3.
|
|
#
¿
Jul 20, 2011 21:37
|
|
|
wolffenstein posted:Nothing. Ask Google to implement it. Considering it took 13 months to change one line to make it so that Chrome doesn't wig the gently caress out while pinching, this is going to take until 10.8. How about that rapid release cycle?
|
|
#
¿
Jul 20, 2011 22:45
|
|
|
Anal Volcano posted:I tried using Safari, but drat, no new tab button? All the way on the right. + Also the omnibar is pretty busted. I don't know how many times I've been infuriated to google search something in the bar, go to the result, click back and it takes me to a blank window without being able to get back to the results. Still busted in canary. I dunno WTF the Chrome devs are even doing at this point with all the version releases.
|
|
#
¿
Jul 20, 2011 22:54
|
|
|
AngryCaterpillar posted:Speaking of Launchpad, what is the point of it if you can't startup with it? I always thought it would replace the desktop. How is it like iOS if you have to manually launch it first? It is one gesture/keystroke away at all times. Now I just hope that I have the option of getting rid of the goddamn dock forever in 10.8 Felis Catus Launchpad also highlights how loving awful some vendors are with how much poo poo they leave everywhere. The usual culprits, Adobe and Microsoft. quote:Can I not rename folders? Click on the name of it while it is expanded.
|
|
#
¿
Jul 21, 2011 01:18
|
|
|
duck monster posted:Thats what happened when I tried to launch eclipse. Once it finished it launched Flash builder Eclipse is an IDE written in Java, Adobe has co-opted it for AIR and Flash app development. It is, however, poo poo.
|
|
#
¿
Jul 21, 2011 06:02
|
|
|
vlack posted:Have we talked about Automatic Termination yet? I don't really see the point of letting the system kill my apps when it could just swap them to disk. Because page faults are the absolute worst case thing you can do. Apple did a shitton of work for iOS 4 to eliminate page faults because the flash storage in the iDevices is sloooooooooow. Very noticeably slow. Carmack even wrote an article on Rage iPhone (can't seem to find it through google) where if he tried to stream from the flash memory it just wouldn't work no matter what because it was so slow. So even the flash memory on the iDevices is really slow, a spinning disc is going to be an order of magnitude slower at least. In the end, the benefit is NOT using virtual memory because it's the most terrible thing you can do. If the OS is smart enough to tell an application to suspend itself and the app can respect that, that'll free up resources and reduce the chance of page faults for something that really needs it. The decision process for figuring out if it can be safely suspended is simple: "it must not be the active application, it must have no visible, non-minimized windows". And this makes logical sense, if you have something that isn't active and hidden, then you're not using it. It is a bit disturbing how network activity doesn't exclude it from the list, but it kind of makes sense. It should be up to the application to decide if the network activity is important enough to allow suspension or not, rather like on iOS if you receive applicationDidReceiveMemoryWarning: then it's your job to bail as much water as possible since the OS has no clue what's safe to bail and what isn't in your app. In the case of Xcode, apparently the developers figured that downloading documentation wasn't important enough to ignore the suspend signal. Microsoft has actually done something sort of similar since way back in 95. If you minimize an application, you're more than just minimizing it. You're telling the OS that you're not using it, and Windows will attempt to reclaim CPU cycles and memory from it with priority to the active process. The biggest difference is that Windows won't ever close or suspend a process entirely, but I wouldn't put it past them to implement that in the future with all of the mobile segments they're getting into.
|
|
#
¿
Jul 25, 2011 08:08
|
|
|
Google, just like everyone else, has as Developer Previews since February and they're just now getting around to thinking about fixing things. Errgh.
|
|
#
¿
Jul 26, 2011 19:16
|
|
|
Xenomorph posted:Well, thanks to how great 10.7 has turned out, starting today we are testing CentOS 6.0. Apple pulled a FCPX by ditching Samba, which is for the best really. Samba never really worked right approximately ever, so now Apple is rolling their own. Like FCPX they likely have a long term strategy, but there's going to be a lot of pain getting them up to 100% feature coverage, but in the end it will probably work a hell of a lot better than Samba could ever hope to do. If you can't hang on to 10.6 until Apple gets their poo poo straight, probably at 10.8, you could get 1U servers from Dell or some such and throw Ubuntu on them. Ubuntu has a fairly decent admin GUI and does SMB and NFS well.
|
|
#
¿
Jul 27, 2011 23:20
|
|
|
SimpleCoax posted:Well, I just found out that Lion and Xcode 4.1 completely remove MPI. Hope macports will get me OpenMPI back easily enough. I'm getting really concerned about Apple's idea for the future of its professional user base. Not just with this little MPI removal, but the other signs that they're shifting focus. I don't want to have to wind up stuck with just Linux down the road. Homebrew has open-mpi. Stop using MacPorts and/or Fink, they are loving awful.
|
|
#
¿
Aug 10, 2011 06:39
|
|
|
Martytoof posted:Why? They are literal ports of Gentoo Ports or the dpkg system and all the poo poo that comes with it. As stated they require their own compiled versions of apps, so installing one installs a huge chain that isn't necessary. Also the dpkg system is just loving awful. Resolving a chain of dependencies is generally nightmare both installing and uninstalling. More often than not when I'm helping someone with some bizarre OSS issue I ask 'do you have MacPorts/Fink' and the answer is usually 'yes'. Removing MacPorts/Fink and using the Homebrew version always does the trick. As stated Homebrew is built specifically for OSX. That means it uses the /usr/local structure that was designated for this sort of thing. Homebrew will never compete with OSX provided anything and will link against OSX provided libraries instead of having a huge chain of cross compiling that sends things into dependency hell like Ports. Finally it's just a whole lot simpler. People generally migrate from Windows or Linux to OSX simply because the OS structure and UI is a lot cleaner. Homebrew follows that idea and is a whole lot simpler and less error prone. tl;dr Use Homebrew, don't think about it.
|
|
#
¿
Aug 10, 2011 18:34
|
|
|
|
| # ¿ May 2, 2024 09:19 |
|
|
unruly posted:Just a caveat. There are some duplicates in Homebrew that compete with various system-provided items, but they have a policy against doing that if at all possible. There is actually even a Homebrew-alt repo basically full of system tools that have been updated, in case you need them (like rsync, or samba). This is true, and sometimes necessary because the Apple provided library can potentially be buggy or very out of date, but it's a very rare case.
|
|
#
¿
Aug 10, 2011 18:53
|
|