skysight-inc/HackerNews huggingface dataset:
I'm on nvidia, x11, kde plasma, ... its probably some firmware package for something instead.
Git is conceptually simple but has a baroque UI. I really recommend spending 15 minutes to understand it conceptually:

objects: blobs, trees, commits, annotated tags

refs: branches (local, remote-tracking), tags, HEAD

other: working tree, index (aka cache aka staging area), remotes

There's lots of good guides out there: git from the bottom up, git for computer scientists, and the git parable are some that spring to mind. The Git Book is also excellent but it's more than 15 minutes of your time.

All the commands become way less mystifying when you understand what they are manipulating. You'll never get into a state where you want to `rm -rf` the entire repo and start with a new clone. There will hopefully be no more teeth grinding or keyboard mashing.

I've used a lot of VCSs over the years (rcs, sccs, cvs, subversion, clearcase, mercurial, git) and I swear git is the one I find least frustrating. The others may have had simpler interfaces, but they were either conceptually more complex, overly rigid in their design and behavior, or both (looking at you clearcase).

Look, I get it: a lot of folks see git as a necessary evil that's part of their day job. I disagree. I think it's really worth spending the time to learn well, probably like you invested some time in your editor and other tooling.

I mean, it's easier than C++. :-)
I guess you could achieve the same (or a similar) workflow remotely by using fax machines.
*Brave
This is historically not how it works. You do not own the records the bakery keeps of when and what the oven is used for. If the cops want to pay for that record keeping you have no say even if you've ordered a cake from that bakery. The fact that you did or did not use the cake to smuggle a hammer into a prison is frankly unrelated.
[i work at Hugging Face]

BTW the reporting in this article is sloppy/incorrect
This is a REALLY GOOD point of feedback. I have done literally nothing for ASO, and what you are saying reflects the reality that I don't see many organic downloads in the App Store. Definitely going to look into this!

On the iOS dev hours: yes, the $120 has been more aligned to seasoned talent with U.S. rates and the $80 has been more aligned to talent outside the U.S.
If you learned from this (excellent) piece, I recommend that you buy and work through https://leanpub.com/learngitthehardway . It will take less than a day, and you'll have a much stronger foundation for a core tool.
I think Linux users will try to help themselves, will check for the application output, find the logs, ask for help and help each other to troubleshoot.

I made an app for Windows, and it was hard to explain the user how to find the log file in %appdata% , after a few support cases I just made a wizard for the users to use it and send the logs to us because it was to hard for them to find and submit a log file.
While the explanation is right in some sense, it misses a few points.

Branches are pointers to a commit and that pointer is refreshed when a new commit is created. One could say they are a wandering tag (without explaining a tag for now).

The actual chain of commits that represent what we see as branch comes from the commits themselves. Those commits point back to their parent commit.

And then one can see why no branch has any special meaning: It is a chain of related commits with a named entrypoint. Once you delete a branch (i.e. the named wandering pointer to a commit), you cannot identify a branch as such anymore. It is just a chain of related commits without a named label now. And nothing besides the name distinguished the branch from other commit chains before.

The master/dev/release branches are then a convention to keep an updated commit pointer on the chain of commits containing changes of interest.
It's unpleasant, but it's not pointless. We've just had days of uninformed and uninvolved randos micro-analysing all things Altman, and pushing various wild speculations. This is seen as okay as long as it's confined to what is essentially office intrigue and gossip. But on the much more consequential topic of potential childhood sexual misdeeds -- nothing.

We don't know whether there's any means of verifying the story until people actually put some effort into verifying the story. Also, it's not unprovable. Perhaps in a mathematical sense, but that's not even required in a courtroom.

Consider all that's been written about Altman's character, using such weak signals as "this former co-worker said this about him". Meanwhile there's this disturbing piece of information that could be a strong signal that is completely ignored.

