skysight-inc/HackerNews huggingface dataset:
A quantum theory of gravity would by definition explain the curvature of spacetime, since said curvature (and its dynamics) is how gravity is expressed.

Asking how a quantum theory of gravity would explain curvature is then asking someone to give you a completed quantum theory of gravity, and it is not at all clear that the first successful theory will describe the world terms of particles.

However, it can be instructive to consider electromagnetism as as classical theory and then as a quantum theory: waves in fields become enormous showers of particles, and these photons then carry the force that attracts or repels and can sometimes interact with each other.
Hahaha "monkey lands plane" reminded me of the ad with the monkey being the taxi driver: https://www.youtube.com/watch?v=sdXbf12AzIM

(not affilated with pepsi, I do not consume sugar-y soft drinks)
If your website is sending requests to your api, then that api is effectively public.

If you have poor backend code, you’re assured to get weird traffic whose purpose is to break it at some point. It’s only up to you to make your backend resilient. If you don’t, too bad for you.
Overproduction, storage and demand side shifting. The market can choose which mix of these works best in which market - which might vary a lot from market to market.

It's rather ironic that the carbon industry spent the last 30 years telling us through Koch institutes etc. that the market knew best (when fossil fuels were most viable financially) and now that the green energy competition is undercutting them to death, suddenly markets don't solve anything.
Alerting and Notifications from SkySQL
Well, making a blocking call -say writing to a log for auditing purposes- in a tight loop can dramatically decrease performance.

There will be no issue in terms of program correctness, but there will be one in terms of performance assumptions. And performance might actually have been why the programmer chose Rust in the first place?

Seems like Rust's async are not correctness-colored, but they are performance-colored.
Digging into the Texas Freeze using Python and ERA5 zarr data
About your edit, that's pretty much what extensions like noscript do
I don't feel like it does vendor lock-in. It only really locks you into using utility CSS, but you can "eject" at any time by throwing out the framework and keeping your compiled file with utility classes.
Because the issues kids in these articles claim to solve are usually large unsolved problems, that have been studied by subject matter experts for years. It's possible someone could dream up a silver bullet, but I believe the trope of an untrained outsider approaching a problem and easily solving something that has stumped "the experts" is nowhere near as common as we'd like to believe. The reality is these solutions take years of persistent hard work and background knowledge, and rarely materialise all at once. But that doesn't make a feel-good headline.
The problem here is that registrars sell domains for much less than they're worth, thus creating trade opportunities.

Handshake[1] has a solution for this problem. Each new domain, instead of being sold outright, is put up for a two-week-long Vickrey auction[2]. If registrars adopted this policy, buying domains just for parking would become much less affordable.

