Altman secretly secured 40 % of the world’s DRAM manufacturing capacity last month. Supposedly Samsung and HK Hynix weren’t aware they were both signing up for it.
That alone would be enough to call collusion if it wasn’t an obvious play to strangle his competition by literally choking them out of hardware.
https://www.mooreslawisdead.com/post/sam-altman-s-dirty-dram-deal
I read people complained that ME1’s character creator was ass. I guess it must have gotten that reputation by being kind of ass for making a dude, because my Shep was a badass bitch. Voice actress was on top of things too. She’s by far the most memorable custom character I played.
Until ME3 where they yassified her from a 40-something war veteran to a glossy-skinned 25 year old lifestyle vlogger. Interestingly that made me - a cis man - feel viscerally connected to the injunction to look a certain way for the male gaze, and I got so fucking mad at bioware during that intro cinematic.
I agree with all you said but it’s still a (bad) abstraction.
By and large, the original market for VBScript or Cobol were people who did not have the means to understand - nevermind debug - their own output. Then actual professionals were hired to fix their broken pile of shit.
Vibe coding is arguably worse in many areas (such as determinism), but I’d argue it’s a difference of degree not nature. The idea and target audience are largely the same, and the results will be as well, which is why I am not worried for my job security, quite the contrary.
you’re at risk of becoming dependent, and not building the understanding you’ll need to make something that matters
Could be – and has been – said about literally any abstraction. Some people still haven’t gotten over the fact that assembly is not the default system programming language anymore.
For me vibe coding is more akin to vbscript or MS Access. It’s for people who neither know nor care about the “how” and don’t give a shit about quality, performance, security, or maintainability (i.e. people who have no interest in software development). It’s a market that’s looked down upon for many good reasons, but it does exist and it does serve a purpose for small-scale and low-stakes DIY automation. Unfortunately that purpose is a lot narrower than the marketing pitch, nevermind all the other deleterious problems with the AI industry as it exists today.
So happy to see the game is not dead.
Combat and movement look fun and satisfying, graphics look amazing. So many moody areas, from gritty snowscape to colorful caves. Mojang could learn a thing or five from this trailer.
I do hope there will be more breadth of gameplay especially on the creative side so those promising exploration mechanics do not feel stale after a few hours of running around and blasting skeletons. That’s one thing mojang does get right, if anything they have too much breadth and not enough depth.
Not sure about the ease of movement when scaling multiple blocks. Figuring it how to get from point A to point B with the limited movement options is a core part of most Minecraft gameplay loops, especially when caving and/or fighting. Seems they made up for it with good fighting mechanics, but they will have to make up for it in the other gameplay loops as well.
Either way I wish them the best and hope they light a fucking fire underneath mojang’s ass.
EDIT:
This is the original legacy engine from the 2018 trailer, running on a four-year-old build as we push Hytale forward again.
Now hold the fuck up. What do you mean this is the 2018 engine? What the fuck have they been doing the past 7 years? Did they rewrite a whole new engine for no good reason? It looks fucking beautiful and seems to run great! I’m sure they had their reasons, and I don’t think we can draw accurate conclusions by speculating, but the insider perspective on the development cycle must be absolutely wild.
EDIT2: Okay their blog post explains quite a bit more. Seems to paint a picture that Riot wanted the engine to be cross-platform (makes sense for consoles) and they could not make it work with a full rewrite away from their otherwise functional Java/C# engine. Kind of a crazy play on Riot’s part to make Java/C# devs and former minecraft modders write a modern game engine from scratch in C++ if that’s the case. Probably a tough lesson to learn for everyone involved. If only they could learn from an incredibly popular voxel-based building/aventure game that went through the exact same engine rewrite away from a GC VM language and faced similar struggles.
As a PC player, great news that they’re sticking to .NET and Java. It will make modding much easier.
I don’t think that’s really fair. There are cranky contradictarians everywhere, but in my experience that feature has been well received even in the AI-skeptic tech circles that are well educated on the matter.
Besides, the technical “concerns” are only the tip of the iceberg. The reality is that people complaining about AI often fall back to those concerns because they can’t articulate how most AI fucking sucks to use. It’s an eldtritch version of clippy. It’s inhuman and creepy in an uncanny valley kind of way, half the time it doesn’t even fucking work right and even if it does it’s less efficient than having a competent person (usually me) do the work.
Auto translation or live transcription tools are narrowly-focused tools that just work, don’t get in the way, and don’t try to get me to talk to them like they are a person. Who cares whether it’s an LLM. What matters is that it’s a completely different vibe. It’s useful, out of my way when I don’t need it, and isn’t pretending to have a first name. That’s what I want from my computer. And I haven’t seen significant backlash to that sentiment even in very left-wing tech circles.
Honestly, PCs are not ready for local LLMs
The auto-translation LLM runs locally and works fine. Not quite as good as deepl but perfectly competent. That’s the one “AI” feature which is largely uncontroversial because it’s actually useful, unobtrusive, and privacy-enhancing.
Local LLMs (and related transformer-based models) can work, they just need a narrow focus. Unfortunately they’re not getting much love because cloud chatbots can generate a lot of incoherent bullshit really quickly and that’s a party trick that’s got all the CEOs creaming their pants at the ungrounded fantasy of being just another trillion dollars away from AGI.
Game preservation. The fact that Sony is scrambling to DMCA videos of this preservation effort is proof that it is not just a forgettable turd, it’s a historical landmark.
Much like ET for the Atari 2600, Concord is and will remain a case study for the downfall of the big game studios in the 2020s.
For systems programming it makes the most sense out of the languages you mentioned. Languages requiring a runtime (Java/Python) do not fill the bill for system tools IMO. Golang is more arguable, but its memory safety comes through GC which many systems programmers aren’t fans of for a variety of technical and personal reasons.
Rust is meant to be what C++ would be if it were designed today by opiniated system developers and didn’t have to be backwards-compatible.
Those are the technical arguments I would use in a corporate setting.
All that aside, there’s personal preference, and my point is that for FOSS projects that matters too. Rust is fun in a brain-teasy kind of way in the same way that writing C is fun, but without nearly as many footguns. Golang is practical but arguably not as fun. That’s the same logic that draws many programmers to write Haskell projects.
The story of the Fish shell illustrates it quite well; the project gained a lot of development attention and contributions when they decided to rewrite from C++ to Rust, where they achieved a stable release with feature-parity a few months ago. It would have been a remarkably dumb decision for a private company to make, but makes perfect sense when you are trying to attract free talent.
The counterpoint is that, especially with FOSS that does not receive much (if any) corporate backing, developer retention and interest is an important factor.
If I’m donating some of my free time to a FOSS project I’d rather not slug through awful build systems, arcane mailing lists, and memory unsafe languages which may or may not use halfway decent - often homebrew - manual memory management patterns. If the project is written in Rust, it’s a pretty clear indicator that the code will be easily readable, compilable, and safer to modify.
if its controlling expression is not a constant expression
Pretty big caveat. If I’m reading this right true definitely qualifies as a constant expression and the loop in the meme would therefore not be optimized away.
Strongly disagreed. A lot of removable storage benefits very strongly from async writes. The performance benefits are night-and-day and worth the hassle of explicitly unmounting.
I think a better compromise would be to mount non-journaled + removable storage (e.g. vfat USB keys) as sync.
On maybe the third day of my first programming job, a colleague pulled me aside and said “don’t give me ‘shoulds’ and ‘probablys’. You need to sound confident so I can know to trust what you’re saying”.
That guy was a bit of a dickhead in general but there’s a lot of truth there. To the question “what’s the expected impact of this change?”, “None.” is a good answer. “Well it should work…” is not useful feedback and a good Operations Manager will rightfully reject the change.
Of course it is better to be hesitant than falsely confident, but far too many (software) engineers hide behind indecisive language to dodge the necessary hard work of validating their hunches. If you didn’t test your shit fully, just say so. If you’re right, say it. Personal ego doesn’t belong in an engineering discussion.
Real answer: it depends.
lsof can tell you which process has which files open. There’s nuance with lazy unmounts and whatnot but that should not be used in most cases.Now in practice you should be wary of one very important thing that changes compared to Windows: Writes are asynchronous on Linux. First the kernel writes to RAM, then it flushes to disk at a later time for performance reasons (this is one of the reasons why writing a bunch of small files is many times faster on Linux than Windows). The upshot is that just because your file copy is “done” doesn’t mean you can just yank the USB cable. Always safely unmount before unplugging a storage device on Linux.
And Hytale got shitcanned!
It’s actually amazing that in an industry so hell-bent on copying successful formulas ad-nauseam (e.g. Quake&Doom spawning the whole genre of First Person Shooters), Minecraft has not seen anything reach the status of spiritual successor in over 15 years of charts-topping sales performance. Not from its own studio, not from its former creator, not with the Late Hypixel Studios.
There are survival games and base-building games and exploration games, but none of them are “Minecraft-likes” in the way that early FPS were “Quake-likes”. CS has Valorant. LoL has Dota. Tekken has Street Fighter. PUBG has Fortnite has Roblox. Minecraft somehow remains truly one-of-a-kind, a gaming UFO that eludes suits looking for a replicable formula. I actually believe Mojang themselves don’t understand why Minecraft works in the first place either, which is why every update seemingly either underwhelms or angers everyone. That game is lightning in a bottle and no-one knows what to do with it.
If Nadella had a stroke so bad he decided to make Minecraft FOSS, I’d be really interested to see what would happen. If any for-profit company was allowed to make direct Minecraft derivatives, I do think we would see a level of creativity and innovation that would dwarf even the already extremely prolific current modding scene.
I think the premium thing is a channel option. Some channels consistently have it, some don’t.
Regular YouTube 1080p is bad and feels like 720p. The encoding on videos with “Premium 1080p” is catastrophic. It’s significantly worse than decently encoded 480p. Creators will put a lot of time and effort in their lighting and camera gear, then the compression artifacting makes the video feel like watching a porn bootleg on a shady site. I guess there must be a strong financial incentive to nuke their video quality this way.
Technology Connections and Hank Green have been shouting this for a while, but that whole issue is way overblown. Some first gen EVs around 2010 had issues, but every major manufacturer since then has way exceeded expectations on battery lifetime thanks to advanced BMS and thermal controls. Car batteries don’t just rapidly degrade out of the blue, the tech has nothing in common with what’s in your phone. But public sentiment has not caught up because most people think Li-Ion = smartphone = dead after 2-5 years, so second hand EVs are way undervalued. Which is great for buyers.
It’s not like you can’t easily total a second-hand ICE by mechanical failure. Just ask anyone who own(ed) a puretech engine. If you went by manufacturer recommendations, the fucking thing might just eat your timing belt one day and grenade itself. And there’s no way a full engine swap on a 5-10 year old economy car is economically viable.
There’s always something that could go wrong when you buy a car. Unless you get comprehensive insurance and warranty, you need to accept the fact that losing the entire car to an accident, catastrophic mechanical failure, or theft is always a risk. If that’s too much anxiety to deal with, get a lease.
GIMP apologists are what Adobe users think FOSS apologists are like. The principled refusal to even consider fundamental UX principles is astounding.
THANK YOU.
I migrated services from LXC to kubernetes. One of these services has been exhibiting concerning memory footprint issues. Everyone immediately went “REEEEEEEE KUBERNETES BAD EVERYTHING WAS FINE BEFORE WHAT IS ALL THIS ABSTRACTION >:(((((”.
I just spent three months doing optimization work. For memory/resource leaks in that old C codebase. Kubernetes didn’t have fuck-all to do with any of those (which is obvious to literally anyone who has any clue how containerization works under the hood). The codebase just had very old-fashioned manual memory management leaks as well as a weird interaction between jemalloc and RHEL’s default kernel settings.
The only reason I spent all that time optimizing and we aren’t just throwing more RAM at the problem? Due to incredible levels of incompetence business-side I’ll spare you the details of, our 30 day growth predictions have error bars so many orders of magnitude wide that we are stuck in a stupid loop of “won’t order hardware we probably won’t need but if we do get a best-case user influx the lead time on new hardware is too long to get you the RAM we need”. Basically the virtual price of RAM is super high because the suits keep pinky-promising that we’ll get a bunch of users soon but are also constantly wrong about that.
So… Cotton/Linen/Wool? The technology is fine, its only downside in most applications is simply cost. Cotton clothes are more comfortable, less stinky, less polluting, and won’t fuse with your skin and disfigure you for life if they accidentally catch on fire. On top of not making microplastics soup every wash cycle.
If we cared to actually solve the problem of plastics in fast fashion we could ban them, with some exceptions for sportswear and shoes where synthetics have some actually useful uses. Hell, we could even make it an easy transition by gradually pulling back the allowable synthetic content for x years.
But it would directly kneecap Shein and H&M’s business model so we have to weigh all the pros against that.