skysight-inc/HackerNews huggingface dataset:
Touch typing is one way to put it. I would say Vim is an imperative editor. You need to tell the computer how to edit text by glueing together chains of small painful commands. IDEs are declarative editors, you say you want to refactor a variable, and the IDE handles it.

Vim is a text editor, not a code editor, and I keep forgetting how weird it is. "Ctrl-X Ctrl-D completes a C preprocessor macro by default" - there is no reason this should be in the core of any editor.

And finally, whatever you think of Vim, it's not worth using unless you've read Practical Vim. Without the knowledge of that book, you're too limited to approach efficient (imperative) editing.
I recently started doing it winter time Folding@Home

Probably reduces life time
16:10? That's a dead format. It was seeing some popularity around ~2006 but quickly died out as 16:9 took over.

21:9 is the popular ultra-widescreen option. 16:9 is the popular regular option. Acting like 16:10 is the direction the industry is going is just bizarre.
If you’re doing all that, the company could be paying you staff engineer or senior manager salaries?
Who are you addressing here with 'you'?
> Biologists are almost unique among scientists in being happy to say how little they still know [...]

Citation needed.

> Up until last year nobody had thought to see whether anything eats viruses! Turns out some do.

Nah, lots of things eat viruses. It's nothing unusual at all. You eat viruses, I eat viruses. They are everywhere, after all.

