skysight-inc/HackerNews huggingface dataset:
There is a fair bit of overlap.

Cog is optimized for getting a deep learning model inside a Docker image. We found that ML researchers struggled to use Docker, so we made that process easier. It generates a best practice Dockerfile with all your dependencies, and resolves the CUDA versions automatically. It also includes a queue worker, which we found was the optimal way of deploying long-running/batch models at Spotify and Replicate.

Bento is more flexible – the models can be used outside of Docker, and it has built-in support for deploying to lots of deployment environments, which Cog doesn't have yet.
This is a good reason to stop changing the core frameworks every 5 minutes, and stop building one off infrastructure to solve individual problems, unless there's a really good reason.

When something is stable and widely used, you can do optimization like this, and justify it for real production systems, and everything built on it benefits.
We do non-linear optimization mith multiple constraints using scipy optimize. What we used was beautifully coded and documented, as I assume most of the library should be, so it was easy to use it, even for beginners.
I mean it's a pretty limited use case, isn't it? The author is basically saying that if:

- you run a production line on a Mac which uses external SSDs;

- you need to check the health of those SSDs regularly;

- those SSDs connect by USB C; and

- you're not prepared to run an install of Mac OS on your internal drive with SIP disabled (which I presume is the security setting they're being required to downgrade),

then you can't fully migrate all of your activities to an Apple Silicon Mac. I don't know how many people that would apply to, but I doubt it would be a huge number, and it's hardly unusual to have either a dedicated machine or separate environment to conduct side tasks that aren't able to be completed in your main environment.

One thing I wasn't clear on was why the author didn't want to format the internal drive to create a separate partition for the SIP-disabled instance of Mac OS. I don't actually see why that would be different (from a security perspective) to running it from an external drive, given that the insecure install wouldn't be running when booted from the secure install (even if they're on the same drive). The author seems to treat it as a binary choice for the main drive in the Mac Studio (ie that it must be 'secure' or 'insecure'), but that's not really how it would work from the perspective of making a second partition's Mac OS install insecure, given that that insecure OS isn't doing anything when you're not booted into it.

If the author was still set on running the install from an external drive, they could partition the internal drive, install Mac OS, disable SIP and install the kext, then clone the partition onto the external drive. If external drives just need to be ejected during the DriveDx install process, this shouldn't stop anyone from running an OS with DriveDx from an external drive after the install. This is obviously a pain, but hardly that much worse from the hoops I've had do jump through on Windows over the years.

I must admit, I'm not familiar enough with SAT SMART or external SSDs that connect by USB C to know why there's no alternative to turning off SIP, or why this was possible on Intel Macs but not Apple Silicon Macs, but it seems like a pretty niche use case from which to extrapolate the conclusion that full migration to Apple Silicon Macs isn't feasible full stop.
And should libraries and book stores ban books documenting past exploits? Where does it end.
And are placed somewhere completely else on Swedish keyboards but it was an Aha-moment when I realized as a child that the keys ,. was really supposed to be <> for arrows in some games 30+ years ago :-)
“Son of Sam” laws in the US prohibit individuals from publicly profiting off their crimes.
Pairs nicely with Opus 1 https://www.youtube.com/watch?v=N7xn5zeJ4D4
I would guess that people who goes skydiving usually don't go up in the plane alone...
Web color is still using linear color space.

There is nothing wrong with this because now the browser can decide how to convert it. So the title should be: browsers still use linear color space.
Ask HN: How do you find credible information online?
Aside from the obvious trick of appending "reddit" to searches, or going straight to wikipedia or scientific literaure, how do you actually find anything?

In many cases, there's forums, wikis, clever people's blogs, but none of them are easy to find through Google/DDG, and essentially rely on manually "indexing" them in your head/bookmarks/notes.

