skysight-inc/HackerNews huggingface dataset:
I'm not really convinced that the story of Nvidia's origin does have the profound meaning the author seems to think it does.

> the Nvidia GPUs [...] were originally inspired by [...] the needs of computer graphics artists in the gaming industry.

I think this passage demonstrates a misread of the quoted section[1] from the interview with Huang. The RIVA 128 was a 3D accelerator / video card for gamers, not game artists. Further, it was pretty clear by 1997 that 3D graphics for games was not a fad nor by that time was it a radical new approach -- Nvidia successfully entered an established market.

[1] Huang liked video games and thought that there was a market for better graphics chips. Instead of drawing pixels by hand, artists were starting to assemble three-dimensional polygons out of shapes known as “primitives,” saving time and effort but requiring new chips.
Leadership was asked why not find new roles for people getting laid off due to project cancellations at a time when we were still hiring like crazy in the immediate run-up and aftermath. The response was “we need to move fast.”

They encouraged those laid off to apply for open roles. But of course it read to employees as a monumental “fuck you.”
LBJ may have had JFK assassinated, and he exaggerated the Gulf of Tonkin incident to kick off US forces in Vietnam.

Bush got us into Iraq, for what?

This doesn't mean Kissinger doesn't deserve criticism.
Yeah, the -M command is wonderful (super handy for ignoring minified files that you don't want to see results from, etc), and also great is the -g command (eg `-g *.cs` and you'll just search in files that have the .cs extension).

Also the fact that it is a standalone portable executable can be super handy. Often when working on a new machine, I'll drop in the executable and an alias for grep that points to rg, so if muscle memory kicks in and I type grep it will still use rg.
The long version is:

/usr/bin belongs to the package manager for your distro. Don't put anything there.

/usr/sbin is the same but house executables that should only be run by root.

/bin and /sbin are analogous but house the minimal set that needs to be present during early boot in case /usr is on a separate partition. In practice, distros have largely moved to making at least /bin and /sbin symlinks to /usr/bin and /usr/sbin, with some making everything else a symlink to /usr/bin.

/usr/libexec holds executables installed by the package manager but meant to be run only by other programs, not by interactive users.

/usr/local/bin and /usr/local/sbin hold executables installed manually rather than by the package manager. By convention, the package manager should never touch this and it will be left alone during system upgrades. In theory, it holds executables meant to be used by every user of a system, but if this is a desktop system with only one user, putting your personal stuff there is harmless.

Not part of the FHS, but according to cross-desktop group standards, ~/.local/bin is where you put executables meant to be used by a single user only. The package manager won't touch this directory, but third-party installers like pip and what not should theoretically be using it (not ~/.cargo/bin like cargo does).

/opt effectively serves a similar purpose to /usr/local, but for software that expects all of its dependencies to be hermetically contained within a single top-level directory rather than shared. This is often because /opt is mounted via NFS and shared across multiple hosts that might not all have the same common system-wide dependencies. I can't think of a whole lot of examples where this is still commonly used, except that Kubernetes puts the CNI plugins here.

Also, technically if you're booting via UEFI, then your bootloader or any other EFI executables should be at the root of your EFI system partition, which in Linux will usually be mounted at either /boot or /boot/efi depending on the distro, but users should rarely be messing with this unless you're doing Linux from Scratch or really know what you're doing. This also includes Linux itself in a Linux distro because the kernel is an EFI executable now thanks to EFISTUB and you don't actually need a separate bootloader if you really know what you're doing.
SEC v. Jarkesy is a current SCOTUS case recently discussed here that's very much about interpreting the body of the constitution:

https://news.ycombinator.com/item?id=38441401
While I've also always thought about this model, I'm curious as to why Spotify doesn't do it? Is it hard to calculate the revenue from a single user? Or is just in their interest that it's complicated? (Btw it should probably be listening time and not nr of tracks, or we only get 30s tracks going forward).

Also, would law of big numbers make it so that this kinda evens out like this anyways with today's system?
Having standardized components like these is pretty valuable and reusable.

One could definitely write them on their own.

It’s also another way to discover other packages in these categories.

Some of the LXC container settings can be a little specific and these scripts manage those we’ll most of the time with a standard install, or an advanced one is available too.
Absolutely this. They just keep trying, one angle or another. They'll be back for another try in a year or three, with new arguments, and having purchased a few more politicians. In the worst case, they'll do something like the USA: institute secret programs that do whatever the heck they want, with no oversight.

Part of the problem is that there are no negative consequences. Again, look at the US: Snowden reveals massive, illegal surveillance. Consequences to politicians and government officials: zero.
>I think a better payout structure for Spotify would be to go per-user. [...] - I only listened to one song this month? The full 4$ go to that artist. [...] I think the current model of per-stream across the whole platform distorts the playing field towards more popular artists

