It wasn’t even just that. In the companies I worked, it seemed like nobody other than me understood how to escape things for XML. I couldn’t even convince them to just use the right libraries/functions that auto-escape and parse things properly. They keep deciding they were smart enough to do it by hand. And it always ended up biting them.

JSON, like Javascript (vs C++ or Java) is a lot more forgiving. It either works or it doesn’t, and the values are just strings or numbers. And some people even do the numbers as strings.

All of the exploits against Intel processors didn’t help either. Not only is it a bad look, but the fixes reduced the speed of the those processors, making them quite a bit worse deal for the money after all.

It doesn’t have to be a “brand new AAA game”. It can be a somewhat-recent AAA game on sale. Some of the discounts in the first year are ridiculous.

And I’ve been surprised at how many games in the past few years were more than my 3070 could handle on high settings, let alone “ultra”.

I was playing Destiny 2 and the lag was only noticeable to me when I compared it to not using Stadia. While I was playing, I didn’t feel like there was anything to complain about.

I think I saw less lag when connected to my house over Parsec, and definitely had less lag when playing locally at my house. I actually considered continuing to use Stadia, but by that point they had pretty much proven that they were not going to bother improving things further, and it didn’t make sense to pay for a service that didn’t provide an advantage over what I could do for free.

I think it really depends on circumstances. I tried GFN and Stadia, and found them to be adequate, and used Stadia for a few months. After comparing input latency with streaming from myself (across town) and playing locally, I decided it wasn’t worth it and left Stadia. I’m still mad at their ridiculous promises that they broke, and killing the service without ever really trying to hit its potential.

IIRC, there’s still a free tier with a limit of 1 hour playtime at a time, and you can’t play during peak hours because there won’t be a slot for you.

The pay tier is still a 6 hour limit, but of course you can just come right back in.

I don’t think the article means dogfooding. I think they mean that you can’t design a system unless you’re intimately involved with coding it.

And of course that’s still wrong. It happens all the time. And things end up working out the majority of the time.

Yes, you’re effectively renting a powerful computer.

Previously, you could just use it without limits, and the math worked out for everyone. It’s something like 3-6 years of service to cover the cost of a decent-to-great computer.

Now, if you’re a hardcore gamer and go over 100 hours a month, that value changes, and the break-even point is sooner. If you play for 40 hours a week, that time is effectively halved.

At the current rates, it continues to seem like a really good value, so long as you aren’t bothered by the slight input lag or the video compression.

But if more people use the service for more time, they’re going to have to charge more money. Either higher base rates, or lower limits. And it’s eventually going to show that it doesn’t really make sense for anyone except as a temporary measure, and then the service will disappear because it didn’t work well enough.

That’s the problem with edgy, experimental projects. You can’t really tell if they’ll succeed until a lot of work has been put into them.

Most of the people I hear being critical of AI Coding are very clear about what it’s good for, and what it isn’t.

If someone is wholly for or against something, their advice generally isn’t very good.+

It sounds like Microsoft is being notified by its Minecraft players that toxic interactions are happening on MinecraftOnline’s server, and they’re taking action to reduce toxicity associated with their IP.

It’s really hard for me to fault them for that. Especially since MinecraftOnline is using the the Minecraft trademark in a way that sounds official in the name. I’m surprised they didn’t put a stop to that as it is.

I don’t see anything that says they don’t understand Git or Github.

They know people will look for them on Github, and they do their official releases there. They host their code on the non-profit Codeberg site for reasons of their own. People can still fork from there. They just can’t click a button on Github to do it. They can, however, click a button on Codeberg to fork.

It sounds to me like they did understand all of this, and decided to let internet popularity work for them (host releases on Github for discoverability and fraud prevention) without giving up how they wanted to manage their code.

While I’ll admit that “wolves” instead of “elves” seems to make more sense, I think that assuming there were 2 typos in a single sentence, both of them going from mundane to fantasy, is just too hard to believe without actual evidence instead of just someone’s whim.

And it killed all interest I had in Vite as well. This kind of thing practically guarantees that they’ll spend their effort on the for-profit stuff and gut the open source project of things it would otherwise have had built in.

Sure, maybe not today, but eventually some bean counter is going to look at it and demand it.

We could always “stop having pointless arguments about it”.

Some people enjoy normal, and some people enjoy inverted. Most people have a strong preference.

There needs to be an option for it in the controls. End of story.

And yes, I read the article. It just says that people have preferences. It does some weird hand-wavey “science” to say that it’s in their brain (of course it is) and not something they learned. Well, either way, it’s in their brain now. This “science” says nothing about where they learned the preference, or if it was innate. It’s a pointless article.

I don’t know yet, but I’ll have to see if I can find people who will describe it fully before I upgrade my firmware. I’m definitely not looking forward to that.

Snapmaker U1 kickstarter is on right now. Watch some videos on how the preview units went and then consider that.

Or the Elegoo Centauri Carbon is getting a ton of recommendations. No multi-color addon yet, but it should be released soon. We have no idea if it’ll work well or not, though.

I still love my A1 and A1 Mini and use them a lot. Like you, I’ve frozen them in time. And I use Orca with them. But I’m not actually afraid to upgrade. I think the “dev mode” will probably be fine, and I actually expect to have to update eventually anyhow. I think Orca will probably eventually update to only use the “dev mode” interface and not work with older firmwares. I can’t see them maintaining 2 different ways to connect to a proprietary printer.

I don’t think anyone puts this much work into something to make it “deliberately bad”.

But when I first saw it, I couldn’t believe it was actually a thing. The mix of things you do in this don’t make sense to me. In what world would I think being a “toll booth operator” involve selling dodgy drinks to people?

The grooves?

The pattern on the left is actually just inside the case, under a clear part of the case. That part is black in the Euro version, but the case looks the same otherwise. (We have cases like that, too.)

Edit: Also, that Japanese one? I’m pretty sure it’s the same style, but turned upside down. That’s the base of the case. Searching Google, I found a copy on Ebay that shows the front, and that section of the front of the case is clear for that one, too.

That sounds like pretty much exactly what we did at my last job, and it worked pretty well IMO. The individual commits in a PR didn’t ever matter. I don’t even think we used them for code review, except if it came up for review a second time after rework. In that case, we were able to just look at the new commit to see if the right changes were made.

And we definitely avoided basing off each other’s branches. We had to do it a few times. The only times it went well was when the intent was to merge the child branch into the feature branch. If they were actually separate tickets (and the second relied on the first) it was generally chaotic. But sometimes, it was just necessary.