MurphyA/hacker-news huggingface dataset:
by pch07 | 2025-12-29 00:28:42+00:00
Thank you!! It wouldn't have been possible without your enthusiasm and encouragement!

I think a lot of people are interested in making cool things but bridging the gap between looking at the project from the outside and actually doing something can be scary, especially for people who are contributing to open-source projects for the first time. For people who are extremely new, it helps a lot to either have direct guidance from someone with experience ("synchronous" due to timely feedback) and/or reading/video educational material ("async" due to something that can be created once and used multiple times after its creation). With regards to Pion, I was lucky to have both kinds: constant feedback from Joe, plenty of material to read via https://webrtcforthecurious.com/ , RFCs, the countless issues in SCTP; it felt a little bit like I stumbled into a lab with all the tools at my disposal and all I had to do was put the pieces together, come up with a plan, and go for it.

Also the https://github.com/pion/webrtc/wiki/Projects-Worth-Doing wiki page was very helpful but this could also be something that we can improve on: having a better understanding of what we want to get done and when we want them to get done (roughly speaking) is good. Updating it can be a bit of a chore though so I wish there could be a more efficient way to keep track of things while getting things done. I didn't struggle with it as much myself but that was mostly because Joe and I were working together nonstop for the last few months, but I can see how it could potentially be confusing for newer folks. It would also be good to mark which issues/features are blocked by others, which is something that I added in SCTP's readme, which has been nice. One thing I wonder about is whether the older parts of the codebase are daunting, but our efforts to put together resources regarding what RFCs are relevant has been great. I wonder if the video streaming world could have some sort of public tracker for different tools/technologies for people to learn about. I feel like that might be the biggest bottleneck for us, especially compared to other specialized software fields.

As for technical things, there are definitely a couple: learning that Windows' networking doesn't play as nicely as Linux's has been a bit of a nightmare, I'm surprised it even works at all haha. Another is how little attention RACK has received; the dissertation (https://duepublico2.uni-due.de/servlets/MCRFileNodeServlet/d...) doesn't seem to have garnered much attention despite having a really big impact. I also think that it's really surprising to be able to sit down and deal with packets and remember that everything is just a bunch of packets and the way we keep track of things we've sent or received is entirely governed by whatever rules we come up with. It feels oddly primitive but very valuable to be able to learn about why and how we want to track whatever heuristics we come up with!
by pixelpoet | 2025-12-29 00:28:42+00:00
Good show, this is how I recommend doing it and have been teaching it for years.

It's quite unfortunate that basically everyone thinks 3D graphics necessarily implies rasterisation and using someone else's API, and I feel extremely lucky to have taught myself in a time when you could trivially display images by direct memory access (mode 13h), and to have focused on ray tracing instead of rasterisation.
by nateb2022 | 2025-12-29 00:29:00+00:00
> 2) Documentation. This is something that really plagues about 90% of ruby projects. And it's not getting any better. It is as if in ruby, only 10% care about documentation - at best. Look at rack, opal, wasm for ruby - the documentation is TOTAL TRASH. Non-existing; look at rack. What a joke.

Are you familiar with the Ruby ecosystem?

You can easily view documentation for all installed gems using yard like so:

yard server --gems

or from the command line you can look up a class like so:

yri Rack::Request

or a method:

yri Rack::Response#set_cookie
by ChrisMarshallNY | 2025-12-29 00:29:10+00:00
> I'm not sure why you would be surprised

Maybe because I'm not especially interested in passing moral judgment on others, for working at a company that isn't a "moral high ground" company, but isn't exactly NSO or Palantir (I used to work for a defense contractor). I feel profoundly lucky to have found a company that made me feel good about what I did. It was worth the low salary (and other annoyances). I understand that I'm fortunate, and I'm grateful (not snotty).

I find that people take the mere existence of others that have different morals to be a personal attack.

I know that it happens, but I'm not really sure why. It's not like I'm thinking about comparing to others, when I say that I worked for a company that inspired me. I was simply sharing what I did, and why.