The novel finding was a critter that lives / can live solely on viruses.
We have been reading these $500/month posts year after year and recently we have been holding back on launching our own as well. Recently we finally decide to just went in after months of working on it. It is called MessageDuck (https://www.messageduck.com) which was built while we were looking for a good solution for SMS data marketing.

We built this after we noticed that there was not much good solution except one which is quite pricey called MailCharts SMS. We are still working on it and we also have a code YC that you can use for 10% off our Pro Plan.

Hopefully, we can reach $500 by 2023 and we can Show and Tell as well.
The announcement is canceled, but per leaks in that very post, Wizards still fully intends to move forward with their plans once the outrage dies down.

This makes it incumbent on the community not to stop being outraged.

We'll see how it shakes out, but it at least looks like Wizards' peers in the industry - Chaosium, Paizo, etc. - aren't standing for it.
No, I’m not sure they did not. I disagree with the parent poster who praises a dictator regime for being able to dispose of people at will.
I make it about 20 minutes into a JS project before I have to go install TS because I'm losing my mind. It's such a no-brainer that the question barely parses. Javascript is medieval and typescript is... less so.

I know it's not an interesting answer and a lot of other people say the same thing; guess I'm just casting my vote.
That's kind of what the experiment was about. They wanted to know: If we run this simple game of chance and delegation with real people, do people delegate more or less than the optimal amount?

They found that people delegated more than would be optimal.

Now -- whether that says anything about liquid democracy applied to real world situations is quite a different question, of course. As you started to point out.
Judging by your popular media, you only use metric in science fiction shows where the distances between spaceships is so big the number is effectively meaningless.

Longing for the day you start using kilograms instead of points for weight in your movies and tv shows. I always have to pause and grab my phone to convert.
You should definitely check out Mold:

https://github.com/rui314/mold
The CEO has to get her 2.5 million / year somehow.
I’ve worked with a few good product managers. I always equate PM to project manager which is totally different and typically useless in software development. The most useless BS role is when companies hire for scrum master.
Serverside, sure, I'll agree with you there (I use Rust for my backends).

Clientside, I've tried a lot of compile-to-JS or WASM languages and frameworks. They're just not there yet, especially when you run into some compatibility problems, not to even mention library support on the frontend. The reason I like TS for frontend is it's just JS at the end of the day, you can strip out all of the types and it works. Therefore, things like compatibility issues are simply...nonexistent.
Ask HN: Mono Repo vs. Multi Repo?
What are the benefits and downsides of choosing one approach over another.
From the perspective of a small team.
Why not switch to a faster linker if linking is your bottleneck? Mold will use all your cores. And even LLD will likely be much faster than the stock linker.

I don’t think there’s much in it between Apple, Intel, and AMD with regards to single threaded performance at the moment, so I’d probably make your decision based on other factors.
Do ADHD meds differ from, say, alcohol from a legal perspective? My understanding is that being drunk is never a defense. The meds are something he chooses to consume as an adult so it seems like he should be compared to an unmedicated standard. But IANAL.
Gopher rocks on DOS[0].

0. https://gopherus.sourceforge.net/
google3 and Plex! God how I miss working with Plex, I didn't know how good we had it.
The open internet will be a dark forest, beautiful, but populated by metal-brains. Meat-brains will retreat inside trusted spaces below or above the empty forest.

https://maggieappleton.com/ai-dark-forest
You still need to aggregate and contextualize these in terms of overall business and product strategy. Yes, engineers can do that too and some percentage of engineers are good at this as well - and being able to understand and formulate product strategy can be an important part of an engineering leader's skill set - but that's not that common and ultimately you need some level of specialization and you can't run an org expecting everyone to be able to do everything.

I've done both Eng and Product and most engineers don't have sufficient understanding or appreciation for the importance of product strategy. It's also important to be able communicate strategy coherently at some scale, especially if execution isn't expected to be completely top-down. At some point, engineers just have too much else to do and you need coordination.

Edit: I'll also add that engineers aren't the only ones doing work - Product Managers are expected to be able to coordinate across functions and get everyone on the same page, not everything is about just providing input to engineers.
It is a sacrifice I am willing to make. I just want consistent approach across the board. I do not believe it is much to ask.
What about the post makes you say that? That wasn't my impression at all.
Judging by your popular media, you only use metric in science fiction shows where the distances between spaceships is so big the number is effectively meaningless.

Occasionally hear grams for small amounts.

That's it.
My voice is my passport, verify me.... aww fuck I have to do a voice activated "I am human" check now?!?
It must have been embarrassing to have had to write that. Anyway I would be embarrassed. "Our existing code is a whole mountain range of mud. We hope new code written in this new language will be less so."

Anyway it will be much slower to write bad code in it, with the compiler kvetching the whole time, so the rate of accumulation of bad code will necessarily be lower.
TS can be a pain. I know, I fight with it all the time. That’s probably my fault though. I’ve learned typescript by being exposed to it in our code base, rather than properly learning it through documentation.

For all the struggle, it makes me feel very confident about the code, and its reliability. That’s worth a lot.
This is one of the more nonsensical discussions of shamanism I've ever come across. It's as if the author read some New Age semi-cultural appropriation nonsense by some LA guru and based the article on that. Maybe some Carlos Castaneda material was added for good measure.

If you want to understand traditional shamanic practices as seen in both the New and the Old Worlds, you probably want to start with the ethnobotanical work of Richard Evans Schultes and similar work - not the work by the cultural anthropologists and sociologists, but that done by the experts in plant phylogeny and pharmacological activity who worked with native shamans around the world to characterize the plants they were using.

https://en.wikipedia.org/wiki/Richard_Evans_Schultes

It's true that the shamanic practitioners had a cultural-religious tradition, but the basis of their activities was using plants and plant extracts for various purposes - wound treatment, psychological treatments, etc.

It's also true that the psychoactive plants get the most interest in the shamanic context in western societies these days, but that was just one part of the native biological pharmacopia. The practitioners certainly didn't have knowledge of infectious disease or anything like that, but their use was based on experiment and observation, just as with modern scientific development.

At the very least, if you're going to write about the topic, start with the plants. Do a Google Scholar search (or Internet Archive Scholar) to filter out most of the woo, using a phrase like:

ethnobotany psychological psychoactive

That at least will give you a sample of some of the more reputable research in the general field, as well as some accurate historical narratives.
Another big disadvantage of monorepos is the size. If you're having to clone the repo in its entirety on a routine basis (think CI/CD pipelines, or there's some other repo that needs to maintain multiple work trees referencing different commits), that repo being some massive monstrosity can be a real pain in the ass.
More extreme than extreme.
There has been a very recent (last year or two) mild resurgence in 16:10 in some segments of the market. For example, while the Thinkpad T14 is still 16:9, the T14s, X1 Carbon, some of the P line are 16:10. The most recent XPS 13 and 15 are also 16:10.
Of a service, yes. Of the entire infrastructure, no.
RIP Auto-Tune
> very valid from an epistemological point of view

