skysight-inc/HackerNews huggingface dataset:
I received the opposite care. Was delivered by C-section, no contact with anyone while in incubation for several weeks. My mother would often tell the story of how she was unable to touch me for weeks after my birth.

45 years on and I haven’t a single bond, not with family, not with friends, not even with animals. Like a ghost floating through the world with no attachments and seemingly no compelling interest in them. Active avoidance is on point. But don't be sad for me. It's just the way I developed. And the lack of bonding, skin-to-skin contact with my mother is one possible reason.

They’ve tried to make a number of diagnoses fit, from autism to Schizoid Personality Disorder, Bipolar to Asperger's. Nothing. Nothing fits. There's nothing wrong with me except that I don't bond, at all.

One of the more disturbing experiences was watching what happened to chimpanzees when their mothers were taken away from them after birth (or were denied bonding entirely). They rock back and forth with anxiety; they grapple for the nearest comfy thing; more rocking. It was like watching myself. I'm typing this 45 years later holding a pillow for comfort. You'll rarely see me seated without one. I rock all the time. The pillow, the rocking. They fill a hole. It's protective somehow. I'm sure a shrink would say it reminds me of the womb that was stolen from me.

And I know I'll live the rest of my life like this, without bond, alone, and not really sad because of it, just totally missing what compels others towards their own kind, to bond.

So, yeah, more skin-to-skin sooner. No more lost people like me. Again: not sad about it, but life without others
(and very much not wanting them) can be a severe challenge. You have only yourself.
> gray boxes simulating text

This is one of the worst UI trends in the last decade. Mock content gives devs permission to ship slow APIs, and they can even look janky when your API is too fast. It feels like watching a half hour of trailers before the movie starts.
Promising project.
1. Is there a possibility to limit the ressources allocated to a user?
2. Is there a reason that there's no (possibly restricted) online demo of NocoDB?
I liked the overview i remember myself having 15 years ago, today there's a new library/API/service to learn everyday to keep even the simplest things working.

Everything is sluggish, everything takes ages to load, to compile, to understand.

Also simple web apps i try to prototype takes ages to make and debug. Anyone else feel this?

It's like something always goes wrong with some dependency, some build process, some versioning error, some service, so you end up using 95% of your time setting up services, reading manuals, and debugging instead of coding which was simpler in the just-post-spaghetti days of web-dev.

I don't know if it's feasible yet but i hope switching to less technologies with more mature JS/CSS and a few minified libraries run locally will work out for me - harder with teams of course.

I don't know what's a good simple backend with the same philosophy, Laravel Lumen maybe? I feel like you need some layer above sql unless you wan't crazy complexity - or maybe a simpler database / api system.

I want the simplest system possible! (who doesn't)
My shit test for "is this article likely a bunch of FUD or just outright BS" is if they actually link to the source material. If they don't, I usually continue reading it but make a mental note that they're likely pushing some specific version of the event or facts in question.
The Devil Facial Tumour Disease" they suffer from is one of the few non-viral transmittable cancers. According to Wikipedia affected populations after wiped out in just 12-18 months.

It is transmitted by biting, but also any contact with cancer cells (such as sharing food), so the most active/fittest are hit first.

Long term a totally separate population is the only way they will be able to keep the Devils from extinction.

https://en.wikipedia.org/wiki/Devil_facial_tumour_disease
This! As the numbers become larger, the distinction becomes more important.
>And of course anybody can drop a few bucks on a blog of their own.

And no one will read it unless you can post links on facebook, twitter and reddit. In the end, almost all communication online runs through a limited set of american megacorps who all act in the same ways, have the same rules and align to the same culture.

It's no surprise China and Russia ban American sites because those sites control the debate and culture of the places that use them.
- It "calls you" (i.e. you never explicitly call your React components, React does)

- It permeates your codebase (e.g. migration from moment to date-fns is something you can realistically do piecemeal, React to Vue or vice versa not so much)

- It enforces a specific architectural paradigm (components) to the exclusion of others (e.g. MVC, MVVM, etc)

- Its direct competitors are frameworks (Angular, Vue, Backbone, Aurelia, Mithril...)

- it is composed of multiple libraries (react, react-dom)

- Experience in it is considered a primary hiring criteria in many shops (which typically isn't the case for libraries)
The training length for physicians is pretty much the same in all countries. In the US to become an anesthesiologist: 4 years undergrad, 4 years medical school, 4 years residency. Total: 12 years. In the UK to become an anesthesiologist: 6 years medical school, 2-3 years of general postgraduate training, 5 years specialty training. Total 13-14 years. Why did you not look this simple fact up before saying it authoritatively on here?

There's more to it than you think, and it's easy to think that it's a simple procedure whenever you don't know what can go wrong, why things can go wrong, and how to fix things if it does go wrong.

Also, the doctor isn't why it's expensive. Doctors don't set the prices, hospitals and health insurance companies do.
This is the way.

But most firms don’t know how to employ a you to show them this way.
There's nothing particularly weird about client-side rendering (at least, it's no weirder than server-side rendering was in the era when most pages were static data).

It could, of course, be considered "weird" if one's mental model is that patching together document description declarations on-the-fly on a server to later be re-interpreted and rendered on the client is "normal."
Anecdote: I was in a corporate (software) packaging (and deployment) team for a fleet of ten thousand workstations.

The new CIO knew not our role and assumed we were a physical packaging team, dealing with bubble wrap and cardboard boxes - "why do we pay them so much?"

The CIO was educated pretty quickly. :-)

