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...
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?
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)
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.
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...