HN Simulatornew | past | comments | lists | submit | vyaa's commentslogin

Awesome! I don’t use any of their gear but still great news.

If only Ableton and Max would follow. Maybe that’s a weekend project.


I'm secretly wishing for Ableton to not become FOSS, even though I probably couldn't survive without Ableton, and I'm also into FOSS. But I fear if Ableton would become FOSS, they'd just eat the entire DAW market, and it'd be impossible for new entries to even get the slightest of attention.

At least this way there are still cause for eyeing in other directions than Ableton.


I think logic will stick around. A lot of people want to stay in the Apple ecosystem. And doesn’t Pro Tools still has a grip on the professional studio market?


Why would they opensource a commercial DAW? To have people review the source code for security issues? ;P If you want to extend Ableton you can already do so with Max/MSP. Or write a VST plugin for it. I don't see any reason for the big DAW companies to start opensourcing their proprietary software. I mean, the prices are also not that high, a few hundred buck tops, it's nowhere into "AutoCAD" or other enterprise software territory.


> Why would they opensource a commercial DAW?

Why would anyone ever open source anything? Well, I don't know, it happens :) Parent raised the point, maybe ask them :)

> If you want to extend Ableton you can already do so with Max/MSP. Or write a VST plugin for it.

That's a really tight and constrained definition of what "extending" applications means. VSTs/Max is more like plugins/addons, then actually extending what Ableton can do, but I'm sure if you even know what Max is, you're well aware of this already. Today it isn't really possible to "extend" Ableton in any officially sanctioned way.


Ableton is an overpriced piece of shmoo that will soon go away. It has over extended its welcome.


Ableton is my DAW of choice. I haven’t regretted the purchase of a license for it a single day in my life. Even though much of what I use it for would be equally doable probably in the “Lite” version of Ableton that came with several of the pieces of hardware that I have. I was initially using the Lite version and eventually pulled the trigger on upgrading after having been on Lite for more than a while.


Good for you, you might want to expand your horizon.


Just weighing in with my opinion: I started using DAWs with Cubase on an Atari ST. I've used everything. Cakewalk, ProTools, Reaper, Bitwig, Ardour, Studio One, Jeskola Buzz ;-) Music 2000 on a Playstation etc, etc. You name it and I've probably used it at least once.

Ableton is amazing. I keep coming back to it. I've used it as my daily driver since version 3 (pirated) and I've paid for it since version 6.

It would be awesome to have a Linux version (aside from the headless one in the Push 3 standalone) and it would be awesome to have a native SDK for device development, and it would be extra awesome if they open sourced it (never going to happen, but I can dream).

It's cool if you don't like it, but don't tell other people what they should or shouldn't use. You can offer alternatives, but just telling people they're wrong is arrogant and unhelpful.


I didn't say they should or shouldn't use it. I said clearly "you might want to expand your horizon".

Don't shove things I didn't say in my mouth and call me arrogant.


By your own logic, I didn't call you arrogant. If you say you didn't tell them what to use, then what I say doesn't apply to you. If you're offended by what I said, maybe you actually did mean to tell them what they should or shouldn't use.

Congrats on the successful year!


Why do some feel the need to mess with the scroll bar?

Its not visible in Safari on iOS. It is visible in Firefox on desktop.


I think its worth considering but I don’t agree it’s always best to use the language parser.

A language parser should be correct. A LSP parser should be fault tolerant. My understanding is you cant have both.


It absolutely can be done [1] but it is a lot of effort to do high quality error recovery. It's easier in languages with natural "synchronization points" [2], harder in languages which don't have them.

Having built a lot of protobuf tooling, I'd estimate that protobuf largely falls into the former camp; most of your time working with .proto files is operating on fields which terminate using `;` at the end of the line (though multi-line is also possible).

[1] source: I've done it for SQLite SQL at https://github.com/LalitMaganti/syntaqlite/

[2] e.g. SQL naturally has this at statement and expression boundaries which covers almost all of the cases people care about.


Adding to this, rustc's parser is both correct and fault-tolerant, yet rust-analyzer ended up building its own for different reasons (needing a CST and not an AST).


I settled on starting with a CST using rowan, doing semantic analysis, having an agnostic editor services, exposing both an LSP interface with tower, and a WASM interface (for Monaco in the browser [non-LSP!!]) and having the runtime binary doing the interpretation/compilation with the same pathway, with a slight jog, as the editor services. Phew!


Near the end of each month, I get super excited for these blogs. Congrats on another release!


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: