Ekky

As a scandi Iv’e been leaning more into ‘enginks’ - close to ‘engangs’ and french kinks.

deleted by creator

Hadn’t actually noticed it was Mac first before you mentioned it, but no, if it works for Mac, then it likely also works for Linux (and that’s what counts, right?).

Contrary to my previous statement, I’ve actually tried downloading Zed. The first thing I noticed was the “sign in” in the top right corner. Feels rather unsightly, but no biggie. It appears to redirect to GitHub authorization, after which it fails with a “OAuthCallback”-error. Might be my fault, can’t remember if I’ve disabled or limited unnecessary functionality in GitHub.

The design feels slick and most options are hidden away or represented by only a small icon with tooltips. It appears that no advanced settings page exists, as nearly everything is handled in JSON (initially thought that a visual settings page must have been hidden away deep down somewhere, but that appears to be wrong).

Coop programming seems to be a big feature, but I’ll skip that as it appears to need setup.

Also, the LLM part is not nearly as prominent as their front page makes it out to be, rather feels like an option than a prominent or forced feature, so that’s really nice.

The included extensions (nice to have them as they’re no given) appear to focus on themes and syntax, can’t find any cross-development nor compilation related extensions which is just fine. Compilation is best handled in the terminal anyway.

Overall it feels pretty solid, definitely different from the first impressions of their page. Might be even better with more diverse extensions, though, I haven’t looked at the internet for unlisted extensions, and I’m not sure how old the project is (the extensions might just not be made yet).

There’s also no pop-ups, start pages with all kinds of featured content, nor settings or buttons that grab your attention away from your work (except the login button, perhaps. I would like to see what it looks like once logged in).

I’m probably missing most features as my GitHub integration fails, but I’m overall positively surprised.

Hmmm, the front page looks like they’re trying to sell a LLM code generator with additional QOL to businesses, and not a developer focused IDE or extensible text editor.

Definitely not something that catches my interest as a developer. Though, I haven’t tried it, so these are just initial impressions from reading their landing page.

Edit: also, why down vote the above? It appears perfectly relevant to the discussion. If you disagree, why not make a comment about it instead?

There has to be a law against such heretical actions somewhere! Even if it’s .00, this computer is an affront to order! I propose we burn it alongside those frivolous computers who think they can simply name themselves .0 or .255!

Huh, I’m not sure they are comparable.

Didn’t USB A and USB B use a master-slave relationship in which the male would (generally) always be the slave, whereas USB C uses agreement and discussion to decide the master and slave roles regardless of connector gender.

Please do correct me if I’m wrong. Also, do we say “agent” now instead of “slave”, or what is the new term?

I’m pretty sure it’s more like

Junior dev: Got all the nice addons, RGB lighting, only uses dark theme, got all the stickers, works from either a café or moms basement.

VS Senior dev: Works on company standard issue hardware, barely customizes visuals (but got a script which makes a cup of coffee on the shared machine in exactly 2 minutes and 30 seconds), works in shared office, has old rolling cabinet with unknown artifacts last touched 10+ years ago.

Obviously this is an overgeneralization and not a catch-all, you might even say that it’s “programmer humor”.

Stacked on top, and vertical orientation since we’re not doing Java here!

Lol, it is indeed one of the cleaner versions that I remember having seen, nice work! ^, ^

But Admiral Patrick, how dare your ancient memes from times long forgotten not meet our modern expectations? Do you at least have a proper shitposting license?

I’ll post mine as reference, may you gaze upon it and ponder the shortcomings of your horrible artifact-ridden memes!

AI: “Can I copy your work?”

Phil: “Just don’t make it obvious.”

AI:

“Fixed issue with ssl python libs,” or “Minor bugfixes.”

In other news, never work more than one person on a branch (that’s why we have them). Make a new related issue with its own branch and rebase whenever necessary, and don’t even think about touching main or dev with anything but a properly reviewed and approved PR (in case they aren’t already protected), or I’ll find and report you to the same authority that handles all the failed sudo requests!

Also, companies that disable rebasing are my bane. While you can absolutely do without, i much prefer to have less conflicts, cleaner branches and commits, easier method to pull in new changes from dev, overall better times for the reviewer, and the list goes on. Though, the intern rewriting multiple branches’ history which they have no business pushing to is also rather annoying.

You are correct! It sets HEAD to the first commit and then force pushes, deleting everything after HEAD.

Though, it only affects the currently selected branch.

like this?

# Let Git take a rest with some yummy awk chocolate logs with delicious nuts and seeds, and don't be pushy!
git reset --hard $(git log --reverse | sed -n 1p | awk -F "[ ]" '{print $2}') && git push -f

EDIT: Don’t actually run it.

Or make a shortcut/link in the readme to the newest release of the most popular OS’s.

A decent release page tends to contain all kinds of files for different OS, so ‘regular’ people who just want the .deb or .exe would likely become confused regardless.

For those wondering how to exceed the 70 (80) recommended character limit and still follow best practices:

1. Write the title on the first line, keep below 70 characters.
2. Make two (2) newlines
3. Write one or more descriptive paragraphs.

The first line will be shown as commit message, and the full text can usually be viewed by checking out the commit. Sentences can span multiple lines, but try to keep the line length below 70 characters for best readability.

This off the top of my head, so feel free to correct me if I’ve misremembered the best practices.