I read comments about people that are excited about what they do, and even how much they make, all the time (I spend a lot of time on HN), and never feel as if they are somehow attacking me. They are enthusiastic, and maybe even proud of what they do, and want to show off. I often enjoy that.
by thousand_nights | 2025-12-29 00:29:11+00:00
the bayer pattern is one of those things that makes me irrationally angry, in the true sense, based on my ignorance of the subject

what's so special about green? oh so just because our eyes are more sensitive to green we should dedicate double the area to green in camera sensors? i mean, probably yes. but still. (⩺_⩹)
by baby_souffle | 2025-12-29 00:30:17+00:00
> That at least removes network delays

But that's often _the source_ you need to work around; there is no way in hell that they're going to get all the light/sound/video/graphics ... etc people in the same 2 square meter area to put on a show like the super bowl :).

For smaller events like a touring act or even a venue with a few hundred people capacity you still need a single master clock but this time it's not "wall time" and is "absolute" time. E.g.: a musician at the front of the house chooses when to start and the video/lighting guy in the back needs to be on the same page so the visuals line up [0].

[0]: https://en.wikipedia.org/wiki/SMPTE_timecode
by Electricniko | 2025-12-29 00:30:20+00:00
CEOs who build great, long-lasting companies would be very hard to replicate. But CEOs who make money for stockholders at the expense of everything else seem like the type of thing that would be much easier to replicate. As others have commented, replacing the people skills of a CEO might be difficult. But if the CEO's job is to strip the company of assets and cash out for the owners, people skills are kind of a hindrance at that point.
by overfeed | 2025-12-29 00:30:22+00:00
> With that handled, all that's left is the cartel that CEOs have invented to justify their exhorbant pay packages.

CEO compensation is determined by board committees often made up of other CxOs. They write letters to each other's shareholders about how valuable CEOs are to build up the edifice.

I wish my compensation were determined by fellow engineers who "truly know my worth". I'd pay it forward if I were on a committee determining colleague's pay packets.
by QuiEgo | 2025-12-29 00:31:07+00:00
> But Linux... it's already better

I think that depends a ton on what your hardware is.

For desktop, I think there's a real arugment to be made for Linux at this point.

For laptop, what laptop running Liunx has comporable hardware quality, battery life, and perfomance to an Apple Silicon mac? AFAIK most people say "Thinkpads!" and then immeidately turn around and say "well, the battery life is worse but I can just plug it in! Or "the trackpad is worse but I don't care!"
Show HN: Deep Code Research – AI surveys 10 similar repos to review yours
by WindChimeRan | 2025-12-29 00:31:21+00:00
Deep Code Research is a CLI tool that automatically finds repositories similar to yours, analyzes how they handle things differently, and produces a comparative report.

Instead of generic advice like "add error handling," it shows you exactly what related projects do and where your code differs. Each finding includes side-by-side code snippets from both your repo and the reference repo, with specific file paths and line numbers.

The tool uses a multi-agent architecture: a main agent discovers related repos via GitHub search, then spawns parallel sub-agents to analyze each one. Results are synthesized into a prioritized list of findings.

I built this because code "literature review" is time-consuming. Before building something, you should survey similar projects to learn patterns and avoid known pitfalls. But reading through 10+ repos takes hours. This automates that process.

https://github.com/WindChimeRan/deep_code_research
by nomel | 2025-12-29 00:31:50+00:00
And this is important because our perception is more sensitive to luminance changes than color, and with our eyes being most sensitive to green, luminance is also. So, higher perceived spatial resolution by using more green [1]. This is also why JPG has lower resolution red and green channels, and why modern OLED usually use a pentile display, with only green being at full resolutio [2].

[1] https://en.wikipedia.org/wiki/Bayer_filter#Explanation

[2] https://en.wikipedia.org/wiki/PenTile_matrix_family
by pixelpoet | 2025-12-29 00:32:53+00:00
The aforementioned Ryzen AI chip is exactly what you describe, with 128 GB on-package LPDDR5X. I have two of them.

