skysight-inc/HackerNews huggingface dataset:
Really? So far as I can tell, only used in avgas (and being phased out), banned in paints in many countries. Food legal limits are outside my ability to judge — though I know they exist, I don't know if the legal limits are "the smallest reliability detectable level at the time the law was written" or something else.

That said, if you know how to turn any lab-only solution into an economically viable solution, please do — the world has plenty of room for improvement! :D
On the one hand, the miniseries on YouTube failed the test I tend to apply to these sorts of adaptations, which is, can you understand it without having read the source material? It's hard to pretend I haven't read the original 3 or 4 times, but I don't think the answer is yes here. Maybe after 3 or 4 viewings, but the cold drop into the universe without the ability to do a lot more exposition is pretty rough.

On the other hand, I have no idea how a miniseries or even a movie could reasonably adapt this for even a general sci-fi audience. As viscerally stimulating as film can be, there are some high-concept stories that just need text.

I will compliment the miniseries for how it selected the subset of stories to adapt. There is a nice natural ending there. A downer, perhaps, but, welcome to the SCP-iverse.

"I forgot what universe this was. For a while there, I thought, maybe… this was the universe where we win sometimes." - https://scp-wiki.wikidot.com/your-last-first-day (not used in the miniseries)
Talk to somebody trying to replace a SFH with a duplex in San Francisco and then get back to me.
1971, you say?

https://wtfhappenedin1971.com/
> If any freshly built housing is bought up by landlords who can afford to outbid ordinary people, then adding supply doesn't alleviate the problem.

Can you explain a little bit more about how this situation is supposed to arise? Perhaps you're saying that regardless of how much new housing is built, landlords will always be able and willing to buy it for a higher price than "ordinary people"? That sounds quite implausible to me. Landlords don't have infinite amounts of money. Maybe you're saying something else.
I don't think this is true of every financial institution. Nubank runs almost entirely on Clojure except for some of its Data Science tooling which is in Scala. Sure it's JVM, but it doesn't exactly scream risk-averse to me.
No, the article clearly talks about the supply of housing in the quote the above comment has outlined.
You can exactly ban what emerges naturally. That's the whole point of regulations.
Given the following, where is the nil implementation found?

package main

type FooInterface interface {
Baz()
}

func bar(fizz FooInterface) {
bizz.Baz()
}

type MyFoo struct{}

func (*MyFoo) Baz() {}

func main() {
var foo FooInterface = &MyFoo{}
bar(foo)
}
Rust + Polars comes to mind.
Hugs to the Ops team over at HuggingFace. Hope this gets resolved soon.
Jitterbug https://www.lively.com/
people always say turn to webapps as an alternative to native apps but on apple for years pwa lacked feature parity
It's really hard to be a good architect, because their job is not supposed to be to leave their mark. An architect is doing a great job when the codebase is boring, and everybody talks about business. That doesn't help the architect however, because people can't tell how it would've been had they not been there. "Our codebase is so simple and boring, why do we even need an architect". That's how you get the kind of architects that try to look impressive to the management.

There are a few things a business can do to get a good kind of architect.

1. Hire them to be hands on with code (give them secondary features or refactors, not major lifts, since shipping speed is not the priority).
2. Don't give them authority over devs, rather ask them to provide mentorship and demos. Their job is to excite devs about a clearly better approach, not to force their opinion.
3. Encourage devs to come to the architect for advice as needed.
4. Have the architect organize long term refactors[1] when needed.

Basically make them a developer whose audience is other developers, and the product of their work is developer buy-in/excitement over good practices and software design directions.

[1]: https://max.engineer/long-term-refactors
I don't know what's worse in that thread:

* They have to visually inspect upwards of 1000 rooms every day looking for vaguely electronic looking things

* They have to use Microsoft Teams

Poor Hilton employees...
It patches a misconfigured reward system pathway in the brain using hormones.

> There are two plausible places GLP-1 drugs could lower weight: the body or the brain. In the body, it could change stomach contraction rate, hormone production, etc. In the brain, it could control the mental sensation of hunger. To separate these two effects, scientists bred rats that only had GLP-1 receptors in the body vs. in the brain. The results were unequivocal: Ozempic and its relatives work in the brain. Although they have some effects in the body, these are short-lived and not really relevant to their mechanism of action for weight loss.

This should've been obvious the moment there was evidence GLP-1 agonists were preventing addictive behaviors, versus solely digestive system effects. Interestingly, this works by crossing the blood brain barrier, so the next question is: can you speed up the effects by temporarily opening that barrier using ultrasound such is done for Alzheimer's treatment [1]? Also, what does an fMRI look like when someone is being treated with a GLP-1 [2]?

[1] https://www.youtube.com/watch?v=7BGtVJ3lBdE

[2] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC10342891/
Knowledge is seeing a white pattern in visual field.

Belief is labeling the pattern and calling it a sheep.

Belief is also the labeling the pattern a Komondor.

Belief is thinking there is a person seeing the sheep.
The Google antitrust remedy should extinguish surveillance, not democratize it
Are you sure that independent generation is actually illegal itself, and not just constructively discouraged? Where is this, if you don't mind my asking? I've got a similar situation where the public utility will only pay for solar generation under a two meter "buy all sell all" arrangement. From what I've seen people just don't plan on selling anything back to the grid, and the overproducers get storage batteries.

(As long as some grid tie is required for occupancy permit, this doesn't really address the original comment's point about bona fide competition with the grid. But on the other hand I'd rather have a public utility than be in a victim market of a "private" underregulated monopoly. My connection fee is like $10/mo. Also they built out gigabit fiber, which just works and doesn't require the yearly threaten to cancel dance of Ma Coax.)
I am curious about the problem from the perspective of a startup idea / nonprofit website. What would you look for in an authoritative source that doesn't exist now? And which topics were you looking into?
Wind is stronger in winter. Wind charges batteries in winter, solar charges the same batteries in summer. Natural gas provides for the statistically unusual droughts until seasonal storage (e.g. hydrogen) is deployed, or significant overbuilding and/or cross-geography transmission is done.
For me, this is very true. Most bioinformatics is done in python, but over the last ~4 years I've ported everything I do over to Go: https://github.com/koeng101/dnadesign

I'm just massively more productive, and the fact that I can read code I wrote years ago and fully understand what I was thinking at the time is amazing, and I haven't experienced that in other languages. I've learned other languages quite in depth, but with Go it is simple enough that when I write code, I'm not thinking about code, it is purely the problem being solved, and the code just comes out onto the keyboard.

Ironically enough, I've recently started porting my entirely-go bioinformatics package to be a python package, mainly because I realize I'm not gonna convince everyone else in my field that Go > python
The Nazis did not like the Bible: https://en.wikipedia.org/wiki/Positive_Christianity

They were not exactly keen on Jewish saviour and scriptures written by jews!

The Bible is not popular with a lot of people now either. People have been arrested in the UK for reading aloud from offensive bits of the Bible.
This is correct. The big picture is supply and demand. RealPage won't let you charge LA rents in Houston, because Houston has a different mix of supply and demand that is better for tenants.

That said: if this system lets landlords eke out even 1% extra compared to the status quo... well 1% of a lot of people's rents adds up to a lot of money and I won't be sad if the company gets sued and loses.

But what you can't do is let your eyes off of the local NIMBYism that so often is the root cause of supply issues:

https://bendyimby.com/2024/04/16/the-hearing-and-the-housing...
Then they were sadly misinformed. The need to prevent cartels and monopolies has been known since the notion of capitalism was conceived.
I understand, for sure. But if there's an effectively-free pipeline running with ancillary benefits of producing humans who want jobs, you're fighting an uphill battle against it.

For structured work, I simply do not understand how making the most complicated machine imaginable is going to outproduce a targeted device made by engineers.

For unstructured work, I simply do not understand how the device can perform at the required level.

There is a sliding structured-unstructured scale, and I'm sure there's a niche there, I'm just not sure where it is.
I cannot see how this is useful outside of being a fun student learning program.

From the data it appears a battery with 1L of electrolyte provides about 18Wh of energy. Mind you this is at ~1.2V, which isn't especially useful without a boost converter. With a boost converter though you would need a low internal impedance from the battery, which I highly doubt is any good with a paper membrane (from what I understand it already isn't great for flow batteries).

Meanwhile a pair of 18650 lithium ion batteries can be had for $5 and can provide 24Wh at a very usable 7V with no power conditioning or a range of voltages with more than enough ability to source current. And it is a fraction the size, weight, and complexity.

I don't mean to tear apart the project, perhaps there is a key detail I am missing, but I just don't see what this is trying to do outside being a learning experience for students.
> Do we really want to have worse tools, just because some people are writing bad code?

People tend to write bad code. It's a fact of life. Tools forcing people who write bad code to write better code can't be worse tools by definition. They are better tools.
Linux software sources are in a weird spot between users and developers.

I, as a developer, organize sources in a way that make it easy to work for another developer. My software will never be compiled by any user. All my users use build artifacts.

I might consider adding autogenerated code, but only when I'm like 99% sure that this code won't ever change. For example that's the case for integration with many organizations where WSDLs are agreed upon once and then never touched. Having Java sources regenerated every build just adds few seconds to every build time without noticeable advantages.

The fact that some Linux users prefer to build software from the sources and at the same time do not want to install necessary build tools is a bit strange situation.

