• 1 Post
  • 30 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle




  • From their FAQ:

    ##What platforms does Zed support?

    As of now, we only support macOS.

    We are a small team, so it’s critical for us to be laser-focused. As a startup, one of our key priorities at this early phase is learning, and right now, we’re focused on the following questions:

    • What are the key features we need to get traction on any platform?
    • Are our assumptions about our eventual business model valid?

    While we’d love to support users on Linux and Windows, adding those platforms doesn’t really help us answer those questions. We’re investing a lot to make Zed portable, but adding other platforms comes with opportunity cost in the short-term and maintenance overhead going forward. Right now those costs don’t make sense for us.

    As Zed matures on a single platform, this cost/benefit ratio will shift, and it will make sense to expand to other platforms. We hope you’ll give it a try when that happens.

    As a general timeframe, you can expect us to begin work on supporting these platforms after Zed is open source, but before version 1.0. Any news will be posted to our platform-tracking issues.

    Linux support is listed on their roadmap.




  • SatyrSack@lemmy.onetoProgrammer Humor@lemmy.mlPackage managers be like
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    edit-2
    1 year ago

    As I understand, when you update npm packages, if a package/version is specified in package-lock.json, it will not get updated past that version. But running those pip commands you mentioned is only going to affect what version gets installed initially. From what I can tell, nothing about those commands is stopping pip from eventually updating a package past what you had specified in the requirements.txt that you installed from.




  • Basically it goes a little like this… I bounce out a song as a WAV, and then convert it to a 320 MP3 using iTunes. iTunes compresses very well (imo), and so if you compare that WAV with that 320, they will sound practically identical. I then take that 320 and Convert it to 128 in iTunes. The sound is STILL practically identical. (Because it is a good 128.) There may be a little rolloff around 8-10k (super high end) but it’s more of a “sound change” than a “degradation”. This conception that 128’s are drastically inferior to 320’s mostly comes from 1. people reading bullshit on the internet, & 2. people downloading BAD 128’s!!! Seriously. Not every WAV is equal, not every 320 is equal. I could take something at 92 KBPS and rebounce it as a WAV. does that make it a lossless audio file? Fuck no. Who knows how many times it’ been downconverted/upconverted etc. Just because you downloaded a rip on /xtrill and its a 128 and it sounds bad doesn’t mean 128’s sound bad. Just because the apple I bought was rotten doesn’t mean all apples taste awful. Basically if I listen to a song and it sounds good, I will play it. People knock me for playing 128’s and I’m just like… If I can’t tell the difference, then neither can you. And the bit about playing it on big systems and it sounding like shit is also a load of crap. TL;DR: If it sounds good on good headphones, play it. (That said, anything below 128 and you will notice audio quality deteriorate VERY quickly.)