HackerLangs
TopNewTrendsCommentsPastAskShowJobs

v1ne

no profile record

comments

v1ne
·11 giorni fa·discuss
Don't worry. Once IT Security discovers that they miss their trusty endpoint security products on your Mac, they'll add it and you'll be in the same ballpark as the Windows machine. Been there, received that, and learnt that Microsoft Defender exists for macOS, too.
v1ne
·25 giorni fa·discuss
"USB data blocker" on AliExpress yields you very small adapters that enable you to run USB-PD, but block the data lines.
v1ne
·27 giorni fa·discuss
I tried to read this, and what the tool works, but this is so much text with little context. Looks like AI fluff. It sounds pretty straight-forward, so this should be a single page with a few paragraphs only.
v1ne
·mese scorso·discuss
Interfaces are persistent in Windows, that's why they get assigned such silly names as "LAN interface (42)".

If the mapping between the logical and physical interfaces changes, that probably means that your NICs lack proper IDs to differentiate them or the bus topology is somehow not stably sorted. I wouldn't blame the OS for this.
v1ne
·mese scorso·discuss
The trick about documentation is depth, not prose. You need context and understanding to write documentation "like in the old days". No amount of LLM trickery will free you from that. Once you have that source material, it's easy to re-shape it into an 80's/90's/00's doc format.

Negative example: I was looking into the German manual of my Canon EOS R5 II, and it is just fluff. Hundreds of pages, full of white space, telling me about features without actually explaining what they mean. Awful automatic translations. Their manuals used to be good (looking at my EOS 6D). But these days: oh boy.
v1ne
·mese scorso·discuss
It's sad to see Xtensa go. Their architecture was a clean design, a treat to read the assembly code. I get it, RISC-V comes without licensing costs, but that's one of the few positive things about it. For a fresh start, it is just already in this "we pile stuff on stuff on stuff" state that you expect of an architecture after 10-20 years of productive use.
v1ne
·mese scorso·discuss
Well, salt may be less volume than brine. But the demand for table salt is pretty limited. Thus: Why pay for its disposal when you can discharge brine for free?
v1ne
·3 mesi fa·discuss
Great! Brings a bit more dynamic into the market. So far, I'm happy with DxO, but I also don't need to manage a library.

I don't know, does Resolve have lens corrections for 100+ lenses built-in? That's the thing that DxO does really well: Lens corrections, matching your camera's color rendering, denoising. Unfortunately, they still struggle with HDR output.

I imagine the tools in Resolve save you much time, due to automation. Probably handy if you shoot a lot. Yet, the biggest difference is that in photography, you're not necessarily limited by throughput. You can and do actually put a lot of effort into single images.
v1ne
·3 mesi fa·discuss
I think it's more people being fascinated by this curious architectural detail. I imagine it's fascinating to people who are not exposed to the intricate details of computer architecture, which I assume is the vast majority here. It's a glimpse into a very odd world (which is your day-to-day work in the HFT field, but they rarely talk about this, and much less in such big words).

TBH, I didn't watch the video because the title is too click-baity for me and it's too long. Instead, I looked at the benchmark results on the Github page and sure, it's fascinating how you can significantly(!) thin the latency distribution, just by using 10× more CPU cores/RAM/etc. Classic case of a bad trade-off.

And nobody talked about what we use RAM for, usually: Not to only store static data, but also to update it when the need arises. This scheme is completely impractical for those cases. Additionally, if you really need low latency, as others pointed out, you can go for other means of computation, such as FPGAs.

So I love this idea, I'm sure it's a fun topic to talk about at a hacker conference! But I'm really put off by the click-baity title of the video and the hype around it.
v1ne
·4 mesi fa·discuss
Does anybody else's fingers also tingle like this is written by an AI?

The formatting is strangely inconsistent, highlighting only some numbers and some variables in fixed-width font. Also there's odd statements like that the reference resistor keeps its value "at all temperatures", which is just not true. Other phrases like "poly-silicon resistor" are highlighted, and then not explained. All in all, I find this article to be quite a mess and not a clear explanation.
v1ne
·4 mesi fa·discuss
All of this works much worse on macOS: Scaling sucks, as it's integer-upscaled rendering + fractional downscaling in a shader. Windows can't span screens either.

On Windows, the window will adapt as you move its center of gravity across the edge of the screens. Sure, could be better than at the moment where the window is the wrong size, but it would always be blurry.
v1ne
·5 mesi fa·discuss
If people make extraordinary claims, I expect extraordinary proofs…

Also, there is nothing complex in a C compiler. As students we built these things as toy projects at uni, without any knowledge of software development practices.

Yet, to bring an example for something that's more than a toy project: 1 person coded this video editor with AI help: https://github.com/Sportinger/MasterSelects
v1ne
·8 mesi fa·discuss
Completely agreed. I sit in dismay, remembering the Microsoft I frowned upon back in the days as a Linux/FreeBSD user. But at least their software was accessible via keyboard and their translations were really good.

Fast forward to now, after being a dev on Windows for years and loving it, and now their UX is a joke. For example, to jump back and forth between chats, neither the back/forth mouse buttons nor any other key combo works on macOS. You have to click the navigation buttons in the symbol bar instead. Translations are AI-powered, and that shows. Also, Teams is dog slow, which I also count as a UX issue.
v1ne
·8 mesi fa·discuss
> Also, ML is now really good to translate between European languages

As somebody who has to regularly bear "German" machine-translated UIs and manuals that originate in English, I can only say: No, it's not. It's atrocious.
v1ne
·10 mesi fa·discuss
Something to hack, but I don't see how to easily type braces and parentheses. Looks like a non-starter to me because for me, I hack by writing in languages that require parentheses.
v1ne
·anno scorso·discuss
The problem is not only the DAW support, but the support of low-latency audio interfaces in Linux. Audio interface makers rarely create a Linux driver, and a low-latency setup on Linux is its own hell, with real-time kernel patches. On MacOS and Windows, it works out of the box.
v1ne
·anno scorso·discuss
Thing is: That's your preference and nobody should force you to use these indicators. Even on Windows, the tray icons are usually mostly hidden away.

I find them highly useful on macOS, but there I lack the configurability I have on Windows.
v1ne
·2 anni fa·discuss
Oh, thank you for the offer! I'll pick it up again and update the PR. Haven't looked into it since then.

I found the OLS, especially with the Demon Core, a really neat piece of hardware.
v1ne
·2 anni fa·discuss
I don't know. My experience as a contributor to Sigrok was sad: I significantly improved a driver and wanted to upstream those changes, but was met with "well, the maintainer has little time, can you slice your changes into smaller pieces?", and honestly, after a months of doing that, waiting weeks for feedback, explaining things, I lost interest. Also, with time, I honestly don't remember some details of the changes beyond what's in the commit messages.

I also found the style of the code quite antiquated, without any wish to change that. But that's my taste.

So, in the end, my work on that driver felt wasted.
v1ne
·3 anni fa·discuss
Looking at the examples given, it seems like Darktable becomes more and more unusable due to a lack of good defaults and easy configurability. I agree with the author that opinion and good defaults help to keep software simple. Yet, I also value having a way to opt out of this and customize it. Take Visual Studio, for example: There are multiple sets of decent keyboard shortcuts and a sensible default layout, plus a menu option to restore it. As a user, you're still free to create your own task-specific layouts.

When I worked at a big music software company, I also valued the strong opinions that kept the UI simple. Because the software was already so packed with functionality that it would overwhelm users easily if it would be exposed too openly.