News


Recommended Posts

I haven't posted much here in a while. In fact, I haven't really been around Neowin very much in a while. Real life is completely biting out of my social and online life - I spent 5 hours writing a 9 page chemistry lab and am up at 12am doing calculus, and right after this I'll do my English and then Economics...

The point is, I'm sorry. I'm sorry for neglecting this project for so long, and am sorry for not putting out an actual product. We've (I've) promised a public test release to be out last weekend, but that never occurred. I'll be honest with you, we only got to the point where we've chosen a wallpaper (which I don't like :p ). We have ideas floating around but no clear vision of what's to come next.

So I quit. I've sent a PM of resignation to the Neowin News Staff to be with Shift (my beloved!). I've spent a good deal of time on these forums and the majority of my posts are in this subforum, and I call it home. I browse it whenever I can, although I don't reply too often. I apologize for that as well, for neglecting the community behind Shift.

I also read every single post and comment about Shift and hey, to be honest, after hearing and reading it 1000 times, "Why Shift?", it does get to you. Why use Shift? Why make Shift? Why bother? Can't we just join another Linux distro? This is a Windows site!

True, this is a Windows (7) site. I won't even attempt to argue with that, but we do have a Linux (and Apple) community filled with experts. Why Shift? Most Linux fanboys would say "Why not?". I've got a better personal reason - because when you've got a few people, ideas, and a place to share resources, it's almost a waste not to put it all together. There are people who design, people who code, people who research, people who write wiki documents - people willing to spend their time to make something. We also don't get paid a dime (we don't get paid with anything to be honest...:p ).

That brings me back to the main point: Where is the "something"? That something is an alpha or preview of Shift. I could give excuses and excuses galore as to why it's not in your virtual machines yet, but I'd rather just say that there will be a basic developer preview out hopefully this weekend. I will put in a great amount of time to get the components together. I can't promise it will work on your hardware and will not even attempt to prove it better than Ubuntu or Fedora (or any other Linux).

And, I will pick a better wallpaper.

However, there is another aspect to this: you. The users. I've had the feeling before: "Who AM I developing for?!". There haven't been a great deal of Shift users, which I can partly blame on myself as well - hey, there's no actual Shift. I just hope that once the switch to Arch Linux is complete, we will have some permanent users, as I can't recall anyone (including myself) who has Shift installed.

So, here's what's going to happen: I will devote more time to Shift. I will release a preview this weekend (hopefully), and I'll post more on this forum. I also hope that the Shift Linux website revives and the strong following bears with us as we prepare a great Neowin operating system.

Thanks for reading, and don't think of this as one huge excuse or bs to buy us more time.

P.S. Shift Linux will include Flash by default. Thanks for voting and commenting. More of those are coming soon!

Link to comment
https://www.neowin.net/forum/topic/728228-news/
Share on other sites

Well, Shift Arch will be based on Arch in terms of packages and their overall releases, but we don't know if we'll use the rolling release. The plan is to pull all of Arch's packages on to our server, effectively making a set of Arch repos, but we'll modify some packages. In another folder, we'll make ANOTHER copy of the Arch repos (mirror) and update those continuously. So, Shift won't have too many daily updates, as someone has to manually go in and post packages to the Shift repo. Maybe a "patch Tuesday"?

Link to comment
https://www.neowin.net/forum/topic/728228-news/#findComment-590493086
Share on other sites

Well, Shift Arch will be based on Arch in terms of packages and their overall releases, but we don't know if we'll use the rolling release. The plan is to pull all of Arch's packages on to our server, effectively making a set of Arch repos, but we'll modify some packages. In another folder, we'll make ANOTHER copy of the Arch repos (mirror) and update those continuously. So, Shift won't have too many daily updates, as someone has to manually go in and post packages to the Shift repo. Maybe a "patch Tuesday"?

Wouldn't it be easier to use Arch repo's and simply ignoring Arch branded packages?

I mean, for example we could make pacman ignore default arch gnome packages, and in our own custom repo, have Shift Gnome packages. That way, we wouldn't have any problems with the brandings, and pacman wouldn't have any updates until we updated our custom repo with latest Gnome (or KDE, or anything that is Arch-branded)

This is simpler to archive, and has the benefits of having a real rolling release system.

Of course, we could make trimestral ISO updates, so when someone needs to reinstall, they won't have to be so outdated (not that important, I have a separated pacman cache partition, so to me, reinstalling is really fast.

Link to comment
https://www.neowin.net/forum/topic/728228-news/#findComment-590504784
Share on other sites

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

    • 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
    • One Year In
      slackerzz earned a badge
      One Year In
  • 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!