If that’s a joke, it’s a good one. Otherwise, well, there are a lot of “this letter isn’t needed let’s throw it away,” in most cases it will not work as good as you think.

This quote from Linus is what I find inspiring hope of a future wider adoption or Rust:

Thanks. I decided to try to do the merge on my own, but failed. I came close, but it was good to have your example merge to see what I got wrong.

The pin_init becoming a crate of its own, but ‘pin::Pin’ being in the core crate ended up messing with my “monkey see, monkey do” approach to Rust merges.

I’ll learn eventually, in the meantime please do continue to give me example merges and I’ll use them as training wheels.

Not everything that’s poorly written is ai, you should give humans more credit

We have an engineering manager that’s about the same, the only issue is that they let PR through because features are wanted and there’s no time to get things right.

I think, I may be pleased to have to redo everything several times to make it better and simpler, but what we get is that everything is bad but we’ll still merge 😞

I now feel at several times I fucked up quite a lot by making something that works but not something simpler.

My girlfriend is gonna be mighty upset is she thinks I’m into that kinda thing. […] please change the image to something Gnome-related and/or trustworthy.

That’s an interesting takeaway from a DDoS issue

It’s a step in between

It then takes it a step further, as they are both 0 in that regard

I’d say that trying to get Rust everywhere is just something that is done in the hope it will help the ecosystem mature faster. It’s a bit hard to compete with languages that are 30, 40, or over 50 years old

TBF, your previous post reads to me the opposite way, like ‘it is not enough of a hate site’. Also I would offer you to look at it as a Venn diagram, if something is a hate site and more, it is still a hate site, just with extra

Yeah, that sounds like a crappy way to promote the product

What’s the use for those in corporate env, that’s not available outside of it?

Far, but being a programmer is usually not about using assembly anymore

Edit: to elaborate a bit, TIS-100 has an overcomplicated architecture but oversimplified command set, and restricts the coder way more than the real assembly (e.g. you have a limit on line length of 12 chars or somewhat close, and that includes the opcode itself). Imo these design decisions allow it to be interesting and simple enough to comprehend, but severely limits what can be implemented on that architecture in reality without requiring for lots of boilerplate

Let’s take a look

Makes sense. But then we’re getting the standard that tries to define everything

The alternative would be

More reasonable, if you ask me. At least I came to value modularity in programming, maybe with standards it doesn’t work as good, but I don’t see why

One can be pro- or anti- any concept or thing, some options just make more sense

Oh, but that’s but a ten year long accident, nothing deliberate /s

This may have been sole reason to do that, so of course he did

They started replacing the default screenshot tool with snipping tool, but maybe it’s not the default to call it with PrtScr

Saving from source was in context of saving from Instagram, I find screenshooting Web pages less fitting than getting into the source of the page, albeit the former is simpler

This reads as if it was an advertisement, colour me suspicious. And that’s even though I use JetBrains IDE myself