Hacker Newsnew | past | comments | ask | show | jobs | submit | cunac's commentslogin

This is insanely good. Can't wait for grandchild :)


As immortal words of the master Oogway, "Yesterday is history, tomorrow is a mystery, but today is a gift. That is why it is called the present."


Or, as Yoyodyne Propulsion has it, “the future begins tomorrow!”


I am utterly fascinated by Japanese joinery


market cap is same as 100% of shares so it is $25B more than Nvidia price


only if you assume there is the same level of instantaneous demand for a supply of 10x as many shares

definitely not the case


Think about it this way: The current market price represents the amount the shareholders who least value their shares would be willing to sell them for. As you want to acquire more, the price is going to go up, not down.


That's pretty irrelevant if it only represents 10% of the total equity, though. It's not like you, as a retail investor who owns a few shares of a company, have any say in whether it gets acquired.


SoftBank values continuing to hold the other 90% of the shares more than the market price or they’d be selling more.


That is what you assume when you look to take a company private.


I am not sure if you realize that Eagle is fully embedded and rebranded within Fusion360 so you will have access to the same functionality but in integrated environment (for better or worse)


Speaking as a subscriber to Fusion: Do-it-all software is nearly always inferior to special purpose software. I don't use the built-in Eagle functionality in Fusion even though I've paid for it.


Yeah, I have no love for Autodesk as a begrudging Fusion360 user, but on the surface it seems that 10 years before sunsetting an acquired product as well as integrating it into an existing platform in that same timeframe is pretty good as far as a product acquisition goes from an end user perspective.


Yeah, on paper it looks an acceptable strategy. Unfortunately it looks like they botched execution.


2016 was not 10y ago tho.


EOL is 2026, so ten years.


if anything I would think that person would write same code but without PR would lost the opportunity of having better quality. People are blind to own mistakes. I can't count how many times I would stare at a code not seeing something and other person would spot problem almost immediately.


not to be rude but 250K uniques users is 3 new users per second and doesn't say anything about concurrent users. Concurrent users are scaling problem


There's a natural distribution to these things, so actually an average of 3 does in fact say "something" about the tail behavior of concurrents (that is, the highest values you can expect under peak load).

As a rule of thumb: it's probably on the order of 5x-10x (absent outlier events); then look at your data to find out what it actually is (users are not evenly distributed across the day/week); then apply the usual 4x or so rule for capacity planning.

That is to say - it isn't necessarily a scaling issue. Especially when you're just starting out and no one is looking at your damn app anyway. If it's well designed and cleanly built you'll have plenty of time to factor for scale when the time comes (if it comes).


That reminded me

The moon is a harsh mistress by Robert A Heinlein


>The moon is a harsh mistress by Robert A Heinlein

That looks good, haven't read it. THANKS!


The Old Man and The Sea, For Whom The Bell Tolls by Ernest Hemingway


wait for next software update to patch security :) , you made my day


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: