skysight-inc/HackerNews huggingface dataset:
Logical replication is also great for replicating to other systems - for example Debezium [1] that writes all changes to a Kafka stream.

I'm using it to develop a system to replicate data to in-app SQLite databases, via an in-between storage layer [2]. Logical replication is quite a low-level tool with many tricky cases, which can be difficult to handle when integrating with it directly.

Some examples:

1. Any value over 8KB compressed (configurable) is stored separately from the rest of the row (TOAST storage), and unchanged values included in the replicated record by default. You need to keep track of old values in the external system, or use REPLICA IDENTITY FULL (which adds a lot of overhead on the source database).

2. PostgreSQL's primary keys can be pretty-much any combination of columns, and may or may not be used as the table's replica identity, and it may change at any time. If "REPLICA IDENTITY FULL" is used, you don't even have an explicit primary key on the receiver side - the entire record is considered the identity. Or with "REPLICA IDENTITY NOTHING", there is no identity - every operation is treated as an insert. The replica identity is global per table, so if logical replication is used to replicate to multiple systems, you may not have full control over it. This means many different combinations of replica identity needs to be handled.

3. For initial sync you need to read the tables directly. It takes extra effort to make sure these are replicated in the same way as with incremental replication - for example taking into account the list of published tables, replica identity, row filters and column lists.

4. Depending on what is used for high availability, replication slots may get lost in a fail-over event, meaning you'll have to re-sync all data from scratch. This includes cases where physical or logical replication is used. The only case where this is not an issue is where the underlying block storage is replicated, which is the case in AWS RDS for example.

[1]: https://debezium.io

[2]: https://powersync.co
All those options are significantly more expensive than what we've been building. I mean, we've built fast reactors, and thermal breeders with thorium, and had pilot efforts for U extraction from sea water. None of them could compete with LWRs with a once-through fuel cycle on conventionally mined uranium.

Fast reactors also present the possibility of prompt fast criticality (that is, an actual nuclear explosion) in a serious accident if enough of the core melts and moves around.
Simplicity, great documentation, IDE that guided you, WYSIWIG, easily multi-threaded when needed. Delphi/C++ Builder is a business failure, not a technological one. No ugly hacks for things like CORS/XSS needed. Electron is basically repackaging a distributed app into a desktop one, so it's clear it's going to be way more complex than a primarily desktop-based dev system.
That's damn true, harsh but true and we need to face the reality
"Cask strength" usually refers to whiskeys that have been aged in the cask, angel's share and all. It means that the manufacturer didn't dilute the product any further before bottling.
The 2012 Smith-Mundt Modernization Act (2019)
This is my share and want to add four things:

- WMDs...were a lie. An obvious and intentional lie. A lie that no one seems to remember. Maybe our collective consciousness is too embarrassed?

-Aside from the shock & awe phase, there was little media coverage. Contrast that with Russia and Ukraine. Yet another subtle example of how The Media (at least in the USA) has lost its journalistic integrity.

- Opportunity cost. Combine Iraq with Afghanistan and that's a lot of lives, time and resources gone. Forever. Imagine even half of that used to move the needle in a positive direction.

- The Military Industrial Complex - It's not a conspiracy theory. It is real. The Biden Administration has push the DOD budget over $800 BILLION and was effectively met with crickets. Money we don't have to over-spend on things that we don't need.
Working around underlying problems with tools and conventions is something that is fine when you get paid for your time.

As a maker, I prefer a clean stack. So that its complexity does not slow me down. Workarounds make development slower and slower, the more it becomes a giant hairball of workarounds and workarounds around workarounds.

In Python and JavaScript, I don't need those workarounds. Would be awesome if PHP catches up.
>"You want a button? you have to style a div to get what you want"

No, you don't, there's a <button> tag. If you don't like the default button style, then yes, you'll need to style it. But that goes for any UI framework.
It depresses me too, but what else can you do? I check what the docs look like, but if I'm to depend on a thing I'd rather choose something popular than unpopular. GitHub stars, Hackage downloads, StackShare... what else can one check?
Molten salt reactors might provide superior safety (the thorium is irrelevant to that). However, they also would likely imply higher operating costs, because now instead of being sealed in fuel elements your fuel is flowing through a larger part of your reactor, and volatile fission products are escaping into the off gas and have to be trapped in another system (which will have to be cooled to prevent melting). So you now have complex systems that are too radioactive for anyone to touch for maintenance. Reactor structural elements are also now exposed to more neutron radiation as well.
That's a very interesting question. There are so many things you can look at. How is the documentation? Who are the primary maintainers? How are they funded? What are their motivations? Are the primary maintainers active on Stack Overflow, Reddit, Discord, etc...? How many contributors are there? How does their Github issues page look? What about the Github discussion page? How many maintainers are there total? How many downloads per week on NPM (for JS libraries)? From all of these things - how long do you expect this library to be maintained? And that's just the initial qualification research, nothing about how it will impact the actual code-base.

What did I miss? What's the best answer you've ever heard? How do you evaluate 3rd party dependencies?
You could make a religion out of this... oh wait
I can't help but think you're making a lot of not particularly charitable assumptions about people who opt out of online culture in this comment.
> The current solution for code reuse (use longer class names to avoid clashes, we help you with syntactic sugar called "namespaces") is the wrong approach imo.

You can in theory create modules with require.

module.php

<?php
return (function(){
$foo = function(){echo "hello from PHP";};
return [
"greet"=>$foo
];
})();

script.php

<?php
$module = require('./module.php');
$module["greet"]();

But PHP namespaces and autoloading via composer ARE the community accepted way to handle namespacing. The ecosystem is so large developers aren't going to move to a different module system at that point. Especially when composer is the defacto package manager for PHP.
There was no need to reach for more sophisticated tools; these were sufficient to give them the results they wanted.

I suspect you wanted research where people look at the world and discover what it means. This is the other kind, where people decide what they want the world to look like, then paint their data to reflect that.
What kind of answer would make you happy?

I prefer to look at the recent commits, or any recent activity on the repo's issues, but I would like to know what else can be used as an indicator.
I actually have no idea if it still applies, but I haven't seen code that uses it for a long time. Maybe it was important for desktop apps?
Exactly this, all the other sciences were a philosophy before they grew and got 'codified'.
AWS has a large learning curve, for sure. I've been using it now for several years as an admin for some scientific applications that present web frontends to customers.

A few notes:

- for personal or small stuff I'd recommend Lightsail instead of EC2.

- set budgets so that aws turns off your services if you go over.

- never expose your ssh port to the public internet. Lock it down with firewall rules from the outset. Lightsail does this by default.

- I'd still not use AWS if it was my money at stake. I have not screwed up yet, but it always feels possible.

- I've had to remediate at least one account whose app and architecture were incredibly poorly designed and were costing over $500k/pa when they should have been designed differently and cost no more than about $1k/pa (less again these days) for function, user load and security. AWS made those poor design decisions easy because those who built it could spin up anything and everything with no second thoughts.
Hey, everyone!

I wanted to share my latest DailyUI Kit on my Figma page with you all. As many of you know, Figma is an incredible design tool that allows for collaboration and iteration in real-time.

If you're interested in design or simply want to see some cool visuals, head on over to my Figma page and take a look. I'm always open to feedback and would love to hear your thoughts on my work.

Thanks for your time and I look forward to connecting with you all!
Version conflicts on shared transitive dependencies is a real problem, to the point that there are tools available to library authors that allow them to rename their dependencies to be under their own namespace to avoid collisions.

If two packages I require depend on incompatible versions of some third package, there aren't any easy ways for me to resolve it.