To answer the original question: the Framework Desktop is indeed still at the (pretty inflated) price, but for example the Bosgame mini PC with the same chip has gone up in price.
by commandersaki | 2025-12-29 00:34:24+00:00
I like skeeto's version [0], but it allows for unbounded parsing due to unbounded zero padding of decimals, so therefore not constant time. Probably only requires an additional counter for the number of digits seen to mitigate that, but it would probably yucky the code a bit.

[0]: https://github.com/skeeto/scratch/blob/2af9b076117838b93fc2f...
by ekidd | 2025-12-29 00:35:58+00:00
I have been overusing em dashes and bulleted lists since the actual 80s, I'm sad to say. I spent much of the 90s manually typing "smart" quotes.

I have actually been deliberately modifying my long-time writing style and use of punctuation to look less like an LLM. I'm not sure how I feel about this.
by strken | 2025-12-29 00:36:25+00:00
This is an oversimplification. Collective action is driven by a mass of individual beliefs that are strong enough to suppress bad actors. If you are one of the bad actors, it's more difficult to force the other bad actors to stop because they can accuse you of hypocrisy.

See e.g. Al Gore taking flights to speaking engagements about climate change. From one perspective, this is an effective tool and probably even carbon-negative if it leads to effective change. On another level, why is a guy with so many frequent flier miles telling me to fly less? Why is a rich guy who can eat the cost of a carbon tax telling me my plane tickets will cost more? Etc.

I am reminded of the "no ethical consumption under capitalism" refrain, which is sometimes used by people who don't like capitalism to justify taking the absolute least ethical option available.
by loeg | 2025-12-29 00:36:30+00:00
The thing I ran into most recently is that std::chrono (weirdly?) only supports clocks with compile-time fixed fractional conversion to reference time (~seconds). E.g., you can't implement a std::chrono clock where the count() unit is the native CPU's cycle counter, which will have some runtime-determined conversion to seconds. The types make it impossible.
by mgraczyk | 2025-12-29 00:36:42+00:00
I think Samsung was doing what was alleged, but as somebody who was working on state of the art algorithms for camera processing at a competitor while this was happening, this experiment does not prove what is alleged. Gaussian blurring does not remove the information, you can deconvolve and it's possible that Samsung's pre-ML super resolution was essentially the same as inverting a gaussian convolution
by Sharlin | 2025-12-29 00:37:15+00:00
No. It's about the shape of the curve. Human light intensity perception is not linear. You have to nonlinearize at some point of the pipeline, but yes, typically you should use high-resolution (>=16 bits per channel) linear color in calculations and apply the gamma curve just before display. The fact that traditionally this was not done, and linear operations like blending were applied to nonlinear RGB values, resulted in ugly dark, muddy bands of intermediate colors even in high-end applications like Photoshop.
by dheera | 2025-12-29 00:37:17+00:00
Journalistic/event photography is about accuracy to reality, almost all other types of photography are not.

Portrait photography -- no, people don't look like that in real life with skin flaws edited out

Landscape photography -- no, the landscapes don't look like that 99% of the time, the photographer picks the 1% of the time when it looks surreal

Staged photography -- no, it didn't really happen

Street photography -- a lot of it is staged spontaneously

Product photography -- no, they don't look like that in normal lighting
by shevy-java | 2025-12-29 00:37:48+00:00
So far all I am seeing is an increase in prices, so any company claiming it will "ramp up production" here is, in my opinion, just lying for tactical reasons.

Governments need to intervene here. This is a mafia scheme now.

I purchased about three semi-cheap computers in the last ~5 years or so. Looking at the RAM prices, the very same units I bought (!) now cost 2.5x as much as before (here I refer to my latest computer model, from 2 years ago). This is a mafia now. I also think these AI companies should be extra taxed because they cause us economic harm here.
by mrkeen | 2025-12-29 00:38:22+00:00
You've just built a calculator, and now you want to test it. Well, you have to push buttons on a calculator, so you build a robotic hand. And that hand needs a power source and some intelligence. And you need to photograph and OCR the result from the calculator screen.

This is kinda how we build software right? A little bit of "our logic" (calculation), represented as objects/actors/modules which "do things", but intermingled with million-LoC dependencies like databases and web servers.

After a while it gets frustrating setting up the robot hand and OCR equipment for each test case. Maybe it's just easier to test manually, or skip testing entirely.