May be containers should be better utilized for this workflow. Like developer supplies Dockerfile which builds a software and then copies it to some directory. You're running `docker build .` and they copying binary files from the container to the host.
> What could be the main cause for things being so hard to cross over from simulation to reality?

When you are simulating you are leaving out of details. Some knowingly, some without you even being aware of them.

Let’s imagine you are working on some perception algorithm for a lidar. You have a cool simulation using geometry to calculate how far each laser goes before they bounce back.

Did you remember to implement that the lidar takes some amount of time to sweep around? It is not making instantenous global captures. (Which is a lot easier to code down.) This causes a kind of smearing effect particularly as things move fast relative to the sensor.

Do you know if your sensor sweeps with one plane of lasers or multiple? What is the exact geometry? Are you simulating it as the sensor is designed or as it is built?

Did you remember that the sun blinds the sensor? And if so, do you simulate it correctly? Including the algorithms it has internally to try to compensate for it?

Did you know that retroreflective surfaces interact with the laser differently? In particular if there is moisture on the lidar. The light straying through water droplets cause false readings.

Did you know that lidars can, under certain meteorological conditions see the exhaust of diesel vehicles? I hope you planed a fluid dynamics engine into your similation to account for the exhaust plume spreading upwards and expanding.

And these are just the niggles of a particular sensor modality from the top of my head. I know similarly long lists for other sensor types. And then we didn’t even got into thermal issues, or the sensor aging or anything. And I bet reality has an even longer list than I do.

Is any of this important in your domain? If yes you ignore them at your peril. If no, you will waste your time implementing them in your simulation. But the only way you will know for sure is when you stumble uppon them and they surprise you out of nowhere by breaking your assumptions and your code.

> Should we invest some more in stochastic programming to handle all the little quirks that cannot be modeled perfectly?

That is robotics. This is what people writing software for robots do. This is what researchers working on robotics problems are working on.

If you want a nice and small example of this maybe read up onnKalman filters or the RANSAC algorithm. If you fancy a more academic treatment of the topic I recommend Probabilistic Robotics from Sebastian Thrun.

> is the major issue that robots must work together with humans

That certainly does not make it easier. Have you seen the video of the russian chess robot breaking its oponent’s finger?[1] That is just the least gruesome of the recent incidents that I can recall. How much is this your “main problem” depens on your problem domain though.

1: https://youtu.be/Mt-1smlom_M?si=19sOPkQf3s6JHoFo
The US abandoned enforcing many of its antitrust laws starting in the late '70s, and is now reaping the long-term consequences of doing so.
Interesting, and explains a lot. I would also question why managers are the "next level" from the contributing roles. I understand it helps because you already have the experience and knowledge of contributing so it would make sense to scale upwards by managing a team, however I think the manager role does not overlap that much in terms of skills with contributors. All the experience you build, especially with technical skills, isn't very useful as a manager, and I think good managers transition despite their technical skills, not so much because of it.
I'm fascinated by the juxtaposition of the idea that "what happens in Vegas stays in Vegas" and the assumption that your bedroom should be searched every 24 hours because of a policy.
Anti-Inflammatory Diet and Dementia in Older Adults with Cardiometabolic Disease
Expo makes it super easy to get started with React Native, offering quick setup, built-in tools, and easy updates, which is great for simple apps or prototypes. However, it comes with some limitations, like larger app sizes and less flexibility with native code. On the flip side, using bare React Native gives you complete control, better performance, and access to the latest features, but it requires more setup and can be a bit more challenging. The choice really depends on whether you need speed and simplicity or full control and customization.
It's odd to blame capitalism for these sorts of problems.

Real estate, property development, and property renting/leasing are typically some of the least-capitalist and least-free-market sectors around.

They all tend to involve extensive and very invasive government intervention that controls or even prevents when and how capital can be used. That's the opposite of capitalism. That's the opposite of a free market.

Government-imposed zoning regulations, onerous development planning and approval processes, rent controls, licensing requirements, and other forms of interference severely inhibit the ability of the market to function properly.

As government involvement in such sectors has increased over time, the situation has gotten worse and worse. Of course, inefficiency and problems are exactly what we should expect to arise due to government interference with the market.

Competition becomes limited, which causes supply to become artificially constrained. This distorts the pricing, which may include collusion becoming possible. Incentives that would help drive down costs, while simultaneously increasing quality and availability, no long exist.

Those calling for even more government intervention than there already is are only making the situation even worse for themselves and others.
> "give us your subscription money or get banned"

This is literally so many businesses. Are you kidding me? Get a membership at a gym. Then stop paying the subscription. And see if they kick you out or not. Or stop paying your netflix bill. See if netflix bans you. Btw, stop paying your patreon, see if you still get the videos. Every subscription business is literally give us your subscription or get banned.

