skysight-inc/HackerNews huggingface dataset:
Yes, But I would say that is a minor issue; I appreciate that there actually is lots of documentation for the precise and unchanging behavior of `git branch`!

Instead of:

"Oh, email this to doc management. Depends on who you get. If you get Nancy, she will double check that your rev C filename matches with your rev D filename in the changes section. Matteo does it differently though, sometimes you do need to include redlines for minor AND major changes, even if the major version gets rev'd. Oh, that doc doesn't have any minor changes at all. I don't really know why, but you better not include minor changes because that will be flagged for sure, only on this document though, for every other one you should have C->D in the footer. Oh that one, the template never got updated so you actually have to type it in manually. Yeah, no idea why it does that.

It would be great if you got the change review back by Wednesday because regulatory has a preliminary product summative scheduled Monday. There's a confluence page for which doc manager should be CC'd for each document to get the review back in time."
> Pretty convenient that he wasn't the candidate, right?

Convenient for some (roughly: the better off), not so convenient for others.

>Suddenly you could pat yourself on the back, convince yourself that your hand was forced.

Provided one has an adequately powerful imagination I suppose.

>There are loads of situations where people try to rationalize their own behavior through mechanisms like this.

Or their beliefs!

> Two fish are swimming along and they happen to meet an older fish swimming the other way. The older fish nods and says "Morning boys. How's the water?" The younger fish beat the older fish to death and take his wallet. "He should have known I'm allergic to water!" one lamented. "He made me do that".

I'm not sure I understand the anecdote, could you explain?
It's just like in Kotlin !
Simon & Schuster sold to private equity firm KKR for $1.62B
I'm not sure if there is a document that mentions this in particular, but it is a consequence of how lifetimes work. The core issue is that .as_raw_fd() takes &File and returns an integer (which doesn't have lifetime information). As a result, the File is dropped at the end of the statement and thus the number you got from .as_raw_fd() is invalidated.