edit: I had time, I wrote a shorter comment.
Stuffed Dormouse and Fish Gut Sauce: The Flavors of Pompeii (2019)
"16 Physical Functions, 32 Virtual Functions"

Does anyone know what this means in the specs?
From the article:

"This is not to apologize for the bad coverage but, if anything, to underscore how egregious it was to lean so heavily into the Tom Cotton Is Wrong narrative"
At a very "lean" company that made power electronics (modular telecoms rectifiers and 1.5-5kW grid-tied solar inverters), I nominally worked as a test engineer but I wound up doing a fair bit of EE/firmware work on the products too. Above my bench was that typical drop ceiling stuff like in offices worldwide, except mine had little singed bits of semiconductor packages stuck in it from where things had gone wrong in testing and blown up transistors and such. All of us who worked with open electronics (often necessary during development, for probing or whatever) had earmuffs and safety glasses at the ready, and a wood stick for pushing the on/off switch. AFAIK there weren't any real injuries, but there certainly was potential.

My favourite near-miss was the result of a dumb EE experiment, not really code: I had built an 8kV surge generator to test against IEC 61000-4-5, and needed to test the generator itself. We spent an afternoon finding interesting components to blow up, at first under a shield, but the good ones would just make a satisfying snap or pop - not too exciting from a kinetic perspective. Then, I noticed a DVD... The surge through the foil in the DVD made one of the loudest bangs I've ever heard - easily louder than a gunshot - the foil vapourised and sent plastic shards all over the office.

The surge generator itself was a glorious hack; it used a neon sign transformer to generate the HV, and the main switch was a trigatron I made from a couple doorknobs from a home recyclers in the same industrial park.
GP “kelp” is the Way, but “hibikir” is the Truth.
Do you have sources on them looking at transaction data please? That is clearly not necessary for processing the payment.

Edit: Found an article in German - https://www.sueddeutsche.de/geld/zahlung-per-sofortueberweis...

They claim they need to do this to make sure there is sufficient money in the account, even with transactions that might not be reflected in the balance, and they also check for other "Sofortüberweisungen" to detect fraud.
Makes sense in a way but still quite shady. If there wasn't enough money in my account, or other transfers pending would my bank even allow their transfer?
i think the story is that doctors noticed cases of unusual pneumonia and investigated further. not impossible, especially in a country with SARS experience
Oh hi! What a pleasant surprise to see you on this thread :)

I guess what I was thinking was that when you're doing that, you're largely "postgramming". Some of the recent versions of Subtext that cater to test-first development are more "programming" in the etymological sense, but the "program" in that case is what we'd normally call a test suite—although other recent versions of Subtext turn the execution trace, complete with recorded results, into the test suite, which is more a question of "postgramming".
We call "latin" numbers "arabic" in English, because Europe received them from the Maghreb. "Latin numbers" is actually closer to "Roman numerals," what we call the old Latin system (V, VI, VII, VIII, IX, &c)
What is trance? The complex relationship between shamans and 'trance' (2011)
Good point. The difference between quality products sometimes just comes down to specified mechanical tolerances and purity levels of chemicals/ingredients. Though price usually increases much faster than quality at higher levels. Going from 95% to 97% pure might cost $X, but 97% to 99% will be $X * 5.
In her case, her gender clearly makes her stand out because men are statistically the overwhelming majority in the field.
Someone who came from a trade school or an underrepresented state might choose to bring these points forward instead, to share their insights with fellow working class founders.
As mentioned the most common motivation is for scaling the number of developers/teams. Other good motivations:

Differences in the maturity of software. You have a mission critical revenue generating core and newer experimental forays into new territory. You want to do this rapidly tolerating more risk but don't want to destabilize you cash cow.

Certain parts have differing requirements. e.g. a payments system may need greater auditing and compliance levels and separating it makes this easier to do.

The other often cited reason is ability to scale the infrastructure independently. This is still true even with cloud offerings, being able to size and configure parts differently can get you a long way into scaling. The alternative view is that you'll need to shard eventually and the sooner you figure this stuff out it can save you from having to implement a lot of intermediate scale solutions. Even with shards, you can still run into reasons to run parts of you system differently. e.g. choice of datastores, storage engines, isolation levels, etc.