I don't care what Epic is fighting in court over. Why is that mega corp the good mega corp? Mcdonalds spent years in court fighting the responsibility to pay for some woman's burns.
This is really a great idea. Once we finalize the choice, when can we expect the upload into the hivemind?
Well, a technological society that loses the idea of truth as it relates to science and technology must inevitably collapse in its level of technology.
You can't maintain functioning tech on a "nothing is true" basis, because you cannot tell what will work from what won't.
Computation errors that will be discovered only with great difficulties, when someone is careful enough to use some additional verification methods for the numeric results. The magnitude of the error caused by an underflow is completely unpredictable, which is why in any serious program it is unacceptable to ignore the underflows.

Even when the errors happen to be discovered soon enough, people will be puzzled about their origin and they may waste a lot of time analyzing their algorithms, because there are a lot of things that can cause numeric errors.

Because at their origin the underflows will neither signal any exception nor generate any unusual value, the errors will be normally caught much later, perhaps after thousands of other operations, when their cause will not be obvious.

This fight between the people who want to get only correct results from computers and the people who do not care whether the results are erroneous as long as the results are obtained after a delay shorter by a few percents than for obtaining correct results has continued for decades, almost since electronic computers have been invented.

Errors are acceptable in games or for some other graphics or audio applications that generate ephemeral images or sounds, but they are not acceptable for any engineering purposes.

The option "-Ofast" is like smoking. There is no doubt that it is a bad habit, but whoever wants to smoke should be free to do it. On the other hand, exactly like a smoker should not be permitted to smoke in a closed room with non-smokers, the option "-Ofast" and the related options should not be permitted to alter the behavior of any other programs that are linked with an object file compiled with it.

The behavior of "-Ofast" where it affects globally the content of MXCSR is unacceptable.

The right behavior would have been for any function compiled with "-Ofast" to save MXCSR, put in it any desired value for the duration of the function execution and restore it at function exit. Moreover, when invoking any other function it should restore the original MXCSR before the call and put again in it the desired local value after the function returns back.
> These are examples intended to communicate the principle, not instructions on how to do…

Thank you. A lot of people don’t get these are two different things. I’m not going for perfect, I’m going for “oh I get it.”
I suggest you take a look at this list of physical constants, paying special attention to the "uncertainty" column, and then get back to us on why you don't accept any of them except the speed of light.

https://en.wikipedia.org/wiki/List_of_physical_constants
> Not everything that ProPublica prints is true.

They didn't. They're quite clear in their articles.

https://www.propublica.org/article/yieldstar-rent-increase-r...

"Apartment managers can reject the software’s suggestions, but as many as 90% are adopted, according to former RealPage employees."

It's a pretty thin veil; a sort of https://en.wikipedia.org/wiki/Will_no_one_rid_me_of_this_tur... scenario.

"'The beauty of YieldStar is that it pushes you to go places that you wouldn’t have gone if you weren’t using it,' said Kortney Balas, director of revenue management at JVM Realty, referring to RealPage’s software in a testimonial video on the company’s website."
Thanks, that's generally more readily available in the billing explorer for most cloud providers.

There is a definite case for pulling usage data from the cloud account to make suggestions about right sizing though, that's a definite roadmap item
The constitution doesn't apply to things that happen between private individuals. I don't have to allow guns in my hotel, hate speech in my newspaper, or have a warrant to search people as a condition of being on my property.

The solution, as always, is to vote with your wallet.
Repeal the Controlled Substances Act
Reform policing in America
Treat drug addiction as a medical problem
Make healthcare, of every type a protected right
Create a separation between business and state
Make political contributions illegal
Create and offer resources that support early childhood development
Establish and empower a third party mediator to stop and prevent bullying and other abuse in school
Create well funded safety nets people can use if they fall to a risk or on hard times
Make Social Security type retirement income a guaranteed right
Implement a finely-incremented progressive tax system to pay for it
I would compare this question to "creating a new page on the Internet just adds to a countless pile of URLs. How important can any one really be?"

And this leads us to: most will be slop, but if you can figure out effective ways to perform (a) Search, and (b) Alerts, then this scenario is definitely a game-changer.

Let's take protein synthesis: imagine if we were able to programmatically generate an accurate paper describing every property of a given protein structure. And we just ran this for every single protein in the Universe. You'd end up with a seemingly infinite number of papers, most of which would be useless.

But if you (scientist or engineer) could effectively look up "binds to receptor X and causes effect Y" and see all valid candidates within milliseconds, it would be more valuable than any technology we've ever come up with.

If you could, also, set an alert eg. "tell me about any combination that has superconducting properties" and get notified when this one-in-a-trillion protein is found, this would also be more valuable than any technology we've ever come up with.
Nightmode is a good idea -- but you'd be better off taking your nightmode cues and colors from VSCode.
Does full erase create all 0s or all 1s on the CD-RW?