HN user

circuit10

1,686 karma
Posts2
Comments963
View on HN

Trying a bunch of sizes in their studio tool (all cubes to make it easier):

5mm x 5mm x 5mm (smallest I can select): $32.58

10mm x 10mm x 10mm: $36.58

20mm x 20mm x 20mm: $82.86

30mm x 30mm x 30mm: $143.60

50mm x 50mm x 50mm: $509.14

100mm x 100mm x 100mm: $3,028.58

150mm x 150mm x 150mm: $9,618.86

195mm x 195mm x 195mm: $20,641.32

(it says it's an estimate excluding tax and shipping)

I think they should just have to properly explain how AI tends to make things up when it doesn’t know, and that it’s good for coming up with ideas or suggesting directions for research but that you shouldn’t rely on it, because currently their advertising makes you think you can rely on it

The “AI can make mistakes” kind of disclaimers they hide in the corner don’t really cut it

Do you not ever want to show someone something on your screen? For a bug report or to demonstrate a project you’re working on? Or do a screen share to ask for help with setting something up (which is admittedly a bit different from a recording but only in that it’s live)?

I can see a lot of non-techy people not knowing how to do this but among people who know how to do it I bet it’s above 50% who use it

It is of course reasonable to restrict what you can do with a product you’re selling for money. There are plenty of laws and regulations that already do this. Without these kinds of laws intellectual property wouldn’t even exist - copyright was only created to benefit society by providing an incentive for people to create and invent things

It’s no different from mandating that the software can’t be malware that puts a ransom on your data, contain other people’s copyrighted content without permission, or just not work despite you claiming that it does when you sold it

And it’s not mandating that anything is structured in a particular way, just that the game works as the buyer would expect and how they achieve that is up to them

If this was about open source software I’d agree about not forcing people to do additional work, but if you’re selling something for money you should be obligated to do the bare minimum of stripping secrets out of a binary so the product you sold can actually work (and this will be barely any work if it’s designed with this in mind in the first place)

We already obligate them to do other basic necessities for consumer protection such as refunding or replacing faulty products

When your code can be completely reshaped by earlier passes and macro expansions and inlining I don’t think it’s feasibly to make a useful warning for that

If you include a library function with a null check that gets inlined you probably don’t want a bunch of warnings there for code you don’t even control

I don’t mean this in a rude way but you should really read the posts I linked, it’s interesting and part 3 especially answers these questions

Direct link to part 3 (but read the others first for context if you can): https://blog.llvm.org/2011/05/what-every-c-programmer-should...

You don’t want warnings for every piece of code in a library you’re not using or sanity check you added that isn’t supposed to be hit

And you can’t warn when you’re optimising based on undefined behaviour because you can’t know when it will happen, that is equivalent to the halting problem

If you warned whenever undefined behaviour could be happening then e.g. every single pointer deference would say “warning: compiling assuming pointer is not null or unaligned”

What if the compiler is able to use that to determine that a whole code path is dead, and then significantly improve the surrounding function because of that?

Compilers optimise in multiple passes and removing things earlier can expose optimisation opportunities later that can affect other parts of the code too

It works fine if scanned by a machine though (ticket gate, self checkout etc.)

I've used a third party app for this for a UK weekly pass train ticket you could only buy physically, but if you buy it on a train rather than at a station they can't print you a ticket with a magnetic strip and they have to give you one with a barcode (technically an Aztec code), which you can then scan onto your phone and use at the gate. But I kept the original ticket with me too and would use that if a person asked to inspect it