From the product perspective, it occupies a different market than Emscripten, and I don't see it's good comparison. Your product is borderline optimized to run C++ code on Web (and Coi is a cherry on top of that). Where Emscripten is made to make native C++ application to run on Web - without significant changes to the original source itself.

Now, the `webcc::fush()` - what are your thoughts about scalability of the op-codes parsing? Right now it's switch/case based.

The flushing part can be tricky, as I see cases when main logic doesn't care about immediate response/sharing data - and it would be good to have a single flush on the end of the frame, and sometimes you'd like to pass data from C++ while it's in its life scope. On top of that, I'd be no surprised that control of what flushes is lost.

(I'm speaking from a game developer perspective, some issues I'm thinking aloud might be exaggerated)

Last, some suggestion what would make developers more happy is to provide a way to change wasm compilation flags - as a C++ developer I'd love to compile debug wasm code with DWARF, so I can debug with C++ sources.

To wrap up - I'm very impressed about the idea and execution. Phenomenal work!

The subscription for bed is not, it locks artificially features to pay monthly. Even more, it collecs data to improve the product (which sounds good) - but you need to pay for this. They have an ability to run model locally - they choose to not.

I like Topaz approach: you have an ability over some time (subscription period) to have up to date model that will help you recognise snoring etc, then if you choose not to pay - you stick with this model, but it still works.

Subscription in addition is something that limits an ability to sell it in the future.

Comments URL: https://news.ycombinator.com/item?id=42890219

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=39111053

Points: 114

# Comments: 14

Do you know some techniques that can be used instead of dot-voting? (I'm not referring to more 'official' methods like MoSCoW or Value/Effort matrix - frequently at the stage we don't have all data to switch to them).

The simplest use case: We have a team retro, where each team member writes a note of some problem has occurred last sprint - then everyone participating to the retro has N votes (3 usually) that are spend of voting of the most important topic to discuss.

I believe the dot-voting has a few biases: - members can vote on already most voted item - members vote on their topic - the most common (not necessary most important topic) problem is top-voted

So far I didn't find any simple but more correct alternative to the dot-voting. Do you share the same problem? Do you have some idea what can be used instead or how the dot-voting can be improved?

Comments URL: https://news.ycombinator.com/item?id=33345748

Points: 2

# Comments: 1

But my problem is that similar to memory leak, I'm facing with the time leak. I spend a lot of time on meetings, or provide support to systems that nobody else knows about. Some of the I wrote, some of them I just get known and I left alone.

It's hard to get rid of that legacy baggage, so that I think a "fresh start" will be the only option to get some air - but it's almost impossible to stay in one company and have a fresh start.

If you are for a long time on one company: How did you survive? How do you optimize your time?

Comments URL: https://news.ycombinator.com/item?id=32011221

Points: 30

# Comments: 16

By removing the debugging ability it's almost pushing the responsibility onto publishers/developers to say "hey, we don't support iOS 10 anymore - we are these bad guys".

In a case when we would like to provide the best possible experience to all players (even if the market share is less than 1%) - I consider as a regression, an unnecessary change and complication.