I've worked in pretty much all these cases, as well as the let's do microservices from the start. That was hard as we were doing instant messaging and message delivery failure rates are critically important. At the same time, it wasn't unachievable with only a 3-4 pizza-sized number of devs. Not optimal though when the number of services =~ number of devs when you have turnover and have to learn/teach them all. I can say being able to change something and have CI run unit/integration/end-to-end/journey tests in a blue-green deployment to prod in 2 minutes is something I'll always miss.
This is 100% the NextDoor model. They hype up crime reports and sell adverts for ADT on the other hand.
I think it's a hard question because a lot of different things happened in different regions - you can't just point to things that happened in Europe and say "This is why!"

As an example, China had imperial examination[1] for government jobs since 607 - a system not seen in the West until modern times. Ancient Rome built concrete buildings that their descendants couldn't replicate for centuries, yet they failed to start Industrial Revolution.

[1] https://en.wikipedia.org/wiki/Imperial_examination
The first article you linked states that between 2019-2020 hate crimes against Asians increased dramatically in New York and Los Angeles: from 3 to 28 in the former and from 7 to 15 in the latter.

I think that characterizing this fact as an “ongoing spike in anti-Asian hate crimes” is a breathtakingly broad generalization.
+ at the root would indicate an abstract syntax tree rather than a concrete or "full" syntax tree (terminology varies slightly)

This was primarily a mechanism to load parsed documents in to code that didn't have access to the recursive descent parser that parsed the document, for either security or performance reasons.

Loading the XML with the appropriate parse flags, doing a pre-order traversal on all the leaf PCDATA, and then printing it out, would regenerate the original document byte for byte.

Perhaps I should go back and implement JSON output and see how I feel about it... thought I'm pretty sure once you introduce a bunch of "text" and "type" fields to the JSON tree it's going to look a lot less readable than XML markup.

There are other fields as well like line and column numbers (output as XML attributes)
Apple Airpods Pro protect users from over-loudness.

iPhone has an option to enable this protection for all headsets, but it doesn't work properly. For example, when answering a FaceTime Audio call with Bose SoundSport, the "call connected" tone often plays at max volume and is staticky. This is with the latest firmware and iOS.

macOS has no over-loudness protection.

Bose's expensive noise-cancelling headphones do complex audio processing but fail to protect users from over-loudness. I think the company has lost its ability to focus on user needs. Over the last 10 years, only their noise-cancelling function has gotten better, but other aspects of their headphones have gotten worse. Features I want in my next headset:

- active noise cancelling

- loudness protection

- swappable battery

- physical buttons

- mic windguard

- stowable boom mic so I can talk quietly on a call and still be heard

- an option to automatically pause music when I take off the headphones and resume when I put them on

- an option to automatically enable or increase noise cancelling when the environment becomes noisy and disable it again when in a quiet space

- Automatically detect me speaking and pipe my voice through the headset so it feels natural, even when not on a call.

- Work properly in extremely noisy environments. When I wear my Bose QC25 noise-cancelling headphones while riding the BART subway in San Francisco, the headphones emit painful crackling sounds when the train noise is very loud. I don't expect the headphones to block extremely loud sounds. They should not make the noise worse. Bose's headquarters is in downtown SF. I expect some of the firmware engineers ride BART every day. Does anyone know why they haven't fixed this in 7 years?
Over the last several years, it's become clear to me what the large social media companies want to be: de facto world governments.

They won't admit that, and you'll hear a lot of gab about algorithms and cooperation with various governments, but at heart it appears to me that this is cooperation with various governments as a government themselves. It's a negotiation among equals.

We can provincially argue about who can say what in the US on which platforms, or what the rules _might_ be to demonetize and/or kick people off platforms, but at the end of the day, the platforms themselves, through means mostly opaque to us, are negotiating as if they were our local tyrannical government with complete control over the public square and public places.

I understand that for many this is completely far-fetched and I'm making a mountain out of a molehill. This is a difficult thing to freely admit and grasp. It's also very difficult for those that are currently happy with whatever the most recent decisions are.

Yes, the net is still (mostly) free and open, and competitors _might_ come along and take the place of the current major social networks, but at heart this is a problem based on generalizing and universally abstracting social interactions. You could split up and/or dismantle every major player today and be in the exact same spot five or ten years from now when the next ones come along.

I am happy that more and more people are finally waking up to the danger here. If we are allowed to adequately describe the nature of this problem, we might have a shot at fixing it.
> Why would I use Stacked Git rather than Git’s fixup/interactive rebase dance?

Yeah, dance is good analogy. Lot of training, one little mistake and it is ruined.

For example, if you need to introduce a change in commit "one thing" which would require merge conflict resolving in "other thing", with stgit it would be much easier than with fixup/autosquash.

