Hacker News Reader

xpaskyon InvoiceNet: Neural network to extract information from invoice documents

Check Rossum's (https://rossum.ai) free trial - happy to hear feedback!

xpaskyon InvoiceNet: Neural network to extract information from invoice documents

Hi, I get why going with an early stage service can feel dangerous Maybe Rossum (https://rossum.ai/) can be a good compromise - a more mature startup with significant portfolio of enterprise customers already and a big momentum, nothing is likely to veer us off the path anymore; our product isn't the cheapest but our customers keep telling us it's the best in class (in the end it's definitely cheaper than trying to build your own).

xpaskyon InvoiceNet: Neural network to extract information from invoice documents

Take a look at Rossum https://rossum.ai/ - hopefully the highest accuracy out there and as good a momentum in terms of dev community etc. as the big cloud services. (disclaimer: founder here :)

xpaskyon Ask HN: Which project does not have any good open-source alternatives?

My dad aches after a good and powerful typesetting tool (for less technical users than *TeX is aimed at), in the vein of the Ventura Publisher of old. Nowadays it seems all about Adobe Indesign but the workflows seem inferior for many book-type workloads. Scribus needs a lot of help.

xpaskyon The Disaster of Python 3

This is a nostalgic article, as underlined in the closing section about XON/XOFF and mainframe-compatible escape sequences.

The world is moving on, and while historic systems are beautiful (I still have a 2.11 BSD emulator running - or rather runnable - somewhere), at some point you need to weight the breakage for legacy users against the cost of maintenance of the compatibility.

Indeed, POSIX is still mandating that filenames are arbitrary byte sequences. But it is just becoming impractical, and in the end it's up to whoever has the motivation to have it working to keep it working, and if there's not enough people with this motivation it's just going to inevitably rot.

It's likely that 10 years from now, anything non-Unicode will be completely broken on modern (desktop, at least) systems and perhaps Linux even gets an opt-in mount option for enforcing filenames to be utf-8-compatible (which may change to opt-out another 10 years on, just as POSIX is going to evolve too in this regard).

Yes, it's a pity and I likely still have some ISO-8859-2 files from 1999 on my filesystem. But I think it's unreasonable for anyone to waste time with that support. And I wouldn't advise anyone wasting extra 20 hours of your developer life on building things around ncurses instead of a more direct approach - build a cool feature in that time instead!