Marco Buono

Vocês gostam de colocar no pódio software ruim. Os líderes de mercado quase sempre são os piores produtos. WhatsApp, o Sistema Operacional do brasileiro, é um poço de improdutividade. Existem aplicações para terminal com usabilidade melhor do que esse produto.

@MattStopa @simonklee It wasn't even about how good Rust is. It was about how Rust ended up being a better fit to the very specific mix of GC, Non-GC, External C/C++ interop and complex multithreaded lifetimes that Bun has. The post literally mentions that most projects aren't like this.

@simonklee The thing is most of the Bun article wasn’t about how bad zig is, it’s about how good rust is. He really didn’t throw any shade at zig at all

I like Zig. I'm one of the relatively small number of people who gets paid to write Zig professionally. Yeah, that may sound arrogant, but the reality is that there aren't many "Zig jobs" out there. Incidentally, the project I work on also uses Bun. I want Zig to succeed. I remember talking to Joran from TigerBeetle forever ago, and my only question was something along the lines of how TigerBeetle could succeed, because it's one of the few major supporters of Zig. It's incomprehensible to me that Andrew chooses to publish something like this. The blog post doesn't help the Zig project. It only alienates users and contributors, moves attention away from what Zig is trying to achieve, and makes the project look bad.

@coreh Architectural changes

I have to emphasize that Elysia 2 is a REWRITE, not an incremental update It just happens to have a similar outer API surface That's why the performance difference is high

@Acerola_t "wow, layoffs suck but at least they didn't close any studios!"

@coreh Okay but you are doing exactly what I point out in my post lol

The new strategy appears to be just laying off all the employees without officially closing the studio so they can have thousands of people online say "wow, layoffs suck but at least they didn't close any studios!"

@Acerola_t It wasn't my intention, I've seen/been through both kinds (actual layoffs vs “let's keep 3-4 people here to answer inquiries, keep lights on and pretend the company still exists” layoffs) So sometimes it is not exaggeration, in this case it's bad but Id still exists in some form

@coreh Regardless dont be obtuse lol "everyone" is a clear exaggeration, the number is still ridiculously high and the studio is now a husk of what it was a week ago

@juvoni @ahejlsberg @typescript Not yet. Eslint and other things still require TypeScript 6, which is why for the time being they will ship both. IIRC they're working on fixing this, but it should land only later on a follow-up version.

@ahejlsberg @typescript Has anyone tested if this is compatible with the rest of the ecosystem plugins, eslint etc?

Huge milestone for our team today: TypeScript 7 is now generally available--a native port that runs 10x faster. @typescript devblogs.microsoft.com/typescript/ann…

@MelohRush @dickiehat I mean, the games don't happen until Eggman does shit, though

@dickiehat They were team cause if matter of circumstance. Each of them basically are on their own 90% of the time until Eggman does shit.

hot take Team Sonic makes the least sense to actually exist out of any other team from Sonic Heroes and beyond

I understand the reasoning behind this advice but to be blunt, I'd rather die

@franciscobmp_ Sonic 1 tem level design bom e consistente para o que propõe em termos de gameplay (speed cap, momentum, rotas superiores/inferiores) Sonic 2 introduziu mecânicas novas (spindash, speed cap alto) mas não aproveitou tão bem. 3 eles acertaram a mão. O Mania é inconsistente.

@coreh level design de sonic é esquisito até no mania antes fosse um problema só desse jogo

meu sonho que o level design de sonic não fosse um lixo

@AndrewGspeedrun PC games can have compatibility/perf issues, so it does make sense to allow refunds. Probably not after having played 1h40 though

My actual opinion here is: game refunds? What? That shouldn't be allowed unless it was like a scam since you paid for it? Concept seems very strange. You don't get to refund a movie because you didn't like it.

@servmux @awesomekling They intersect in being more and more impractical over time, as various pieces of the stack are adopting AI (Linux kernel, various libraries, applications) and also as websites switched from JS as an enhancement to fully relying on it

@awesomekling I don't see how those two intersect, ai boycott is mostly political, while the JavaScript boycott is technical and/or privacy driven.

"I'm just not going to use software that was developed with AI" is the new "I'm just not going to visit websites that use JavaScript"

@theo Nobody thought that, but modern compositors/window servers work by sharing memory with various processes in a long-running session, with critical privacy/security/performance considerations. It shouldn't be this surprising it makes heavy usage of Virtual Memory

“Theo you’re so stupid it says virtual memory! Did you really think it was using terabytes of ram??” I swear my haters have never been dumber

@FMastronzoIT @CRBN78 @emhjr O Europeu é menos tolerante a essas coisas, e separa mais o trabalho e vida pessoal. Americanos, Canadenses etc não.

@FMastronzoIT @CRBN78 @emhjr Já trabalhei remoto pra empresas do Vale do Silício, e nas viagens pela empresa, dividir quarto de hotel era super comum, inclusive eles perguntavam se você queria ficar com a galera quieta ou a galera barulhenta. E em algumas sim, tinha bizarrices parecendo seita também

O Ministério Público vai ter trabalho essa semana hein kkkk o amigo do Luciano Huck se superou nessa

@GobaDev ear and chin IRL variations are seemingly way underrepresented in most games haha

god tier reference if you're trying to decide on facial morphs for a character creator or something. lots of variations here i would've never considered

@matteocollina @nodejs running a custom test suite that calls the package, as a consumer, exercising the public api of the package a lot of the package's tests are there to verify their own internal logic and wouldn't break no matter what changes node did, so running them all is not really necessary

@coreh @nodejs how would we know they worked, if we didn’t run their tests?

Hey everyone! I triaged a @nodejs vulnerability, wrote the fix, and pushed it through the security process. I now think it shouldn't have been a CVE. And the fix broke a big part of the ecosystem. 🧵

@matteocollina @nodejs Oh, I didn't realize you were running the modules _own_ test suite. I thought they were custom smoke tests calling a bunch of modules and doing basic operations with them. This is more like Rust's set up without the benefit of first class test runner support via cargo, then

@coreh @nodejs Because 90% of module test suites do not pass out of the box and require special CI config. There is also the non-zero chance that there is an actual breaking change in Node and the module would need to be patched.