At this point you can have an epiphany, and realise you only care about the numbers going in and out of the calculator, not the button pushes and pixels.

Mockito swoops in and prevents you from having that epiphany, by making it easier to keep doing things the stupid way.

Instead isolating the calculation from any IO, you can now write things like:
when(finger.pushbutton(1)).then(calculator.setState(1))
when(calculator.setAnswer(3)).then(camera.setOcr(3))

(I've mostly worked in Java, but it seems like other languages typically don't let you intercept calls and responses this way)
by kittikitti | 2025-12-29 00:38:53+00:00
Acknowledging this sort of theory was considered pseudoscience for many years, in the realm of epigenetics. I'm glad the gatekeepers are coming around to finally acknowledge this as real science. Now we just need a designated media personality to communicate it to the masses. After that, I can finally have a conversation about it without people casting me as a lunatic.
by senshan | 2025-12-29 00:39:05+00:00
It is your choice, but for me, it is strictly professional. Some overlap with friends, but those who I never worked with, are not on my Linkedin contact list. Somewhat counterintuitively, no recruiters. Many/all recruiters have very "noisy" contact lists which complicates navigation via degrees of proximity, like 2nd, 3rd, etc. When the list of contacts is carefully curated, it adds value.
by coldtea | 2025-12-29 00:39:52+00:00
The activity I describe started well before the 21st century.

Remember "yuppies" - the boomer ideology that dialed up consumerism and financialization of all aspects of life. Reaganomics? The 1989, 2000, and 2008 crashes? The Great Outsourcing? Also in the eve of 21st century, boomers were merely from 40 to 54, so well represented in all positions of power and business. Clinton and Bush J were boomers. And Boomers got more entrenched as time went by and as they reached their 50s and 60+ for the later ones.

Same in Europe too, were e.g. people like the French 68'rs (the youth of the late 60s student revolts, roughly similar to the same era youth in the US later turned yuppies), have been running things since the early 80s in the most selfish, destructive, and narcissistic ways.
by shimman | 2025-12-29 00:39:55+00:00
Why not? Let's not act like the average CEO isn't also an actively hostile member of the company toward its workforce. Why should people be forced to work under such hostile regimes? People should be empowered to vote for their leaders where they work. Boards have this authority already, there's zero reason why workers shouldn't be granted the same priviledge.

It won't make the companies worse run, why would workers want to destroy their means to live? CEOs do this with no skin in the game, the workers should take that skin as they will always be better stewards than the single tyrant.
by Rochus | 2025-12-29 00:40:14+00:00
The goal of my compiler is not to get out maximum performance, neither of CoreCLR nor Mono. Just look at it as a random compiler which is not C#, especially not MS's C# which is highly in sync and optimized for specific features of the CoreCLR engine (which might appear in a future ECMA-335 standard). So the test essentially was to see what both, CoreCLR and Mono, do with non-optimized CIL generated by not their own compiler. This is a legal test case because ECMA-335 and its compatible CLR were exactly built for this use-case. Yes, the CIL output of my compiler could be much more improved, and I could even get more performance out of e.g. CoreCLR by using the specific knowledge of the engine (which you cannot find in the standard) which also the MS C# compiler uses. But that was not my goal. Both engine got the same CIL code and I just measured how fast it run on both engines on the same machine.
by lidavidm | 2025-12-29 00:41:07+00:00
Olympus and other cameras can do this with "pixel shift": it uses the stabilization mechanism to quickly move the sensor by 1 pixel.

https://en.wikipedia.org/wiki/Pixel_shift

EDIT: Sigma also has "Foveon" sensors that do not have the filter and instead stacks multiple sensors (for different wavelengths) at each pixel.

https://en.wikipedia.org/wiki/Foveon_X3_sensor
by Lalabadie | 2025-12-29 00:43:03+00:00
For similar reasons, I ended up sticking to a bullet journal (ish) format after I tried it ~10 years ago. I don't do long-term planning with it, but I have 1-2 weeks laid out in advance, and years of stuff logged.