This problem exists because of the global nature of PHP namespaces.
I wrote a tiny tool which calculates the "brightness" score of a github repo based on calculating the total star count of the people who starred your repo. It will automatically detect these kinds of scams (assuming that it's mostly low star bots giving the stars).

https://github.com/Hellisotherpeople/Bright

Edit: I love clustering, I really do, but I think that techniques like the one I am using are far superior to unsupervised learning for trying to detect fake accounts in this context.
As a relatively old person, I've had a few experiences of waiting for my favorite niche language to finally get a decent GUI library. In my experience, it never happens. It's just too much work. Only the most popular few programming languages in any given moment have usable GUI options. Even something as comparatively mainstream as Go lacks a good GUI story.
Street style from Seoul fashion week
Generating 3D meshes with machine learning
Check out our MeshDiffusion model that can generate 3D meshes effortlessly. The code is available here: https://github.com/lzzcd001/MeshDiffusion/
The move does show, though, that Docker isn't shy about changing existing terms. So there's merit for some projects to take control of their namespace. It doesn't seem inconceivable that at some point in the future, Docker will say that exchanging tokens in a personal user account to enable "hacky" org type features is a ToS violation.
Recently I nuked my Reddit account. I didn't delete the actual account, but I purged everything I've posted as a comment or submission in the past 10 years. I don't think it's a loss even for the cases in a thread where I was being helpful to someone. Most interactions, even this comment I'm typing right now should be considered a conversation in a coffee shop or a small convention where the topic at hand that gathered us is the OP link/post. As soon as the convention is done we all go home. Whether we want to remember the conversation and what was said is up to us. Most threads devolve to single-to-single interactions anyways or at most 3 people exchanging ideas in a sub-thread.

In my view these conversations should be ephemeral, but in reality the internet can keep them (barring digital or natural apocalypse) forever. I truly don't think there's value for keeping the vast majority of online interactions stored forever. There are actual physical limits here as well. At some point in the future there might be a case for which types of information has to be stored for future generations and which shouldn't etc.

All of us as humans have some inherent capacity of comprehending and analyzing information. The internet turns out is not like a second brain for us, but more like a crazy neighbor screaming at us at all times.

Maybe I'll nuke my HN account at some point too. Don't get me wrong I've searched old HN/forum/reddit threads to great success, but like I said above, I think we're not capable of handling all that information maturely. Who decides what's useful or not I can't say, but I'm at least responsible for my own comments so I can make that decision for myself.
Can you explain why is it "natural" to try to get your repo to have many stars in a world where starts can be bought?
> There was less than 100 deaths from chernobyl

There may well be tens of thousands of deaths from Chernobyl. No, we can't state that these deaths absolutely occurred/will occur -- they are spread throughout large populations, mixed into the vast number of naturally occurring cancers -- but technology regulation is not like criminal prosecution where things must be proved beyond reasonable doubt. Technologies are not innocent until proven guilty.
Regarding this street fashion, it hasn’t really progressed much since Tokyo FRUiTS of the 90s which was basically the apogee
Similar to the palm oil, when imported, the tallow comes in on chemical tankers (whose cargo tanks' most recent cargoes were things like benzene or methanol at the cleanest).

Yum.
There has been a lot happening in Norway in the last five years when it comes to farming kelp. The industry is still in its infancy, but I know one company that have invested toward expanding production toward 100,000 mtn.

It's a lot of exciting new problems to handle though. How do you conserve biomass, preventing it from rotting without using excessive energy. Kelp is high in iodine, so for human consumption how do you get it out? Labor is very expensive, so how do automate seed production and harvesting? And how do you find a market and ship the product there?
I used to be a musician and as i worked in tech, I set up my own website. Everyone else thought i was crazy, MySpace was here to stay - that was the standard that everyone used, anything else was a waste of effort.

Because platforms (like MySpace) can disappear almost overnight, I would always recommend setting up a blog on a domain that you own and control. Mine is https://markgreville.ie and i have been on the front page of HackerNews a couple of times. I have had lot of people reach out to me over the years, including some very famous tech luminaries (people who’s books i read from cover to cover as i was learning to be a programmer, then architect, then leader). I have also found a lot of great talent through it.

My struggle initially was worrying that i would seem pompous for writing publicly, and that no-one would find any of it interesting. However, most of my friends ignored it, and i found a community on HN that was my tribe instead.

If you are reading this and haven’t blogged before
1. Register a domain now
2. Set up a simple site (Wordpress will do for now, don't over think this bit)
3. Write about something you have done, or something you are passionate about
4. Have a trusted person read it for you and take feedback
5. Edit, publish, and post on HN
6. Start the next post
Europe really isn't that much better these days. Obviously it isn't as extreme as in the US, but plenty of people still have had their lives ruined because of the pandemic and most societies are pretending like nothing happened. I hope there is a European country that is set to be better in 10 years, but at least I don't know about it.
That seems strange, odd to throw out all away at that stage, when all the work has already been done and the expense of typesetting it has already been paid. Getting it bound is relatively less, unless they wanted more than one copy.

Maybe he disagreed with the corrections? Or maybe he had run out of money to correct minors? Maybe the reviewers were critical and he was annoyed by that.
Excellent, we're getting Soma. All the pieces of the perfect dystopian novel are coming true...
I'm using a mixed monitor setting on KDE on Pop_OS (I know, I added KDE to Pop_OS just to try Plasma and loved it). It all works on X11 but the jank is true - I am indeed afraid of any plugging/unplugging to avoid disturbing the setup (using a Lenovo thunderbolt dock with Thinkpad X1 Extreme Gen 2 which uses Nvidia MaxQ graphics).

Maybe I'll go back to using straight-up Kubuntu (or even just Debian) - the only worry is quality of support for Nvidia card - Pop_OS folks were the only ones with a fully working Nvidia setup when I started using it but maybe by now, Kubuntu and/or Debian also has similar level of support. Would be great if someone using Kubuntu/Debian on a mixed monitor setup with an laptop with Nvidia graphics can share their experience - ideally with Wayland since I'm interested in moving to it for better multi-monitor support.
What do you mean? Backwards compatibility in PHP is amazing. I have several large projects that I've been working on for 15+ years, and upgrading to newer PHP versions has been a dream.

What kind of things are you having problems with in regards to backwards compatibility?
Rust's 'one-size-fits-all' approach and the 'rewrite it in rust' movement are due to the language's high-level flexibility whilst also being as low-level as C.

If you set out to write a new language in Rust, to escape the perceived limitations of the language, you end up extending Rust, not building a new language, and now you have Rust without the limitation you started with, and others can benefit from your work.

I've written two videos on the topic that I'd love to know your thoughts on, the first talking about Rust's universality due to both the unsafe and macro systems:
https://www.youtube.com/watch?v=PuMXWc0xrK0&list=PLZaoyhMXgB...

The second a deeper dive into the macro system:
https://www.youtube.com/watch?v=MWRPYBoCEaY&list=PLZaoyhMXgB...
There are diminishing returns to everything, travel included. If you go deep enough, you’ll typically just uncover the mundane, everyday realities, that people are often not willing to share with a foreign, relatively wealthy tourist.
It's still taking time I think. We understood that L1 should never have been the place for the end consumers and that's why all the chains (Bitcoin-Lightning; ETH various systems like StarkNet, zkSync, Loopring and so on) are currently in the process of finding out how to make everything that is happening on L1 possible on L2. On Ethereum one big part left out is still the the general ability to run EVM code on L2, but that is happening like right now.

Biggest problem after that will be user experience, but I am currently in the Ledger Connect (now Ledger extension) Testflight beta and it makes using dApps on iOS with a hardware wallet a really good experience. No cables, no app switching, no weird abstraction barrier. The new Stax also seems like a well thought out wallet that was created with a focus on UX. Only thing I don't yet see is a good NFC integration for existing payment terminals.

I still think the industry is really early. Layer 3 is now a topic for privacy preserving user interactions which is super interesting. It doesn't then stop at being your own bank, but with it you will be able to really control your own identity without anyone standing in the way. For needing less trust sharing your data and being self sovereign. Using the chains just as a highly accessible, authorized data store.
What's wrong with hallucinogenic LSD?
> ConfigureAwait(false)

It’s literally the configuration, to be used according to your needs
most people don't know that stars are bought
In mice. Nothing to see here(yet).
How did the Ethereum research community disappoint us all?
You never want to block your UI thread for any amount of time a user would notice say more than 20ms. And if you use async or another thread you can always update the UI to disabled with spinner state. This is all less
convenient for the programmer but much better for the UX. Blocking the UI
blocks it all, even the close button!
Hours instead of weeks? What makes you assume that? An experienced web developer can iterate pretty damn fast.

I can understand the appeal and advantages of using native GUI tech. Really. But there is a reason people use stuff like Electron/Tauri/Wails. Web tech has seen so much investment, and as a result, you now basically have a app platform that runs anyhwere, offers a huge ecosystem and a great developer experience. Which I never found to be matched in any other GUI toolkit.

If there was a GUI toolkit that offered me all of this without requiring the bloat of a browser, then I would switch in an instant. It's just not there.
That's sounds pretty good, actually.
I'm confused by the discussion of OO. Just use an enum, aka algebraic data type, if you want control over the data. You can build an extension point into the ADT for user defined components, if that is desirable. The tradeoffs of OO style vs FP style vs having-your-cake-and-eating-it aka the expression problem are well studied. (This comment is a bit cryptic. Sorry. Don't have much time right now. Might return later.)

My experience using ECS in bevy is it feels like fancy spaghetti code. I'm not convinced it's a great approach, at least on the small scale I'm working at.
Im curious what work you do that you need that many 4k monitors, let alone 8k ones?
Very cool but deep fake news for all is scary!

Is the last face in the demo a mix of bill gates and will Elon musk?
I always use sprinkles of jQuery over React/Angular/Front End Framework de jour if given the choice.
The utopia is crashing and people are mad.
Therefore, we performed a pan-aminergic-wide GPCR functional screening campaign using a G protein dissociation BRET-based assay platform38 optimized for 33

human

aminergic GPCRs (including serotonin, dopamine, adrenergic, histamine, and muscarinic subtypes; Figure 1B; Table S1)

From the paper itself: https://doi.org/10.1016/j.celrep.2023.112203

It’s an interesting read.
Natural: promote the repo, people see it and like it. I don’t beg for them.

Unnatural: pay some bot runner to buy stars.

I prefer natural as the stars are a metric not an end goal.
The difference is that for James Cameron's projects could rely on buying existing expertise from contractors. A small nation has to build that themselves in secret.
Do you use PopOS with KDE on System76 hardware? I tried that and the trackpad was not fully functional.
Dumping 1M gallons of radioactive water in Hudson is ‘best option,’
It's nice but maybe too crazy for some, or interfering with your general agenda of the day
News of a bad thing happening to someone far away does not really impact survival as well.

The point was not about providing a good counter-example. I wanted to show that when one hand-waves away a behavoiur to an abstract selection criteria, one can easily come up with criteria that contradicts that notion.
Because the web has nothing to facilitate that. Almost literally nothing: from rich components to data handling to control over rendering if needed.

So the VB/Winform model of building GUI on the web has to re-invent all controls from scratch, then all dat abinfding from scratch, then...
This is the result of you surrounding yourself with terminally online people. Those who don't spend their waking days using social media are perfectly fine but you don't hear about them.
Next keyword: market of lemons. If you can't rely on said signals anymore, you must treat every item the same (untrusted), which drives out the legitimate players from the market. We have a lot of lemon markets, we can probably infer from them what the social result will be..