• 1 Post
  • 338 Comments
Joined 2 years ago
cake
Cake day: July 30th, 2023

help-circle

  • Building electronics can be a long process. The FW16 itself experienced many months of delays before it was finally released to preorder. Also, the 13" board that runs the same generation as the FW16 came out before the FW16.

    As a FW16 owner, I’d love some news myself, but they did just add two whole new SKUs which is going to take up some component of R&D time. They may be working at a tick/tock cadence for updating small devices then coming back to the large device.





  • From memory I can only answer one of those: The way I understand it (and I could be wrong), your programs theoretically should only need modifications if they have a concurrency related bug. The global interlock is designed to take a sledgehammer at “fixing” a concurrency data race. If you have a bug that the GIL fixed, you’ll need to solve that data race using a different control structure once free threading is enabled.

    I know it’s kind of a vague answer, but every program that supports true concurrency will do it slightly differently. Your average script with just a few libraries may not benefit, unless a library itself uses threads. Some libraries that use native compiled components may already be able to utilize the full power of you computer even on standard Python builds because threads spawned directly in the native code are less beholden to the GIL (depending on how often they’d need to communicate with native python code)














  • I work in IT. If someone came to ask me if they could install this on their system I’d tell them no, based only on this trailer. You’ve got to give us more info.

    I’m all for open source and open systems that can be built up as needed, but people like me would need information to make decisions. Unlike your typical corporate executive or manager, technical people aren’t as easily conned by hype videos. I’ve seen more information published from a game company that’s trying to hide spoilers. The only technical information I could spot was that neofetch like screen, so I know you’ve got something Unix-like.

    Also, if you’re going to be coy and post publicly but then send people on a treasure hunt, pick a less generic name or else you’re going to get lost on page 3 of Google. You list “Open Systems OS 1.0” on one slide, and that search for me returns OSF/1 (1990s), OpenKylin (a Chinese Linux), and classic Mac OS as the top results.

    I get that software development takes time, and good software development takes even longer, but if you don’t have the info it’s too young in the development cycle for a hype video. It also tells me that if you’re using semantic versioning you’re using it wrong, because v1.0 of semver implies to be your first stable API, which you either have and are hiding or don’t have so you shouldn’t be at 1.0.

    Even just one sentence “I am building a Unix-like operating system using a [custom|Linux|BSD] kernel which is designed to [fly model airplanes]” would be better than a void. That kind of sentence will get the right people interested in you project and asking the right questions. For example, if you’re about model airplanes or server hosting, I might be interested. But if you’re building an OS around someone who wants to use their computer like a VN, that’s not my cup of tea personally. You haven’t dis-proven the latter yet, though I assume it’s an unlikely occurrence.