skysight-inc/HackerNews huggingface dataset:
> I assume you're from DC (per your name).

If you'd clicked on my handle, you'd immediately see that's an unfounded assumption. (Although I did live in suburban Maryland for a few years in my early teens when my dad was stationed in downtown DC.)

> Do you live in Columbia Heights since you think all people are equally interchangeable?

Somehow I don't think you're a lawyer — please stop trying to play Perry Mason (you do know who that is, right?), because competent lawyers don't do what you're seemingly trying to do here, not even on cross-examination: Jurors see through the bullshit and it pisses them off.

> Are you one of those limousine liberals that advocates for policies you know could be destructive but know you have the money to shield yourself from?

Au contraire: I didn't grow up with money; while I'm not poor, I hardly qualify as a limousine anything. But as I've gotten older I've become less rigidly judgmental; less inclined to berate people for (what I regard as) their fuck-ups; more respectful of differences in viewpoints; and more tolerant of errors in judgment (of which I've made my share). I've also come to appreciate that more people need opportunities like the ones I had --- as well as those that I didn't have.
China Stops Publishing Youth Unemployment Numbers Amid Faltering Economy
I work(ed) on testing storage products. So, here's a probably more precise answer to your question: nobody knows.

There are at least these two reasons: proper testing of endurance of a device is not possible, you can only test that in a pretend kind of way. We are talking about years of service that have to be somehow emulated in at least weeks... and, of course, you cannot really account for physical behavior of materials from which the disk is made by simply running multiple I/O workloads. Now, add to this that the larger the storage capacity, the harder it is to check durability because throughput becomes the bottleneck. I.e. if you emulate device wear by running more I/O workloads, then, proportionately to the size of the device, you will be able to run fewer of them per unit of storage, because you are bounded by the throughput.

Any real (good) tests so far rely on previous generation of devices, and don't necessarily reflect the current situation. I.e. if your SSDs survived for only five years, who's to say that the next generation you will buy will last more or less? They are very likely not the same kind at all...

Also, it's really silly to measure disk durability in units of time... I mean, most tests that intend to measure durability model it by running I/O workloads, so, they'd typically measure durability in something like "how many times can a unit of storage be written over". The usage patterns vary dramatically across different kinds of workloads. So, if, eg, you are running a build server, you will wear your storage a lot faster than if you are running a (well-configured) database server, and still much faster than if you were running a video streaming service, and still much faster if that's a (well-configured) Web server... and the difference could be an order of magnitude between these.
Which in the context of this thread / OP is proof that the history must not only be preserved, but must be promoted, honored, etc.

I could of year ago I work at an agency and one of the new dev starter and said something about being into hip hop. I mentioned Rakim and the reply was, "Who?" Don't get me wrong, I respect Nas, Eminem, etc. (i.e., all the lyrical magicians) but they stand on the shoulders of The R.
Ask HN: Any recommendation from books on First principles thinking?
I keep reading/hearing that you need analyze things for first principles, but I dont find good resources on it. Any recommendation for books on First principles thinking?
I actually prefer pregnenolone to DHEA, I've found it to be more forgiving. I agree wrt Berberine, the lactic acidosis issue turned me off metformin as well. I believe it's the reason Peter Attia stopped using it also.
No, they won't figure it out. That's why I'd leave. I believe quality is incompatible with the size of their "target audience". You cannot make everyone happy.
Your personal inability to read text off charred, rolled paper tells us literally nothing about whether the people actually doing it can. If a paper implied that nobody could, but you were doing it, that would be of interest provided you could explain how.
Yes, but you are only doing chemical analysis of the liquids, not the solids.
I still get invited to random overseas "conferences" vaguely related to work I did. I left academia almost a decade ago, although I still have co-authorship on some recent publications from my old group.
That's style dependent. Nobody's belting or doing fry/false chord distortion for 3 hours, but a gentle throaty style of singing could easily be sustained for longer with water breaks.
Business differentiator. Presumably, Europe simply wasn't very profitable for them until the parks opened up
I would not touch this with a 10-foot pole, and would be likely to reject an investment possibility based solely on this being on the cap table.

It is marketed as being a way to preserve angel-investor equity in the event of an outsized exit.

What it actually does is minimize that equity, in exchange for earlier cash-flow repayments. If the business wants to grow, repaying money at that stage is the worst thing possible.

And as far as an investment in a business that will never grow: it seems less-desirable than simply getting dividends, and the complexity on the cap-table will make an acquisition less desirable.
> In that case, it was a chicken and egg situation where selling devices without a WhatsApp app was very difficult, but WA didn't want to develop an app for a new OS until it grew to tens of millions of users.

Disclosure: I worked at WA during the FirefoxOS time period as well as when the KaiOS client was developed and launched.

I honestly don't remember the internal sentiment on FirefoxOS, and I don't know if Mozilla ever approached WA to ask for a client. But the public interfaces for apps were insufficient for a WhatsApp client, so that's a bigger issue. The KaiOS client (which afaik, Jio approached FB/WA to ask for) was difficult to build in part because the OS was missing important features for apps, and that takes time and collaboration to get added to the OS and then pushed out to users.

From memory, the major missing interfaces were around access to TCP sockets and ability to run code that accesses the network in response to a (silent) push message that optionally submits a notification for the user. If FirefoxOS didn't have push messaging (I can't remember), then ability to keep a socket open always and post notifications at will would suffice. Arbitrary tcp sockets are needed because the chat protocol is not http based; running code on pushes is required for e2e, so sender names can be populated from the device's address book, and to avoid notification horrors. Horrors include getting a notification about a message you can't read because the client hasn't fetched it yet and getting a notification about messages you've already read; WhatsApps model is the client is the source of truth, and so there's no reason to accept notification horrors that are common with server source of truth systems. e2e was under development for quite some time, so even if the public timelines don't match up, it would be a requirement for supporting new OSes.

