@airtable is rewriting their database in Rust 🦀
@airtable is rewriting their database in Rust 🦀
Rust usage according to Rust survey Results 🦀
Ply: Build cross-platform apps in Rust via @robey https://lobste.rs/s/lsk3gq #graphics #rust
https://plyx.iz.rs/blog/introducing-ply/
It will be interesting to see which target languages are more suitable for LLM-based code generation. Intuitively, I would think that the more strict and typesafe languages, such as Rust, Ocaml, F#, would fare better. If the compiler can stop me from doing something stupid, surely this must work for AI-generated code also?
Node.js runtime — executes JS server-side, has full OS access, file system, network, require() etc.
wasm-pack output — targets the browser (--target web). The generated search.js uses browser APIs (WebAssembly.instantiate, fetch) to load the .wasm binary. No Node.js involved at all.
If you buils with --target nodejs instead of --target web, wasm-pack would generate a package that works in Node.js using require() and fs.readFileSync to load the .wasm. Different glue code, same .wasm binary.
So the .wasm binary is portable — the JS glue changes depending on the target environment. --target web is what you want for the browser search.
#Rust is the implementation language, #WASM is the compilation target, JS is the glue.
No #nodejs #python needed only other thing I am tempted to try for this is #zig
And #typescript can be glue instead of #JavaScript which I personally hate
If I implement server side with #tailscale funnel , I don't even need to rent a server , just some board/box that boots ll be enough
[Show GN: 바이브코딩 자율주행 FSD
Vibe Coding의 '자율주행 FSD'는 AI 작업 흐름을 자동화하는 앱으로, 화면 픽셀 분석을 통해 버튼 클릭 등 인터랙션을 자동화합니다. 주요 기술 스택은 Tauri v2 + React, Rust, xcap, enigo, image이며, Claude Code, ChatGPT Desktop 등 AI 도구와 호환됩니다.
I added an example to my tiny #Bevy #ProceduralGeneration library, #fernweh , demonstrating how one may use it to implement "layered" chunk-based procedural generation, that is, procedural generation where some data is shared across several chunks. This is typically useful for large-scale terrain features.
The example below works in a similar way as in the previous toot: chunks are represented by colorful polygons, chunks close to the player (the white disk) get spawned, chunks far away get despawned, and there is an artificial delay to simulate expensive computations.
The difference is now chunks are grouped in groups of four chunks which share data (namely, a color — blue or red). The point is that data is only computed once, even though it is used by several chunks.
Fernweh is very flexible, so it is possible to use the same approach to group groups into even larger groups, or group chunks one way for one type of data, and another way for another type of data...
Keep in mind, though, that this relies on a yet unreleased Bevy feature, scenes (very likely to land in Bevy 0.19).
https://codeberg.org/glocq/fernweh/src/branch/next-gen-scenes
Experimented on same exact project with #llms first in #elixir (that I can read and vaguely code) and then #rust (that I understand decently well).
The rust one ended up so much better it's insane. I'm not sure if that's gpt-5.4 just not knowing much of elixir, or rust being more anal around compiling, but I think the defenitive bit is my understanding the slop patterns immediately and telling the llm to refactor things before it gets too bad.
Which is a funny problem. With people vibecoding more and more, who'd be this guardrail from letting the llms slide into slop? llms are chaotic by nature so the longer codebase is llmed without review the worse it gets.
#gamedev progress:
The normals of the animated mesh still look wrong. Not yet sure why.
#shaders #animation #rust
Link:WebGPU Data Memory Layout
https://blog.libove.org/posts/link-webgpu-data-memory-layout/
@AAKL @TheNewStack Fallacy. That's number from 7,156 participants of survey, participants who know what #Rust is.
Conservative estimates start at 20.8 MILLION of professional developers on the planet. You can't do any statistically significant estimate from a 0.3‰ sample consisting mostly Rust fans.
@rayk @tomekw It's my experience that convinced me the #Rust is the right way, despite things I don't like or lack of things I like.
The reason of why new projects in #Rust pop up like mushrooms are in fact Rust's complex features and safety mechanisms. It makes people confidently build more advanced stuff quickly.
2/2
Is it possible to write Rust on a low end system?
Out of Place
#photography #vernissage #darktable #rust #France #Turenne #buildings #ruins
Ne pas se sentir à sa place…
Yeah... lol :ferris: 🎵
Rust in My Veins - by Jake Reynolds
https://www.youtube.com/watch?v=9E3U1ddExYA
(via Invidious: https://yewtu.be/watch?v=9E3U1ddExYA)