Philosophers can be dangerous creatures (if unwittingly), perhaps some of the most dangerous. It's incredible how you can draw a straight line from many of the most destructive political narratives (across the spectrum) to reasonable seeming scholarly papers and debates.

There's a near universal consensus today regarding the horrible, unacceptable presumptions behind Social Darwinism and related theories from the turn of the 20th century. Mid-century philosophers, particularly structuralists and post-structuralists, led the charge in attacking those earlier theories. (By first identifying the underlying cultural presumptions, and then "deconstructing" them.) And yet you can draw a straight line from, say, Putin's whataboutism and ethnoreligious rhetoric--not to mention all the culture war narratives (from both the left and right)--straight to those philosophical ideas and debates--i.e. structuralism, post-structuralism, etc. I mean, Putin's rhetoric has always existed in some form, but those and other philosophical schools absolutely supercharged the rhetoric and its intellectual resilience. If there is no objective truth, and if even older moral pillars of Western philosophy, like the exaltation of individual dignity, can be just as illegitimate as any other principle, then Putin supporters can argue the legitimacy of his viewpoint and it would be dishonest to outright reject absolutely everything about it. (There are obvious and time-tested counterarguments, but they're in tension with favored moral norms in the West, such as victim culture. The left birthed victim culture, linking moral worth to membership of a persecuted minority, but the right has embraced it for all its worth.)
I’m looking forward to NPCs having dynamic responses with real voices

Doesn't have to be prerecorded, just trained
I’ve written a bunch of stuff, over the years. Most can be found here[0]. I haven’t done much in a while, but I do want to get back to it. It’s just that my dance card has been a bit full.

The app has had a fairly long and winding trajectory. Most of the reason that it’s taken this long, is because the other stakeholders really didn’t know what they wanted, when we started, so the project kind of “accreted.” It’s really been a long prototype phase. Much better than an MVP, because we were free to make massive changes, whenever we wanted. It has a couple of backends, but they have been stable for years. Most of the thrashing has been on the UI.

The last few months, the functionality has stabilized to the point that I could factor out this SDK, and things will move very quickly, from here.

We’ll see what I can write, once I can come up for air.

[0] https://littlegreenviper.com/miscellany/
I prefer 16:10 to 16:9 by far. While the difference might feel small, the usability improvement from seeing more lines of code is very noticeable for me.
There seems to not be any standard list of unrecoverable panics/aborts, but this Stackoverflow post [1] has a list of a few.

As far as the user/developers are concerned, it doesn't matter too much, since you have no option to recover them, but it would be nice if it was explained if defers are still ran. I'm assuming they are not.

1. https://stackoverflow.com/questions/57486620/are-all-runtime...
>Seems a bit silly to believe she volunteered for that

People volunteered for some weird shit back in the day. Their morals and beliefs are nothing like ours.
“ regarded by some as having a net positive impact” is a pretty great example of damning with faint praise.
Why link something that has already been proven false?
Mono all the way.
There was a time, once, when I did things with vanilla JavaScript. Not huge, ambitious things, but not trivial things either. Now TypeScript has ruined me. I'm pretty sure it didn't really mean to, but I've become so used to encountering `any` and saying "that needs to not be" and fixing it that now there's a reflex in my head that makes the thought of `any` just uncomfortable. I try to write vanilla and I start sweating, it just feels so unsafe.
I am dancer
Write programming guides and ride my dual sport making maps for other riders.

