skysight-inc/HackerNews huggingface dataset:
> but in the case of medicine, I think we pretty much know why we make the decisions we do

Why know why we do many of them, but not all. I'd guess not even most. Image diagnostics, lab analysis, there are plenty of areas where doctors make fuzzy decisions based on a lot of intuition.

Logic classifiers (a superclass of expert systems) are good for when we know why we decide stuff. ML is good for when we don't.

And yes, once we have some AI that do stuff well but don't know why, the next obvious step is to reverse engineer it.
crypto isn't a ponzi scheme inherently and allows for in his case dissidents cut off from financial networks to actually function.
It's not so much assuming bad types as saying that names and types properly used serve different needs. For example, if you have types defined in your program, you could literally replace them with some random characters and the type-checking would be equally good, for the compiler, even if you don't undestand a thing. The value of types really is in the structure they represent, and enforcing certain constraints, not in any human understanding of the program. You could even have badly structured types with decent labels.

When you're using types as a means to check names you're likely to misuse types. Synonyms are a good example of this, where people will make so many types each type only ever occurs once, instead of having a well named variable of a more generic type.
That's not a new idea, it's in a book already: https://www.goodreads.com/book/show/23848027-new-moon
This is probably similar the debate around giving SBF a 'platform', which ultimately did almost nothing to help him, quite the opposite.

In this particular case I doubt it provided much negative press for the scheme (AFAIK, it remained very niche) and the runners probably tried to memoryhole it as soon as possible. The only real gain was probably the run-up to the event where Snowden's name could be attached to it.
I follow the author on Fetlife and remember when she was fishing for people to fill out a survey.
I grew up in a piping wholesale business in the midwest that's still going after 35 years. Orders could be ea. (each, single part) or cs. (case, which is arbitrary based on supplier). That industry is never arbitrary unit (e.g. per "units")because the suppliers sell in bulk and piecemeal, and buyers all have their own specs for how they order.

So I can confirm that at least one other wholesale market is indeed different.
"I wish I could just stick with a language and thoroughly master it."

Assembler, C and shell script have been and will be around for many years.

As an end user, i.e., someone who runs programs more than she reads/writes/edits them, I find Python's startup time is just too slow. I have a folder full of tiny, fast shell scripts and C programs that I rely on year after year. Replacing this with a folder full of Python scripts is difficult to envision.

Assembler, C and shell script will still be ubiquitous and foundational no matter what subsequent programming language hype comes over the internet. Boring stuff that works. I am typing this comment from a program written in C.

"The industry" (cf. the end user) seems to have endless time to burn because the stuff it promotes through hype always presents a massive timekill to those who embrace it. A conspiracy theorist might imagine that the industry is trying to keep itself busy and maintain peoples' attention. Regardless of intent, that seems to be the end result.

It is like that hardware company that wants people to keep buying new computers every few years, and tries to prevent/discourage anyone from repairing and retaining them.
Fault tolerance is an important feature but, given Python’s popularity in data science, the most interesting part of this project to me is support for Python UDFs.

In principle, the programming language should not be the greatest consideration because developers can learn and use different languages for different applications. In practice, being able to draw on familiar syntax and libraries can make a real difference in usability.
The American Center for Law & Justice (ACLJ) is a politically conservative, Christian-based legal organization in the United States. It is headquartered in Washington, D.C., and associated with Regent University School of Law in Virginia Beach, Virginia.

The ACLJ was founded in 1990 by law school graduate and evangelical minister Pat Robertson with the stated "mandate to protect religious and constitutional freedoms". ACLJ generally pursues constitutional issues and conservative Christian ideals in courts of law.
Sleeps, but there's a weird bug where it will not log in unless I briefly push the power button first.
I like any language which has opinionated style rules. I don't especially care what code looks like, as long as it's legible and consistent.

C# actually has great comprehensive defaults, they're just not enforced as strictly as they could be.
The biggest PRO TIP you have to know about ChatGPT is the following pattern:

User sends almost any non-obviously "safe" request

ChatGPT says "i'm sorry, you can't make me do that"

User resends the exact same request without any changes

ChatGPT does it this time
Does that include deploys?
there are not a ton -- the pain points mostly boil down to:

Don't use it for extremely latency sensitive UI's (there is around trip and most of the time for most uis this is not an issue even using a server across the world).

Don't use it for animation heavy UIs (you can do animations with it but think things like game UI).

It does not work offline (in most cases it s the same point with standard web and offline).

All of that said, the answer to your second "question" is: There is a process (this is an erlang process and VERY light -- much lighter than a thread its not unusual to have millions of them running at a time in beam) per active page. So one per use per tab or session.

