今日已更新 403 条资讯 | 累计 36418 条内容
关于我们

标签:#m

找到 10843 篇相关文章

AI 资讯

The Cybercab is the lightest, most efficient Tesla ever made

Against all odds, the Tesla Cybercab is in production. And while Elon Musk's company may not have a very coherent plan for the tiny, autonomous two-seater, it's still taking the necessary steps to certify the EV's legitimacy. As such, Tesla recently filed paperwork with the Environmental Protection Agency that reveal many of the Cybercab's specs, […]

2026-06-16 原文 →
AI 资讯

Pour one out for Roku City

By this time next year, Fox Corporation CEO Lachlan Murdoch intends to have added Roku to his already expansive media empire. Should the acquisition go through, Fox will gain control of Roku's modest library of original programming, and the newly combined company will become "the third-largest player in U.S. television" in terms of viewing share. […]

2026-06-16 原文 →
AI 资讯

I built a storage engine in Go (from scratch without any AI), here's the entire process documented.

I spent the last 2 months building a storage engine from scratch understand how storage engines actually work. To respect the rules of this subreddit, we will not discuss the features ør benchmarks, for that you should read the repo yourself. To understand how I came up with the bits and pieces to put together this project, follow along. So here's my entire journey. Two things: - I built this project because of a recent interest in low-level and systems programming, that combined with my general affinity towards stateful systems made this project an obvious choice. - I see a lot of cool projects (on various social platforms) and when I attempt to read their code, it's obvious that it's written by AI. I intend to share my thought process here because I want to spread awareness that it's very much possible to build something like a storage engine using your first principles intuition. ---------------- Let's begin: 1 . Given all the knowledge I had and using first principles thinking, I setup an in-memory KV store but then it's obvious I had to make it persistent. I added persistence by writing a single line to the file every time someone made a PUT request. The file now had a bunch of {key: "hello", value: "world"}\n. So during startup, I would read all these lines and recover everything into in-memory. 2 . For me, at this point that's all the upfront knowledge I had. So I asked some very basic questions: > How would I recover the entire file into memory on startup? At some point it just wouldn't be possible because the file is growing unbounded. This means that I must not load everything in-memory and instead access the file directly > But then if I read every line top to bottom on every GET then my latency would be literally obliterated? This means I must somehow efficiently query the file. I came up with a solution, I created files based on alphabets, all keys with prefix A will end up in file A, all keys with prefix B will end up in file B and so on. By first prin

2026-06-16 原文 →
开发者

Polynomial Fitting: a rabbit hole

This one is bit math heavy. I started of building a small timeseries compression library, and ended up digging through some numerical algorithms, linear algebra. I learnt through a hose during last week and found something genuinely beautiful. If you stick through it I suppose you can see what I saw. submitted by /u/ennamo_po_madhava [link] [留言]

2026-06-16 原文 →
开发者

Stop exposing your S3 bucket URLs. a dead simple image proxy with CDN caching

How I replaced all the ugly S3 URLs on my Laravel blog with clean /storage/media/... and /storage/og-images/... paths. The setup: Laravel + Octane + Traefik + Cloudflare. Two buckets -- a private one for uploaded media and a public one for auto-generated OG images. What's in the post: - MediaUrlBusiness helper class that centralizes URL generation (replaced 6+ blade templates of raw Storage::url() calls) - ObjectProxyController that streams files directly from S3 using readStream() + response()->stream() -- no memory buffering - Cache-Control: public, max-age=86400, immutable so Cloudflare caches aggressively - Route setup in routes/static.php with a middleware tweak that doesn't overwrite the proxy's own cache headers One gotcha: Storage::download() and streamDownload() buffer the whole file into memory. Switching to readStream() sends it directly from S3 to the client. submitted by /u/HolyPad [link] [留言]

2026-06-16 原文 →