Your idea has been suggested many times but as other sibling comments already noted, Spotify didn't have the leverage in business negotiations to implement that type of payout.

In other words, Spotify needed the vast song catalogs from the Universal + Sony + Warner -- more than those Big 3 Labels needed Spotify.

Your idea has higher payouts (i.e. "more fair") for independent musicians at the expense of less payout for the Big 3 Major Labels. In contrast, the current payout system favors the Big Labels at the expense of independents. Why did this happen? Because the Big Labels have more leverage.

Some factors leading up to the Big Labels negotiating from a position of strength to get more favorable treatment from the "weaker" Spotify:

- 2000: Napster lost its case against Metallica and RIAA

- 2000: mp3.com lost its case for "users CD-ownership-verify-then-playback service"

- 2003: Big Major Labels felt they got screwed by Apple & Steve Jobs iTunes deal with the flat 99 cents pricing.

By the time of 2011 licensing negotiations, they were already winning their lawsuits against the internet "stealing" their music. They were in no mood to give Spotify a sweet deal for access to their song catalogs.

This is why the no-name artists get fractions of pennies adding up a few dollars while Taylor Swift gets millions from Spotify. This unbalanced financial arrangement was the carrot to help get the Big Labels on board. To add to this, Spotify also gave the labels part ownership stock[1]. In contrast, smaller independents like CDBaby and TuneCore didn't get offered Spotify stock. Examples like that should give an idea of how much leverage the Big Labels had.

[1] https://thehustle.co/the-economics-of-spotify/#:~:text=The%2....
Yes I agree it does does 2 things, but remember my argument was to qualify that in the cases I mentioned I didn't think a PIP was passable. It doesn't mean you don't still have to do it, and yes, I guess in some extreme cases this raising of the stakes could be the thing that finally makes it "click" for the person that this is important. I just have seen enough PIPs and their pass-rates over a few years that I doubt them as a practical tool to actually get people to pass it. If that was the point companies wouldn't come up with a process with such a low pass-rate and would always be working to tweak the PIP process to increase pass-rates. Of course you might have different experience than this and I'll probably also change my mind if I see different outcomes in other contexts later on in life.
Yes, it has all been documented in a movie named idiocracy.
Simplicity is huge for reliability… but Volvos from that same early 70s era were also crazy simple yet used solid state boxes to control everything… and were way more reliable than the VWs.
The hardest bug I have ever worked with was an embedded device losing all data on the flash chip.

But the issue was, this was happening even after we removed all instructions to delete data from the flash.

The device had most traces between controller and flash completely hidden as a precaution for hacking/snooping, making it extremely difficult to diagnose the issue as the issue completely vanished in a test harness when the flash was connected to controller outside the board.

The problem also happened exceedingly rarely -- we needed about 100 of these devices to run constantly a certain operation and it took us to wait for about a week until one of these devices died on average. But we had millions of them in the wild and we would get hundreds or thousands die on our customers every week.

It took half a year of debugging and tens of millions of dollars in losses.

We found that one of unrelated components on the board emitted too much noises. And a software change to speed up writes to the flash removed a special sequence of that preceded and followed every one word write to the flash. This special sequence protected the flash from accepting a random noise as a command. Usually, the command would be something harmful or meaningless. But sometimes it would be interpreted as a real command -- and one of these was a command to clear entire flash chip.
Cool thing: you can set a window gap too.

Discovered the setting this week, my desktop looks so aesthetic now.
Seems weird to be writing about croissants here but the Costco croissants are no where near the quality of a croissant made by a skilled baker, to the degree it is hard to call them a croissant in anything but form. The ingredients, flavor, flakiness, number of layers, etc. are all inferior when compared to what is possible from an artisan. I've bought the Costco croissants a few times in the past to make sandwiches out of as that's about all they are good for.
Higher interest rates -> less money to invest into IPOs, I suppose. A number of zirp-times IPOs were... less than stellar investments.
Why doesn't it make sense to use in that case?
Honestly, if I were starting my career today, I'd choose a different career. I love being a developer, but the industry has changed significantly for the worse over the decades. Enough so that I don't recommend people enter it.
Sure, but none that compete with an EV. Can you name a hybrid vehicle from any manufacturer that matches up with a Model 3 or Y that isn't shrinking rapidly in market share? I'm amazed that people are trying to argue this point. It seems extraordinarily clear just anecdotally (count all the new Teslas around you!), and the data backs it up.
Yeah, I agree 1 and 2 tackle very different problems. For additional context on what I've observed

