emscripten VS ravynos

Browsers limit the ability for these platforms to use raw sockets, there simply is no API for it. The best that can be done /today/ is to use WebSockets, which are not the same thing any can't be used for HTTP requests without the server expecting a WebSocket connection:

https://github.com/emscripten-core/emscripten/issues/5196#is...

Only half true. Emscripten implements the SDL 1.2 (and also SDL_mixer 1.2) API in Javascript here: https://github.com/emscripten-core/emscripten/blob/main/src/.... On the other hand SDL 2 (and SDL_mixer 2) are proper ports (which you linked to).

So there's quite a size penalty to using SDL 2 rather than SDL 1.2.

Playing with low-level stuff is fun, but I won't use it anywhere in productionable code. Well, at least without considerable experience and understanding of the Emscripten code base.

Thank you for your comment!

WASM gave Figma a lot of speed by default for a lot of perf-sensitive code like rendering, layouts, applying styles and materializing component instances, our GUI code is mostly React and CSS.

WASM engine performance has not been a problem for us, instead we are constantly looking forward improvements in the devex department: debugging, profiling and modularization.

One of the largest challenges of the platform we face today is the heap size limit. While Chrome supports up to 4GB today, that's not yet the case for all browsers. And even with that, we are still discovering bugs in the toolchain (see this recent issue filed by one of our engineers) https://github.com/emscripten-core/emscripten/issues/20137

The challenge of the perf-testing at scale in our company is helping developers to detect perf regressions when they don't expect them - accidental algorithmic errors, misused caches, over-rendering React components, dangerously inefficient CSS directives, etc.

https://github.com/emscripten-forge/recipes/tree/main/recipe...

Re: emscripten fs implementations: https://github.com/emscripten-core/emscripten/issues/15041#i... https://github.com/jupyterlite/jupyterlite/issues/315

Moving onto the project, let’s first install Emscripten from their git repository. Emscripten will compile C into Wasm code. An important note is that I will be using Mac OS for this project. If you want to follow along using Windows, use this link. To Begin, open your terminal and clone down Emscripten with:

I got pointed to this one here: https://github.com/emscripten-core/emscripten/issues/15487

If you want to do it, go to town. This is the only reference I could find to anybody targeting wasm with i2pd frankly I really hope the person inquiring in the issue is also you.

Right, and if that momentum is going to last 20 years, then that's going to dictate what's a good strategic decision and what isn't for the next 20 years. Thanks for letting me know what the good options might be when my infant daughter is halfway through college, that doesn't help me save for it in the meantime.

Prior familiarity is a very good reason to pick an option for a greenfield project if you're operating on any type of serious budget (time or money), especially if you need to hire others to help out. There's also the annoying reality that most libraries for new/up-and-coming languages are simply inadequate, despite whatever claims they make.

For instance, one of my personal side projects involves getting familiar with WebAssembly (note: not on a serious budget), and I'm using emscripten to transcode because that's what the internet seemed to think was the closest thing to a standard toolkit. I found a bug simply by combining two pieces of example code from Emscripten's own documentation (you'll note I'm transcoding from c++ due to prior familiarity): https://github.com/emscripten-core/emscripten/issues/17143

This is not a dig on emscripten per se, merely pointing out that it's probably not mature enough for the stress of corporate-scale development, where you encounter all sorts of crazy edge cases well beyond the sample code. Java over the years has obtained that level of maturity. The edge cases are largely solved or at least known, and there's an army of experts and consultants ready to help if there's a problem. When time is money, that matters. It determines the risk profile of any project, greenfield or otherwise.

Java's momentum hasn't stopped, at best it's simply slowing. And at this rate it'll take decades to come to a stop, and decades more to recede to any meaningful degree. I'll also point out that C is very much alive and well in the embedded world. Plenty of job postings looking for C experience explicitly.

