piker

24 ms·

1. 571.▲
   by piker 1y ago

   Working on Tritium, the legal IDE in Rust ( https://tritium.legal/ ) This month I'm improving CI/CD for e2e testing across Windows, macOS, Linux and Android. Also adding support for unlocking password-protected PDFs
2. 572.▲
   by piker 1y ago

   Right, but the point was there is precedent for laws affecting American operations when distributing software into a jurisdiction.
3. 573.▲
   by piker 1y ago

   Classic case of Wolfenstein 3d being banned in Germany in the 90s rings a bell.
4. 574.▲
   by piker 1y ago

   > Existing no_std + no alloc crates written for other purposes can generally run on the GPU without modification. Wow. That at first glance seems to unlock ALOT of interesting ideas.
5. 575.▲
   by piker 1y ago

   > For named tuples, you are better off using the typed version typing.NamedTuple [1] instead of the classical one suggested in the article. Aside from providing typing, the typed version has a much nicer syntax to define it and lets you
6. 576.▲
   by piker 1y ago

   Probably their web servers are getting hugged to death by all of their worldwide users grabbing the phone to check who to call.
7. 577.▲
   by piker 1y ago

   There are a whole lot of downsides to that approach. Most applications don't do it, although perhaps it does make sense for the general audience like mine. Fortunately, however, a lot of Macs are using Chrome or Firefox that expose thi
8. 578.▲
   by piker 1y ago

   Yeah for folks who are viewing this site it's obvious, but my target audience doesn't have a clue for example.
9. 579.▲
   by piker 1y ago

   This comes with some downside because to protect privacy Safari blocks some useful APIs. For example, you can't tell if the user is running Apple silicon or Intel. That means you have to ask them whether they want the Intel or Apple si
10. 580.▲
    by piker 1y ago

    This looks awesome. Why Python? Probably because most of the SDKs are python, but something that could be ported across languages without requiring an interpreter would have been really amazing.
11. 581.▲
    by piker 1y ago

    "You're all too lazy to read the French words." "Here I've copied and pasted the French words, also you're lazy." is exactly the type of sentiment that makes zero sense.
12. 582.▲
    by piker 1y ago

    Nobody is proposing that people will be writing markdown by hand in text editors. Just that a lot of the complexity of rendering stuff on the screen precisely as it would be printed on, say, A4 paper can perhaps soon be left behind. People
13. 583.▲
    by piker 1y ago

    Yes, the markup is hidden and the document is rendered in all cases. The point I was making, and I believe the parent was making, is that it doesn't have to be wed to the physical medium. Perhaps we're talking past each other here
14. 584.▲
    by piker 1y ago

    I think you're missing the point that the "G" in WYSIWIG is "when printed". Everybody wants uniform rendering across applications in the way that, say, websites render uniformly across browsers. But fewer people car
15. 585.▲
    by piker 1y ago

    Without knowing too much of the EU history, I have always understood that anti-trust pressure from the EU effectively forced Microsoft to publish the OOXML spec in the first place.
16. 586.▲
    by piker 1y ago

    Agreed, but the point the author is missing is that complexity doesn't exist due to deliberate corporate lock in, but because the product is 40 years old and has had 10-11 ways to do just about everything it does. Unfortunately, as you
17. 587.▲
    by piker 1y ago

    Not sure why you're getting so downvoted. It's a totally reasonable opinion in 2025 but it faces massive adoption headwind. People still cling to the idea of printing pages of documents even if it's increasingly rare (even, s
18. 588.▲
    by piker 1y ago

    While I generally agree, I don't think the author is complaining about the XML spec's complexity per se but rather that rendering the underlying structures to a page is hard.
19. 589.▲
    by piker 1y ago

    This is a dupe from: https://news.ycombinator.com/item?id=44606646 but I'll repeat what I said over there. I feel qualified to opine on this as both a former power user of Word and someone building a word processor for
20. 590.▲
    by piker 1y ago

    Woosh!
21. 591.▲
    by piker 1y ago

    TIL
22. 592.▲
    by piker 1y ago

    My take as an interested third party as well.
23. 593.▲
    by piker 1y ago

    I feel qualified to opine on this as both a former power user of Word and someone building a word processor for lawyers from scratch[1]. I've spent hours pouring over both the .doc and OOXML specs and implementing them. There's a
24. 594.▲
    by piker 1y ago

    LibreOffice is free and GPL.
25. 595.▲
    by piker 1y ago

    Thanks so much Peter - how do non-US people typically work in SF during YC? I am a US citizen but have a few non-US citizen friends who might join if accepted.
26. 596.▲
    by piker 1y ago

    Would be good to hear more details about the journey from bootstrapped North Carolina house to a decent-sized team out west. Is Jefit profitable now? Then? What were revenues like during those times? What's the software stack? Interest
27. 597.▲
    by piker 1y ago

    I sense a settlement agreement with strong non-disparagement terms is in the works here.
28. 598.▲
    by piker 1y ago

    That was my issue. Integration works, Outlook itself not so much, afterwards. (I.e. memory error.)
29. 599.▲
    by piker 1y ago

    To be fair though, unsafe rust (where the COM lives) is basically just C, so I totally expected it to be tractable in the same way it has been tractable for the last 20ish years? But it isn’t. Why is interacting with the OS’ API in a compi
30. 600.▲
    by piker 1y ago

    Actually hadn’t tried Gemini with it yet. Perhaps worth taking a look.