Live data from Hacker News

Viewing profile — tobias12345

tobias12345

HN member
Joined
Tue, Nov 22, 2016, 4:30 PM UTC
HN karma
28
Public activity
30 items

About tobias12345

No profile information was provided.

Recent public activity

  1. comment
    Comment #48551705

    True, you have few external dependencies... but you have random code thrown into your repository in the form of vendored 3rd party libraries, header only libraries, and bits and pi…

  2. comment
    Comment #47813865

    To handle supply chain attacks, you need to know where yiur code comes from. That is often not a given when working with languages where it is easier to copy and paste in code from…

  3. comment
    Comment #47813820

    I doubt that ideomatic code is easier to write in C once you switch to Fil-C. Your code will just get killed by the runtime whenever it does something it should not do (and the com…

  4. comment
    Comment #47529377

    "Memory safe" means that there are no memory safety issues. One of the most critical areas targeted by exploits is just gone. And this in turn leads -- according to the numbers pub…

  5. comment
    Comment #47177957

    Yeap, systemd is just another init system existing on a level playing field. They just dare to be successful by tackling problems that people have today over trying to deliver solu…

  6. comment
    Comment #45642445

    How will porting a single concept like `defer` from zig, a language that is not memory safe, to C and C++ make those memory safe? `defer` is a poor man's RAII. C++ has had RAII sin…

  7. comment
    Comment #45286135

    > we talk about supply chain attacks, a thing that Rust with Cargo falls deep into. How so? By listing all dependencies in an easy to digest way? Making it hard to have a dependenc…

  8. comment
    Comment #45239403

    Sean Baxter stated that he is not working on Safe C++ anymore, so that proposal is dead. But is somebody still working on safety profiles? I have not noticed and profiles related p…

  9. comment
    Comment #43033606

    Does it matter whether it is a common class of bugs or a not so common one? The point is, this is a class of bugs you do not have when picking a different language. C++ claimed for…

  10. comment
    Comment #40399821

    This has been going on for over a year now. Any progress in C++ land towards more memory safety?

  11. comment
    Comment #40247406

    Nope, editions cover that use case nicely: Rust breaks things every three years -- without breaking existing code. Basically you have to opt in your project to the new normal. All …

  12. comment
    Comment #38613124

    RAII is great, but unfortunately it breaks down when the resource it manages leaks out of the RAII type. E.g. Whenever handing out the raw pointer stored in a unique_ptr, the code …

  13. comment
    Comment #38071886

    I am not arguing that there is a lot of C++ code and that this code will be around for a long time. But I would prefer to see C++ as a language with a future and not as the languag…

  14. comment
    Comment #38068545

    So your argument is: C++ will be a great legacy language and we will enjoy its memory bugs for decades to come? I really hope it can do better than that. Note that Window ships a k…

  15. comment
    Comment #38067890

    There is more out there than C++ and Rust, but yes, if you are stuck with C++, then you have no option but to wait for a couple of years and start to rewrite wehn C++ is ready. I s…

  16. comment
    Comment #38067801

    > There is no "rewrite it in another language" option. How about "Wrap your C++ code in FFI wrappers and use it from a safer language"? It is conceptually not much different to "re…

  17. comment
    Comment #38067691

    Which option? To write wrappers now instead of later? I just see no way to be able to use current C++ code in a profiles world without wrappers or even a rewrite. For some code wit…

  18. comment
    Comment #38067535

    I am disappointed: I have to wait a few years for the C++ committee to define profiles. Then a few more years for tooling to become available. Then a few more months for the toolin…

  19. comment
    Comment #38067450

    C++ did a lot to improve safety over the decades, but it seems to have ended up in a local maximum. I doubt you can break out of that local maximum by doing all the things you did …

  20. comment
    Comment #36255327

    There is accessibility using the Qt backend and I started working on accesskit integration, which should cover the rest of the backends. Yes, more work needs to be done there, but …

  21. comment
    Comment #33592316

    The problem is that the different crates typically address certain sub-eco-systems and produce better results for that one dialekt spoken there. It is hard to generalize all that.

  22. comment
    Comment #33592307

    I missed more: There are a lot of tools out there addressing special cases. Those typically address certain C++ sub-eco-systems that follow certain rules that make the mapping in s…

  23. comment
    Comment #31678855

    There is still work to do to make Slint's accessibility support great, but this is an important first step: It validates the ideas we had to make Slint UIs accessible and puts a lo…

  24. story
  25. comment
    Comment #28850131

    Yes, there should be pre-build binaries of the viewer available. Right now there is not, but work is being done to cover the common platforms.