919 karma · joined February 10, 2025
Dynamic linking gives you M binaries + N libraries. Static linking is M * N.
Yeah, that's fine, but a 16 ounce glass of orange juice has way more than one orange in it, and it's got a hell of a lot of sugar.
The point about AI isn't about efficiency, it's about accountability. This administration already has a huge accountability problem, and the AI is another layer of "Oh, that wasn't really me who did that thing I did." This isn't just cynicism, the current admin is incapable of taking responsibility for anything they've done wrong (and perfectly willing to take full responsibility for things other people have done right).
This would be a ridiculous expectation if you were working for the federal government. Politics affect your work to an extreme level there. Not discussing politics at all is not discussing your job.
> I don't want people badmouthing their job or work or company. All of these behaviors are toxic and I would guess 80% of people are like me.
If your company was involved in something really bad, you'd rather just not know? If you worked for Theranos, Nikola, or Enron, you'd rather be able to continue on with your nose down than know what's going on?
I want to know the truth about my company. I don't want to be complicit in crimes or things that I consider unconscionable, and I don't consider willing ignorance a good excuse for partaking in unethical or illegal activity.
I still haven't watched the movie yet.
I don't know if this is better for that use case, but even if not, luarocks is clunky and annoying to use at best.
Right, it's an optimization problem. You fight the fraud to the point that it optimizes loss. If it costs $1 million to stop $10 million of fraud, you do it. If it costs $1 billion to stop $10 million of fraud, you let that fraud happen.
Even Von Neumann said "truth is much too complicated to allow anything but approximations."
The thing is how you research, what you expect to get out of it, and what you're willing to pay. There was absolutely a gold rush on bottom-dollar development by cheap overseas developers by management who had no idea how software really worked, and thought they could build a business on cheap offshore development. These were software farms staffed by unappreciated undertrained people from diploma mills. I saw truly shocking things. I saw code written entirely with gotos instead of loops, because the developer had never learned how to write a while loop. The companies spent way more in the long run trying to iterate, ask for changes, and ultimately having to hire higher quality talent for much more money.
I agree with the GP. The LLMs will get better, maybe people will learn that you need an LLM with a skilled developer, or maybe the agents will get good enough to fully drive themselves properly, or maybe just good enough that a non-technical pilot can get good work out of them. Right now, "vibe coding" is largely non-technical people making messy, unmaintainable, insecure code. Some of these are programmers and non-programmers just playing around, but some people are trying to build money-making businesses off this, and it does feel like a very similar situation.
This article is a bit more balanced, though, and clearly isn't criticising use of AI in programming, but specifically the "Jesus take the wheel" style of vibe coding. It's the same old "if you write code as cleverly as you possibly can, you are not smart enough to debug it", but to the next level, where people are writing code that they aren't even smart enough to read.
https://pubs.opengroup.org/onlinepubs/009604499/utilities/xc...
Wario Land 3 is a really really good Game Boy Color game.
Or are you actually responding directly to what I was saying, and it turns out that on big scenes, even apart from the memory use, CPU rendering is somehow more efficient than GPU rendering? I don't think I'm prepared to accept that claim without a lot more substantiation.
edit: I found this thread here: https://news.ycombinator.com/item?id=25616372
I guess the conclusion is that it is really about memory use, but at least 4 years ago, there wasn't a total consensus on the topic.
edit: I'm actually not seeing the C FFI, looking at the library. It must be there somewhere, because it's being used from a C++ codebase. Can somebody point to the extern C use? I'm finding this inside that `fontations` repository:
> rg 'extern "'
fontations/fauntlet/src/font/freetype.rs
161:extern "C" fn ft_move_to(to: *const FT_Vector, user: *mut c_void) -> c_int {
168:extern "C" fn ft_line_to(to: *const FT_Vector, user: *mut c_void) -> c_int {
175:extern "C" fn ft_conic_to(
187:extern "C" fn ft_cubic_to(
>Which is why I'm in support of always building your own software with -O3.