Mark Logan

609 posts

Mark Logan

Mark Logan

@technicaldebtor

The dark side of the force is a pathway to many abilities that some consider to be unnatural

Katılım Şubat 2013
161 Takip Edilen262 Takipçiler
Mark Logan
Mark Logan@technicaldebtor·
Something people don't understand about LLMs and security: It's not an arms race. Once you fix all the bugs, you win. Defender has the advantage! There is no AI model powerful enough to find bugs that don't exist.
English
0
0
0
20
Mark Logan retweetledi
Unconfirmed Labs
Unconfirmed Labs@unconfirmedlabs·
We've been working on a more scalable read and write layer for @SuiNetwork. Our solution, codenamed Hikari, is a near-parity drop-in replacement for Sui gRPC nodes, and unsupported requests automatically fall back to a full node. On the read side, we designed a custom storage backend that's fronted by multiple layers of caching, each serving a unique purpose. In our benchmarks for GetCheckpoint and GetTransaction requests conducted in 5 regions around the world, we're seeing the following p90 results: - Baseline Full Node: 400ms - Hikari (Origin): 54ms - Hikari (L3 Cache): 42ms - Hikari (L2 cache): 37ms - Hikari (L1 cache): 28ms - Hikari (L0 cache): 20ms That's a 22x improvement in latency. For writes (transaction submission), we implemented a lightweight service that's edge-deployable. Furthermore, unlike full nodes, Hikari can be horizontally scaled up in seconds. We benchmarked Hikari against fullnode.mainnet.sui.io across 5 regions, and achieved a 15-25% faster p90. We are working closely with the @CodaNetwork team to pilot Hikari. After a successful testing period, we will make Hikari available for the broader ecosystem.
English
2
4
35
2K
Mark Logan retweetledi
Terrible Maps
Terrible Maps@TerribleMaps·
The Pacific Ocean is so vast it could hold 16 Polands
Terrible Maps tweet media
English
291
2.4K
56.4K
7M
Mark Logan
Mark Logan@technicaldebtor·
@FFmpeg The real problem with GC is that it is non-local. If you have code that is slow because of calling malloc(), you can remove the malloc(). If you have GC pauses, the cause of that is the _entire rest of the program_
English
0
0
23
9.6K
FFmpeg
FFmpeg@FFmpeg·
This is the reason FFmpeg is not written in a Garbage Collected language. We can't just stall for a few milliseconds. Also unlike gaming which can just lag and reduce FPS, video (de)compression must maintain real-time to have smooth video. 1ms is a lot but it isn't at the same time.
Sebastian Aaltonen@SebAaltonen

Same is true for time. 1ms is a lot in real-time software. 120Hz displays (new phones) = 8.33ms budget. 1ms = 12% of your whole budget. I remember an old article saying that garbage collection is a solved problem, because it just takes couple of milliseconds...

English
73
293
5.6K
730.5K
Sebastian Aaltonen
Sebastian Aaltonen@SebAaltonen·
Exceptions were a big design mistake. Hidden gotos all over the code base. Not easy to write "Strong Exception Safe" code. Rust returns error codes just like C. Wrapped in syntactic sugar. Return type can be error or actual type. Much nicer design.
'(Robert Smith)@stylewarning

I'm overhearing a FAANG tech meeting about how this 10?-year product written in C is being transitioned ("modernized") to C++. Started by changing to a C++ compiler, and slowly rewriting to use classes/exceptions, &c. It's been 3 months, and the C++ service keeps failing in prod.

English
63
23
859
73.2K
Mark Logan retweetledi
Mark Logan
Mark Logan@technicaldebtor·
@jb_61820 @SebAaltonen The problem is not what happens when an exception is thrown (aka hidden gotos). The problem is that you don't know what exceptions a function can throw, which means that every function has an extra invisible dynamic return type.
English
5
0
4
404
Jonathan Bartlett
Jonathan Bartlett@jb_61820·
@SebAaltonen People say stuff like this, but in my experience I’ve never hit an instance where a thrown exception caused problems that wouldn’t be equally caused by return codes, and it greatly reduces code complexity by having error exit routes not have to be explicitly encoded everywhere
English
3
3
33
2.2K
Isaac King 🔎
Isaac King 🔎@IsaacKing314·
Recently met a guy excited to tell me about how Cantor's diagonal argument is wrong. Concerned he was a crackpot, but I heard him out and turns out he was totally right. (Ok, the actual argument is correct, but most popular explanations of it are wrong.)
English
24
0
242
30K
Carmine Paolino
Carmine Paolino@paolino·
Types don't help AI, they actually hinder it. Proof: look at Ruby with Steep - a Ruby type checker - and without! Or Python vs Python with mypy. Token efficiency and expressiveness is way more important for AI generated code. That's why Ruby was the best language in this test!
Yusuke Endoh@mametter

I benchmarked which language works best with Claude Code. Ruby, Python, and JavaScript came out cheapest, fastest, and most stable! See my article in detail: dev.to/mame/which-pro…

English
19
1
61
50.4K
Mark Logan
Mark Logan@technicaldebtor·
@SnowFake3 @L8BL0oM3r @IsaacKing314 They are countable in that you can count to any specific integer no matter how large. Same for rational numbers. Not so for the reals.
English
2
0
0
34
Mark Logan
Mark Logan@technicaldebtor·
@unconed The reason he has bad experiences on the internet is because he thinks he knows everything, is often incorrect, and concludes that everyone else is wrong/an idiot
English
0
0
0
23
unconed 🛸💫👻
unconed 🛸💫👻@unconed·
Jonathan Blowhard Jonathan Blown or just Jonathan Blow (cocaine) I want the guy to do well but you get the idea he's had such a poor experience in any open internet interaction he just expects everyone to be retarded and disingenuous, even when the issue is him. (Earned my blow block by daring to have opinions on game asset pipelines after building one)
'(Robert Smith)@stylewarning

A Jonathan Blow story in 3 parts.

English
10
2
71
8.9K
Mark Logan retweetledi
Rob Wiblin
Rob Wiblin@robertwiblin·
Huge repository of information about OpenAI and Altman just dropped — 'The OpenAI Files'. There's so much crazy shit in there. Here's what Claude highlighted to me: 1. Altman listed himself as Y Combinator chairman in SEC filings for years — a total fabrication (?!): "To smooth his exit [from YC], Altman proposed he move from president to chairman. He pre-emptively published a blog post on the firm's website announcing the change. But the firm's partnership had never agreed, and the announcement was later scrubbed from the post." "...Despite the retraction, Altman continued falsely listing himself as chairman in SEC filings for years, despite never actually holding the position." (WTAF.) 2. OpenAI's profit cap was quietly changed to increase 20% annually — at that rate it would exceed $100 trillion in 40 years. The change was not disclosed and OpenAI continued to take credit for its capped-profit structure without acknowledging the modification. 3. Despite claiming to Congress he has "no equity in OpenAI," Altman held indirect stakes through Sequoia and Y Combinator funds. 4. Altman owns 7.5% of Reddit — when Reddit announced its OpenAI partnership, Altman's net worth jumped $50 million. Altman invested in Rain AI, then OpenAI signed a letter of intent to buy $51 million of chips from them. 5. Rumours suggest Altman may receive a 7% stake worth ~$20 billion in the restructured company. 5. OpenAI had a major security breach in 2023 where a hacker stole AI technology details but didn't report it for over a year. OpenAI fired Leopold Aschenbrenner explicitly because he shared security concerns with the board. 6. Altman denied knowing about equity clawback provisions that threatened departing employees' millions in vested equity if the ever criticised OpenAI. But Vox found he personally signed the documents authorizing them in April 2023. These restrictive NDAs even prohibited employees from acknowledging their existence. 7. Senior employees at Altman's first startup Loopt twice tried to get the board to fire him for "deceptive and chaotic behavior". 9. OpenAI's leading researcher Ilya Sutskever told the board: "I don't think Sam is the guy who should have the finger on the button for AGI". Sutskever provided the board a self-destructing PDF with Slack screenshots documenting "dozens of examples of lying or other toxic behavior. 10. Mira Murati (CTO) said: "I don't feel comfortable about Sam leading us to AGI" 11. The Amodei siblings described Altman's management tactics as "gaslighting" and "psychological abuse". 12. At least 5 other OpenAI executives gave the board similar negative feedback about Altman. 13. Altman owned the OpenAI Startup Fund personally but didn't disclose this to the board for years. Altman demanded to be informed whenever board members spoke to employees, limiting oversight. 14. Altman told board members that other board members wanted someone removed when it was "absolutely false". An independent review after Altman's firing found "many instances" of him "saying different things to different people" 15. OpenAI required employees to waive their federal right to whistleblower compensation. Former employees filed SEC complaints alleging OpenAI illegally prevented them from reporting to regulators. 16. While publicly supporting AI regulation, OpenAI simultaneously lobbied to weaken the EU AI Act. By 2025, Altman completely reversed his stance, calling the government approval he once advocated "disastrous" and OpenAI now supports federal preemption of all state AI safety laws even before any federal regulation exists. Obviously this is only a fraction of what's in the apparently 10,000 words on the site. Link below if you'd like to look over. (I've skipped over the issues with OpenAI's restructure which I've written about before already, but in a way that's really the bigger issue.)
English
1.8K
5.4K
23.8K
111.6M