For calling, access to UDP sockets would also be needed as well as ability to run native code as the voice codec and data marshalling is in C; although Firefox OS came out before WhatsApp calling. Calling didn't make it to all platforms, and would have been an acceptable thing to defer, IMHO.
This is my sense as well. Text generation LLMs haven't been the best source of embeddings for other downstream use cases. If you're optimizing for token embeddings (e.g., for NER, span detection, or token classification tasks), then a token training objective is important. If you need text-level embeddings (e.g., for semantic search or text classification), then that training objective is required (e.g., what Sentence BERT did to optimize BERT embeddings for semantic search).

That's a great list of existing embeddings models (in addition the SentenceBERT models https://www.sbert.net/docs/pretrained_models.html).
curl is such an amazing tool. Most of my coworkers are not comfortable with the command line and prefer to use GUI tools like postman. Having curl as part of your shell's history is a minor super power.

What was that API end point that was failing 3 months ago with a weird status?

1. Hit C-r for reverse search (bonus if you've got fzf installed)
2. Type a partial URL
3. Identify the curl command you want, and hit enter.

I recently used timing support (as described in the article). I actually found it in AWS docs when I was trying to understand why things weren't as fast as expected. Now it's in permanent record in my shell.

Anyway, +1 for curl.
As the preface points out, it was totally acceptable to denounce Churchill and even to advocate peace with Nazi Germany, but not to denounce Stalin.
Related: https://en.wikipedia.org/wiki/Predatory_conference
It’s not a one for one replacement but edge has vertical tabs and tab groups built in. I have to use edge for work and it’s a decent compromise.
Putting in a CC for a trial to access your service doesn't end up deterring anybody because you can just buy a massive CSV with stolen details for relatively cheap. Even if they're frozen/cancelled, the card numbers are still valid numbers. If you want to pay to authenticate each and every one of them, you'll probably run yourself dry.

Can also just use old empty VISA gift cards, ethically sourced from relatives and friends of course.
Tesla is looking for people to build 'first of its kind Data Centers'
I'd say don't give anyone bad ideas, but we are too late:

https://github.com/oraoto/pib
This is the best approach moving forward.

I also had a similar incident where I received a wrong shipment object from eBay and promptly returned it on same day. The seller issued a refund in a nonexistent PayPal account(I owned that e-mail too but PayPal never sent any notifications).

After 5 months of helpless back-n-forth trying to explain what happened(I didn't receive a refund yet), eBay simply decided that my account is fraudulent and I contact PayPal of whereabout of refund. Paypal told me, I can't be supported without sharing when and from which account the refund was issued and also blocked my PayPal account as suspicious behavior.

After 5 months of frustration, I decided to involve my lawyer and he just told me to write a new email to eBay and CC PayPal about whole incident and how if not action taken they'll expect a notice from my lawyer in 14 days.

Within 2hours of that e-mail, eBay sends me the most polite email with "heartfelt apologies" and shared the info about the refund details and PayPal suddenly offers me a nice email about how to claim the refund from nonexistent account. So suddenly my eBay and PayPal accounts are no longer blocked and a nice PayPal agent moves the refund to my account immediately and reassures me that they reported the incident "for investigation" so such inconvenience doesn't happen to anyone.

Sorry for the long rant, but these bigCo support are real cesspool of lazy support people who are too busy just copy lasting scripted responses and screwing insecure people. Sometimes you need to bring them to court.
If science is valuable and draws readers who pay subscriptions, then the journals should pay the researchers for their research reports - instead of the 'pay to publish' model that exists today. Journals claim they are the ones providing services to the researchers (in terms of publicity, career advancement, funding opportunities, etc.) - but what about the public's rights to information largely created with public funding?

The reason that publishers don't want to go to the open-access model (which makes sense for a product that is largely taxpayer-financed, i.e. government agencies make their reports available to the public without fees usually) is that universities pay thousands of dollars a year for each journal they subscribe to. (There is archival value for printed paper versions of journals, however.) This becomes particularly important for research into known subjects, e.g. if you want to get the complete history of a certain antibiotic's discovery and production and testing history, at the level of primary research reports (which include methods etc.), it's still very difficult to do that without access to a university library with a comprehensive set of journals, and that's what publishers are trying to protect by going after sites like sci-hub.

The model that Nature and Science want to perpetuate is their 'high impact value', meaning if they accept a paper, it's good for the researcher's career in terms of getting tenure and more funding, and a switch to open-source publishing on arxiv-type platforms might disrupt that stable system. A sticky point is the peer-review system, which is kind of a mess anyway.
Archive link: https://archive.is/RiSK2
I evaluated using FreeBSD for a project. The biggest challenge for me was I couldn't figure a way to fit modern DevOps into FreeBsd. OCI compliant containers are not supported. The best way I could come up with for a minimum blue-green deployment strategy was writing a ton of scripts myself. I can not imagine running a fleet of FreeBSD servers where a team of developers deploy 10+ times a week to a swarm of containers running micro services.

What solutions do other practitioners use with FreeBSD? Or do you abandon modern DevOps practices entirely and hold a meeting to determine partition sizes, provision servers to individual services running on specific named computers and plan for a software upgrade for weeks in advance of a deployment?
I still think it's literature, just that most of it is trash literature. But then again, I was an English major and was trained on how to dissect literature. I realized a while ago that there was a book and a method I learned in English Lit 101 that I think informed how I read code. It's called The Critic's Hornbook, by William Dowling [0]. In short, it's a methodology for meticulously breaking down the meaning of every word, phrase and reference in a text, without resorting to any subjective interpretation. He showed us how, with proper understanding and research, you can find a lot of latent information about what's going on in the text. I find myself doing something similar when I read code, and when I write code.

Code reading is also archeology. There are always layers of code accumulated over time, and you can start to see the minds of the people from years ago. And if you understand the constraints they were under and the assumptions they had, then it can help to understand "Why the hell did they do it _this_ way?"

[0] https://www.amazon.com/critics-hornbook-Reading-interpretati...
There's probably a better way to say this, but here goes:

Anything you learn before you start working on something is familiarization.

Familiarization is important, but it is not working knowledge or understanding.
Awesome explanation! That was clever and concise. I am working with pixels every day (in computer vision) but had never thought about what one could do with HSL.
Just as we trust parents to look after the needs of their children in every other way, we also trust them to defend their rights and privileges of citizenship. That includes suing if somebody infringes those rights and privileges.
>I don't think that follows logically. People who won't pay for Red Hat, after Red Hat's deemphasis of desktop work

Obviously, certain types of desktop work have been de-emphasized. However, there are a lot of other types of desktop work which Red Hat does, which are continuing or even increasing in resources.

* Pipewire

* Filling in the Wayland gaps, e.g. color management and HDR

* Contributions to Firefox e.g. VAAPI hardware acceleration

* Mesa / RADV driver contributions

* Improving the Nvidia driver situation in collaboration with Nvidia

It's perfectly fine to be upset about the work that's being stopped, but some people in this thread are acting like everything is shutting down, which is ridiculous. And it's not like this stuff that is being worked on is insignificant, either.
> This also disregards that someone is always in the chair. Okay, let's say he quits. Then they're short an additional controller, making the situation worse, and someone else is still sitting in the chair when the exact same thing happens. "He voluntarily worked in an unsafe environment" is just a deflection from the responsibility of the people who have the authority and the opportunity not to make the system unsafe.

I can sort of see different ways to look at these situations but I usually don't see them that way. While desperately holding together a broken system seems heroic, it assumes that help is on the way. Many times no help is on the way because the system is sort of barely functioning so there is no priority to improve it. If he left maybe the other controllers would all leave as well, ending the farce.

> His only agency was to quit his job or not, which wouldn't have any effect on the outcome.

He probably wouldn't have been murdered and blamed for the the outcome!
Are you smarter than a scammer?
React has more implementation of its components model (preact, react, solidjs, inferno,…) than web components (chrome, ff partially and safari partially), is more used and is more indépendant from the current web monopoly. Anything w3c is now a standard to keep dominance.
As others have said, the convergents of the simple continued fraction representation give the best rational approximation [1] relative to the size of the fraction, in the strongest relevant metric: that of absolute error bound. Proofs can be found in any book on Diophantine Approximation; the classic (and readable) reference is Khinchin's Continued Fractions book.

[1] https://en.wikipedia.org/wiki/Continued_fraction#Best_ration...
That would be one of the 1st things I'd love to see myself. Plus opening of "internal" to let folks build new stuff on top of Terraform elements.
You might want to consider that perhaps — just perhaps — you're not quite as clever as you clearly seem to think you are, chief.

Bye.
Nature does not solicit your work and then hold them hostage. That's the relevant difference here.
More hardcoded credentials than ever, and sloppy coding is to blame
> hard drives are not particularly reliable for backups storage

This is true when you compare them to media designed for long-term storage. But HDDs aren't all that terrible at it. I recently needed to dig out a 30 year old hard drive to recover some data from it, and it worked flawlessly.
‘DoubleDrive’ attack turns Microsoft OneDrive into ransomware
That’s still not her “claim to fame”, as the OP phrases it. She’s famous for her music, not her wealth. A better fit for the OP is someone that is “famous for being famous”.
I don't know.. Imagine you have a react component that needs to interact with something written in svelte...

I'm not convinced that people are building integration APIs for consumption by external code. That means no JS events (redundant since it uses stores or signals and whatnot) and minimal callback availability to hook into a component state.

One might not control the code if this is from an open-source library for instance.

Maybe the premise is "don't do that" , but then people still wanted WebComponents at some point. So seems there exist use-cases for component interaction. Or were people mistaken in the first place?
Michael W Lucas has his Ed Mastery [1]. I am not sure how good it is as I am yet to read it, but I have enjoyed his OpenBSD books.

[1]: https://www.tiltedwindmillpress.com/product/ed
May be it's time to reboot Yahoo 2.0 along with its server infrastructure which were all running on FreeBSD.
> Generally, it is worse as a desktop system than more even obscure OpenBSD.

Only because you couldn't get AA with chromium? FreeBSD is my daily driver, stable as a brick. Everything just works.

Never going back.
I was thinking that too.

I guess another possibility is that he wants to keep some work/life balance, so he doesn't want do write software outside of work.
> Music is art, and art is important and rare. Important, rare things are valuable. Valuable things should be paid for.

the rarity is not the source of the value, but an amplifier for the value in a market driven society

> It’s my opinion that music should not be free, and my prediction is that individual artists and their labels will someday decide what an album’s price point is. I hope they don’t underestimate themselves or undervalue their art.

does she understand privilege? she's a music slaver, she's advocating that music remain a limited experience accessible for a few. I have a HUGE problem with this.

this is, in my view, an energetic interaction centered about value, perceived value, and measured value. i could say more but i rant... something something digital assets can be copied for free let's not let a scarcity mentality ruin this for all.

finally, what she really sells in her shows has real value, the scarcity is her physical existence, this is NOT THE SOURCE OF VALUE. the energy/money dynamics are a form of power.

edit: I echo this sentiment: "Sad to see generations grow up on music being a spectator sport and not a communal, participatory activity". but notice how this huge Taylor mega shows ARE a communal activity. Dancing is the main avenue for communal musical participation
Your product looks really helpful! One note on the website though, you show the line of HTML, but I don't know what that will look like on my website, so it might be good to add a couple pictures showing what the user of my website would see to give feedback. Otherwise, everything else looks nice!
Bike maker VanMoof also files for bankruptcy in Germany
"Last chance for VanMoof customers to collect their broken bikes this week" - https://nltimes.nl/2023/08/15/last-chance-vanmoof-customers-...
Cool. I was wondering what Tanimoto meant, since I've tried to make myself familiar with all the useful similarity measures, and apparently it's just another name for Jaccard Index.

I do think there is a lot of potential in exploring more sensitive measures of similarity or statistical dependence. It seems like the ML community has basically decided that all the heavy lifting should be done at the model embedding level, and then you can just use cosine similarity for speed and the answers just "fall out". Which is definitely nice because then you can search across millions of records per second.

But there are some lesser-known measures of similarity/dependence that can pick up on more subtle relationships-- the big drawback is that they are slow. I included a couple of these exotic ones in my project, Hoeffding's D and HSIC, mostly out of curiosity.