Have you spoken to anyone in your life who has been molested, or abused? It really cuts through the abstract arguments and illustrates that this dynamic is how abusers get away with it.
Return to Work Is Coming for Your Pandemic-Era Home
You are probably missing "git add" but otherwise, it is fine... unless you fuck up.

Unfucking thing is what of most of my knowledge of git goes to. Committing in the wrong branch, the wrong files, starting from the wrong commit, etc... Before you push, almost all mistakes are fixable, but it requires knowing a few more commands.

Then there are the project specific things. For instance, I worked on a project where we didn't have a central server we could push to and pull from (airgap). So we had to work with bundles. Git does that really well (it really is decentralized), but it is uncommon. Some people prefer a rebase-based workflow, some use cherry-picking extensively, some projects are more prone to conflicts than others, etc...
Some of Julia's tweets started to get suffixed with "I don't want advice about this". It must have reached unacceptable levels.
Streisand effect in action, can't wait to read this now. :) https://web.archive.org/web/20231121200115/https://insideroc...
Any link for the new hardware quirk added to lsdj?
> Some people insist that Linux distributions be called GNU/Linux, not just Linux. The reason is that, strictly speaking, Linux is just a kernel and, when you are using a Linux system, you are primarily interacting with the GNU userland. While I sympathize with that idea, I’m not the one to adopt the GNU/Linux name, in part because most Linux distributions today ship with software developed by many more vendors than just GNU. In this post, however, I use the GNU/Linux term because saying Linux alone would be unfair to Linux.

Hear, hear!
This is my favorite. It allows one to easily create "service" branches based on tags where you apply to that tag a select set of commits from the development branch that you can then easily deploy to PROD without including the rest of the (perhaps not sufficiently tested) commits and without having a convoluted branching strategy.
As opposed to being responsible for maintaining and doing operational support of the service...

I still don't get what advantage exactly you are expecting.

Scaling it is only ever a problem for the service; you don't even have to think about it in a library. You can get telemetry from a library just as well as from a service; your users may find that a bit invasive, but it's still way less invasive than calling your service. And you can replace the internals of whatever, without having to worry about who will get affected, that's what defines internals.
Any source on what they actually capture? Seems interesting to me.
I want to see studies to measure the impact of disease transmission in a hospital.

Pick a random (perhaps new) hospital, and make every patient live in their own sealed plastic bubble. No air goes in or out - instead it is recirculated per-patient like a space station. Make staff wear hazmat suits.

Then, after a few weeks, compare patient outcomes.
Does it work for background jobs as well?
I agree. Yes, you can. Quill is the example here.

Actually, back in 2015 when we started prototyping CKEditor 5, we started with this approach as well. Our goal from the beginning was to combine real-time editing capabilities with an engine capable of storing and rendering complex rich-text structures (nested tables, complex nested lists, other rich widgets, etc.). We quickly realized that a linear structure is going to be a huge bottleneck. In the end, if you want to represent trees, storing them as a linear structure is counterproductive.

So, we went for a tree model. That got many things in the engine an order of magnitude harder (OT being one). But I choose to encapsulate this complexity in the model rather than make it leak to particular plugins.

In fact, from what I remember, https://github.com/quilljs/quill/issues/117 (e.g. https://github.com/quilljs/quill/issues/117#issuecomment-644...) is a good example of issues that we avoided.

I also talked to companies that built their platforms on top of Quill. One of them ended up gluing together countless Quill instances to power their editor and overcome the limitations of the linear data model but is now looking for a way to rebuild their editor from scratch due to the issues (performance, complexity, stability).

So, yes. You can implement a rich-text editor based on a linear model. But it has its immediate limitations that you need to take into consideration.
This is great news, have to say i love they keep taking whacks at it.
If you can maintain a stable service API, why can't you maintain a stable library API?

I don't see any inherent reason why it should be easier to change the behavior of a service rather than a library.
So you're implying those are one and the same set?
> A commonly said piece of feedback from someone who's learning Rust as a second language tends to be that enums are far better supported in Rust than any other language.

