sorry, just saw this

@ThornVaux @saltyAom Just plain incorrect. You can leak memory in any language that allows dynamic allocations and can be long running.

@saltyAom No there have been memory safe languages for decades. It's trivial to prevent memory leaks in Java and Rust. They're also simple to detect since if you try the program halts and says you can't do that. Fixing them is also fairly simple. Hard is silent leaks like Heart Bleed

It’s ludicrous easy to accidentally create memory leaks, really hard to fix without rewrite the entire thing and almost impossible to pin down where There’s also absolute zero tools to prevent or easily detect that, not even a linter

@BenjiGameDev Sees to imply that the answerer did something wrong, but end users should not be held responsible for how and whether search engines in the future decide to rank or derank things

when you google a question and the top result is a link to a forum where someone asked the same question and the top reply is "I’m curious if you tried googling?"

@yitscar (and also 100% of non-valid C++)

@yitscar If it doesn’t correctly handle 100% of valid C++ by spec, then it’s a terrible lexer that should be retired. That’s the job

Since I'm teaching C++ I can just straight up tell the students about the "converges to" operator

@Sl33pyThingg @N4pstr this bro is probably still using a mouse or touchpad on the desk instead of a gyro mouse

@N4pstr Fuck the sensor bar all together, just get a wiimote with wii motion plus & emulate it

why does every single person who talks about real wiimote usage on dolphin bring up the Dolphinbar™ you don't need anything fancy, you can just get a USB sensor bar off Amazon. they're dime a dozen

@valigo “This creator is a backup of tsoding from the era during which he was a backup of primeagen”

I am genuinely so confused

@yitscar @lisyarus … why? The language spec allows such use (or non use) of spacing and (non) parentheses.

@lisyarus Any lexer that would accept "-->" as two tokens is an abomination.

@simeydotme @JLarky Typically the glyphs are for arrow tails. compart.com/en/unicode/U+2…

@JLarky Absolutely abhor code font let ligatures, the triple equals and not equals is so ick With your example idek what I'm looking at, what is that even supposed to be? A yoke? Terrible!

why I would never use those stupid ligatures in my terminal

@JLarky @Shreyassanthu77 Specifically, do you meant all font ligatures should be off by default in ghostty? Or just the “contextual alternates”? Unfortunately depending on the font, both of those choices might not solve the user problems. It’s all maybes & tradeoffs. But I hate the JB Mono ligatures too

@Shreyassanthu77 Top screenshot? :) I think it's build by people who asked tok many "wouldn't it be cool if ...?" and not enough "how do we make it actually useful?"

@JLarky @Shreyassanthu77 mux is just a common abbreviation for a multiplexer, if we are going by other names we should maybe assume cmux is some sort of multiplexer for the C/C++ languages

@Shreyassanthu77 Two worst parts of it so far: ghostty and the fact that the name implies that it's somehow related to tmux I mean, it's better than default terminal, but way worse if you actually care about terminals 😂

@devinjameson @DavidKPiano That’s just what programming is. When you have powerful and expressive tools, understanding the best ways to use them for each situation means understanding a lot more than syntax. It’s on you to know when constructs are positive and when they’re negative. All frameworks & lang.

@DavidKPiano Quick React tip: stop using React. After 10+ years, we’re still sharing “tips” like this to avoid shooting ourselves in the foot. This should tell you something about the quality of the tool. None of us have any toes left.

Quick React tip: don't subscribe to data that you don't render; it causes unnecessary rerenders. If it's only used in event handlers, read it there. AI coding agents tend to get this wrong.

@NueveXUno @timetravelslop2 (I wish you would go back and write this tweet a second time)

@timetravelslop2 I wish I go couldbsck and read this for the first time

ive been reading books of old

@Aspie96 @SebAaltonen Such considerations are generally left to an optimization called dead store elimination, which is not based on how the operator is used but rather whether the result is used, and they fall within a separate optim step from the initial semantic analysis. And again, it’s optional

@fashy @SebAaltonen The compiler needs to know what is and isn't a valid instruction and handle any unused result correctly. The compiler already knows that the meaning of "i++" is different when used as part of a wider expression or instructions and when used as an instruction on its own.

Pre-increment operator doesn't need to create a temporary copy of the object. It can be faster. No difference for integers of course (they are in registers), but matters if you use a complex iterator object. Compiler tries to optimize the copy away in release builds.

@Aspie96 @SebAaltonen Doesn’t seem related to the conversation about the increment operators in C and whether they each have two semantic definitions

@fashy @SebAaltonen Not all expressions are valid instructions in C the way they are in (for example) Python. Pick the name of a variable: it can be used as an expression, but not as an instruction on its own.

@Aspie96 @SebAaltonen That is not correct, at least for C. For one, there’s no concept of a “command” form. It’s just an expression with an unused result. & Compilers are free to wastefully store unused data while still being fully spec-compliant. And they typically do when optimizations are disabled

@SebAaltonen i++ and ++i have different meanings when used as expressions vs when used as commands. When used as commands they don't return anything, they are commands. No output value is stored, added to the stack or sent to anything. And when used as commands they have the same meaning.

@AlbinoGorillaDs @shumibomber4 Wait until you find out what Nissan is short for

@shumibomber4 You mean to tell me that nippon steel is just Japanese steel?

日本を英語にするとJAPANなのよく考えたら謎だな NIHON、NIPPONならともかくＪはどの辺から取ってきたんだ

@mrsteyk1 @valigo There are quite a few pieces of software (mostly games) even today with bugs or performance degradations that are worked around by end users renaming the .exe

@valigo I remember seeing a reddit post a couple years ago about a guy changing his application or engine name (don’t remember) and getting better perf, so yes?

Because old graphics APIs were very high-level, drivers had a lot of compex code to optimize specific games and game engines on case-by-case basis, and every driver changelog would have a list of games with improved FPS. To my knowledge, Vulkan generation of graphics APIs meant to give a lot more control to programmers, specifically so that drivers can remove all of this bloat. However, Vulkan's VkApplicationInfo has fields for game/engine names and versions. Why is it needed? So that the driver can have special cases for it built in? If so - doesn't it kinda defeats the purpose? Can anyone who actually knows what's the deal here explain?

@dcolascione @zplesiv @jordwalke “It’s not risky or fraught when I do it” is a very natural sentiment in programming. But we don’t design code for the perfect experts that we think we are (or at least, we should not)

@fashy @zplesiv @jordwalke It's not a good thing, because nested ternaries as a poor man's COND works fine and should be formatted flat.

@PixelCNinja Is this a scam to boost watch time

"70% of Japan's youth don't know the fact that a dog's chain breaks after being pulled 49 times” Make that 99.7% in the UK 😂

@zplesiv @jordwalke The fact it gets formatted like this is a good thing, and if seeing the nested nature of it visually discourages you from the pattern, that is a good thing as well

@jordwalke The real issue with JS is that prettier formats it like this by default.