HackerTrans
TopNewTrendsCommentsPastAskShowJobs

didibus

8,734 karmajoined 13 лет назад
All opinions are my own.

comments

didibus
·позавчера·discuss
Article did a decent job of showing discipline and care and human involvement to assert the automated rewrite was done diligently, as best as it can be when using AI for it. I does make me feel a bit more comfortable about it.

As an aside, I don't know why anyone would not want to use a memory-safe (and possibly race-safe) language in 2026. Rust gives you that in a performant package, so if you are turned off by GCs and immutability for performance reasons, you still have the option to use Rust.

I can understand when you need the absolute best performance and you decide to drop to down to C++, and I also relate with just personal preference, but beyond those it seems a no brainer to me.
didibus
·позавчера·discuss
> to exhaustively come up with reasons why the changes create bugs or do not work

My biggest issue currently, is I can't seem to get a code review that's about the simplicity of the code, and no /simplify ain't it. Removing certain bugs and generally working seems to be doing alright, especially if it's following either an example code (like in the Bun rewrite case) or a well defined "spec" of how to proceed.
didibus
·6 дней назад·discuss
That's true, that's a money constraint, which hopefully would mean as they gain more paying users, they can scale their index further, and rely less and less on other indexes.
didibus
·6 дней назад·discuss
Ya, because the upstream repos already did the majority of the work to port the game to Linux and MacOS. This fork used Fable to add iOS support with touch controls.
didibus
·6 дней назад·discuss
The port to MacOS is from the parent upstream repo, which also has it working on Linux, this fork added iOS support.
didibus
·6 дней назад·discuss
It added iOS support, the upstream repo had already ported the game to Linux and MacOS.
didibus
·6 дней назад·discuss
Diff of the changes Fable added to the parent fork (which does not appear to have used AI): https://github.com/ammaarreshi/Generals-Mac-iOS-iPad/compare... for those curious.
didibus
·6 дней назад·discuss
It seems it didn't:

> Built on EA's GPL v3 source release via fbraz3/GeneralsX (which did the heavy lifting of the macOS/Linux port — this fork adds the iOS/iPadOS port and a set of engine fixes)

Fable added 19 commits on top of the parent fork, which did not use AI.

You can see the diff of what Fable added here: https://github.com/ammaarreshi/Generals-Mac-iOS-iPad/compare...
didibus
·7 дней назад·discuss
I'm confused, that's just a feed?
didibus
·7 дней назад·discuss
SearXNG is different though, because it still relies on a data-harvesting, ad-driven online economy. Off course if all you care about is privacy, might be fine, not sure how good it is at hiding you, but if you care more about not having your data/attention be the revenue source and having software incentives be to offer something customers are willing to part money for, Kagi is still it.
didibus
·13 дней назад·discuss
I see, so just major refactor, or almost live-rewrite of a very messy code base, but mostly in the medium/small design space. Ya that makes total sense. It's mostly we already did this and have figured out the ambiguities, we just need to clean it up to basic coding standard and code structure/patterns.
didibus
·14 дней назад·discuss
> I don't have too much unknowns in my work, I simply have way too much to do.

Interesting, I'm curious what work you do? My software engineering career has never been in that situation, it's always so much ambiguity and unknown that trumps everything.
didibus
·20 дней назад·discuss
I'm getting a bit tired of these disguised adverts.

Here's how non robotics engineers used AI to do a short robot integration task faster than other non robotics engineers without AI.

Where "better" mostly means faster, and who knows what happens on longer horizons, with actual robotics experts, robustness requirements, or tasks where the hard part is control rather than API spelunking.
didibus
·22 дня назад·discuss
Same, I use Spacemacs in holy mode, which is spacemacs with normal emacs key bindings and not vi modals, but still I wish there was a good config that was straight up emacs bindings and didn't pull in evil at all.
didibus
·22 дня назад·discuss
Has something changed since you last told me:

> I think Gloat/Glojure has the best hosted runtime story because of its AOT to Go src pipeline - you can grab anything Go at compile time. OTOH let-go can roundtrip any Go value including structs, functions and channels but it does not allow pulling arbitrary go libs without wrapping them up first - they'd need to be built into the runtime for this.
didibus
·23 дня назад·discuss
I believe this is the most promising Clojure hosted on Go, as their has been a few recently, this is the only one with full proper interop.
didibus
·25 дней назад·discuss
For sure, we'd need to be careful about implementation. Maybe we can't come up with a good version and decide not to do it.

But we should at least be able to discuss the problem.

Some people seem to think it's totally fine for wealth accumulation to be effectively uncapped, and for ownership to keep concentrating gains no matter how large the numbers get.

Past some point, that seems hard to justify.
didibus
·25 дней назад·discuss
[flagged]
didibus
·26 дней назад·discuss
Why do you think ownership should be uncapped and allowed to capture majority of wealth?

PG is absolutely right, if you want to be a billionaire, you need accelerated growth, you need to find something that a large number of people will pay for and you need to make sure you own equity into it as it grows, equity that grows with it.

And that's exactly the source of the debate, this trick to billionaire-level wealth, is that a good thing? Because it wasn't earned through labor, no one can earn a billion dollar through labor, you can only accumulate it through vast equity into market capture of a large market.
didibus
·26 дней назад·discuss
[flagged]