It keeps a record of things done and lived. In terms of planning and task keeping, the paper format also forces me to let things fall off the list if they won't get done after all.

I also joke that I'll be the person who can actually answer if one day an investigator asks me "What were you doing on the night of November 22nd, 2019?"
by jiggawatts | 2025-12-29 00:43:13+00:00
I've been studying machine learning during the xmas break, and as an exercise I started tinkering around with the raw Bayer data from my Nikon camera, throwing it at various architectures to see what I can squeeze out of the sensor.

Something that surprised me is that very little of the computation photography magic that has been developed for mobile phones has been applied to larger DSLRs. Perhaps it's because it's not as desperately needed, or because prior to the current AI madness nobody had sufficient GPU power lying around for such a purpose.

For example, it's a relatively straightforward exercise to feed in "dark" and "flat" frames as extra per-pixel embeddings, which lets the model learn about the specifics of each individual sensor and its associated amplifier. In principle, this could allow not only better denoising, but also stretch the dynamic range a tiny bit by leveraging the less sensitive photosites in highlights and the more senstive ones in the dark areas.

Similarly, few if any photo editing products do simultaneous debayering and denoising, most do the latter as a step in normal RGB space.

Not to mention multi-frame stacking that compensates for camera motion, etc...

The whole area is "untapped" for full-frame cameras, someone just needs to throw a few server grade GPUs at the problem for a while!
by to11mtm | 2025-12-29 00:43:19+00:00
I think they are both more asking about 'per pixel color filters'; that is, something like a sensor filter/glass but the color separators could change (at least 'per-line') fast enough to get a proper readout of the color in formation.

AKA imagine a camera with R/G/B filters being quickly rotated out for 3 exposures, then imagine it again but the technology is integrated right into the sensor (and, ideally, the sensor and switching mechanism is fast enough to read out with rolling shutter competitive with modern ILCs)
by reactordev | 2025-12-29 00:43:23+00:00
Unity has a unity problem.

While it’s easy to get in and make something (it’s got all the bells and whistles) it also suffers from the monolith problem (too many features, old code, tech debt).

The asset store is gold but their tech feels less refined. It’s leaps and bounds where it was when it started but it still has this empty feel to it without heavy script modifications.

There is the problem. The scripting ending designed around mono doesn’t translate as well to CoreCLR and using the same Behavior interface gets a little more complicated.

There are times (even with my own engine) that one must let go of the old and begin a new. Dx7->dx9, dx9->opengl, opengl->vulkan, vulkan->webgpu.
by chrisoverzero | 2025-12-29 00:43:23+00:00
Mhm! Exactly! In the system those other languages use, once you see the variable’s declaration:

User activeUser

…you’ll always know that `activeUser` contains a User value – something that might have an `Id` property. And the convention is enforced by the language, so it’s easy to communicate. These semantic distinctions are very useful, I agree.
by why-o-why | 2025-12-29 00:43:56+00:00
I don't know enough about different industries to know if this is true in general. But I do know in tech it is all about networking (aka soft nepotism): spending your career making friends ("swiping right on every work relationship"), and the fraction of those who go on to massively succeed you can then call in favors. At least that's how I made three huge jumps in my 35+ year career, and how the majority of my peers got the big step-functions in pay.

Perhaps in my original post I'm just confusing academia with industry, since I know so few academics.
by llmslave2 | 2025-12-29 00:46:47+00:00
> This is how successful American propaganda is. 39% of people believed something that definitionally could never be true.

It's not that difficult to get into the top 1%. Most Americans earn a top 1% income. Even the top 1% of America is only a salary of around $500k. It's possible 19% of survey takers were in the top 1%, or were on a path to make that in the future.

I don't see how it's definitionally untrue to believe you could make $500k a year at some point...Let alone $34,000 a year...
by whstl | 2025-12-29 00:47:46+00:00
I've seen similar things from the inside in other companies. Even existential threats (like lack of Apple Silicon support for performance-critical software), getting heavily delayed because the feature treadmill won't stop and the "important thing" is a pet project of some engineer. It is basically death by a thousand papercuts, where nobody can say what the focus is.

People complain about web development but working with native apps can be depressing sometimes.