Would be good times.
The general idea is that the set of all contingent things can only be explained by something non-contingent (ie necessary).

A necessary thing, by definition, is its own explanation. "I am what I am" etc.

From there, classical theists attempt to connect that necessary thing to what you'd commonly understand as God.
Again all I'm saying is what matters is that enough kids do in fact play VR, today, to fuel the tech so it can mature into a mainstream technology. The only way this hypothetical (future) parent issue would discredit VR as a mainstream technical innovation is for VR companies to have bet solely on causal/kid gaming for their long term success.

This is why OP missed the point. Because I didn't agree that that was an important point he a) got emotional for being disagreed with b) assumed that I thought it wasn't true. But I only ever said it didn't matter, not that parents or regulations dont have power in this dynamic.

Evidence points to Quest 2 being very popular among kids and their casual gaming platform via Android-esque VR games has provided a strong and sufficient market from which multiple companies can mature the technology to a wider market.

It was a faulty premise to dismiss the technology, because it fundamentally mischaracterizes how technology normally mainstreams (by first having a real and successful initial early adopter market from which you adapt and mature to mainstream markets - not betting on early adopters to BE the mainstream).

Although I will agree I probably should have said "yes you're right" so OP didn't feel I misunderstood. Altough if he wasn't so quick to win an internet "fight" he might have let me explain.
> Any update requires updating the version everywhere

Much of the benefit of using an IDL like this is to be (mostly) forward compatible, so you don't have to upgrade everywhere immediately.

> you have to independently debug which version of which library was being used by which application at the time a bug occurred

You have to do that anyway; it's easier if your repository history reflects the reality of which applications were upgraded and deployed at which times. There's nothing worse than having to debug a deployed system that was deployed from parts of a single repo but at several different points in that repo's history.
Networks with outbound SSH access blocked are depressing. It‘s not that hard (but still annoying) to tunnel through them via HTTPS or similar.
When I was young I was gifted a full encyclopedia set along with another one called “tell me why”. This was pre-internet. I was utterly fascinated with all the different stuff in each alphabet and read the whole thing.

It really opened up my mind and made me who I am today. Wikipedia rabbit holes come close but not quite the same.
Most heat pumps made in the last 2 decades are computer controlled with a wide array of temp and pressure sensors. Stuck reversing valves do happen, but it's likely the unit will shut down due to an ambient outdoor temp, cool temps, or refrigerant pressures that are too high for heating mode.

Not much different from a gas furnace. If somehow the computerized safety controls went bad and the unit ran without the blower fan, it would quickly overheat and destroy itself and possibly catch the house on fire.

Luckily, these failsafe systems are well engineered with multiple redundancies. They aren't hacked together React apps.
"Always step up into the lifeboat."

