kookybakker

It's clear some talent is on display here, but I think it's being focused on the wrong thing. If I had to give some advice, focus on making something people want to use instead of trying to impress by making up arbitrary challenges.

I am quite sure it has been submitted and rejected before although indeed in my short search just now I couldn't find evidence for this statement.

Edit: Seems like the earlier attempt stopped before ever getting to the proposal stage, maybe it is worth pushing through even though some of the requirements for the unicode standards can not be met.

Seeing stuff like this, but knowing we can not get a unicode symbol for the https://en.wikipedia.org/wiki/Flourish_of_approval despite how ubiqitous it is in the Netherlands always frustrates me.

When you bring up the lower mass and let it go, it seems to push the upper mass away, which should never happen. This whole site smells off vibe coded jank.

In theory a get request sent to a server should not have any side effects and only retrieve some data. In practice implemention is completely up to the developer and their rule is about as useful as putting up an exit sign to prevent people from entering your building.

I have to admit I'm jealous of such a stylish suite.

I think even for a company like TSMC these ideas are important to understand.

To give you an example TSMC might have a factory with 10 expensive EUV lithography tools, each capable of processing 100 wafers per hour. Then they have 4 ovens, each able to bake batches of 500 wafers per hour.

TSMC could improve efficiency by reducing the number of ovens, because they are running only at 50% capacity. But compared to the cost of the EUV tools, the ovens are very cheap. They need to be able to produce at full capacity, even when some ovens breakdown, because stopping the EUV tools because you don't have enough ovens would be much more expensive then operating with spare capacity.

How about floats in scientific notation?