I wish ticket sellers functioned that way. This would let artists get the true value of their tickets (which is much higher than what they're usually sold at. Ticket scalpers would also have to disappear, as real customers would be paying the true ticket prices directly to artists, and there would be no opportunity for profit.

Disallowing the transfers of domains (with exceptions) is another way to solve the problem. Transfers should be allowed only when the new owner is going to continue using the domain for the same project, which is also transferred over. In all other cases, the domain would be returned back to the pool, where anyone could buy it for the normal price. A similar strategy is already used by some ticket companies.

[1] https://handshake.org/
[2] https://en.wikipedia.org/wiki/Vickrey_auction
Perhaps a good start would be to have a standard way to signal the licence of the JavaScript received by the browser.

At least users would be able to see it, or only allow the ones with a licence they agree with.
hey you can use it in a browser now which is better than what we had in the last 5 years.
Me neither, try Tachyons which is what Tailwind wants to be, minimalistic, atomic, great UX.
If you were trying to be diplomatic you wouldn't have included the word "woke".

Different people like different things for different reasons.

> refusal to follow this norm

That's why it's called a norm, not a universal law.

(Random personal anecdote: I last visited San Francisco a long time ago, in the early 2000s, but as a Brit it seemed to me that there were hardly any Indian restaurants compared to what I was used to. Of course, British-Indian cuisine is a laundered version of Indian cuisine itself .. and the restaurants are more likely to be run by Bangladeshis. What is authenticity, really?)
Serious question: What's wrong with their/them etc.? It took me some time to internalize these (very dissimilar to my native language) and they sound perfectly gender neutral to me.
I’m hesitant towards C++ as it seems an ancient programming language and I don’t know for how long it will be around.

As a rough rule of thumb, the older a language still in use is, the longer it will be around into the future. I believe C++ will outlive you.
I'm pretty sure you're joking, but the client's browser makes the request for a resource. If you're letting your browser request code you don't want to execute, that's on you.
if you ask a question in r/reddit (I know it's not officially part of the community) you get answers telling you to google stuff or to "just" check the docs where someone writes a package name.
The Benefits of Serving Stale DNS Entries When Using Consul
>"It prevents that ever growing pile of intractable mud that every CSS codebase tends to turn into over time"

This is why the key is not having a seperate CSS codebase. The separation of CSS and JS is just a legacy of web development from the time before component based application development. At most you might need a common source of basic variables like theme colors. But essentially everything else should be scoped within the context of an individual component, and live directly within that component. Huge stylesheets with specific selectors and complicated BEM style class names just aren't necessary anymore.
"If you can suppress the urge to retch long enough to give it a chance, I really think you’ll wonder how you ever worked with CSS any other way.” - Adam Wathan

The advantage of Tailwind [1] is very subtle over the short term (such as not having to constantly context switch between HTML & CSS files), but dramatically impactful over the long term.

Both in terms of time-savings, as well as code quality and ability to work with others quickly.

It really is something that you must earnestly try to gain an appreciation for.

My initial reaction was the same as the authors when I first came across it. Actually using it on a real life project changed my mind.

[1] - https://planflow.dev/blog/the-main-advantage-of-tailwindcss.
You can't experiment if you don't even know the basics.

> We really need to teach kids

Ah yeah. Because every single beginner is a kid, and everyone learns to cook when they are kids.
What an odd title.

This is about the recent git LFS RCE (CVE-2021-21300), which afaik does not effect linux.
It's okay if you decide for yourself that you want no part in this. But I don't think our global waste problem will be solved by berating people that enjoy smart homes as a hobby, convenience, or both.

I've been a fan for about 5 years now and I have everything connected as well. It used to be a big pain and it still can be sometimes, so I don't agree 100% with the comment you replied on that it saves time in a significant way. Though I assume that depends on your setup and how much you tinker with it. I know I will never get back the time I invested over the years in trying to make things work by not having to press light switches anymore.

But you know what? It's fun. I like it. It's the closest thing to an Iron Man like house we have so far. And I will be damned if I let it be ruined by you shaking your head and calling us enthusiasts mad.
The whole French Nuclear industry is government owned, steered and run - there currently is no economic model in the western world, which supports a successful market-based model for nuclear power.

France runs a lot of totally outdated reactors, because there is not enough money available to replace them. Even extending the lifetimes costs a lot of money, which had better be invested in a future decentralized market-oriented energy landscape.
Nothing about encouraging people to actually pay for the services they use then?
The analogy isn't great, because you having car A ( with its advantages, like easy to remember, good SEO, good pun on the company name, etc.) doesn't preclude anyone from having the exact same car bought elsewhere. Domains are unique, cars rarely are.
I don't think this project is feasible, it would be
much easier to disable all JavaScript-files except white-listed files
When I started in a project that made use of tailwind, I initially exactly felt the points the author is making here: The HTML is a mess, dev-tools don't play as nice, why would anyone like this?

Unlike the author though, I have grown to love it - not having to look at two files to understand what's going on (html/css) really felt like a big boon, especially for "trivial" UIs that just need a bit of flexbox, css-breakpoints and a margin here and there to get going. For more complex stuff, falling back on custom classes is still perfectly fine.

Also, the "html becomes a mess" argument was only an initial issue. Once you get used to the tailwind-classes, most of it becomes fairly readable - the examples of the author are, in my opinion, just as unreadable in css, especially if you're not a design-oriented css-geek (like myself).
I think you’re spot on - development is a big tent and it’s totally cool for this to be personal preference.
Here in eastern germany it is still not recommended to eat mushrooms from the forest regulary. And the meat of every wild boar that got hunted, needs to be checked for radiation levels, too - and they do not disclose how much meat has to be thrown away. All as of today - because of a event, that happened 34+ years ago.
CSS-in-JS originates from the needs for reusable and/or separated web components, so if your website can be factored like them it might be better. To be sure, I do hate "do it in JS" movements and I will gladly get rid of them if I can achieve the same without JS, but it is way better than keeping your HTML (templates included) and CSS (Sass included) in sync. Tailwind does nothing in comparison; it is just an abbreviated inline CSS with opinionated defaults.
>My first question is: is it really less dire there?

Yes, the situation is comparably better in Europe. We don't really know what you Yankees are doing on the other side of the pond, but we don't want any of it here for sure. Your nation is a bad example to all of us.
> This has nothing to do with corruption.

In the end it has. Development and building of energy storage systems of any kind was not in the focus in the last decades because nuclear energy and coal was always "the solution" for energy problems and the big four told us not to worry about anything, so they could do their business as usual.
> And the whole point of gender discrimination is that "on average" women's technical skills and experience are undervalued.

As have been pointed out before: most of us live in somewhat capitalist societies. Capitalists are AFAIK primarily greedy not primarily evil.

I don't believe for a second that Facebook wouldn't take the opportunity straight away if they could get the same work done for less money by hiring women instead.

IBM too. That should cause a feedback loop that increases salaries for female engineers until balance is reached.

Anything other would imply a lack of information somewhere or that capitalists were more evil than greedy.

Now that I think of it: Lack of information one or more places is actually an interesting hypothesis in its own right.
The space and capitalisation makes it even more confusing, `f#king` wouldn't have been so bad; `f##king` or `f*king` (or the more common vowel-omission style `f*cking`) better.
Well, it worked 7 months ago for this item: https://news.ycombinator.com/item?id=23895789
What is the EU doing to address the innovation divide? [pdf]
Indeed. Also, "very painful" is subjective. I never had issues with async code in JS (well, I had bugs, but it's not a fault of the language). There's nothing painful in async JS.
It's indeed a weird one. Like how is it a problem that one has to a lean a framework?

Just RTFM.
I thought that's what I wanted too, but then I got the big 4k TV and in the end the "smart" features are really convenient. You don't have to control a separate box to watch something. You don't have to cast from your phone. You don't have issues with an Apple TV show not casting to a Chromecast. You just click on it with the TV remote.

And if you think you'll put up with it just to avoid connecting the TV, your family members won't.

So I just blocked the ads via DNS. So far so good.
The point is: they can rely on their neighbors as a kind of safety net for times when renewables output is not sufficient. And the Norway hydro-storage potential also plays a huge role here, it allows Germany to have less domestic storage and gas peak plants, thus preventing the electricity cost from soaring even higher (which is already the highest in the EU).
I used to think like this for a long time, but after using Tailwind on real projects - there is a definite moment when it clicks and you wonder why you've been doing it any other way.
Nuclear power plants rarely have been used for district heating. Lot's of nuclear power plants are heating up rivers...
>removing microplastics from laundry discharge water

Much better way of addressing a lot of the microplastics problem IMHO. Regulate it out of common frivolous sources like e.g. "exfoliating microspheres" and then start requiring washing machine OEMs to put replaceable filters on the discharge.
Great site.
One request, can you put a description into the readme, along with a link to the hosted site?

It took me a second to figure out how to run/use it.
Nice article, just some of my opinion on the points raised:

> In my personal experience, poor naming conventions (or just poor variable names in general) are the source of a lot of confusion when other people read your code. I would rather look at some CSS that has padding: 0.25rem or margin: 0.5rem instead of trying to mentally map Tailwind’s p-1 or m-2 to their CSS equivalents.

Short names for commonly used concepts helps readability (quick to read, takes up less space) and makes it less tiring to type + change. It super tiresome to write long winded CSS (media queries are especially bad for this) and then find out you went in the wrong direction and have to rewrite it.

> Look, I don’t like Tailwind for lots of reasons. But none of them are nearly as concerning to me as vendor lock-in. It’s why I don’t want to invest time in migrating existing projects to Tailwind, and why I’d be reluctant to use it for any new projects.

Is this a real concern? I've migrated sites from custom CSS -> Bootstrap, Bootstrap -> Foundation, Bootstrap -> custom CSS etc. and it's always painful not matter what. At least with utility classes, you don't get problems where you're scared to delete CSS because you're never really sure where it's being shared. You generally just want to rip out all the previous stuff too as combining two frameworks isn't practical.

> For starters, if you’re not sure what to call that <div> in your markup, consider whether it’s actually needed. One of the great things about the Semantic CSS paradigm is that it forces you to structure your markup logically and meaningfully.

I think what makes utility classes nice for custom designs is there really aren't good semantic names for a lot of things that are only there for presentation reasons. Like I need to put a <div> around the heading + intro text so I can add some padding between those and the screenshot under it...so call it `.intro-wrapper`? Now there's a CSS quirk that requires me to wrap that all in the <div> so call it `.intro-container`? I want to make the three lines of the header animate in one by one so call them `.header-line1`, `.header-line2`, `.header-line3`?

It's tiresome coming up with name for stuff like this you only use once and even more so when you're experimenting and might not even need them. It's just noise that requires you to keep jumping between your CSS and HTML definitions to get anything done. Use semantic HTML tags like <header> <h1> etc. and custom class names for things you're sure you're going to reuse though.

Either way, utility classes is yet another "it depends" choice where there's no single answer. Use it where it makes sense.
Aren't all statically typed languages colored anyway? With something called a type.

What's the point of using a type system if "color" is not a feature?

It eases maintenance and working as a team.

And regarding complains about requiring to add or removing await everywhere, this is equivalent to saying "you shouldn't tell everyone that your proc can suspend and all assumptions about the real control flow are off".
> And they will switch to Lignite / brown

Germany does not. coal usage has been going down.
Institutional Crypto Trading on Coinbase Reaches Record Volume
I think the resolution to the author's consternation is that Rust's/some/most async run-times have "good enough" (in his view) color management.

You still need to manually manage color (aka blocking vs non-blocking, sync vs async). E.g., it impacts how you write the calls. So, the coder must be aware of the colors -- a big chunk of the problem / annoyance even if compilers / type systems can perhaps flag / catch errors.

I think what happened here was that the author found such awareness and management personally easy enough to use that he wanted to dismiss the entire coloring complaint. Then, in his zeal for dismissal, he made logical errors / mischaracterizations / exaggeration. It happens. Probably best to just move on. (EDIT: Focusing on such situations doesn't help perceptions of programming language evangelism/propaganda.)
> Merkel would have governed against the strong will

Her changing positions got a 10 point bump. It’s a large group for sure, but it’s still just placating dimwits to gain quick political support to stay in power. The vast majority clearly didn’t care.
I've always found the architecture to be amazing. It's my go to reference for implementing things like plugins or events into other python projects.
And then... you'll keep two wildly different CSS styles for the same project? That doesn't seem reasonable.

Vendor lock-in doesn't mean that you can't get out at all, just that it has significant cost. Maintaining both Tailwind and another CSS framework/philosophy/classes in the same project has a significant cost.
I will pedantically note that in database theory, "relation" is a name for what we usually call a table. You're talking about relationships.

https://en.wikipedia.org/wiki/Relation_(database)

If your data is completely flat, and fits in one table, that's still a relation!
I'm actually on the same train right now, are there any good learning resources to get into modern C++(CPP17/20)?
The big "aha moment" with dev tools for me was realizing that instead of interacting mainly with the style editor, you transition to interacting primarily with the classname editor with tailwind. Then dev tools is your friend again.
I laughed seeing that headline, as I uninstalled WebEx from my work machine not 15 minutes ago and came across this gem: https://imgur.com/8l572YF

Which for me really drives home how "up2date", modern and user-friendly this abomination of a software is.
The Ocean Cleanup project started somewhat like this. They made prototypes and extensive testing, and concluded honestly that cleaning the ocean isn't doable, so they turned to cleaning up the source of most oceanic plastic: rivers. Their river cleaning boat is completely different from their initial idea, but it works well.

Ideas are cheap; execution is hard...
> On the other hand, the rest of the 64-bit ARM world has largely converged on two competing standards: UEFI + ACPI (largely used by servers running Windows or Linux),

It's not supposed to be just for servers, the Arm Base Boot Requirements (BBR) require it for any non-embedded use https://developer.arm.com/documentation/den0044/latest

The new ARM64 laptops follow BBR so they have UEFI+ACPI, which means they can run standard Windows or Linux distributions from Red Hat / Canonical. By using device tree instead, it means other operating systems won't be able to run out-of-the-box without some modification. I can totally understand and respect the decision not to touch ACPI, I just think it might not be a great long term decision.
Im really surprised to hear it didn't work for a resin printer. You should create an issue for it.
No sql injection, can set permissions for each proc, isolates app from DB implementation so you don’t have to redeploy app. Eg you can migrate older data to an archive table and query it on certain circumstances. App doesn’t need to know.
> If a cloud customer isn't continuously testing a migration they're naive

this is a dumb point of view, that only cloud providers (and their employers) can advocate.

if i'm a company, being "on the cloud" doesn't automatically makes me money. my business makes me money. if every two years i have to waste a year (or even six months) re-architecting then "the cloud" is costing me people money on top of the infrastructure money.
It's like people only see one side of home automation: "everything is connected to the internet"

Please do some reading or at least inform yourself this is not the case.

99% of all "smart" devices in my home are connected to local APIs only without any need for the internet.
I second that. The majority of web projects I've seen had class names scattered all over different files and it was always a nightmare to make significant changes. You don't have this exact problem with Tailwind.
And we could use that energy instead to fill storage systems, be it water reservoirs or large battery packs or what might come.

But we need to have the right technology to do things like that...
It usually is. You can usually find some research or news about same tech used.

from 2013 article [1], though it seems not practical [2]:

"W2Plastics has shown the viability of magnetic density separation, where flakes of shredded plastic such as polyethylene or polypropylene are mixed into a magnetic fluid made by adding iron oxide to water."

I am not sure which one is better to show kids they discovered something existing, or praise them like this

[1] https://horizon-magazine.eu/article/magnetic-attraction-recy...

[2] https://cordis.europa.eu/article/id/131208-sorting-plastic-w...