How do YOU go about this?
Target FPS varied between N64 games. F-Zero X, Super Smash Bros. and some others ran at 60 FPS, while Zelda only ran at 20 FPS (17 FPS in PAL regions).
> that is not what i asked. why did YC fund hackerrank? sounds like a shitty idea and bad for our industry.

Idea of assigning number to a person and then judging that person based on that number? How it could happen in real world... Also if people are willing to pay for it (even if they don't know about it yet)in capitalism it is a good argument to pump money into it.

Also:
https://news.ycombinator.com/item?id=31052764
It would be nice to have explanations and comparisons of the techniques that are employed for the current behavior and the new behavior. The color gradient criticism feels valid from an aesthetic standpoint but the problem seems to be that a simple linear interpolation doesn't provide the desired color properties. This raises the question as to what exactly are the desired color properties from a technical standpoint and when is each technique applicable. Say we changed all color interpolations from an interpolation in RGB space to HSV space (as I imagine the color gradients suggested are achieved), would this have any unforeseen consequences?
Funny, I’ve followed the sub for a few years and was unfamiliar with this history. It explains a bit how all the threads are fairly boring and repetitive. I’ve never seen the rejected threads for other topics that might be more controversial or true debate.
The gradient mixing example is broken.

"Color gradients are supposed to be equally bright around the midpoint"

This is false. Nobody mandates this.

There is no "correct" way to do it, every one of them is arbitrary (although some do look better than others and the suggested method is better than the default linear interpolation).

It is completely analogous to smoothing curve in animation - it's about what sort of interpolation mechanism you use.

If there would be a standard for specific perceptually pleasing gradient, then one could claim "does not follow standard X".

The point of the article is usually abslutely correct, though:
"The correct way to process sRGB data is to convert it to linear RGB values first, then process it, then convert it back to sRGB if required."
Maybe there are 2 faces to this: current users and acquiring new users.

First one has been discussed in other comments: current users do not want to relearn the UI of the software. And I second that.

Second one: new users may turn away quick when seeing an old UI when trying an app or web site for a first time. So moving the UI from old to new, from time to time, may be a way for an app / website to just survive, otherwise the user base may be eroding.

Thoughts?
Understanding CVSS severity and using them effectively
Could you explain what a multi-hour intestinal cleanse from the Yogic disciplines is?
Fun problem. When solving with Gecode, you might want to add the annotation `:: domain_propagation` to the `all_different` constraint (https://www.minizinc.org/doc-2.6.2/en/lib-stdlib-annotations...). Sometimes a good idea, sometimes not.

If you can extract some instances you could send in your problem to the MiniZinc challenge (https://www.minizinc.org/challenge2022/challenge.html), preferably with several instances with varying complexity. The benefit for you is that it is a good way to ensure that your particular problem is tested for a lot of solvers, and may be used for improvments of solvers in the future. The deadline for this years challenge problem submission is 6th of May.
My short summary of this: pretty much every x86 client system since 2012 has shipped with working UEFI support (because Microsoft required it for new Windows 8 systems), and from a compatibility perspective Linux works Just Fine with basically all of them. Servers took a little longer (HP, especially, wanted to do things like just add GPT support to their BIOS implementation), but even that's in a good position now. The biggest concern I have is around cloud, where many providers still don't offer UEFI support.

I was on the Fedora technical committee in the past, and if I were still there I feel like I wouldn't go for this now. But I've also been very marginally involved in Fedora in recent years, and I don't think I have a good sense of what the tradeoffs are here. There are legitimate points where it's reasonable to say goodbye to the past, and maybe this is one of them.
Unless a company is running an engineering team composed of monkeys, it will be hard to achieve 1% optimization per month, even without compounding. There are a lot of optimizations which look good on paper but in practice bring other unforeseen cons

Anyway, a profitable software company will be looking at getting a big multiple of 10x the salary of their engineers
Err they do. You can just brew install smartmontools and use it. Even disk utility reports the device status.
UEFI emulation is a thing.

For people with legacy-only firmware systems, you too can run UEFI on lazy cloud providers and legacy hardware. I do this on my 14 year old dell laptop just so that all my x86_64 systems have the same boot efistub linux kernel images. All you need is to use one of the EDK DUET bootloader builds such as BootDuet¹, or for an easier user experience CloverBootloader². Only complaint is secureboot emulation can be a pain. But I imagine with Windows 11 around the corner requiring TPMs (which might require emulation on older hardware that doesn't have it) and secureboot, UEFI firmware emulators with these feature will probably get more popular and more accessible.

¹ https://github.com/migle/BootDuet

² https://github.com/CloverHackyColor/CloverBootloader
Do you know what the source of the crash in this video [1] is?

I’ve wanted to know ever since I saw the same clip in a few films, including Airplane 2

[1] https://m.youtube.com/watch?v=sGQpQabwf8U
I live near one of the cities shown in the video (Assen). Look it up on Google streetview. Most streets are dominated by bikes and pedestrians, not cars. Cars are mostly routed through streets are designed to accommodate them.

Accidents are rare, but we can always do better. All accidents are documented and safety statistics are freely available here:
https://swov.nl/nl/verkeersveiligheidscijfers
I usually don't have swap on my workstations either, which is why I initially thought I could get away with it on my server.

Probably different usage patterns. I routinely memory map something like half a terabyte of data on this machine. Might also be due to huge pages, that feature seems a bit janky to be honest.
I also completely agree with everything you said.

I have stopped using swap on all my servers, desktops and laptops about 20 years ago.

I have never encountered any situation when swap could have been useful, but I have always installed generous quantities of RAM on all computers.

As long as the quantity of used memory does not exceed the physical memory, swapping pages cannot improve the performance in any way.

The only exception, which is mentioned in the parent article, is when some very seldom used memory pages would be swapped and the freed memory would be used as a disk cache, hopefully increasing the performance for a I/O bound application.

Whether this strategy of hoping that a larger disk cache, filling all the available physical memory, can improve the performance more than what can be lost if the prediction that the swapped pages will not be needed soon is wrong, is extremely application dependent.

This hypothesis, that a significant performance improvement can be enabled by a slightly larger disk cache, might happen to be true in certain cases on computers which still use slow HDDs.

Except for backup/archiving, where the disk cache matters very little, I have not used HDDs for more than a decade.

On computers with SSDs, the chances to find an application where a small increase in disk cache size can cause a noticeable performance increase, larger that what is lost by swapping the seldom used memory pages, are negligible, in my opinion.
The Worst Programming Language Ever – Mark Rendle – NDC Oslo 2021 [video]
This is literally not an option - systems have shipped without BIOS compatibility for a long time now, so refusing to support UEFI is just not an option.
> People simply get bored with how their apps and websites look after six to seven years. They need a change.

Imagine if *nix-utils (ls, grep etc) used this method, every few years the switches/options changed !
it's not really happening, or at least not yet. I don't see why this even got posted the way it was.
I suggest learning to use the Compose key. For instance with no clipboard use at all, it enables «this».

Compose+<+< and then to close compose+>+>

Also see “curly” quotes: compose+<+" and compose+>+". This illustrates the power of composing: I had forgotten the shortcut, because I rarely use it, but I was able to guess it in 3 tries.
They use sRGB color space. If it used linear color space it wouldn't have this issue.
Not OP either, but there are many different aspects to solvers that make them useful in different situations.

For example, I would perhaps not use the same solver for a best-effort problem where I can program strong heuristics, vs a problem that must be optimized and no natural heuristics exist. Sometimes problems have a natural type of formulation, and it is best to use a solver for that type of problem (linear programming, mixed integer programming, SAT, pseudo boolean, constraint programming, ...).

Choosing a solver also very much depends on the deployment situation; how should a model be used and what operational concerns are there.
I don't see a clear "why" for fixing this explained in the post. Yet if we assume this should be fixed, how should the community fix this?

Has this been discussed at the appropriate standards bodies and conferences?
On the other hand without generics they are literally using a text templating language to generate the code.
Look, even if RHEL 10 gonna drop UEFI support maybe sometime in the future, there's gonna be some retro enthusiats who would happily fork it with BIOS support returned.

Also, why are you so focused with corporate decision of a distro that is obviously cattered for future devices?
From Desing-First to Automated Deployment with OpenAPI
Amazing to see a former gg2 player do this :)
> UUIDs ... endianess is not little, big - its mixed. mixed in the same value

UUIDs do not have any endianness. They are just a sequence of individual bytes.

It's true that some ways of generating UUIDs work by using the bytes of longer numbers, which I can believe use mixed endianness (I don't know them well enough to remember myself). But no one should be relying on that when reading UUIDs back out, except maybe for debugging purposes.

Or does GPT require interpreting the parts of UUIDs? If so, that is the real problem.
It would be helpful to have the expected result near the browser output.

anyway, I think the "correct" scaling is at the very least objectionable. from a numeric point of view, it whould mix in gray, but from a visual poin of view we do preceive the outer box as darker because non linearity in dislpay and perception.
Do you think youtube should systematically go through all videos for perceived dangerous people or people who look like views might "make" them do dangerous things, or just the ones that are brought to their attention by angry mobs / report volume?

And would "dangerous" include technically legal but dangerous actions like speaking up for gay rights in Yemen or criticizing cartels in Mexico? Or would they be more limited to the youtube wrong-think-corrections officer judging the video to demonstrate outright illegal actions like protesting Putin's special operation while in Russia, or publishing documents containing evidence of western war crimes?
> You made a factual mistake: MBR/BIOS based boot does not depend on a specific filesystem, nor does it depend on a specific executable file format except for the boot sector.

I never said that.

I said removing bios support allows you to remove anything that provides bios support and that choosing to not remove it won't allow you to get rid of the EFI dependencies so it is a moot point to talk about old techs used by EFI.
It is funny (as in, not funny at all) how a few common steps I use break stuff these days.

Formatting ext2, because journalling doesn't help with failing flash, e.g. USB keys -- it doesn't help you recover anything and it does more writes, hastening wear. No, "just disable journalling on ext4" is not a good answer: it's non-trivial to do, compared with just using a non-journalling filesystem, which is a single step during installation and lasts for the life of that install.

Using `noatime` and so on in /etc/fstab also breaks some stuff, such as maildir.
The UEFI runtime services provide functionality that is not generically exposed through any other OS environment. Linux could just refuse to provide those runtime features, and things would roughly work[1] - we'd still need to call some UEFI features in the boot stub, but the same is true of BIOS (look at what the 16-bit code does in terms of obtaining information that the kernel uses after init). If you want to drop all access to runtime services after kernel boot, you can by simply passing efi=noruntime to the kernel arguments.

[1] Some features would be broken, like recognising whether the system had booted successfully
Hn is not forum

Forums have way deeper discussions meanwhile hn's approach is wider
A few observations:

- Film "FUIs" are almost invariably dark these days. I wonder to what extent the designers are influenced by the dark modes in the tools they use.

- Most of them pack enormous amounts of stuff in with tiny fonts. Probably to stop the viewer from getting distracted trying to read stuff. But there seems to be an ambient assumption that 'futuristic' stuff is way more info-packed than today's UIs are - where does that come from?

- Most of them over-use transparency to absurd degrees. For holograms where you want to see the actor's face it makes sense but it appears even in shots where no actors are visible, e.g. https://www.hudsandguis.com/home/2018/florida-hospital-ui

- A typical film FUI has a lot of animated data visualizations, but real UI almost never does. Is this because such visualizations are useless clutter or because film makers have better tools for creating them than actual programmers do?

The difference between "actual" FUI and film FUI is best illustrated by the concept videos produced by engineering/tech firms:

- https://www.hudsandguis.com/home/2018/surface-hub2

- https://www.hudsandguis.com/home/2017/3/21/bmw-inside-future...

- https://www.hudsandguis.com/home/2015/10/18/lg-oled

We see way less detail and much more light-mode stuff.

I guess I'm curious how much of the gap we see between real UI and stylized/imagined UI is to do with lack of tooling, different design fashions and the different needs of film UI.
For perfect dark the content you lost was the main game, so it was pretty essential for it.
Car's aren't nearly as fragile as people make them out to be.
I work in perform engineering, although in a client rather than backend role. We usually do better than 1% a month. In fact we do this even as >1% of regressions make it into the build from the software development process.
> In 1939, a misunderstanding brought about surprising results. Near the beginning of a class, Professor Neyman wrote two problems on the blackboard. Dantzig arrived late and assumed that they were a homework assignment. According to Dantzig, they "seemed to be a little harder than usual", but a few days later he handed in completed solutions for both problems, still believing that they were an assignment that was overdue.[4][6] Six weeks later, an excited Neyman eagerly told him that the "homework" problems he had solved were two of the most famous unsolved problems in statistics.

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

Does anybody have more examples?
If a site or app has a dated design, I usually discount it. I assume that it is going to be outdated in functionality as well. And that it will have a myriad of unsolved bugs, none of which is ever going to be fixed. New bugs have one advantage over old bugs: they have a better chance of somebody caring enough to fix it.
First they came for the edgelords

Then they came for the racists

And in the end they didn't come for me because I don't spew hate on forums, nor am I the one user in two million that gets shadowbanned for saying death to jews
Yeah, that's clearly reaching into "better have insurance" territory. I'm not the type who is prone to take insurance for trivialities, if I drop my phone the last thing I'd want is dealing with a claims process (some people seem to enjoy that kind of stuff, trying to "win at insurance").

But in this case it was the reverse, not "buy some service, hope for insurance to accept the bill" but "tell insurance that there's a problem, let them do the rest". I'd have been glad to have that procurement problem outsourced even if they only paid for a small fraction of the bill (just big enough to make them still care for price)
Its relevant for converting them from and to their string representation.

https://en.wikipedia.org/wiki/Universally_unique_identifier#...
The vast bulk of people that end up in the ER or the morgue are there for reasons that are more often than not just silly. The list of near misses is probably 10 times longer.

On my list of near misses:

- the trailer incident above (but not a scratch on me, so no accident)

- a central heating line in an old house that was shorted live 240V (and yes, there was a ground fault protector and no, it didn't trip, and hey if not for the apparently very well insulating paint someone probably would have died). Long story short: the circuit that was run from the panel to the heater didn't have ground so they stuck a grounded prong plug into an ungrounded socket and called it a day. Good thing I'm paranoid about such stuff and checked against a waterline before working on that system. After plugging the heater into a grounded extension cord the breaker immediately tripped.

- hoisting up roofjoists the knot got caught and the rope had gotten more and more tension. We were hoisting about 20 of these one by one and it had gotten more or less routine. That one was anything but. When the knot slipped over the point where it was held up the tension in the line had gotten so high that the whole thing came flying over the building.

- a windmill that I built got caught in a storm and refused to furl due to a minor assembly error. Fortunately I'm a better welder than windmill-assembler and everything held up to more than 8 times the design stresses but I'm probably a much happier person not knowing how close I came on that one.

- sitting on a roof of a building that was about to have it's whole front replaced I leaned forward over the top to check the angle of the drop only to realize that the whole thing was already loose. One single kick and there were only a few tons of rubble left to clean up. The number of times I drove by that house right in front of it...

- replacing lightbulbs in an old chimney the ladder gave out (one of those iron cage jobs). Fortunately some of the rungs were in better shape.

If I think for a bit longer I'll probably find more of these.
That's why they are the keys in fact. Those are the usual shortcuts for frame navigation in some video editors.