Recommended Posts

MacBookPro 15" (2007) 2.4ghz Core 2 Duo 4gb ram 500gb HDD (7200) OSX 10.6.6 (machine always with me)

MacPro octo (2009) 2.66ghz x8 Xeon 6gb ram 640gb HDD 3x1tb HDD OSX 10.6.6 (beast for video editing)

iMac 20" (2008) 2.4ghz Core 2 Duo 4gb ram 320gb HDD OSX 10.6.6 (music creation and random)

MacMini (early) 1.5ghz Core Solo 1.5gb Ram 160gb HDD OSX 10.6.6 (media centre in bedroom running plex)

  • 2 weeks later...
  • 2 weeks later...

Updated my machine a bit since last posting here I think, now sporting;

Mac Pro 2010/16GB /2x120 SSD/4TB SATA storage

Macbook Pro 15"/4GB/120GB SATA (2007 Spring/Summer)

Macbook Pro 15"/4GB/160GB SSD (2010 Spring/Summer)

Use them all for work , also I'm doing a bit of video editing at home on the side and various other things, think I'll need more HD space soon - got a bunch of 750G/1TB USB drives around but they're just not enough anymore.

Long time away, and I've gotten new toys since way back when :)

15" Early-2007 Macbook Pro 2.16 ghz C2D, 4gb RAM, 320gb HD, Snow Leopard 10.6.6

Custom-built Intel Core i3 Hack, 4gb RAM, 1TB HD, Nvidia 460 GTX SE 1gb, Snow Leopard 1.0.6.6

13" Mid-2007 Macbook, 2 ghz C2D Santa Rosa, 1gb RAM, 80gb HD, Intel X300 integrated GPU, Lion Developer Preview

  • 4 weeks later...
  • 2 weeks later...
  • 3 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!