Trying desperately to keep the ponzi scheme going, but his biggest customers already have warehouses full of GPUs that will never get connected.
The bubble is full, dude. Just try to minimize the damage from the pop so we don’t try to figure out what size pitchfork your dumb leather jacket is.
It also discouraged you from finding/starting an open source solution for those problems, thus undermining the high-quality open knowledge ecosystem that it relied on in the first place.
As Cory Doctorow says: code is a liability, not an asset
Keychron is solid, and offers a wide range of sizes so you can balance real estate vs functionality
I was once a fool like you :)
Mike McShaffry’s book “Game Coding Complete” is a good guide to the practical side of using a game engine IRL to get things done.
It’ll give you a good idea of how things should be shaped in order to be useful, and some things you can “skip ahead” to. Off-the-shelf engines have to be extremely general in order to be flexible enough to be useful to many customers, so game devs have to put in the effort to make them more specific. You’ll have to start off by being specific, if you have any chance of actually finishing something.
Eberly’s book “3D Game Engine Architecture” deals with the nuts and bolts, the rigorous academic engineering stuff. It’s pretty solid, but it’s aimed at making a general-purpose engine, which is beyond the scope of a one-person project.
Backing up though… You don’t have any language or library opinions? You might need 5-10 years of experience doing general programming (or game dev) before you can sustainably tackle this, or else you’re likely to paint yourself into a corner.
Edit: Probably the biggest PITA with game engine dev is testing. If you’re not already an expert in setting up test harnesses at multiple levels of detail, you’re gonna find it impossible to keep moving after a few months.
Good luck!
I can tell you that when I use GameHub Lite on my Retroid 5, the stats widget sometimes shows Zink, along with DXVK, DXVK+, and VKD3D
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.
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.
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.
Nix, but I’d only recommend it if you share my same brand of mental illness
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:
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.
They’ve been telegraphing this for a while — long before the RAM crisis
Why would you expect that?
I’m down, but RISC-V has a looooot of ground to make up first. Last I checked, total number of RISC-V devices in existence was an order of magnitude less than what Qualcomm produces in a year.
Not sure about Apple-mediated payments, but you can usually support the creator more directly and get an ad-free RSS feed that you can plug into the Podcasts app and it Just Works™. Usually ends up being a better deal for the creator, too.