Nintendo used to be ahead of the curve with the N64, but you’re right that they’ve been trailing behind for a while now. The Switch still uses the Nvidia Tegra X1 CPU/GPU, which was released in 2015.

Stringing is unavoidable with bowden extruders. Don’t waste time trying to fix it.

Blender is well received in the industry and can compete with the best. It also has a few nice features that aren’t standard and make it stand out among the competition.

FreeCAD is none of that.

Fusion 360 is amazing in the Getting Shit Done^tm department, which is the weak point of FreeCAD. I have managed to steer through the byzantine UI of FreeCAD to create a CAD model, but it needed support by someone who has spent years in that application to get the more complex stuff, and even he didn’t exactly know how to achieve it, and that’s on top of me having participated in a 16 hour workshop on how to use FreeCAD. For Fusion 360, I’ve watched a few 5 minute videos on their official channel and that’s it, everything else I was able to accomplish through just looking at the UI.

I learned Fusion 360 before FreeCAD, so it’s not just that I had prior experience in another similar tool.

I think the basic problem with FreeCAD is that it’s a collection of tool benches written by different people who don’t talk to each other. They have overlapping responsibilities while still having vastly different feature sets and don’t integrate with each other most of the time. So, if you want to create a model, you first have to plan ahead to understand what kind of features it’s going to have, and based on that, you have to decide which collection of tool benches you have to pick. More than once I picked the wrong one in the start and then had to do everything all over again in the different one once I ran into a dead end.

Fusion 360 feels like it was written by a single team with a single vision, and everything fits together.

The problem with FreeCAD is that the UI is abysmal. There is tons of duplicate functionality in different benches, but if you start in one you might discover that it doesn’t have what you need and have to start over in another.

Sorry, I meant the Underhanded C contest. This is a contest for code that looks benign, but does something completely different.

http://www.underhanded-c.org/

At least any spy shit that we know of. Just look at the obfuscated C contest what’s possible in that abomination of a language.

Think printers, factory machines and so on. If they run Linux and not Windows CE, it’s always an ancient kernel.

When the came for the squares, I didn’t say anything because I’m not square…

Your Zigbee light switches won’t do anything unless the machine running Home Assistant is on. Being able to control your lights while the computer isn’t running is really convenient.

The LIFX bulbs announced your WiFi password to anyone who asked. This is not a breach of the bulb itself, it’s a gateway to your LAN.

In my company’s product, we allow users to place images into a composition and alter the colors (like tinting/colorize in Photoshop, so only globally). When doing that, the outline of the drawn image should not change color, and also there might be multiple color areas (think an image of a house where the walls have a separate color from the chimneys).

To do separate full-image manipulation, we need multiple layers. Right now they’re just a tilemap with the layers next to each other, but that doesn’t work for repeating patterns.

Rust has the turbofish: ::<>

No layer support? Or can that be faked by using 4 channel-chunks?

Futurists are people who cosplay as scientists predicting stuff they have no clue about.

They tried to revoke a perpetual license.

Still, nothing comes close to a native UI experience.

That’s not really well defined on Linux. It feels like every application comes with its own toolkit and its own behavior. Even on Windows, there is a mixture of three different generations of Windows UI systems (Windows XP-style, Windows 8-style, Fluent) that are completely different.

Unity doesn’t give out perpetual licenses any more, it’s a subscription model. If you don’t like it, you can leave at any point in time, but then you also don’t have a license to distribute their engine along with your game.

The problematic part (for Unity) is that they used to have a clause in the contract that said that you could keep using the old license terms as long as you didn’t update the engine. They removed that last year, but developers who are using an older version than that should be able to have a chance at the court. The problem is just that small indie devs don’t have the money for this multi-year legal battle.

On ArchLinux, many Electron apps use a central installation of Electron that is kept up to date by the package manager. That works pretty well.

Of course, snap-based distributions like Ubuntu and other systems without a proper package manager like macOS and Windows can’t do it like that.

The bigger question is, will developers be able to talk to their USB-C equipment without an MFi chip?