446 karma · joined August 9, 2025
I mean the 5150 pc not the 5160 XT they mention.
Per Google, most HP printers are made in China.
A more likely explanation has to do with the economics of ink jet printers. The ink sales are so profitable that HP and other manufacturers subsidize their printers. This leads to prices at or near cost.
Since Ali express vendors can't count on follow on ink sales, they can't compete on price. And competing on price is Ali express's reason for existence.
So, ink jet printer are harder to find on Ali express. At least, low end consumer focused ink jet printers.
Laser printers, which aren't subsidized are common
It's like asking someone playing roulette to value "13 black", after they bet on it.
There valuations are always based on expectations of huge growth, not current value. Growth predictions with an extremely low confidence level. VCs make up for it by making a lot of bets.
The companies NEVER have current profits (The actual measure of value) that would justify their valuation.
So, it's comparing gambling payouts to corporate valuations, aka "apples to oranges", which are not related.
When the predicted growth doesn't occur, the companies valuation becomes based on its actual value (profits).
People are biased 25 vs. 55 not 33 vs. 34.
How many of us have made house plans at some point?
I might be better off getting something with a beefy GPU on AWS or Google cloud.
Other comments mention davinci resolve has this built in. How would you compare the two?
Everything the parent comment mentioned were implementation details that did not affect the correctness of the code.
I just wanted to point out that there are implementation details that DO affect the correctness of the code.
And, of course programs need to run on multiple architectures. So it's hard to do what people seemed to be talking about in this thread and verify code just from the source code.
If you have the luxury of proving the correctness of the CPU, compiler and OS, that should be a big win. Otherwise, it seems to just be another type of testing. Still useful, but calling it verified or proven seems a bit much.
From my perspective, it seems more to be writing another, more complicated program, with more opportunities for bugs, and seeing if the results agree
You can prove that f(a,b) always returns a+b.
And then you overflow the int on that machine.
Oops.
No. And this is a great example of the problems with specifications. You still have to write a spec. And this, too, is subject to bugs.
What's wrong with the statement above is there are 17 space characters in Unicode and another eight whitespace characters, like newline.
If you try to verify that something ends in whitespace, you have to make sure you have the right definition.
Not picking on parent poster! It's just a great example of the fact that you can verify, but if what you are verifying is wrong, it doesn't help.
Tried safari and Firefox focus
The company doesn't have to go away, the app just has to have issues. At least with web apps, you aren't depending on the manufacturer investing in nearly continuous upgrades to work in the rapidly changing phone environment
A web UI will continue to work for decades. And app will likely not last a year without updates.
If I search for Apple on food central, I get offered different types of Apple, like Fuji, honeycrisp, etc. with nutripedia I just get raw and cooked, which are within each type on food central.
In addition, nutripedia has a bunch of what looks like AI written text that is not particularly useful.
Writing an AI generated wrapper around something is not enough to be interesting. What do you see as your value add?
How do I do that?
First one is simple and focused, the second one tries to be & do everything. And frequently never ships.
Yet another reason to use open source.
That's a bit concerning. Runaway waiting to happen.
Now, it looks like the providers I use have good limits. But I do worry about this.
I compared it to another OCR of the same image, using http://ocr.space, and ChatGPT was correct in all the small number of differences, even preserving misspellings in the source.
1960s era. Humorous instructions for the IBM 360/69.
If the image link doesn't work, I've OCRed it:
IBM SYSTEM/360 MODEL 69 FEATURES AND DEVICES
Early Card Lace
1401 Incompatibility
407 Emulation
Chinese Character Set
Branch on Burned-Out Indicator
Branch on Blinking Indicator
Branch and Hang
Branch on Chip Box Full
Branch on Power Off
Branch on Sleepy Operator
Inquire and Ignore
Reverse Parity and Branch
Branch on Bug
Read While Write While Ripping Tape
Add Improper
Divide and Overflow
Subtract and Reset to Zero
Add and Reset to Zero
Scramble Program Status Word
Pack Alpha and Drop Zones
Pack Program Status Word
Punch Invalid
Rewind Card Reader
Backspace Card Reader
Read Print and Blush
Forms Skip and Run Away
Stacker Select Disk
Write Wrong-Length-Record
Write Noise Record
Seek Record and Scar Disk
Eject Disk
Rewind Disk
Backspace Disk
Punch Disk
Punch Operator
Execute Invalid Op Code
Read Card and Scramble Data
Select Stacker and Jam
Read Invalid
Rewind and Break Tape
Write Record and Run Away
Make Tape Invalid
Reverse Drum Immediate
Transfer and Lose Return
Print and Smear
Read Chads
Sharpen Light Pencil
Transfer and Drop Bits
Erase Card Punch
Read Inter-record Gap
Read Noise Record
Erase Read Only Storage
Destroy Storage Protect Key
Update and Erase Record
Move and Drop Bits
Circulate Memory
Move and Lose Record
Move and Wrap Core
Move Continuous
Execute No-Op and Hang
Develope Ineffective Address
Halt and Catch Fire
Scatter Print
Re-initialize Meter
Update Transaction
Reduce Thruput
Print and Break Chain
Lose Message and Branch
Burst Selector Channel
Invert Record and Branch
Illogical "or"
Illogical "and"
Bite Baudy Bit and Branch
Triple-Pack Decimal
Slip Disk
Stacker Upset
Uncouple CPU's and Branch
Scramble Channels
Edit:formatting.