Hi A long time ago i saw an opreating system called ravyn os(it's name was airyx before) and i was impressed by how beautiful they made thier gui to look too similar to apple one's and when i get a bit deeper in thier the code i discovered that thier gui was made by using apple cocoa 😅https://github.com/ravynsoft/ravynos So here's my question could i make a gui library using opengl and make it look like apple cocoa 🤔 or it's not the thing that is made by API like opengl and is made by a ready gui library 🤔

Hi Since a bit longer i found an open source opreating system called ravyn os (it's name was airyx before but it changed now) and i was impressed by how the made thier gui which was too similar to apple cocoa gui but when i get a bit deeper in the gui code i found that they did it by using apple cocoa library 😅 https://github.com/ravynsoft/ravynos So here's my question how could i make an application using a library or even an opreating system that pop up a window with a good looking such as apple or even to design my own style for the window and should i use any API such as vulkan or opengl to make such a thing or this is unnecessary?

Here is the ravyn os https://github.com/ravynsoft/ravynos

My feelings about Mac OS X are similar to the author's. I switched from a Windows XP/FreeBSD dual boot configuration to Mac OS X Tiger back in 2006 when I bought my first modern Mac, a Core Duo MacBook. I've remained a Mac OS X user from Tiger all the way to Mojave. Mac OS X in the 2000s to me was heads-and-shoulders better than the competition. It had a well-designed user interface, and most applications conformed to the Apple Human Interface Guidelines. It also provided me a Unix shell whenever I needed it. In my opinion Mac OS X peaked at Snow Leopard; in fact, I'd be comfortable using Snow Leopard (or even Tiger) as my daily driver today if it supported current hardware and if there were a modern web browser for it. It was a nice marriage of NeXT technology and an updated version of the venerable Macintosh user interface. It felt much more pleasant than Windows of the era (though I admit I liked Windows 7), and the desktop environments for Linux and the BSDs simply didn't compare.

Then came the Tim Cook era, and with it came the gradual locking down of the Mac, both in terms of hardware (for example, the soldering of formerly upgradable components such as RAM and storage) and software (for example, notarization). The user interface also gradually started adopting more iOS influences, which I think take away from the desktop experience. Due to my disappointment with Apple's direction (especially since roughly 2016), I opted not to upgrade my aging 2013 MacBook Air and 2013 Mac Pro with new Macs, instead switching to a Microsoft Surface Pro (running Windows 10) and a custom Ryzen 3900X build (which runs both Windows 10 and FreeBSD). I miss macOS, but I enjoy the openness of PCs, and I enjoy the flexibility of Windows and FreeBSD.

I am keeping an eye on two very interesting projects that attempt to replicate the spirit of early Mac OS X: helloSystem (https://hellosystem.github.io/docs/) and airyxOS (https://airyx.org/). Both projects are based on a FreeBSD foundation, but the major difference between the projects is airyxOS is a much more ambitious attempt to reimplement macOS's infrastructure (even going as far as to aim for supporting "trivial" Cocoa applications), while helloSystem has different (Qt) underpinnings, with an emphasis on replicating the Mac OS X look-and-feel and promoting adherence to the Macintosh Human Interface Guidelines. If these projects become successful, this will provide people who desire the early Mac OS X experience modern systems that will maintain that experience.

As another commenter mentioned, AiryxOS is working on an API-compatible open-source implementation of many macOS Frameworks, however it is incomplete.

Our focus right now is on running FreeBSD and Linux applications. But the https://airyx.org/ project is aiming for source-level compatibility and eventually possibly even binary-level compatibility. If they succeed, maybe the improvements will flow back into FreeBSD and helloSystem one day.

> … Probably best to not try to make BSD into modern Linux which is basically FreeWindows. …

airyxOS, based on FreeBSD, aims to provide "… the finesse of macOS with the freedom of FreeBSD. …".

<https://airyx.org/>

I wish well to projects such as this, however I rarely engage – testing and feedback – because the focus on Apple keyboards is too much for me.

(I taught myself to use the keyboard in a very different way when I switched away from Apple after twenty-something years. I don't intend to un-learn that switch.)

0.5. Wait for airyxOS to be fully complete and run it. It is a freeBSD based system that aims to be compatible with MacOS.