I will argue that stuffing a corpse full of formaldehyde, putting it in a sealed box, likely plastic-lined, and then burying it in such a way as to ensure that no future life forms benefit from the sequestered biology (composting) is pretty odd.
Cremation is pretty odd as well: we are like 80% water (or whatever), so it's more like boiling someone away and then burning the desiccated results. It's quick energy-intense, and to what end?
I've heard of some recent innovations in mushroom caskets that help decompose the body in short order. I would imagine that silicone prosthetics and what-not are somewhat of an issue...
the interest in self-driving cars (by anyone except salivating bean-counters and CEOs) has been greatly exaggerated.
Most people seem to prefer driving to being a passenger, particularly the passenger of some broken half-baked tech
(the kind of semi-broken tech all consumer computing systems seem to say is OK to bring to market)
That's a very short-sighted way to read the room.
Doubt has been sown at a critical Rust adoption juncture, and major damage has occurred, and the stench will not simply blow away or only stick with the forkers, it's damaged RUST and The Official Rust People need to wake up and smell some burning coffee, or the dreams of this unique lego just evaporating while you claim it's all a tempest in a teapot.
Note: I have no horse in this race other than using Rust and wanting to have a stable unique lego for all things from baremetal to high level, which is here and being threatened by all this nonsense.
HN teapot tempest = something Official Folks better heed, or pay the price for... problem is, this strike is damaging the company, and management thinks it's no big deal...
There have been various toy DAWs the have web GUIs.
I've never seen a production-capable DAW with a web GUI.
I suspect that existing web-as-native-GUI frameworks make presumptions about threading that won't work where a realtime audio callback thread piping data to other audio processing threads and back is the real show, and where the GUI may need things like updated zoom levels dirtying many waveform drawings at once requiring recalculation of peak values in viewable windows to draw the little lines that make the waveform, among other things that may make simple partitioning of systems more challenging...
Well, in the sense of "lifetimes" that I mean in terms of ownership, scope, and destruction, yes we do know the lifetime (removing a plugin-instance and de-allocation in an orderly fashion is part of a plugins API, for example)
Audio is literally a major domain where GC is a big no-go... (even a GC running in another GUI thread can be an issue if it's a stop-the-world operation)
You won't find a single audio backend in a GC language.
GC is obviated by Rust anyway (it's native RAII pattern involves "ownership" which allows "borrowing", things are immutable by default...) and there are ARC and Box implementations (check out Box particularly)
You could always slap something like Boehm on, lol...
These things need to be solved by the Rust community, regardless, so it's full-steam ahead, and GC is not something tenable when there are ways to control the timing of resource freeing that won't glitch audio playback, which GC would do.
GC is for when you have no idea about the types and lifetimes of the objects you create.... when you know these things, why wouldn't you setup proper shrink-wrapped alloc/de-alloc in a time-coordinated fashion?
Ableton isn't open source. There are also several other DAWs and Ableton isn't some pinnacle of software engineering.
Take Larry and ESR and anyone else with some pinches of salt, because accepting some proprietary implementations of DAWs as a tombstone on the FOSS development of DAWs is rather reductionist to the point of being totally wrong.
Why would you bother posting such a comment?
Your notion that all questions regarding how to do the manifold tasks a DAW are resolved is specious, and you couldn't possibly prove it to be true because it's false.
Ableton has managed to make a product that solves the DAW questions in one particular way, and it's a black-box to boot, so that's not in the public domain, as Meadowlark is.
The technical questions entailed in Rust trying to mate with GUIs are EXTREMELY UNSOLVED AND RELEVANT RIGHT NOW! Let me tell you, state, state, state.
I can't even propose that you work for Ableton as they are classier than this!
Their product is a good and useful DAW for many people, you bet.
Your point is?
your entire complaint appears based around the timeline of windows support.
you are free to use windows as a principal OS, but please inform us of your biases when totally trashing a team and product for what is essentially a technical issue of significant proportions, not a product of laziness or slowness, as you allege.
Crystal has already "taken off" for me, in the sense that it does everything I need it to do. The standard library is replete with http client and server, as well as JSON, and a host of other useful bits, just have a look: https://crystal-lang.org/api/
I can use any/all command-line utilities with an IO buffer (image processing, other out-of-band processing)
The stock "DB" module supports Sqlite, MySql, and PostGres out of the box.
SPEED: anyone "sticking" with RoR is not paying attention here: Crystal is a compiler and spits out a binary executable with low memory usage compared to it's interpreted cousin. This binary executable can be run by systemd as a normal system service, started with command-line options, etc.
Apples-and-Oranges comparison: I've turned a nodejs-based app that used roughly 600mb memory into an executable using 12mb. The latter has also not leaked any substantial amount of memory after running for 5 months straight now (still says 12mb) so, take that as you wish...
For me, Crystal has already arrived. I don't need group approval for this to be the case. I can happily use version 1.7.3 for the rest of eternity, so I don't see this rug being pulled from out from under me in the near future.
Perhaps use private shard repos if this is your actual concern.
Raydev appears to have no interest in learning anything about the music production process nor putting in any work.
I suggest that they are using "expensive gear" as a proxy for "effort, work, sweat, time"
mechanical skills are EARNED, and are a lot of fun to exercise when functioning.
*before anyone suggests "ableism" I refer you to Django Reinhardt, the drummer from Def Leppard, and anyone who has overcome physical disabilities to express themselves upon the musical instrument of their choice.
"democratization"!? It wouldn't be YOU or another PERSON gaining these capacities, in such a scenario, it would be the tool, and you would be the toolmakers customer.
ATM, LLM's of reasonable sophistication for such tasks are not running on your laptop, and at the point they do, something else will be getting all the limelight, and it won't be within your reach.
As a lifelong musician and composer and producer, it's just automating things away that I don't want automated away. Producing music is about making decisions.
You act as if Radiohead just inserted money and out came pro music, but really you appear to be wishing to skip any hard work and appear to be asking for instant gratification. Well, I can tell you, as someone who could readily train AI in music, that you only cheat yourself by cutting corners.
Knowledge is power to do what you actually really deeply want to.
Handing off the minute decisions that add up to making a masterpiece = cheating oneself of being a creator.
I think it's rather the opposite. Those tools are controlled by large capital, at the level of being capable of wowing people with cutting-edge realistic content.
I predict a renewed interest in human scale art and culture and socialization.
The lines for the toilet at the worlds biggest party are surely long...
Well, coding != complicated frontend development, which it appears you are teaching your students as an allegedly "easy" programming environment.
You could perhaps consider starting them with Racket or some other "batteries included" programming environments specifically designed to avoid tooling bogs?
Cremation is pretty odd as well: we are like 80% water (or whatever), so it's more like boiling someone away and then burning the desiccated results. It's quick energy-intense, and to what end?
I've heard of some recent innovations in mushroom caskets that help decompose the body in short order. I would imagine that silicone prosthetics and what-not are somewhat of an issue...