Also yeah, there is no lock in -- you can have 99% of your pages use static rendering (dead pages) and just use liveview for the ones that would benefit. The choice does not come with sharp edges.
He'd probably charge too much
> Wondering if eventually, as more jump on and settle in, we'd see a measurable downtrend in productivity

The reality of digital automation is that productivity is bound to go up dramatically anyway, at least for the next 20-30 years. "Losing" a bit of human-based productivity would likely not be a net negative.

In the end, we weren't put on this planet to crank out widgets or print money. Work is a mean to an end (human welfare, peace, etc). If we can reach that end with less and less work, that's good news.
"Enthusiastic consent" viewed as more taboo than "doggystyle position", "cunnilingus", "blowjobs" or "fingering vaginas"? Also "romance" and "cuddling" as more taboo still? Quite disappointing and sad if true!
Wayland's "just don't send callbacks to hidden windows" approach is completely backwards and should have been replaced by the same event-based visibility notification every other GUI uses. The scaling model was wrong, but they've finally admitted that and real fractional scaling (as opposed to over-rendering+downscaling) is close. Wayland blandly dragged X11's biggest technical debt -- implicit synchronization -- along with it, even though every other modern GUI synchronizes explicitly (i.e. moves a lot of work out of the critical path of drawing a frame).

Most significantly, the "only the focused app should be able to read input" is wildly, fantastically wrong, mind-bendingly deviated from the norm on literally every other graphical user interface in the history of humanity, and utterly incomprehensible to anyone who is not an outright "cybersecurity" fetishist. Imagine a windowing system where you are playing a video game with a USB controller, you mouse over to a window to send a text message and your video game loses the ability to process the controller input. This is clearly surprising behavior, if not outright user-hostile, and only Wayland gets this wrong. Rather than fixing it, Wayland devs gaslight users and developers into believing anyone who opposes this bad behavior is anti-security and therefore pro-badguy, or something. So, each separate desktop environment tribe is now having to produce their own bespoke utilities to mux input clientside to enable normal use of computers, because the Wayland protocols are empowered by divine right instead of technical merit.

I want to add that despite the above litany I do regard Wayland as a marked improvement over X11 and I have no interest in going back to the bad old days. None of the problems with Wayland are unfixable in a 2.0 or so bad that it's worth going back to X11. The actual big problem with Wayland is the unwillingless of the core developers to take advice, but that was a problem back when they were the X11 core developers, and I don't see it changing. For those of us who don't have to interact with them, it's a non-issue.
The standard benchmark mentioned (krausest) is for JS frameworks. But Tamagui is not a framework. (It uses React as the framework on web, so would have similar perfomance to that in krausest.)

Tamagui is a style and component library (plus optimizing compiler). Do you know of any standard benchmarks for any of those?
I’m horrified.

I know we’re “just” talking about code here but decisions will be far-reaching and if we let the powers that be force AI-generated content to be copyright-attributed, two things are going to happen:

1. The biggest benefits of AI are going to be pushed back for decades and possibly indefinitely

2. Artists will be absolutely slaughtered as the same rules will come at them full-force. Almost every artist draws inspiration from other creative work. That’s how creativity works. Can you imagine how stifling it would be for every artist to have to document and “pay for” every piece of art they’ve ever seen??
> Type hints are basically for documentation and metadata.

They are also for static checking.

If you choose to run the code despite that failing (which you can, because there is no execution dependency on type-checking) that’s a choice, but its kind of odd to complain that Python lets you do that.
> BUT I also had to replace the battery after a year or two (it was swollen to the point that I couldn't close the laptop anymore

That happened to me too with the first one, but they actually on their own initiative sent me a new battery. I've had no problems with the second laptop.
SouthwestAirlines' Meltdown Shows How Corporations Pit Consumers Against Workers
Same here, I found that, for myself, If i am talking to much, I am trying to fill up space. Its not my job, I dont need to please anyone. I have interests and objectives and if the line of conversation falls into those categories then I cane speak, otherwise, I really don't need to speak.
Based on my reading of the docs (I haven't looked at the code), it appears that it uses the existing langchain[1] (which I have used and is excellent) library for constructing longer prompts through a technique known as prompt chaining. So for example, summarizing long documents would involve a map/reduce style effort where you get the LLM to summarize chunks of the document (with some degree of overlap between chunks) and then getting the model to summarize the summaries.

For answering "queries", it appears like it iterates over the documents in the store, i.e., NOT using it like an index, and feeding each document as part of the context into the LLM.

[1] https://github.com/hwchase17/langchain
The covid canonballers also had volunteers tie up the cops by intentionally breaking the law at speed traps ahead of the arriving racer. Not something to be proud of.
As a language that celebrated its 50th birthday this year, C is already a long-lived language. It's not terribly far behind the first non-research compiled language, Fortran, which celebrated its 65th birthday this year.

Both are, for all practical purposes, immortal languages at this point. You correctly point out that they aren't guaranteed to survive the next technological mass extinction event, but I think that might just be a truism.
Funny to read this & be op, since I blogged about that exact thing in 2022.

https://www.friendlyskies.net/maybe/the-name-s-roo

(And wondered about propagation...I mean do these people get a sense for when you have just a perfect local atmosphere for whistling on a given day? A good day to try for a record and reach a friend down at the bar? Guessing so...CQ DX)
I’ve worked on some pretty large codebases and while there’s usually no IDE button for it, there are good and well known patterns for refactoring dynamic code.

As for bugs, the research on this has always been mixed at best, I guess YMMV.

I’d personally argue that the structural typing in Elixir is more useful and practical than the types in most popular static languages like Java or TS.

Mostly I think it’s a wash where you get a little but give up some useful things too.
> You do have to embrace types though; if you have a dictly typed program where everything is a Dict[str, Any], then putting that in annotations isn’t going to be very helpful; converting the dicts to named tuples or dataclasses is.

Or even just TypedDict, which often works without any changes besides annotations.
It’s probably safe if they are just going fast in areas where they know it’s empty.

But telling the story provides cover for 19-year old kids trying to impress their friends who definitely do not have an advance drone checking for other cars.

As long as 30,000+ people die on our roads every year…my patience for these antics is very limited.
An agenda piece, nothing more. Look at her byline.
> sex with your own dead body

That's one I've not heard before!
The linked article compares ratios across companies, in this case it is more relevant I think, to look at how much of Tesla's revenue is spent on R&D.

According to statista.com:

2018 6.6%

2019 5.5%

2020 5%

2021 5%

This should give you an idea about your odds.
Yes, it has other potential uses than Ponzi scheme. However, when it’s advertised as a probable positive ROI it comes from being a ponzi. If that’s not accurate enough, one could then say that it’s remarkably ponzi-esque.
I like using replit as a toy, but it's got so many bugs and quirks and sharp edges, I can't imagine using it as my everyday IDE.

I'm hoping it'll get more robust over time.
In Chinese it's dian3, which is used as a time indicator (i.e. analogous to "o'clock"), and also part of dian3 xin2 (meaning snack, dim sum is the more common form in English but it comes from Cantonese). I'm not sure what it means in this context but this is just to say the pictographic analogy likely doesn't work because it probably is some unit here and not actually referring to the bath itself. That comes from the katakana which reads "Unit bath"
I wonder how many buyers were persuaded by the branding and reputation of Tesla and Musk?

Now that that reputation and 'cool factor' seems to have been shattered, I wonder what the market share will look like in Jan/Feb...
> It’s dumb, and essays such as the “blub programmer” feeds into it

I don't think the Blub essay is about learning a constant stream of new languages. I mean, the author of the essay doesn't seem to be constantly learning new languages.

The Blub essay, whatever its flaws may be, is about people being unaware of languages and features more advanced than their tool of choice, and finding them strange. Or in other words, that it's easy to see how poorer tools are more limited than the ones you're using, but very hard to understand how better tools are better, or even acknowledge they are better at all.
I had SAX-style parsing of XML and XSL transformation as concrete use cases in mind, because that happened to be what I worked with. I believe I went with Node.js at the time, which had a library that was much easier to work with than what was common for Python. Although, I mostly used Microsoft's or Saxon's XSLT processors overall in that job.

Another use case was parsing proprietary, text-based file formats with ancient encodings. I believe I did use Python for that as there wasn't that much data to convert anyway and it just worked.
I couldn't find how you turn off/on case-sensetive?
It'd be an excellent joke to not fix it
Apart from the Olympics, which I subscribe to cable for a month for, and hotel stays, I haven't watched network television in 13 years. I don't have any friends who have a cable or satellite tv service and most don't even bother with an antenna unless it came attached to their house already.
"and are actually pointing out a flaw in their system - chatbots are completely useless"

If you managed to find an actual flaw, then chances are that the next humans you will talk to, will be completely useless as well and only if you bring enough patience and have nothing else to do, eventually you will be escalated to someone with competence. At least that was my experience and usually I cut my losses and give up before making it that far.
The type checker from WhatsApp is open sourced and actively used. See https://github.com/WhatsApp/eqwalizer
I found that this is true in my encounters with people as well.
That's pretty neat! It must have been fun to demonstrate that skill for others.

I admit I'm hoping that a certain Daniel Pinkwater story could become real just in terms of having the right hardware in one's mouth. Maybe a filling made with something similar to those blob-chips you see on PCBs sometimes?

> https://bellard.org/linmodem/

I like it & will explore, thanks.
> Dell only support the XPS 13 for Linux.

They won't refuse to repair it. It's identical in all ways except for the screen size, so. If something really weird happens, they might kick it back to you, but nothing really weird is going to happen.

> My advice for buying any Linux laptop would be always get one that comes with Linux out of the box even if you're going to replace it.

Or get a Dell XPS 17 and install your own ;)
I don't agree with that, but I could be wrong.
Like many people, I decided a couple of years ago, in my case, that sports weren't sufficient for me to subscribe to live TV. And, given that, I may watch a few series more or less when new episodes drop but rarely same day.
> Do most people want to constantly fuck every second of every day?

Depends on your age and gender, I suppose. For most 15 year-old boys, the answer is yes, they do want to constantly fuck every second of the day.
> be just as horrible

I don't get the utility of making ontological statements about people including serial killers. Maybe someone who does find utility in them could chime in and explain it.
I didn't imply there was some well-built, useful and simple reality we could all just switch to. its all broken to some degree. not at all surprised that something inherently flawed could be useful.
Sorry if I missed it -- Are there plans to offer a way to query this in actual sql? I believe SingleStore is MySQL compatible for example which I think is a nice feature. Basically I want to be able to interact with this much like I'd interact with another database I'm using or perhaps with a sqlalchemy core integration (which both SingleStore and Snowflake have).
A type system saves a lot of time when reading code that has been written by other people and has evolved over time. In Elixir, I often end up adding debugging statements to code and running it, just to check the data structures.

A type system also gives additional assurances when changing code that is used from many places. It's so nice to make a change and have additional confidence in it because the type system is happy with it.

I can't think of many bugs that I've seen that would have been prevented by a type system. I'd still like to have a type system though, it's sort of extra documentation within the code.
That has been my experience too. The only time I book appointments with NPs is when I know I need a specialist and want to skip the whole dance of “let’s do some tests and then determine that you need a specialist who will order the same tests”. It’s a cheat code to get better healthcare by working with the system.
Oh! One more critical point for an ELI5!

'Although models that make use of non-invertible, artifical features may still be biased, it's less likely. Using only invertible features eliminates some risks of bias, but not others.'

At this point I think one might have to explain the Naturalistic Fallacy (which accounts for much of the remaining possibility of bias in a model) but it starts to get into tit-for-tat hand-to-hand ontology: what 'bias' means, what different kinds of bias are possible, and how even 'unbiased data' can create a model that demonstrates behaviours that colloquially and idiomatically count as biased.

But one must cut the cloth of the universe somewhere
Specificity: not so great

Selectivity: perfect
Ha, I've also been wondering this for a while. Would love an answer, unfortunately threads like this often go ignored here, but we'll see.
Here's another way of looking at it: Many mutations are going to happen in the wild, but only a few will make the virus more viable in some host or hosts. Most of the mutations will be dead ends, or jump to another species and then mutate away. Only rarely could one emerge and jump all the way to humans, spread across the globe and cause a pandemic. Ebola couldn't, and SARS1 as well due to speed of mutation. (The only original SARS1 around any more is in laboratories, except when it has escaped.)

In GOF you speed that process up by orders of magnitude. You arrive at the viable mutation sooner, possibly infinitely sooner if random mutation would never have arrived. If you engineered part of it, there's a good chance it would never have emerged naturally. It might have come into the world in a few decades or centuries, or it might never have. But you have it now, and have to guard it perfectly as long as it remains in your lab.

Bottom line, it probably won't escape, but it probably never would have emerged naturally either. IMO, to make GoF a beneficial trade-off, it should be focused on viral species that are close to emerging naturally and do not need their genomes to be artificially manipulated in order to become dangerous.
It's like an airplane bathroom.
There's high end and then there's high end. I don't know this roaster well, but I can take a stab at how this works, based on roasters local to me.

The absolute biggest and best roasters have relationships and locked-in supply or exclusivity with farmers. They're also likely re-investing profits in those farmers. There are a very small number of roasters of this scale and sophistication, and they're probably already the ones in national retailers.

Everyone else is buying high quality but still commodity green coffee and roasting it.

The first group is able to get higher quality and guaranteed supply because of the deep relationships. They're excellent roasters, but they also are able to attain a higher level of quality because of the garbage in garbage out principle. Everyone else is competing on who can do the best job of roasting the same product. Important, but not quite the same.

I can't say that this company falls into the second category for sure. But if they do, that explains how they can get lots more supply very quickly. Their coffee is high end, they're doing a good job of roasting it, but it's not so high end that there isn't a bunch more green supply that they can get.
I installed the latest TreeSheets release on mac and it asked for permission for incoming connections. Doesn’t look good