This does happen elsewhere in Rust, but often when you have methods on &self that return something you use later, the method returns something with the same lifetime (fn foo(&'a self) -> Foo<&'a>) and thus the original object will be kept alive until the end of the scope. It just so happens that file descriptors are tied to the lifetime of the File in a way that Rust cannot express nor detect.

I don't know if clippy has a warning for this particular case. It might be useful to add it.
As if four Google engineers advanced a proposal to make sure ads on the page get served because of their own, non Google, interests.

"They just love ads!"
Cool stuff - but there’s no need for react. Not sure why web developers are fixated on that framework.
> You agree to grant and hereby grant Zoom [...] license and all other rights required or necessary to [...] create derivative works [...]

> [...] for the purpose of product and service development, marketing, analytics, quality assurance, machine learning, artificial intelligence, training, testing, improvement of the Services, Software, or Zoom’s other products, services, and software, or any combination thereof [...]

Those two clauses, coupled with the current murky state of AI-from-copyrighted-material, should make everyone run screaming from Zoom as a product that can be entrusted with confidential information.
This looks excellent! It's a great interface for two things I'm struggling to make LlamaIndex do: explain and debug multi-step responses for agent flows, and cache queries aggressively. If I can work out how to hook it into my LlamaIndex-based pile, happy days.

Feature/guidance request: how to actually call functions, how to loop on responses to resolve multiple function calls. I've managed to mock a response to get_current_weather using this contraption: https://pasteboard.co/aO9BmHG5qsFt.png . But it's messy and I can't see a way to actually evaluate function calls. And if I involve the Chat Turn node, the message sequences seem to get tangled with each other. Probably I'm holding it wrong!
With respect, I do not think this is a newsworthy case.

> Mr. Kirkhorn will continue to serve Tesla through the end of the year to support a seamless transition.

Absolutely zero things to discuss here.
Actually the vast majority of the time it's not at all a big deal. The average tenure of a CFO among the S&P 500 is 3.5 years. It's really not a big deal.
Or any of the Tesla workers that have been subject to the company's culture of racism: https://www.latimes.com/business/story/2022-03-25/black-tesl...
That does look like a serviceable intro to those topics and fantastic in total though.
I think I'll get myself a copy of the latest edition. I recognize the design, but I've never looked more closely before.
Thank you!
When I formed my first company, I tried to min/max my costs and tax savings. In the end I accomplished neither buy forming a California LLC with C-corp taxation. I did a very good job of not correctly reading a DIY book how to set up your own business. When my accountant saw it, he said “Wow, I’ve never seen one of these before. You picked the absolute worst possible choice. I’m going to show this to my friends!”
There is no reason why it could not continue to use the exact representation and operations if it wished (and that's what FatRat does). It's just an ill-conceived concession to performance.
> Yes, Kirkhorn "will continue to serve Tesla through the end of the year to support a seamless transition", but this reads as a rush notice.

I don't own any $TSLA (or one of their cars), but this is like the opposite of a rush notice. Heck, he will continue working for Tesla for almost half the year. Seems like typical HN "everything Elon does is bad" bandwagoning.

I mean, just earlier today the HP CFO resigned[1] and was replaced immediately.

[1] https://finance.yahoo.com/news/hewlett-packard-enterprise-cf...
I made an electric longboard a few years ago. Before they where popular, and you cant buy or legally use it in germany anyways.

It worked pretty well. I guess it could drive s.th. like 35 km/h for 10 km. It even had brake energy recouperation. A higher topspeed would be no problem, but its already very dangerous^^

It was a very simple design. Just a brushless outrunner attached with friction to one of the wheels.
Fedora Linux on M-powered Macs will be here shortly
> Has anyone put together a resource - or better yet, an automated service - for migrating away from Google (Gmail in particular)?

1. Set up a new mailserver/register an email somewhere else;
2. Google Takeout your existing data;
3. Redirect all your incoming mail from GMail to your new email address;
4. Change over the email address of all services you use.
AFAIK it's finding out what prompts to use for what LLM to get the answer your want

E.g. this

> Compare response quality across prompt permutations, across models, and across model settings to choose the best prompt and model for your use case.
13 years is a long tenure as CFO, on surface this means nothing.
Why the hell is HN doing that...
The article confirms my suspicion that it's not going to be great for productivity. Limited FOV, hard to read things, limited/more difficult input methods, and it being tiring to wear for a stretch of time.

It also doesn't seem to be designed for gaming, not for games where you move a lot and require fast and precise input.

The part of the presentation where usually developers show their finest creations this time was rushed and showed low poly toys apps as we've known from AR apps for a decade now. Sure, you can say it takes time for the ecosystem to develop, but that ignores a big problem.

It doesn't just take time. It's beyond the reach of most app developers entirely. It's extraordinarily expensive and difficult to build a compelling 3D world that is convincing enough for somebody to want this device as well as keep that headset on. It needs to be spectacular and convincing. Because ordinary consumer experiences, say the PS5, already deliver that fidelity and engagement. You need to up that significantly given the cost and discomfort of this device.

It seems to me that only the likes of Disney can pull that off, and not the small app developer. Even for Disney it will be a questionable ROI.

So what remains? A device for solitary passive entertainment? In a world already saturated with digital experiences and content?
Accelerate SF – an AI hackathon to solve challenges in the city
He has worked at Tesla for 13 years. When would be the right time to go? He’s already done very well from his stock grants.
It's just the languages everyone knows are bad.
A classic anticompetitive case of 'the rich get richer'. The world's wealthiest corporation, Apple, which closed today with a $2.8 trillion market cap, uses its money to (1.) ensure none of its competitors can make 3nm chips, so competitors cannot initially offer the same performance per watt, and (2.) force TSMC to eat costs that smaller competitors normally must eat. Apple did this same thing when launching the M1 and many praised the M1 as revolutionary....

If you compare Geekbench scores[1][2] and top 500 "green" supercomputer rankings (gigaflops per watt)[3], you see x86-64 still reigns supreme not only at peak performance but also real world scientific performance per watt:

[1] https://browser.geekbench.com/processor-benchmarks

[2] https://browser.geekbench.com/mac-benchmarks

[3] https://www.top500.org/lists/green500/list/2023/06/

Apple's laptops nowadays essentially amount to ultra premium Chromebooks. Nice rigs for running a web browser and doing npm+JS dev. Everyone doing serious AI and science is on AMD64 though, particularly AMD64+nVidia, running either Linux or Windows+WSL. The cheapest Apple you can buy with 64GB is $2399 (Mac Studio). Go to pcpartpicker.com and you can build a nice 64GB rig for under $1000 and get minimum 3 to 5 year warranties on all the individually user replaceable components you buy. But if you buy a Mercedes for 2.5x the price of an equivalently comfortable Toyota you get to flex that three pointed star badge on the front of your car....
4 months seems like plenty of notice, and the opposite of a rush.
Exactly. Since CFOs are in charge of the numbers and can be legally on the hook for them [1], their departure always gets people to perk up a bit. Even if there isn't crime involved, when they guy who knows the financials best decides he'd rather be elsewhere, it can be a sign that there's a coming plateau or downturn.

That's especially interesting in the case of Tesla, whose stock is down something like 40% from peak, and who is facing increasingly stiff competition from basically every automaker in the world.

[1] e.g., "fraud by negligence": https://www.reuters.com/business/sec-charges-smart-window-ma...
First, that user just posted a link, so accusations of "stealing" are out of line; take it up with Santa Fe Institute. Second, your response to a link to a PDF paper is to post a Twitter link? That's laughable. Well, I laughed, at least.
Aren’t old line companies like TI and ADI king in that market?
If you block all of Google's IP addresses, the web is kinda broken
It is not really a "niche". The ".NET world" is more-or-less everywhere: it is cross-platform, open source, and runs on Linux/Windows/macOS/iOS/Android/more.

The ".NET world" is comparable to the "JVM world" or even the "LLVM world": a virtual machine target with a varied language ecosystem and a lot of real machines supported at runtime (in a cross-platform, open source way today).

".NET world" is defining a complex language ecosystem, and it probably isn't as "limited" an ecosystem as you seem to think.
Bottom of the 8-K document says "Date: August 7, 2023". So possibly (I'm not familiar with SEC filings) filed late Friday after business hours Aug/4h and then it got published by SEC Monday Aug/7th at start of business day?
cheaper than zero???
> an alternative approach might be to buy a piece of land and start building for yourself

Yeah I thought about that... if only land was not so expensive in Europe and UK. I can't afford to do this investment by myself just yet, but that is what I'm working towards anyway.
Redundancy in title:

"US scientists repeat fusion ignition breakthrough for 2nd time"

is no different in meaning from

"US scientists repeat fusion ignition breakthrough"

Yes. I know that's being pedantic. But it's something that just screams at me.
Just to put things in context, the average tenure of a CFO among S&P 500 companies is 3.5 years.

I don't think that's a big deal, but apparently people commenting here think a CFO departing is some kind of major signal of something. At any rate, it's at least worth knowing quantitatively that this happens once every 4 years or so.
> With the notebook you have a single password compromised which has the chance of serving as a canary to detect the compromise.

This sentence makes no sense. There is no canary with a password compromise. Either the site compromised announces the compromise, or a security researcher finds a new list for sale on the dark web and announces it, or nobody knows about it. The password generation/storage method does not matter.

But you definitely will have a huge pain in the ass to figure out alternate passwords for sites when they do get compromised and need to be rotated. Obviously you can't replace this sheet or you'd be resetting all 268 or whatever passwords you currently use.

> With a password manager potentially every password is instantly compromised.

Sure, but the same is true of this weird password map on paper thing. Any "algorithm" most people could actually use to "decode" passwords on that map can be trivially defeated by an amateur. That's why we stopped using paper ciphers like 150 years ago.

> I'm talking about using passwords that eg. are a combination of a notebook part, and a secret only you know, thereby having a unique password for each service

Or you could use a password manager, and just have unique passwords and no memorization.

> If you have to pay attention to security researches to use a package manager it is already impractical for the wast portion of the population.

It's not impractical at all, just use BitWarden or 1Password. This isn't rocket science dude. Just do what security expert tell you to do. (Hint: NONE of them suggest writing passwords down)

> Remembering 239 secure passwords, even with a mnemonic is a fulltime job. It's not in any way realistic.

So. Use. A. Password. Manager.
> I never understood why devs who work for game and movie studios don't quit and work for companies that pay 2-3x as much - other than for the pure love of what they do.

A very real aspect is credits. If you're developing some SaaS product or whatever, you stay a nameless cog in the wheel, and in the worst case your entire work was for nothing because the company goes down in flames anyway.

In contrast, games, movies and (at least it used to be) music? That's for eternity, even if you're an accountant or someone else with barely a tangential role to the production, your name will still be somewhere on the credit rolls. Something to one day show your grandchildren and say them "that was stuff I worked on, these were my colleagues, and these were the best war stories". And your grandchildren can brag to their friends at school "my gramps used to make Marvel movies, one he worked at is still in the top 10 of highest grossing movies ever". You leave actual legacy behind, and the jobs that offer this opportunity are rare. This is why people keep going to entertainment.
I hate to say this, and I don't wish death on people, but lockdown was good for the planet.

To be brutally honest, if a rogue CIA wanted to slow down CO2 emissions, that sort of virus was a good fit.

I really wish humans would organize and agree to reduce emissions, but since it's geopolitically just not really happening, that virus is a good coincidence.

If it was engineered: good. If it wasn't, that's also nature reacting the appropriate way. If it was negligence, it was a happy one.

Disclaimer: I have chronic depression, and a therapist told me that I felt happy during lockdown because average people were finally sharing and experiencing my distress. It really stuck with me.
Anywhere. There are lots of examples on the topic ; running NetBSD driver code inside NetBSD's user-land is the simplest use-case (https://www.netbsd.org/docs/rump/sptut.html), but that code is portable without modifications to just about any context possible.

Check out Antti Kantee's The Design and Implementation of the Anykernel and Rump Kernels if you want details on the architecture.
Here's my current workflow:

1. write some code on a local branch

2. upstream has new revisions? rebase my branch on top

3. if not finished with my task yet, go to 1

4. if ready for review, open PR

5. if accepted, squash and merge

6. if changes are requested, write more code

7. upstream got more commits causing a conflict? don't rebase! it will screw up the PR history on GitHub and can cause issues for reviewers who might've checked out your branch locally and maybe done some experiments. merge upstream into your local branch. then you can push fast-forwardable commits.

8. push new commits to PR and go to 5

I used to think of rebasing as just rewriting commit history. But now I also think of it as altering the history of collaboration that is captured in a PR. So I switched from rebasing onto new upstream base branch commits and force pushing to PRs that already had reviews, to merging in new upstream base branch changes. I only do this after someone else has done anything on my PR; if I open it but nobody has reviewed yet, I'll do the rebase/forcepush to keep it current until someone does.

I prefer squashing to merge because I prefer the default branch to have one commit per unit of collaborative work. The way different people split up commits on a branch is arbitrary and varies widely; you'll never get more than 2 engineers to agree on a convention here. Keep all the messy stuff in the PR, and you can always revert one of those individual commits if you want finer-grained rollback. If you want a PR to have generated more than one commit, then it should be more than one PR.
I would definitely use the ASCII versions.
Teaching git by showing commands is like teaching how to write letters by showing LibreOffice Writer's toolbars. It only makes sense when you're moving from another similar DVCS that you already understand and know what you're operating on by using it.
Secular stigmata: Women are caught between different forms of bodily shame
TFA probably came from being mentioned in this video from Adrian's Digital Basement: https://youtu.be/slY_F1MxGlk
In university I made a Muon imaging system that kind of worked: https://www.instagram.com/p/BTar-wghXFB/

Started with a single detector: https://www.instagram.com/p/BSz_rZ1h_sN/
I love Nextcloud. What will eventually happen is that Zoom (and other services in this model) will cause some problem that is so catastrophic that companies realize the true risk of being so deeply entrenched into these toxic one-sided relationships and then will begin to adopt more self-hosted tools.
Ok, we've changed to that from https://slaynews.com/news/scotland-chopping-down-16-million-.... Thanks!
> Can anyone explain why not "functional core, functional shell"? Is this partly because the shell has to mostly interact with things like UI APIs, file system APIs, network APIs and database APIs that are usually implemented in an imperative way already so you'd make your life harder this way? What if the APIs were written in a functional style?

Fundamentally the user isn't functional - if you ask them what they want to do they'll say different things at different times. You can have a 100% purely functional programming language that works like a calculator (with no memory) - the user can put in expressions and the language will evaluate them - but generally users want their language to be able to do things that are non-idempotent and non-time-symmetric and so on. You can, and should, push that part to the edge, but it needs to be there somewhere.
You've done what 99% of this website's userbase cannot, which is grasp this embarrassingly obvious conclusion.
Ancient man finds a cool rock and immediately thinks about the cool weapons he can make from it.
There's must be one or two for either Python or Perl.
Well:
https://github.com/sidneycadot/oeis
Around the Globe with Unicode
I read point 1 as against using SQLite at first. :-D
The other top-level comment (https://news.ycombinator.com/item?id=37041492) linked superuser answer mentions a similar single line for uBlock Origin:

accounts.google.com/gsi/$3p

Any substantial difference between the suggested two, and this one?
I see, the old "China was first" that mix a pinch of science with a little of politics. Is an old anthropological war but Africa and Europe provided much more evidence until today If I remember correctly.

Even if they don't recognize neanderthals, is a well established taxon, and this does not differ a lot of them (in my non expert opinion), so they should show why this is enough different to deserve a second "oriental neanderthal" species. I can imagine easily neanderthals following migrating animals and conquering most of the northern hemisphere just walking from Atlantic to Pacific coasts in several generations.
but like.. objectively what he does is bad. I wish there were a smaller bandwagon to bandwagon-onto.
“Pfff. I could make that shot,” said the spectator on the couch.

The beauty of the Web is that it’s easy to get started. By all means, make one without React.
def. that should be the case, we have iot companies pushing us on a single pthread a a few megs of ram.
> Is this issue that SDXL needs more fine tuning for it to be useful and it will be better than SD1.5 once it is?

No, its that SDXL is better than SD1.5 right now, but some SD1.5-derived-checkpoints are still better than base SDXL, at least foe their focal use cases. There are already a bunch of SDXL-derived checkpoints, but obviously not as much effort yet into them as SD1.5 (though a lot more being pumped out than ever happened for SD2.x).

(Also, while I think some of the forks do, base stable-diffusion-web-ui doesn’t have a built-in workflow that uses the SDXL refiner model, to get full SDXL effect you have to generate with the base model and separately do img2img with the refiner model.)
I'm not really talking about the "errors" ergonomics, but more about error handling.

The methods like .map .map_err .and_then I feel are way easier to reason about and also often shorter that what would happen in a control flow breaking catch block.
haha yeah, pretty tricky - thanks for sharing!
Why apply i-messed-up on main/master? Am I missing a meme here? What's the point of this?
>he will continue working for Tesla for almost half the year

Well that's in the the declaration
I recommend not reading fashion or beauty magazines.
I hope they win the vote. The conditions they work in are miserable.

https://www.youtube.com/watch?v=eALwDyS7rB0 The first minute of this video describe the conditions they work in.
Because it is more expensive to dig underground vs. just slapping heat generators(ac unit) on top of everyone's house and collecting the extra money in the power bill than doing it the right way.
Depending on the use case the tos gets read in my world, but in no way the majority of the time or as often as it should be.

Your comment though made me realize that LLMs can probably help with understanding ToS’