HN user

cAtte_

246 karma
Posts0
Comments75
View on HN
No posts found.

the original title is "Most people who buy your game won’t play it", which is actually equivalent to what you're saying (even though it still says 'most people'!). HN mods edit titles to avoid clickbait and the like, which can end up like this

If my IP address says I'm in Romania but my browser is asking for the English language version of the page... That's a signal.

jesus christ don't give them ideas. it's annoying enough to have my country's language forced on me (i prefer english) when there's a perfectly good http header for that. now blocking me based on this?!

Microsoft Edit 1 year ago

well the editor was obviously designed primarily for Windows, not sure why the title says Linux

you are wrong. typst's lead dev has stated that an important goal is to have the CLI (which is open source) and web app behave identically, even refusing to implement such a basic feature as PDF embedding because, due to technical reasons, it is currently incompatible with this goal. [1]

typst, the project, is not by any means a "mix" of open and closed, even if typst, the company, is. indeed, the most thorough LSP implementation available (tinymist) is not only open source but a community project. for another funny example see typstify, a paid typst editor not affiliated with the company. [2]

[1] https://github.com/typst/typst/issues/145#issuecomment-17531...

[2] https://typstify.com/purchase/

this solution is just fundamentally insufficient. in the age of LLMs it's pretty insane to imagine programmers manually hard-coding an arbitrary subset of grammatical corrections (sure: it's faster, it's local first, but it's not enough). on top of that, English (like any other natural language) is such a complicated beast that you will never write a classic deterministic parser that's sophisticated enough to allow you to reliably implement even the most basic of grammatical corrections (check the other comments for examples). it's just not gonna happen.

i guess it's a nice and lightweight enhancement on top of the good old spellchecker, though

the pdfkit from the first google result doesn't seem to be related to apple's. what happened here is that "pdfkit" is a very generic name (that will tend to show up because people love writing pdf-related software) that also happens to coincide with apple's convention of naming their frameworks something-kit (uikit, appkit, avkit, ...)

they're not asking for a structural typing overhaul, just a way to make ad-hoc anonymous types with named fields and pass them around. a lot of times with tuple return types you're left wondering what that random `usize` is supposed to represent, so having names for it would be very convenient. i don't see why, under the hood, it couldn't just be implemented the exact same way as current tuple return types