trzeci

the real shovels for the real shovels is energy

I love the idea and execution. I did some reading of the code webcc and it's just brilliantly simple, and delivers to the promise.

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!

Thanks for this! The automatic title translation are so low quality I'm surprised the same company created Google Translator. In a lion share cases they are plain wrong, in most they are awkward, in all - they are misleading that the content somehow promises native experience.

Dragon Sector's doing good!

I don't get it - why the world, Excel can't just open the CSV, assume from the extension it's COMMA separated value and do the rest. It does work slightly better when importing, just a little.

Cigarettes is a consumable resources, as for any resources like that it has fifferen justification as you cant produce it.

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.

VHD that use ReFS to improve build times

Got to 45 level, just by pressing arrow up for 15 minutes. There is no penalty for loosing a life, so - it's not a game per se, as you can't lose.

What's the device model (in Apple signature, like iPhone14,4) when Vision Pro is used?

You might be surprised what is the real money printer in ABK.

It feels good, right?

There is a cool effect, when you populate every field

How this is "Show HN"?

Update: I found a good blog post that states the problem I feel: https://stephenanderson.medium.com/whats-wrong-with-dot-voti... with a possible solution it to then.

This is a very good advice - and helped me a lot to survive for these 8 years here, also it's a very good opportunity to increase the network of connections inside big organization - which is good also.

I see still opportunities for me to grow (now on the tech lead side) and value I can add to this org. Compensation wise it's on the market level (I do research once 2 years how the market changes, even I participate to interviews for the curiosity - so far the current company wins as an entire package)

Apple does not limit minimal version of iOS during the submission process - which is a signal that this version is supported.

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.

Lack of support for the on-device debugging for iOS 10 is at least confusing.

And yes, people still use iOS 10, and at scale we should be able to troubleshoot problems on that iOS.

Hoped for MX Master 4 to be honest

Did I miss something, but I don't see any mention about improvements in debugging capabilities. As a game developer that targets iOS/Android/UWP/WASM - WASM will be never a first target to work with, if there will be no debugger connection between IDE and Browser, that understands WASM.

The current solution that works only for Chrome and allows to use DWARF is an improvement but it has lot's of limitations: One of them is the limit of 4GiB (or 2GiB - don't remember) of DWARF file. Secondly - the entire browser tends to crash with that plugin on larger projects.

DOM API? Why? This can be added by any third party library. Wasm should not care about DOM

Thanks for bringing that topic, for me as an expat it a major pain. I live in a country with rather unusual language, but I have only contact with English speaking people. And every service puts the locale of this in default - even with stating in browser settings what are my preferences. The worst part of this is that in many places I don't even know how to change local on specific pages manually.

VPN is the only valuable option for me unfortunately.

I'm not quite sure if this is a right content for the HN.

I'd rather discuss about challenges in the production or testing process. Perhaps discuss future of the base old gen consoles (This is a first title that has quite different content between PS4 and PS5).

Discussing about game itself is polarizing, I know people hate this game, I know people love it and people don't care.

+1 On that. Cuda is the only editor that supports my work challenges, that is editing huge ASM.js files (100MB+) without any problem.

It's impossible to provide a list of all ads urls. Simple RegEx matching works better, but that requires a dynamic approach

It's an unconfirmed rumor.

Also I'd be skeptical to some extend on this. Maybe back in time when a chip fail ratio was lower was a case. But now, there is a quite measurable amount of chips not passing requirements for a high tier cards, but can be used in the lower models (with limited amount of cores etc or worse thermal efficiency).