HackerTrans
トップ新着トレンドコメント過去質問紹介求人

wizzledonker

140 カルマ登録 5 年前
Just your usual Software Developer from Sydney, Australia. Currently working in CAD/CAM software.

コメント

wizzledonker
·3 日前·議論
We maintain a semi-large complexity application with plugin support in Qt. I was able to port it to webassembly in under a day a few years ago, it was essentially a process of hunting build issues in dependencies, patching QOpenGlWidget’s behaviour and adding a few #ifdefs around platform specific code. A bit of fun, seems like a good use for an LLM but not overly complex to achieve.

EDIT: Now that I’ve read the article I’m reasonably confident this port was made far more difficult than it actually was. Might be the LLM hallucinated some unnecessary steps and reported them as necessary.
wizzledonker
·24 日前·議論
I think the real issue might be that how “good” the code is matters less than being able to form a mental model for what the human who wrote the code was “thinking”. If written by a machine, this contract is broken and we get more confused, even if our traditional methods of evaluating the code come out equal.
wizzledonker
·28 日前·議論
Did you mean 2025?
wizzledonker
·先月·議論
That is quite literally exactly what they have done
wizzledonker
·3 か月前·議論
Slightly unrelated: are the OCCT unfolding components a paid add on or included in the open source distribution?
wizzledonker
·4 か月前·議論
I don't necessarily agree in this case - OCCT is more than capable for what FreeCAD is offering. Add to that the development trajectory of OCCT also seems to be really taking off recently (with the 8.0-RC, they've re-worked how all B-Spline algorithms work, with implications for all operations).
wizzledonker
·4 か月前·議論
That would require calibration with the camera, and even then the camera and lidar sensor can’t be in exactly the same place. I doubt results would be better.
wizzledonker
·5 か月前·議論
I'm so confused. Sentry is a native client crash reporting tool. What does this have to do with MCP or the LLM itself? Do you mean when interpreting the crash data?
wizzledonker
·5 か月前·議論
Qt is not a horrible mess to use, the problem is just people don't bother to learn any tech stack outside web. It's so obvious that this is the issue to anybody who actually does native development.
wizzledonker
·5 か月前·議論
Qt with QML works fine. The real reason is that companies can't hire enough native developers because the skill is comparitively rare.
wizzledonker
·7 か月前·議論
Only if they work in a fundamentally different manner. We can't solve that problem the way we are building LLMs now.
wizzledonker
·7 か月前·議論
Definitely a good one - probably one of the best CLAUDE.md files you can put in any repository if you care about your project at all.
wizzledonker
·8 か月前·議論
After a cursory glance at commit messages, looks like most of it.

Like all AI co-authored code it’s a matter of time before this becomes unmaintainable and abandoned.
wizzledonker
·8 か月前·議論
The reason most creative media is good is because you see the vision of a creative team or individual.

If the vision is diluted due to lack of control afforded by AI tools, then the tools won’t be used.

Many times in Hollywood have we seen directors spend unjustifiable amounts of money in the pursuit of creative control.

Hand camera tracking a dinosaur in Jurassic Park, developing a novel diffraction algorithm for THE ABYSS, hand-drawing 3-Dimensional computer animations for 2001, creating an entire scale model practically for a single fight scene in LOTR.

AI allows you to get anything. The best movies are a direct reflection of a particular vision. AI can’t provide this and I see no way to solve it.

A natural response is - well directors already outsource some creative control to VFX artists so why not to a machine instead.

Because an artist can control everything. Even if the artist is prompting a model, at the end of the day an artist can drill right down to the tooling itself (photoshop for example) and exactly achieve the vision.

I don’t see AI achieving this granularity while maintaining its utility. It’s a sliding scale of trading utility as a time saving device for control.

If you lean too far to the control side, well you might as well fire up photoshop. If you lean too much to the utility side, you sacrifice creative control.

When looked at under this lens the utility of AI generation is actually limited as it solves a non existent problem. One can think of it as an additional piece of tooling for use only as a generational tool where there is less need for control, such as for background characters.

The team at Red Barrels, for example, train a local model on their own artwork to automatically generate variant textures for map generation. Things such as this. No need to be doom and gloom about this stuff.
wizzledonker
·昨年·議論
If you watch a little further until about 20 minutes what follows is an explanation of what the primaries represent (described by you as “colorspace coordinates”) along with a reasonable simplification of what a transfer function is, describing it as part of the colorspace. I believe that’s reasonable? He merely explains Rec. 2100 as if using the PQ transfer function is innate. Definitely all seems appropriate and well presented for the target audience.
wizzledonker
·昨年·議論
I’ve seen skeuomorphic designs done with vector art, surely this can’t be the only/real reason.
wizzledonker
·昨年·議論
Just because I’m curious, why the issue with reading GPL code? My understanding is that you would have to essentially directly copy and paste the code for the GPL license to apply to it.
wizzledonker
·昨年·議論
Then I’d say just pick the one you are most familiar with
wizzledonker
·昨年·議論
This is a fantastic tool and I recommend it! I use it every day to recursively solve bottlenecks in our code base.
wizzledonker
·3 年前·議論
I have an AMD 6700xt.

It was laggy in Windows and under X11 on linux, but under Wayland I get 60-80fps and it's very usable.

Not sure what the cause is

EDIT: Under Chromium (compiled from AUR) the performance is roughly the same