Deno has always made more sense than Bun, but all the social media influences jumped on the new thing.

I use Deno over node on new projects purely for the security model, and the fact that their standard library means I don't need a spaghetti nest of dependencies.

Deno shares one minor annoying thing with node. The features of both slowly change over time in such a way that I need to use a specific version of Deno/Node for each project. The node community solved this with NVM. Deno has it build into the cli with deno upgrade v<semver goes here>. The annoying thing is that it downloads a Deno binary every time instead of switching to a cached one. Great if you're online, but if you're on a laptop on the move it's annoying.

But knowing Deno, they'll just build in that runtime caching in a year or so, they already do it for dependencies between projects.

Do you understand how bitmaps and raster drawing works?

Yes I know the difference between vector and bitmaps

Everything is represented as a 2d array of pixels.

Only after the rasterization has taken place.

The circle selection before you paint can be moved/scaled/etc and then when you actually want to draw the circle trace the path with the appropriate thickness and use antialiasing if you need to smooth it.

The problem is that the selection itself can lose information, it's handled internally as a raster mask. That's why you should use a real vector shape.

If you want to make vector drawings, take a look at InkScape. GIMP is the wrong tool for that, so use the right tool for the job if that’s what you want to do.

No. Raster editors can support vector shapes. They vectors are rasterized during the final export, not while creating the shape (which is lossy and what selection shapes are).

Look at how to create, move and transform a circle in photoshop (or if you don’t want to give adobe money, use photopea).

Raster editing programs can support vector shapes. They are rasterised during export, not when the shape is created.