For 1: I work in the live streaming space and see cases where an input stream may need to be composited, transformed, mixed in, or something and an entire webrtc stream needs to be setup (usually going through some 3rd party service, e.g. twilio). OBS is normally the go to for a single broadcasted show however in the cases I work with it's a lot of shows (independent streams) that need to be managed and generally have rules around how the compositing works. Hiring a person to manage OBS, VMix, etc... is wasteful and expensive in this case (and not necessary). WebTransport helps in being able to deliver audio / video (or any data) to an app and take care of that. If anything I see this technology as making it easier to build apps for AV and hopefully getting rid of some of the reliance on existing broadcast software which is really intended for the traditional studio setup.

For 2: It definitely seems like adoption is growing. Cloudflare supports WHIP/WHEP (in beta), livekit supports WHIP ingress, and Dolby.io supports WHIP/WHEP (although thats not a surprise since Sergio Garcia Murillo works there after the milicast acquisition and he's at the forefront of some of those standards).

Regarding 4, cloud rendering, this is just mainly a use case I've had to deal with more and more of lately where folks are trying to get off OBS and VMix for compositing shows. An example use case is joining streams from multiple sources at scale (usually for large scale LED wall installations and such) and dynamically adding content / graphics based on interaction, data, etc....

It's much easier to program in the rules and have it be re-useable / configurable vs requiring someone to setup OBS scenes (at least at scale). I agree, I don't like the browser dependency (primarily since the devex is quite terrible for all of this). However it seems to be coming from a place of the lowest common denominator. It's easy for someone to whip up a figma/design of what they want and have that translated to html, use a motion library for animating, and stick it into a video feed (especially if you're trying to stick with an existing brand where you may already have a website and web apps with all of that ready to go).
Or maybe her scene was the only reason to watch that movie...
1. Thanks for this, instantly added to my dotfiles

2. You nerd-sniped me into getting rid of the unnecessary `cut` process :)

file=${result%%:*}
line=${result#*:}
line=${line%%:*}
What’s the term (may be colloquial) when law enforcement obtains information illegally but figure out how to fake or back fill the reason they know it so it becomes plausible in court they obtained the information legally?

It would be a more certain bet that they’ve done this with the AT&T surveillance than putting money in any cryptocurrency.
I think you can fix that incentive issue relatively easily by allowing people to choose the allocation arbitrarily after some sort of minimum tax, e.g.

The first $4 of your monthly sub is divided amongst all artists you listen to based on time spent listening, and any additional money you decide to add to your subscription is distributed to artists as you see fit. You can elect to use the same distribution algorithm as the first $4 of your subscription, use the same algorithm with different weights (e.g. your favorite artists listen time is doubled before payout is computed) or you can choose to have an arbitrary percent of it go to whatever artists you want, even if you don't listen to any of their music. Spotify already has to have a payment engine to support paying all the artists anyway, generalizing it beyond fixed subscriptions seems like an organic way to address the issue of unfair income distribution if they were interested in doing so (I don't think they are).

In the above system, the issue of "don't listen to other artists" only comes up if you don't have enough money to give to the artists you want to support, no different than the incentives of "don't buy the CD of artist A or you won't be able to afford the CD of artist B, who you like and wish to support more."
I find rectangle actually preferable to tiling, which I've tried on my linux boxes. Rectangle has the benefits of keeping the application-defined sizes (e.g. the terminal when opened up is 80x20 instead of whatever space is available on the screen) and playing nicely with the system defaults (like command-tab, command-~ to cycle through applications and windows). I find if I ever end up using a public or someone else's device, it's easier to cope; I'm not as helpless without rectangle as I was when I got used to a tiling WM muscle memory.

And the name of Yabai -- which translates to "danger" -- never sounded appealing to me to introduce into my device.
If anyone is looking at proxmox, running these scripts from the host will speed up experimenting.

It’s great to have something up and running in minutes to only redo it slightly differently.

If you are considering two proxmox hosts ensure the second one added to the cluster is an empty proxmox host, and the proxmox cluster from the first box will assign unique id’s to all containers on any host.
Could you give adequate sources, how you decide that 2014 was coup?
Firefox suffers from the same problem almost all other browsers suffer - it is ad-supported (indirectly in its case). This impedes its ability to be the real user agent, as its customer is the world's biggest advertising agency, not its users.

Like with Kagi search, we wanted to build a browser that gives power back to the user and aligns all incentives. We find this incredibly important.

This is why, unlike Firefox, Orion is both zero telemetry and comes with a built-in ad and tracking blocker. And also unlike Firefox, this makes Orion both privacy respecting and privacy protecting, by default. And that is just a start of things you get when you align incentives in a browser.
It works on my machine now too
Were you close to vest your stock options?
It is probably a way to give workers fake kudos without actually giving them anything.