This is nonsense. I doubt that this is common feedback and it is just not correct that it is far better supported in Rust than in any other language. Why would anyone say that? Rust pretty much has support for ADTs, sum types and product types. Just like any modern (functional) language has.

Haskell, Scala, F#, OCaml, etc.

(And I love rust, write it in my day-to-day as well as on my spare time.)
It's all fun and games until you hit version n+1 or n+2, and often realize how slow many customers are to upgrade the library. Then there are the potential conflicts in your own dependencies. And let's not forget the occasional breaking change you introduced.

You are now sacrificing the money saved by not hosting to maintain what will likely be a growing matrix of possible versions, underlying assumptions, and my personal favorite: weird customer deployment scenarios that break your library functionality. Bonus points if you are developing in a language without strong typing, or need to integrate with a dependency manager.

Plus, if there was anything about your service that leveraged unique algorithmic improvements or some other proprietary tech, it is now at the mercy of anyone with a decompiler and sufficient time.

I suspect the author may change their mind if exposed to scaled up solutions and technologies.
[citation needed]

also though if we're talking about such mega-engineering projects you can float them on the ocean, which has a lower albedo than solar panels. or use some of the energy to make a lot of white plastic netting and drape it over a low-albedo region
Amen! Thank for that encouragement. I think you are right. I need to be calculated and disciplined about it. A short-break would do me some good, and I'm sure my family would agree :)
Or you internalize the functionality with a library.
> No, I clicked the adjust for inflation button.

Generally we have to adjust much more for inflation, as official inflation numbers are mostly fraudulent.

I agree with you on the cost of producing and distributing music going down, and I think it's fair to say that the creative part is easier and cheaper as well.

But don't people have more time to listen to music today when it is accessible everywhere?
: ${FORCE=no}

Also, it's not so difficult

while getopts :hab:c o; do
case $o in
a) opt_a=x ;;
b) opt_b="$OPTARG" ;;
c) opt_c=x ;;
h) usage 0 ;;
?) usage 1 $o "$OPTARG" ;;
esac
done
shift $((OPTIND - 1))
D=/nix test -d $D && echo $D exists …
Does size matter in Pull Requests: Analysis on 30k Developers
Or:

git reset --soft HEAD~1
This scene is at least 7 hours in, at episode 1 no one ever expects Maeve, the sex worker to be such a focal point in the series.

Her being the first to wake up this way and become more conscious is a huge spoiler.
no.

but they smell quite funny since many years ;))
I don't get it. Can anyone kindly share where this practice can be applied to a commercial software? I am struggling to wrap my head around "how run by user" works where they are using a commercial software service.
I had a weird one on my network I never managed to solve before I moved:

I had symmetrical 1gbps up and down. When wired, I could get nearly the full amount on the WAN. When wireless, I could only get 300mbps to the WAN.

However, when wireless, I could get ~800mbps to another device on the LAN. I could also get 800mbps to the internet if I proxied from my wireless devices to my wired device before going to the WAN.

My router company sent me two additional routers, one with a similar chipset and one with a chipset from a different vendor and this persisted. I checked it with a competing router and it persisted.

It did not matter what the wireless device was, Mac, windows, phones, or tablets, and it persisted.

Moved somewhere else with a different ISP and it immediately stopped. I still don’t know how an ISP would identify and throttle a wireless device, but that was pretty much the only explanation I could come up with.
BitKeeper already did it.
Oof, this is terrible news, might have to treat all of these materials as hazardous and incinerate it all instead of reusing.
Maybe has customers but it did not seem to be widespread knowledge outside, if it was known for year widely then I can not image why Veeam would have devoted developer time to support a product that announced its EOL just a few months after they released their support for it.

