After 16 years of work, mostly as a freelance developer for multiple companies, I have a burnout. Fortunately, it's not an "I don't want to work anymore" - last week I had the first day that I just didn't want to work. But it never happened before. So it's like 7/10 on burnoutmetter.

But what is the hardest thing for me is that I'm not able to mobilize myself to work on my projects. I have two good ideas. It's possible that I would be able to monetize these ideas. But I'm not able to move forward. Over the years I tried to work on more than 10 own projects and none of these projects were successful. Should I start work on the 11'th and fail again? I burned out on failings ;)

"a Rust CLI" - "C 96.5% Rust 1.4%"

Not that I'm complaining ;)

Is it a new way to market a C tool?

The C is all generated parsers, all our actual coding is done in Rust.

this audience will also enjoy(?) the tree-sitter discussion going on here: https://news.ycombinator.com/item?id=39762495

there are very similar complaints about "yikes that thing just vomits a massive amount of loosey goosey C" so I hope you've not experienced the crashes they're talking about

The generator is written in Rust, so all emitted C code is safe and blazingly fast (rocket emoji)

I think you missed an /s

Such fameous hacker like Zalewski should better distinguish language and library interfaces design issues.

Yeah, this is just trolling. There's nothing inherent to rust that requires ( or even recommends) writing code like this. There's nothing inherent to C that prevents bad API designs like this.

Nothing about this post is notable or interesting. It's low-effort rage bait.

"There's nothing inherent to C that prevents bad API designs like this."

I don't have any data to back this and library interface designs are so personal taste-prone, but I would say that the average Rust crate has a better API than the average C library.

Say that to corporate java writers. Language creates culture and this applies to human as much as computer.

The JavaEE APIs essentially set the example for everybody to then imitate. Of course it didn’t help that design patterns were in peak fashion. The Java core language is small, and most of the SE APIs aren’t particularly byzanthine. But EE then went all in for some reason.

So my instinct to avoid Java at all costs wasn't irrational dysphoria after all!

This was my first thought as well. Rust certainly lends itself to unnecessarily complicated API designs, but so does C: OpenSSL requires something like 5-6 layers of indirection to do basic things like converting a sequence of X.509 structures into a buffer of PEMs.

I've yet to discover a language that doesn't allow a sufficiently clever engineer paint themselves into a corner with API complexity. Even deliberately simple languages like Python suffer from this.

That's a lot of releases for a dead software. I had 5 bug fixes releases for a software that is in pre beta release stage ;)

I asked Thorsten about Windows support today, he said "Zed, you mean? After Linux, I'd say.". So there is some plan :)

> So there is some plan :)

How does that follow from the rest of your comment?

Logically it doesn’t, but in actual good-faith communication people usually follow Grice’s relevance maxim[1]: the points they mention are relevant to the conversation and the point they’re making. Thus, if neither Linux nor Windows support are planned, and the question is about Windows support, saying that Windows will come after Linux would be (vacuously) true, but the mention of Linux would be irrelevant.

(Notably, communication coming out or through legal counsel cannot be assumed to be good-faith, the premise of the court system being that the best we can achieve is two bad-faith adversaries and a neutral arbiter. But that’s not what we are dealing with here.)

Pedantry aside, I think I remember one of the developers saying they do plan on Linux support at some point in one of the previous Zed threads here. There were also some “small team” and “laser-focused” and “best possible experience” in that comment, but they did say outright they were planning on it. Though plans change, I think that’s the best we could hope for at this point, as I doubt even they themselves know more about their future.

[1] https://en.wikipedia.org/wiki/Cooperative_principle

Hey! I'm the mentioned Thorsten. Linux is actively being developed. Here's a PR from 2 days ago that shows file-opening in Linux starting to work: https://github.com/zed-industries/zed/pull/7852

And so far Linux support has been a big community effort. I think more community member contributed to Linux support than Zed teammates. Very cool to see.

So: Linux is in the works. Windows will probably happen after that, or if someone in the community wants to emulate what the Linux users are doing and start before that.

Windows support is happening locally on individuals machines. We’ll start upstreaming things up.

Where can we track this work so as to not duplicate it?

I’m trying to get to a point of convergence with 3 different contributors hacking on it right now, and make it a PR. There is also a new “windows-port” channel on Discord. Finally, we are waiting for Zed team to confirm if they are interested to have Windows port in tree at this point.

As a side note, Linux is going pretty strong!

What a beautiful comment. We should make it the MOTD for perpetuity.

Rust could help with some vulnerabilities that are not related to memory safety too. It's type system can help you preventing vulnerabilities that are caused by logic mistakes.