Hacker Timesnew | past | comments | ask | show | jobs | submit | nasso_dev's commentslogin

interestingly, french speakers just have to pronounce "wero" as "nouro" for the same pun to work ("eux-ro" vs "nous-ro")


titling "Building for the Future" the announcement of a mass lay-off is disgusting and makes me sick to be honest

is this really the future we want to build?


The future, for those who have the capital. The rest may die, shareholders don't care.


Then we must build our own future. One where we deny the capitalists access to their own automated killer robot armies.


>Then we must build our own future.

Sure. How many of those hated capitalists have started with exactly same thought?

People should stop drop this naive act.


I don’t think I’m the naive one if you think those “hated capitalists” had the intention of building a bright future for the collective us.


> if you think ... had the intention of building a bright future for the collective us.

Never said or implied such thing.


You shot off a one-sentence rejoinder about capitalists building a future. What does it mean? Not worth your time to explain, but worth your time to nuh-huh about your autor intent after the fact.


are you saying c++ can be used as a basis for other projects whereas rust cannot? ...why?


it is indeed pretty weird. clippy has a lint against this iirc. it's recommended to just create a custom error type, even if its just an empty struct or a single-variant enum

this lets you implement `std::error::Error`, which you really should to make it less painful when you want to erase the type (`std::error::Error` is `dyn`-compatible)


wow we're at ffmpeg 101 already? ffmpeg 8 felt like yesterday


this is what happens when you let agents push, approve and release code while you sleep!


check out https://margin.at !


this is super cool as an art form but ASCII art is an accessibility nightmare so please don't use it for docs unless you know what you're doing and have made it accessible in some other way


Is there any way to make images accessible other than the alt tag? I'm sure SVGs are more machine-readable, but how would that help vision-impaired folks?


im not an expert on a11y best practices, but id say an <img> tag with alt text is enough

for inline SVG, i read somewhere you can use <title> and <desc> to describe the SVG document, but i don't know how they work in practice


Is it still true with llms being so good at interpreting it? I just tried all the examples on the home page, it works perfectly. In the past couple months I've moved almost entirely back to the terminal because I can just ask my coding agent to "have a look at this tmux session".


Good reminder to keep in mind.

At the same time, I don't think one should necessarily limit your expression based on constraints like accessibility.


they definitely are. im not sure why they did that, still pictures are okay too and much greener


Aren't procedural macros amd build.rs arbitrary code being executed at build time?


Pretty much, yes. And they don’t have much as far as isolation goes. It’s a bit frightening honestly.

It does unlock some interesting things to be sure, like sqlx’ macros that check the query at compile time by connecting to the database and checking the query against it. If this sounds like the compiler connecting to a database, well, it’s because it is.


i like the points the article makes, but i really wish it used looping videos instead of actual GIFs

i don't really see any reason to use GIFs here; any widely available video codec like H.264, VP8/VP9 or AV1 will result in significantly smaller file sizes, look better, and will allow enabling controls for seeking and play/pause


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: