Or the original upload: https://youtube.com/watch?v=39jsstmmUUs

Not to be confused with SOLID, SolidJS, or Solidity.

It’s a neat idea. Because of the need to operate on data close to web servers and backend services for potentially long timeframes, I think we’ll need a widely-adopted CRDT solution in order for something like Solid to really take off from a technical standpoint.

And from a business standpoint, there’s really no upside. Sure, you delegate some cost for storage, but compute tends to be the more expensive aspect, and if you’re spending more time to interact with these external data stores, it may be more expensive in the end.

“Issues are for work items only. Communications go in discussions.”

posts this communication as an issue

Seriously though, this approach makes sense to me and I wish more projects did it.

I’m gonna need to see that math

Conceptual analysis of proximity isn’t exactly what I expected to see when I joined Lemmy

But it’s… 😎 close

Gamehub Lite is pretty wild. It does take some fiddling, but it’s amazing how well (and relatively easily) you can get x86 Windows games to run on a $200 ARM Android device.

I’m 12/13 so far on getting games to work at an acceptable level.

Inexplicably, Vampire Survivors causes the entire device to crash. I guess they pull some pretty silly memory tricks to keep that game responsive with potentially hundreds of thousands of projectiles, so maybe it’s not so surprising.

Security guard is one. Had a friend in college that basically got paid 8hrs/night to do 2hrs of actual work and 6hrs of building his portfolio. It can definitely work well for some folks.

Got Megabonk working on my Retroid, and can’t stop playing it. I thought I would try getting some other games going, but I just play Megabonk instead.

Opus Magnum

That game scratches my brain in such a satisfying way

Fuck AI

Sure, but do you need a discrete video card if you’re gaming on an ARM SoC? And we’ve seen from the struggles of x86 iGPUs that graphics APIs pretty much have to choose whether they’re going to optimize for dedicated VRAM or shared memory, cuz it has inescapable implications for how you structure a game engine. ARM APIs will probably continue optimizing for shared memory, so PCI-E GPUs will always be second-class citizens.

Nvidia does not care about the ISA of the CPU at all.

That’s kinda my point. They’re stuck communicating over PCI-E instead of being a first-class co-processor over AMBA.

Fex

1. Nvidia abandons x86 desktop gamers
2. The only hardware that gamers own are ARM handhelds
3. Some gamers stream x86 games, but devs start selling ARM builds since the x86 market is shrinking
4. AI bubble pops
5. Nvidia tries to regain x86 desktop gamers
6. Gamers are almost entirely on ARM
7. Nvidia pulls an IBM and vanishes quietly into enterprise services and not much else

Mostly agree.

But I think their advice falls prey to the “only a Sith deals in absolutes” problem, when they start contrasting “concrete advice” vs “generic advice”. They are offering “generic advice” with this post, aren’t they?

They hedge against that hypocrisy by offering some special carve-outs where generic advice is still “allowable”, but Idk. I think this post could’ve stuck to the 60% of the topic that was a slam-dunk instead of trying to take on the entire topic of design principles.

After all, I think you could argue that when experienced designers appear to contradict design principles, it’s because they understand the underlying logic of the principles and are recontextualizing them for this specific problem. That argument prioritizes concreteness but also doesn’t paint design principles as unimportant.

As Picasso or someone once said: first you must learn the rules, and then you must break them.

Make computers do stuff for what purpose?

I joke to my family that I just name things for a living. When you take away all the incidental stuff like files and pointers and ports, that’s really all it is. “This sequence of events with these properties is called <this>, and when you ask our system what to do about it, it does this other sequence of events with these properties which we call <this other name>.”

It’s kinda like those ancient stone tablets that are the first example of writing, and they’re just like “Ramses owes Jeremiah 5 chickens” or whatever. It’s just how we manage abstract concepts moving around our civilization. Yeah there’s math involved, but every endpoint is a human being in one way or another.

Yeah…

Human mistakes tend to 1) look like mistakes, and 2) are surrounded by lots of hints that the author had trouble with that section of code.

AI mistakes tend to 1) look like regular code, and 2) look just as confident and effort-ful as the rest of the code.

Tech bosses have well and truly lost it.

Consider that:

• Code is primarily to communicate from human-to-human, and only incidentally for computers to execute
• A codebase that is 30+ years old has an absolute shitload of learnings incorporated into it, much of it very subtle
• Languages are, in fact, different. So some things cannot be directly translated with exactly the same semantics, so devs will need to fully understand the intent and resolve ambiguities
• A million lines per month is a lot of text for someone to successfully interpret and translate without losing any subtleties

Why?

The language itself is… fine. It has some bad decisions baked into it, but what language doesn’t? And it has a pretty mature security model, which is a big help for embedded devices.

And given that so many embedded devices these days are talking to cloud services — that are probably running JS, but are at least communicating via JSON — being able to share some cross-platform code or tooling can help things go quicker and/or safer.

Edit: This is probably not a route for teams that are chronically tight on memory and choose to solve that by spending hundreds of dev-hours on optimizing code rather than adding BOM cost. But for teams that could stand to increase BOM cost as long as the savings on dev-hours make up for it… it could be an option.

Why would you expect that?