Seems odd.
While I agree with you, I can understand going with enum so that they don't scare away the C and C++ crowd with being too fartsy with theoretic stuff.
Modern broadcast is a completely different animal than it was for the original. It is however, not encrypted, yet, so it's not impossible.
Throttling, tarpitting, and circuit-breakers are something I'd love to visualise in future, too. Throttling on its own is such a massive topic!
The hamburger menu has a "viewing mode" option, under which lies a "research" toggle. The UI there might be more to your liking.
They both pay approximately the same for premium subscribers, and Apple's trial period pays approximately the same as Spotify's ad supported model. They're both trying to drive premium subscriptions, which make both them and rightsholders more money, but using different strategies to get there
As a Linux user I was trained to never report any bugs if you use the proprietary Nvidia drivers, because the report will just be dismissed (no matter if the stack trace indicates the crash being Nvidia's fault). Though I guess for a game this would finally be different!

In fact I submitted a fix for a crash in a game (you can compile it yourself, but not open source license) that affected all OSes before.
Ask HN: How are you using LLMs in your personal projects today?
I started working with AI / LLMs recently, and now I'm learning about the ecosystem. The possibilities seems unlimited and I know many use cases for big companies. However, I'm curious to learn about what people are hacking with LLMs on a personal side.

What are you building? What are you solving with LLMs? How do you run them? How do you integrate them in your app / service?
No, you, and the author, are assuming the antecedent which we have to do to make your question relevant. If we do assume that what is done in public, which you've willfully involved a 3rd party in, is somehow 4th amendment protected- it isnt and never has.
Apple/OpenAI Holiday Film
Pararells between Apple film and what hapened in OpenAi
For me the best learning resource has been Mozilla Developer's Network (MDN). It serves as an indispensable reference to the language specifications, browser compatibility, as well as plenty of examples and guides.

Learn web development (HTML, CSS, JS) - https://developer.mozilla.org/en-US/docs/Learn
A solution to A16Z Nakamoto challenge on "Compliant Programmable Privacy"
Wins looks really good, and congratulations on having sold so many licenses! This is just my opinion, but I think you’ve priced too low. It’s an interesting balance and I don’t know the magic formula to pricing but before I looked at the price I looked at the features and my first guess was $30 and was surprised to see $6.99.
This is talking about "Clostridioides difficile" bacteria, so despite the title it is not about how difficult it is to get rid of those bits of legacy C code nobody understand any more.
Plus the title makes no sense to me, "Final Release" ?

After people just finished struggling to get to v3 of SSL, if that is true, I would say people should move to LibreSSL.
https://github.com/openzfs/zfs/issues/15526#issuecomment-182...
Background sounds distort concentration and verbal reasoning performance (2021)
Developer, pull request thyself (2019)
> but it’s not graphics programming.

As someone who’s been in the field for a long time, I kind of disagree. Game engine jobs don’t define the boundaries of what “graphics programming” means. That is a very narrow and specific kind of graphics programming, and there’s lots more graphics programming than just games. I’d probably even recommend people wanting to do games graphics programming to start outside of games, because the engine consolidation with Unity and Unreal has brought with it an overall reduction in the number of people doing graphics programming for games. There’s indie games and a few studios that still do their own engines, but there are a bunch of other industries that hire graphics, for film and effects, for 3d tools, for visualization, for mobile/web/desktop applications, for science & research, for VR/AR, for industrial applications, etc., etc.

Being fluent in C++ can only help you, so do work on that. Games engines need more and more people who can do ray tracing and neural nets, and some of the old guard of raster API experts didn’t learn as much about those things, so that is one angle of attack for getting in. Another is to be very fluent in the math of graphics, and you can learn and practice that in any language, and find non-games jobs that will pay for it. Math experts are generally more valuable and hard to find than API experts.

FWIW, my path was graphics in school, undergrad + MS, then scientific visualization for a university, then C programming for a CG movie studio, then I was hired to do games engine graphics programming (precisely what you’re talking about) and I moved into a tools generalist and gameplay lead role instead (which was more fun than wrangling shader compilation), then I went to a web app company and did 2d graphics while learning JavaScript & WebGL, then started my own web app company using javascript & WebGL, and then switched to doing CUDA and ray tracing with OptiX. Along the way, lots of fun graphics projects in Python. All of this involved real “graphics programming”, and almost all of it is outside the boundary line you drew. I say this not for argument’s sake, but to ideally give you more hope, and to help you & others see there’s a wider range of options to get into game graphics than ‘learn C++ & DX’.
Yes, some small town cop might not have any oversight and if he starts requesting phone records of "famous" people it can quickly become a huge issue not that warrent-less access isn't already an issue for everyone else.
They say:

> The second reason, which mainly makes sense with our terabyte services, is to have a high limit but one that deters the really heavy users, i.e. the people that literally use hundreds of times the typical usage. By excluding such customers from these services we can provide a faster and better services to our customers
Your response makes it sound like you think circuit breakers are server side and not related to retries. They are not; they are a client-side mitigation that are a critical part of a mature retry library.
"where possible" is a keyword here and easy to argue about. For example:

* my logic requires a database
* my logic should be isolated for compliance reasons
* my logic accesses a service which is not available for everyone
* my logic should be processed async and needs to store state, how do I make sure library owners have that environment
* customers embedding my library are not upgrading it frequently, which leaves us to support 15 years of libraries
* ...
Yeah, we've known C. difficile spores are also resistant to alcoholic solutions. Pseudomonas can contaminate hand soap too.

It is recommended to wash your hands with water and soap, but if there is no visible dirtiness, hand sanitizer will do.
Computer Scientists pick the best names for things
I wonder how this will affect Spring.
That doesn’t seem like the opposite to me. It seems like the same thing. Rather than rejecting people’s intuition as ‘understandable but wrong’ why don’t we use it as the basis for a better solution?
I know nothing about this stuff, but as a bit of off-hand advice I'd guess leaning heavy into social media / influencers would be a good way to get traction for a fitness app. You could also organize local free workout events to help push the app.
>after a few support cases I just made a wizard for the users to use it and send the logs to us because it was to hard for them to find and submit a log file.

There must generic libraries for this?

Whats the standard way to do it? Do they get sent as email? as Post request to a server? or does it create a ticket or github report?
Some times one guy will have headset, but everybody use various setups quite randomly.
I was stumped the first time I read about Graal. It felt like 15 years too late and made zero sense to me.

Please, if you could share more about that, I'd be happy to share the pain
While I understand your argument about IE6 which was shipped with Windows, Chrome didn't have that advantage for a long time - it's only now that Android phones and Chromebooks are shipped with it, but I don't know of a single person who does not download Chrome on their Windows Desktop too - even now when Edge is based on Chromium! Firefox has always been my primary browser (it still is, I'm typing this in Firefox), but say what you may, Chrome has taken the internet forward in many aspects. I work on an in-browser CAD tool, and I can see how vastly better Graphics performance is in Chrome when compared to Firefox for example (and it's just one example).
License fees, just like the old days. Either fixed cost to license the library, a royalty based scheme (# of users/installs), or both.
I have personally used fastmail and I am happy.

I have personally felt Microsoft/Outlook service is better than Gmail. I have a couple of clients in shipping business, and they had issues with Gmail. Moved them to Outlook in 2018 and they are still happy.

Of recently, I have suggested Zoho to some clients. Its been good.
They don't have insight into what the actual artist gets. Spotify pays distributors and labels, who have their own contracts with artists.
Microsoft has managed to resurrect from the dead though. Now it feels like a “fresher” company than Google.
Correct link is here: https://old.reddit.com/r/SideProject/comments/181a6pu/my_jou...
You can't argue with "the truth" here. Global warming has been a mainstream scarecrow for decades now.

In truth, it was just a way to slow down the growth of rival industrialized countries, or countries that are yet to industrialize. By promoting expensive, inefficient "clean" energy sources (but not nuclear!), they are stunting the growth of developing nations.
AKA, the classic case of the Ford Pinto

https://en.m.wikipedia.org/wiki/Ford_Pinto
Amazing series. Great refresher on assembly too.