Live data from Hacker News

Viewing profile — andy_threos_io

andy_threos_io

HN member
Joined
Thu, Oct 22, 2020, 10:03 PM UTC
HN karma
119
Public activity
54 items

About andy_threos_io

Andy at threos.io

andy@threos.io

Recent public activity

  1. comment
    Comment #44766489

    2010–2024: Wireless voting system for a bank’s annual shareholder meetings. ARM-based handheld terminals with 2.4GHz RF and LDPC error correction Custom embedded OS, base stations,…

  2. comment
    Comment #44766486

    Location: EU / Hungary Remote: Yes Willing to relocate: Mostly no, but open if absolutely necessary Technologies: Embedded systems, OS development, C/C++, Assembly, Python, Java, L…

  3. comment
    Comment #39723418

    With a better coding you don't need more than 8 bits for a move (less for some). The implementation should store a state machine for the game, a struct for each pieces, and also th…

  4. story
  5. comment
    Comment #38455848

    My view that, this code is nice, however IMO there are several ways to make it more portable, and programer friendly, specially the ported assembly code part. Example. In file thre…

  6. comment
    Comment #37575949

    Real world manufacturing machines (CNCs) are using G codes. Like most laser cutters and engraves, Ex. LaserGrbl software for laser machines. G codes in fact have command for arcs. …

  7. story
  8. comment
    Comment #31681575

    win10 is slower on some aspect than win7. (not the bootup, but normal operation)

  9. comment
  10. comment
    Comment #28917004

    I found this [1] from MS very useful when I designed some PCB inductor coil for a project. It was only 2D, but some 100 lines of code made the development so much easier. [1] https…

  11. comment
    Comment #27761197

    Just a not so recent news from the rust compiler: https://blog.rust-lang.org/2021/05/10/Rust-1.52.1.html "The Rust team has prepared a new release, 1.52.1, working around a bug in …

  12. comment
    Comment #27659468

    Nowadays, it's better to use x86_64 only. The 32 bit x86 has many drawbacks. The 64 bit is much cleaner and better in many many ways. -no segmentation, flat address space -better i…

  13. comment
    Comment #27548866

    I know a good number of people who will move away from Linux after Rust get in the kernel.

  14. comment
    Comment #27445905

    Not a big deal in the age of gigabytes. All sort of magic happens in BIOS, but after transition to 64bit, it should be fine. The only problem is when BIOS programs some kind of har…

  15. comment
    Comment #26908423

    In our operating system (threos [1] ) this is the way the loader works (page fault exception handling code is from the loader task, mapped and running in the owner context) Also if…

  16. comment
    Comment #26627224

    There are other more portable way to do OS wrapper, and maybe faster (but it's not an issue). Just write the wrapper as a C extension module, and in the module make the system call…

  17. comment
    Comment #26467126

    Most of the implementations are unable to handle larger words than the read (64k) buffer. The C is for sure. edit: Also the C implementation will get in infinite loop with more tha…

  18. comment
    Comment #26440799

    I tried it, but the underlying Roswell system isn't perfect at least. Simple Make fails on linux out of the box. And the look&feel and features are very far from emacs.

  19. comment
    Comment #26143780

    Irq accounting depends on architecture and code usage, e.g. like some kind of barrier (serializing) before the RDTSC. on newer x86_64 the accounting code is around 100-200 cycles, …

  20. comment
    Comment #25896845

    Solar energy will not run out in the near future (at least 5 billion years, even earth will be destroyed way before the sun run out of fuel), fossil fuels will run out, it does not…

  21. comment
    Comment #25896773

    As you may already know, we have a HUGE fusion reactor ( fuses 500 million metric tons of hydrogen each second. [1] ) approximately 149.5 million km away, and it's ready and free* …

  22. story
  23. comment
    Comment #25796149

    The example program presented is not a good solution, it goes against all the rules and recommendations. Your program (made this way) will NOT WORK at all in the near future, ex wh…

  24. comment
    Comment #25793616

    And it's a total lame, bad assembly code. Lacks any kind of material knowledge or practice.

  25. comment
    Comment #25789772

    /usr/lib/system/libsystem_kernel.dylib