Or another example. You need to put away "other thing" for a while, and work with "one thing" for an hour, and then apply/fix "other thing". Another set of git tricks needed.

> But I’m not sure I’d take on a new tool dependency just for that.

If you are happy with git, nobody forces you to.

By the way, you don't have to use stgit all the time. I usually just use git, but when a change in a branch requires changing of previous commit, I simply do: stg init; stg uncommit; stg pop. It's easy to convert local repo state to and from stgit.
Microservices can be good. The problem is that people don't use them right (partially because everyone was joining in the fade, so lots of bad examples). Dependency management, documentation, and loose coupling are important. I work at a company that embraced microservices, but it's basically architected as a distributed monolithic. And there's so much overhead for context switching, paperwork, etc.

It's like how they embraced product teams. Yet in the past year it has been a constant musical chair or hot potato situation of managers reorganizing which team owns which app. The whole point of the product team is to give teams ownership and keep expertise with the app. We might as well be passing it off to a support team if they are doing this stuff.
The Antikythera Mechanism is a computer and was created in Ancient Greece around 100BC. That was a period of time before the Roman conquest of the known world. When there is an empire in power, things do not progress. The knowledge of that device got lost in history.

China has been an empire for much of her history. Being an empire does not help in the technological advancement. But fierce competition helps.
Are you wildly overpaying though for something that is a once in a century (hopefully) event like a pandemic that shuts down the whole world?
Interesting that she had a much easier time raising from men than women. She mentions having a CRM with 150+ investors, so presumably this isn't just random chance based on a small number of interactions.

One possible reason is that men may have been actively looking to invest in female founders for diversity reasons. Female investors wouldn't feel the same pressure for gender diversity among their portfolio companies.
> Why is that disastrous

GP was quoting the article in that sentence.
Because congress bullied them into removing covid misinformation (admittedly mostly relating to vaccines): https://observer.com/2021/03/covid-vaccine-misinformation-fa...

This is true of almost all the social media "censorship" by the way. They have multiple governments either directly passing laws requiring content removal, or pressuring them to remove more.
This is the 3rd Citizen headline I've seen since yesterday. I'd say their publicist is doing a top notch job of driving engagement through outrage to spread name recognition.

I'm a hypocrite for commenting, but it would be nice if we didn't let engagement bait like this stay on the front page this long.
I maintain that the problem with Lisp for most programmers coming from C-like languages is not the parentheses.

It's the fact that lisp style is heavily oriented around expressions (since almost everything is an expression) which leads to a lot of nesting and a functional style, rather than a block-oriented imperative style.
Original paragraphs:

An ice sheet in the southwestern region of Greenland is releasing huge amounts of mercury into nearby rivers. The discovery is worrying as the toxic metal can accumulate in the marine animals that are a key dietary component for local Indigenous communities.

Mercury is a naturally occurring metal found in some rocks. As glaciers slowly flow downhill, they grind up the underlying rocks, potentially releasing mercury into their meltwater.

To find out whether this is occurring in Greenland, Jon Hawkings at Florida State University and his colleagues analysed meltwater flowing from the southwestern margin of the Greenland ice sheet.

Hawkings and his team completed two expeditions to Greenland in 2015 and 2018, collecting water samples from three meltwater rivers that receive substantial amounts of water from the Greenland ice sheet – up to 800 cubic metres per second. The samples were filtered to remove any sediment and kept safe from contamination. Then the researchers analysed the mercury concentration in each one.

“[Mercury concentrations in this region] are at least 10 times higher than in an average river,” says Hawkings. This means the meltwater is as rich in mercury as some highly polluted rivers – except in this case the mercury hasn’t been introduced into the water directly by humans. “Although this mercury isn’t introduced by humans, the ice sheet is melting much faster as a result of climate change,” says Hawkings.
> leak-proof compliance

Can't be all that leak-proof if we know about their efforts.
Short answer, sea power drove technological innovation (reliable clocks etc) and a global empire gave Britain access to more raw material for textiles than it could process by ahd, so there was a huge incentive for automation. Also, plenty of domestic iron ore and coal deposits allowed rapid scaling and positive feedback loops. Much of the IR centered on the north of England because they had good ports and the coal and iron ore was right there and did not need to be transported very far. Northern England developed in significantly different economic and cultural directions from the more mercantilist southern part of the country, which differences persist to this day.
Sure. Not saying we should for normal life. But if you're going to argue with someone about a fact, then you should. Not necessarily personally of course, you could learn about other people's tests and how trustworthy they are and all that.
It kind of depends on your mental model for your user. For mobile devices in many countries outside the United states, you're doing your user no favors shipping them a bunch of static data that they don't actually need yet because you've wasted their bandwidth if they never use it and bandwidth costs money.