AFAIK, most of valve’s stock is held by employees, not private investors. It’s usually a pretty hard sell of “make the company you work at shittier to make more money”, especially since most of the employees probably know gabe personally (valve has less than 400 employees) and likely approve of his leadership.
FWIW, at this point, that study would be horribly outdated. It was done in 2022, which means it probably took place in early 2022 or 2021. The models used for coding have come a long way since then, the study would essentially have to be redone on current models to see if that’s still the case.
The people’s perceptions have probably not changed, but if the code is actually insecure would need to be reassessed
I guess that would just be a GPU?
Actually would either be a TPU (tensor processing unit) or NPU (neural processing unit). They’re purpose built chips for AI/ML stuff.
People frequently make demakes with pico-8
However, if you ask me to pick one specific project, I get overwhelmed because I don’t know what’s reasonable.
I don’t know enough to know if my ideas are achievable, or if I’d just be bashing my head against the wall. I don’t know if they’re laughably simple tasks, multimillion-dollar propositions, or Goldilocks ideas that would be perfect to learn a coding language.
List out some ideas you’re thinking of. While it may not be obvious to you, someone who is seasoned (me or someone else) might notice at least a general theme or idea to point you in the right direction for where you should go and what you should learn, regardless of if the projects are reasonable.
Note - Most projects take teams to realize, so if your ideas are too large, they might not generally be feasible alone.
What are you looking to actually do with your programming skills? That will heavily influence which languages to recommend you learn. Do you want to make websites? build games? do AI stuff? Create enterprise-level software? something else?
Earthbound is eternally on my list of games i play through every couple of years. Its such a great game. Some aspects of it are a tad clunky by modern sensibilities (inventory management, going through the menus for a lot of things, etc.), but overall it holds up really well. Also if you liked earthbound, mother 3 is also 100% worth playing. Mother 1 (or beginnings, or whatever you wanna call it), is hard to recommend to anyone but the most diehard fans, though.
I like earthbound the most of all of em, but thats purely for nostalgia reasons. From a critical perspective, i think mother 3 is the superior game.
thats because they legally cant include the cores in the steam version. You’re able to go add any additional cores you want, however.
As of java 21, you can actually just use:
void main()
isnt that basically what government contracts are? subscriptions?
most will just slow the rate your deck discharges (if you’re using it), you need a high output charger to actually charge it. Anker makes a few that will, i personally have the 737 and think its worth every single penny with the steam deck.
to my understanding, C# is sort of a “second class citizen” on godot; There’s a lot of stuff you can’t quite do or is more clunky than using GDScript. But i also havent used godot enough to really weigh in on that (only a couple of small projects).
That said, while GDScript is very “python-like”, it is definitely not python. If you want to focus on C#, i would definitely echo the unity sentiment over godot.
All in all, the best way to learn is to just do it. Go out on youtube and find some tutorials, and just hunker down and try!
yeah, its hard to predict what will happen to it, especially after gabe steps down or dies, but depending on how much of the company is broadly owned by employees vs individuals, it can help to shield it from bad decisions. Unfortunately, we don’t know the exact numbers. If gabe + mike own 51+% then it could potentially lead to overriding employee will in a bad decision for money (either through their actions or through inheritance like you say). Or the employees could just collectively make a bad decision too.