A lot of north american modern management theory seems to think that praising your employees is the best way to get them to perform. By telling someone who's good but not great a "You got exceed expectations!!" they'll feel like they are valued.
I've seen all the replies before, and all of them take some random thing,

See, this is the problem.

Two random things this time, which are not based upon reality.

1) Driving distance

You missed the part about being a Canuck, and escaping the winter.

This means I, and more than a million other Canadians, typically take our cars. Why? Well if you're gone for 3 or 4 months, a car rental is far more expensive than just taking your own car.

And this applies for even shorter timed trips too. Not to mention, the amount of luggage you can haul.

And no, you don't have a better way. And no, renting a car doesn't make sense. I know. We know. We're the ones doing it, and we're not dumb.

It's an enormous cost savings to drive.

(Love how you tried to invalidate my statement that electric cars have no legs, by instead saying it's just silly to drive long distance(just fly!))

2) Speed limit

It may be reckless driving in your state, and perhaps others, but it sure isn't everywhere. Otherwise, 25% of the cars I drive with on my trips are all looking for that same charge. And by that I mean, I'm barely speeding.

But it doesn't really matter, now does it? Because a) everyone is doing at least 10 mph over, and b) I do 140km/hr.

And you still hit extra wind drag, and therefore reduced range specs as a result. And yes, moving from 100 to 140km/hr makes a massive time distance on long trips.

Always, people with random points that really aren't relevant.

There is no need to defend electric cars. They have their place, people are buying them, and range is slowly extending.

But for now?

Not for long trips.
In the 80's, a self-important white-haired Christian lady would have clutched her pearls about such a joke. In the 20's, self-important secular progressives have joined in on the moralizing and pearl-clutching.

The rest of us like to laugh.
The idea isn't to pander to the majority, but to include facts that at least a substantial minority believe are relevant even if most people think those facts aren't relevant. This would not make the majority feel pandered to, it would probably make most people believe the article isn't ideologically aligned with them which is the entire point. Democrats would say "why the hell is the article mentioning that Chicago is controlled by Democratic politicians? That's not relevant!" And Republicans would say "why the hell is the article mentioning that America's gun violence rate far exceeds that of other developed countries, that isn't relevant!" However in both cases they would have to concede that the article did include the facts they personally believe relevant (those facts which the other objects to) even though it also included irrelevant facts. This isn't pandering, this is impartially reporting the facts that some significant fraction of people might believe to be relevant while at the same time not conforming to their preferred narrative by omitting facts inconvenient to their narrative.

You can't pander to both at the same time. What you can do, and typically is done, is pander to one or the other by conforming to one narrative or the other, choosing or omitting facts according to the needs of one narrative or the other. That is pandering.
> llama.cpp already compiles and runs pretty much everywhere.

Well, it simplifies things when you don't need to compile things.

Also, you literally can't download or compile the wrong binary by mistake, it's the same binary for all supported processor/OSes Cartesian product matrix.

> Why introduce one more container?

It makes stuff more convenient.

`application/zip` is also a ubiquitous standard. I doubt anyone is being "introduced to it".

I also appreciate the fact that tooling for handling `application/zip` is very widespread, so you don't need totally bespoke tooling to retrieve the models from inside a `llamafile`.

> Who benefits from binary distribution of this sort?

Anyone that doesn't have a compiler SDK on their computer.
Hardware is doubly hard when you are as international as AirBnB. Wifi has to conform to local regs with regard to channels and tx power. I wouldn't be surprised if there were varying local regs for CO detectors, too.
In that era (when I spent some time in the music industry) it was common for labels to tell artists to not release 12 "Good" tracks. It was more like 3-4 Good tracks and then basically Filler tracks/B-side quality. But if you wanted the Good tracks, you had to buy the whole CD, and you might listen to the Good tracks 30 times, but the Fillers a lesser amount.

This makes the per-track payment extrapolation from CDs somewhat challenging as these days users have more control over specific tracks, and artists can also do a track-only release as easily as a full album release if they want.
> I'm not sure how old you are but when I was growing up in America in the 70's, eating out meant either high-end/pricey restaurants or MacDonalds, Burger King, Pizza Hut, or Taco Bell.

I grew up in US flyover country and I remember the 70s and that's not the case.

There were diners. There were mom- and pop-owned holes in the wall. There were more respectable "family restaurants" that didn't serve what was called "ethnic food" at the time but were certainly not fast food and were also reasonably priced. I remember my 15k-ish population town's one Italian restaurant and its one Chinese restaurant and the short-lived Greek place, none of them chains but all highly Americanized. Half an hour away in a nearby small city there were many more options.

> Now you can get Thai, Sushi, Indian, Sichuan, and more.

Those are all things we can find in the present-day equivalent of a 70s food court. They're part of the new fast food - mostly garbage.