Look at how to create, move and transform a circle in photoshop (or if you don't want to give adobe money, use photopea).

No, that was Fish who made Fez, announced Fez 2, then crashed out after some poor communication on his part and left.

That's not a circle, that's a grid of pixels being colored in. It's a lossy representation of something else.

A circle is a shape which is a graphics primitive. Graphics primitives can be moved, transformed, skewed, etc... with no loss of information.

If you do that with a grid of pixels, you're going to lose information.

Edit: Five downvotes. Apparently people don't know how to use vectors in bitmap authoring software, or why selections are the lossy way to create shapes. See details in my comments below.

That's 41 degrees for everyone who doesn't measure things in bird per gun.

Good.

If you didn't write the code, then you didn't think through every detail.

If you didn't think through every detail, then you have gaps in your understanding.

If you have gaps in your understanding, then why are you submitting code and pushing the burden onto someone else to understand it for you?

What makes you think they'd want to accept that burden?

cURL was one of these for a while (according to my limited understanding)

It was made in the 90s and it didn't get commercial support until a few years ago.

Github has always had being a job site be it's secondary feature.

Except that it has a slightly higher bar of entry to recruiters and recruitment bots spreading toxic positivity, and anyone asking for a job is able to prove (at least some of) their value by showing off their code and how they participate publically in other repos (if at all).

What's with all the complaints here?

New users expect middle click to bring up an auto-scroll widget instead of pasting by default.

You can set up your computer how ever you want.

Want auto-scroll? Set it to auto-scroll.

Want paste? Set it to paste.

The first thing you do on a new system is set up the computer how you want.

No one's taking anything away from you.

I don't see any actual temper lost here.

In one case he points out that someone is making commits that have messed up a file's indentation, and to stop doing that because it's messing things up (they were).

In the other case he points out that rust's default format rules are wrong (in the context of version control readability, they are) and asks someone to fix them.

There's a reason Teams is/was shit.

The first teams was written in AngularJS (which is a slow to run resource hog, but fast to develop) wrapped in Electron. It was kind of a minimum viable product, just to build something quickly to get some feedback and stats on what people needed.

The plan was to build a new native version of teams and build it into the next windows while having an web fallback (built on react) for everyone else.

They stopped working on the original teams and started working on the new versions.

They got half-way through working on the native and react versions when suddenly, covid happened.

They couldn't keep working on the new versions because they wouldn't be ready for a while, so they had to go back and resume development on the old one, introducing patch after patch to quickly get more features in there (like more than 2 webcam streams per call).

Eventually covid subsided and they were able to resume development on the new teams versions.

Windows 11 launched with a native teams version (which has less features but runs super quick), and the new react based teams (which can now be downloaded in a webview2 wrapper) has been in open beta since late last year (if you've seen the "Try the new Teams" toggle, then you've seen this). The React+Webview2 teams will replace the AngularJS+Electron version as the default on July 7th.

What to know about blue supermoons:

1. They literally mean nothing.
2. The change is imperceptible to everyone.
3. Expect useless clickbait slop about it until it passes.

Good.

A programming company which produces nothing, has more lawyers than programmers, and whose entire company runs on signing ridiculous deals with corrupt managers who then leave the blast radius before anyone else finds out how bad the deals are deserves to die.

Hopefully once the company is torn apart into a million pieces and each piece sold off, maybe sensible things start happening again and the Javascript language can finally get the rights to the name Javascript.

It's not rebase vs merge, it's rebase AND merge.

Commit your changes into logical commits as you go.

Then just before submitting a pull request, review your own code. That includes reviewing your own commits too, not just the code diff.

Use rebase to:

• Swap commits so that related changes are together
• Edit your commit messages if you find a mistake or now have a better idea of what to put in your messages
• Drop any useless commits that you just end up reverting later
• Squash any two commits together where the first was the meat of desired change and the second was the one thing that you forgot to add to that commit so you immediately followed it up with another commit for that one missing thing.

Then, and only then, after you have reviewed your own code and used rebase to make the git history easier to read (and thus make it easier to review), then you can submit a pull request.

What do you mean "filesystem"?

That's the data format that you'll find on a USB flash drive, hard drive, ssd, etc...

It has nothing to do with web development, they're completely separate things.

What you're asking makes as much sense as asking: "Which temperature smells best? Words or tired?"

You've gone down the wrong road and we're not sure how you got there.

You'll have better luck if you explain what you're actually wanting.

Serious question for anyone who actually uses Bun:

Why are you using Bun instead of Deno or Node?

If you would have asked me 10 years ago, what were the biggest problems with JS as a whole, I would have stated:

1. Poor type safety

2. No standard library which leads people into dependency hell

3. Poor security (installing a project should not even allow the possibility of key stealing or ransomware)

4. No runtime ergonomic immutable data structures with fast equality checks (looked like it was going to be resolved with the Records and Tuples proposal, but it was withdrawn and discussions are continuing in the composites proposal)

Today I consider point 1 mostly resolved and point 4 a problem for TC39 and engine implementers, and not resolvable by runtimes themselves.

That leaves us with problems 2 and 3.

I see Node having poor solutions for 2 and 3.

I see Bun having poor solutions for 2 and 3.

I see Deno having great solutions for 2 and 3.

As far as I can tell, people have chosen Bun for either hype or speed reasons.

Hype doesn't seem like an important reason to choose Bun since it's always fleeting and there's enough investment in the industry to keep each runtime going for a long time.

I do see speed being a moderate issue with JS, but that's mainly due to:

• dependency install times which should be a one time cost, and which can be reduced anyway by using a standard library

• slow framework slop, which isn't really a runtime issue.

So I'm not sure speed fits as a reason for choosing Bun.

I'm not sure what the other reasons are, but I'm genuinely curious.

If you're using Bun in projects today, why have you chosen bun?

There are only two genders...

Except for: <giant list of genetic, epigenetic, developmental, etc... things that happen with human beings>.

Not to mention all the other things that happen with other living things

It's for the best.

Learning how code works is better than getting an LLM to produce convincing looking code without anyone having an understanding of how it works.

LLMs just teach students to paint themselves into a corner without them even realising why bad things keep happening to them.

All the CEO needed to say after funding that fascist was:

Oops, sorry. I didn't check out that developer's history before funding his project. It won't happen again. I promise going forwards that we'll google people's names first before sending them any money.

They didn't have to make a big deal about it, even a simple quickly forgotten post on their personal social media account would have been enough.

People still ask him about it, and he'll talk about anything else.

But he won't give a simple apology.

His silence is deafening.

Better to just go for the EU version of framework without the fascism: https://novacustom.com/

Edit: Changed "All the CEO had to say" to "All the CEO needed to say" to avoid confusion.