This is advice, hard won, by mariners who abandoned their ship, were lost at sea in their lifeboat, and left behind them a ghost boat that eventually makes its way to shore.
That alone is not sufficient. Your body makes backups every time it creates a new cell. Once you make a backup of something corrupted, you're going to get corrupted restores. Also, even when you make a non-corrupted backup, it can only be used somewhere around 50-70 times in most cases, and in the few cases where this doesn't apply, well.. you don't want too many copies of them for other reasons (else you get tumors). Lastly, corruption most often happens when you're reading or creating a backup, so simply restoring from a non-corrupted backup might result in corruption. So altogether, doing more backups, won't necessarily solve the problem.
I want my ashes thrown in a 1-gal pickle jar with liquid mercury, shaken up and then thrown at an obsolete chemotherapy machine which will then fall off the back of a truck in front of the statehouse at 3am, or something like that. I'll make sure to set aside bail money and whatnot for my heirs.
I'll give a good faith reply to this, many laptops in recent years have moved to a 16:10 aspect ratio. MacBooks have used it (infamously) since the late 2000s, while brands like Dell have recently shifted (some of) their XPS laptops to 16:10 displays. My understanding is it's become very popular across "macbook like" ultraportables in all the major brands for its greater vertical resolution.
Yes! Complexity is Apex predator of grug brain developer.
> If you immediately set out with the mindset "your spell checking service shouldn't also be an autocomplete service" as if this is some sort of wisdom (it really, truly isn't), then you're hamstringing yourself from getting these kinds of easy wins.

It's not "immediately setting out with a mindset", it's looking back on coming-up-on-2-decades of software development experience and noting that every time I think bolting a second responsibility onto a unit is an easy win, that decision comes back to bite me. It seems like an easy win now, but everything you change in that area of the code from now on needs to consider two different, disparate responsibilities it needs to maintain.

If you're seeing this as an easy win, it's likely that your software didn't see much use that played out the problems, or you didn't stick around long enough to see the problems arise, or someone else did the work to fix it and just didn't tell you.

> Nobody who was using its old features; they don't have to change at all.

Not yet, but if you assume they'll never have to change, you're going to have a bad time.

What's the longest you've ever worked on a codebase? Have you ever been the sole developer on a large codebase, where you had to pay for your own mistakes?
If you're using a Mac you have an easy way to reproduce the distinction: save a file called café.txt and look at what filename it has in a directory listing. (It will look the same but have a different byte sequence).
I find this theory really interesting, and the fact that it is possible to reverse the epigenetic aging process to the unknown “backup” described in the article would support a mechanism that is coordinated like this rather than random.

But it’s possible that the changes are indeed random or probabilistic and that they simply build on each other over time in a way that merely resembles coordinated aging.
That's not what they said at all. You love to see people unable to read a couple of sentences before jumping to their own conclusion.
I don't even know if I'd call this a disaster recovery fail. Depending on what they meant by "corruption", a roughly 6-8 hour turn around time is not awful for a database restore.
My parents have had endless problems due to their Tesla roof and regret ever buying it. Tesla’s response to their problems is slow to non-existent.
No, it's linear with frequency, and proportional to the square of the voltage. Outside of the frequency "sweet spot" you have to crank up the voltage though....and leakage increases as well.

https://en.wikipedia.org/wiki/Processor_power_dissipation
Carbon dioxide is actually a relatively weak greenhouse gas. At least compared to water vapour, or even methane.

Btw, CO2 does 'magically' disappear. Into the oceans. Alas, from what I've read it'll take about 2,000 years to do so.

> [...], but the general direction of travel cannot be seriously disputed without arguing against the above simple facts.

I don't want to argue against global warming, but I want to argue that can't argue against global warming without arguing against your 'simple facts'.

Your 'simple fact' about CO2 could be true, but global warming could still be a myth. (I don't think it is; but your argument is far from sufficient. It's a complex system. Eg from time to time volcanic eruptions produce a lot of CO2, but they are typically associated with a cooling of the climate, because of other factors.

Similarly, burning coal releases a lot of CO2, but it also used to release a lot of SO2. Locally, SO2 is pretty bad (ever heard of acid rain?), but SO2 converts to sulfuric acid aerosols that can block solar radiation. These days most coal fired power plants have measure to avoid spewing so much SO2.

It's conceivable someone could find a coal so 'dirty' with sulphur, that burning it would decrease temperatures. I don't think it's very likely, but it's conceivable. So you need more empirical observations, than just your simple facts to make your argument.)
I can feel you. I was in the same situation.

In the end, my team broken up. Cofounders (my best friends) left. We are not friend anymore.

I closed that company and start a new one. Luckily, things are better now. Dont outsource sale, someone need to do that. That is a hard lession
This is awesome for any kind of situation where you need a (human) speaker. No tripping over words, mumbling, mispronouncing --all fluid and audible with perfect enunciation!