skysight-inc/HackerNews huggingface dataset:
> Tools like Git Bash and MSYS2 let me write one set of build scripts that work across Windows, macOS and Linux, because all of the tools exist on the three platforms.

Powershell is cross platform too these days, which makes this kind of a moot point.
mobaxterm has the basic cli tools as well perhaps even more so than git bash. For example it additionally has rsync and I think mc too
I have regretted when you fail to follow that lesson.

I did a survey once in about 3/4 of the comments were either wrong or useless. Examples:

//Add 1 to x

x+=1;

//Add 1 to x

x+=2;

//Seconds per normal day

x = 86400;

--

"Why not" comments are incredibly valuable except they suffer from explanatory decay as much as other comments.

The hope behind Intention Revealing Names is that the dissonance will be too great for the subsequent developers to ignore when they change the code.

Of course, that isn't always true.
Compatibility comes with costs:

- Fundamental prerequisites cannot be changed or abandoned, even where they impose limitations on the overall platform.

- System complexity increases, as multiple fixed points must be maintained, regressions checked, and where those points introduce security issues, inevitable weaknesses entailed.

- Running software which presumed non-networked hosts, or a far friendlier network, tend to play poorly in today's word. Well over a decade ago, a co-worker who'd spun up a Windows VM to run Windows Explorer for some corporate intranet site or another noted that the VM was corrupted within the five minutes or so it was live within the corporate LAN. At least it was a VM (and from a static disk image). Jails and VMs isolate such components and tune exposure amongst them.

What you and I can, will, and do actually do, which is to spin up VMs as we need them for specific tasks, is viable for a minuscule set of people, most of whom lack fundamental literacy let alone advanced technical computer competency.

The reason for making such capabilities automated within the host OS is so that those people can have access to the software, systems, and/or data they need, without needing to think about, or even be aware of how or that it's being implemented.

I've commented and posted about the competency of the average person as regards computers and literacy. It's much lower than you're likely to have realised:

The tyranny of the minimum viable user: <https://web.archive.org/web/20240000000000*/https://old.redd...>

Adult literacy in the United States: <https://nces.ed.gov/pubs2019/2019179/index.asp> <https://news.ycombinator.com/item?id=29734146>

And no, I'm not deriding those who don't know. I've come to accept them as part of the technological landscape. A part I really wish weren't so inept, but wishing won't change it. At the same time, the MVU imposes costs on the small, though highly capable, set of much more adept technologists.
> In recent years I see more people arguing that whys do not belong in comments either, that they can be embedded into LongFunctionNames or the names of test cases.

Who is arguing this? Usually, if I'm adding a comment on why something is done a particular way, it's something that is going to take at least a full sentence to explain if not a whole paragraph.
> In particular, destroy everything Russia puts over the border, and maybe even everything it's staging in an offensive posture near the border, but don't invade Russia.

Oh, I wouldn't go that far. In fact, I think you could occupy as much as 80% of Russia. As long as you make sure that Putin and his friends were left alive and in charge of the remaining 20%, they wouldn't do a thing.
I don’t know. Could you imagine if you were in charge of investigating something like this and you _didnt_ check one of the computers involved just because the guy who owned the computer claimed it doesn’t have anything useful on it?

There could be logging bugs in Tor that you were unaware of, or the owner could be using Tor as a cover. It would be negligent _not_ to at least check the device logs for anything useful.
Is Panic done with Nova? (Native Mac text editor)
Thanks!

I'm not sure if beam search would help much since it's just based on combining word probabilities as opposed to overall meaning, but something like "tree of thoughts" presumably would since I doubt these models would rate their own hallucinated outputs too highly!
Yikes—you can't post like this to HN and we have to ban accounts that do. It's not what this site is for, and destroys what it is for.

If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.
For me, GitHub PR review drives me crazy. It's good for exactly one round of exchange. After that nobody can tell what the heck is going on. So my self-reported mental health would be worse.

But on non-subjective metrics it seems like LLVM PRs on GitHub are gathering noticeably less discussion than they used to enjoy as Phabricator diffs.
Well.. funny you say that.. I did move to Tijuana some years ago. One time while I was there, I was sick and a neighbor (Mexican) seemed to insist that I go to the doctor. She recommended a hole in the wall office above a pharmacy that looked like a little-league concession stand.

It was a serious 30 something woman who collected something like 50 pesos (around $3), listened to me for about 30 seconds, and told me to make sure I slept and ate well (I think she specifically said chicken soup). I asked about antibiotics or medicine and she indicated it wasn't necessary.

So I rested quite seriously and ate as well as I could and got better about a week later.

During the time that I was in Playas de Tijuana I would normally go to nicer pharmacies though, and they didn't ask for a prescription for my asthma or other medicine which was something like 800% less expensive over there. They did always wear nice lab coats and take their job very seriously if I asked for advice. Although I rarely did that.

I do remember one time asking about my back acne problems at a place in the mall and the lady immediately gave me an antibiotic for maybe $15 which didn't cure it but made it about 75% better for a few months.

Another time at the grocery store I asked about acne medicine and the lady was about to sell me something like Tretinoin cream for a price probably 1/4 of US price. She didn't have anything like oral Accutane of course. It was just a Calimax Plus.

There are of course quite serious and more expensive actual doctors in Tijuana but I never ended up visiting any of them. I was on a budget and luckily did not have any really critical medical needs. But if I had, I am sure it would have cost dramatically less than across the border.

EDIT: not to say the concession-stand office lady wasn't an actual doctor. I don't know, she may have had training, and certainly had a lot of experience.
I am the person who wrote this. AMA

EDIT: Also, I'm not sure if this is against the rules, but I also need a new job as of recently. I like working on dev tools and other hard problems. If you liked reading this, want me to make your dev team more productive, or just want to experience and enjoy my excellent (and occasionally eclectic) taste, the email is in my profile.
Yeah, "My" is actually pronounced wrong by 99% of all MySQL users.
Honestly there are so many differences and little things on Windows that make using any of the CLIs not worth it. You will run up against gotchas developing on native Windows cmd, Powershell, git bash, and WSL. I left for Linux a long time ago and never have had to look back at the utter mess that is Windows. People stay on that platform for what? A graphical menu in the corner? Compatibility you don’t actually need? Use a real shell and OS and save your sanity.
I'm definitely open to adding profile photos. So far I've mostly been developing based on what I personally want because I do enjoy using the service myself. Description has been on the backlog for a while. For location: you can currently set a flag to show up on your profile in your settings, but I agree it would make sense to expand it to a full location. Messaging will definitely be coming.

Right now the only way to see if you have common discs with someone else is to directly visit their profile and a "Discs In Common" section will show up. But that's sort of impossible to stumble upon since user discovery is non-existent at the moment. Will be improving this in the near future (others who've collected this disc, etc).

I'll come up with an actual roadmap this week, but here's a few ideas that will be on it:

- Bio, messaging, full location, profile photos
- Album reviews (only after collection)
- Improved empty state and onboarding
- Folders to organize your collection
- Readable profile links

Appreciate the great feedback!
> The most concerning part, users say, is that Facebook does not notify them when their posts disappear from public view.

IMO a fundamental lack of transparency is sometimes the biggest frustration across a great many big services. While it's sometimes explained as "we can't give more details or bad people would figure out how to bypass it", more often than not it feels more like "we don't know why we the magic box decided this but the magic box is always right because caring about it costs money."
Well, for one Kamala herself said she was proud to be endorsed by Dick, one previously deemed the be(s)te noir of the left.
Maybe you have misconception about the scalability of PostgreSQL.

> According to Instagram representatives, the number of platform users exceeded 2 billion last year. This is quarter of all humanity. This mass of people publishes nearly 50 million photos a day. Football star Cristiano Ronaldo has over 600 million followers; singer Ariana Grande has over 380 million. Talk about huge databases!

> Instagram uses many RDBMSs, but PostgreSQL and Cassandra were chosen for the main tasks. The goal was to reduce delay and ensure users can easily and comfortably use the application.

PostgreSQL is also the most popular database in StackOverflow surveys.
Not just poor wording but I think you misunderstood the authors context too. Some of his comments were comparing git bash to other POSIX layers like WSL, rather than Bash vs PowerShell.
Trouble with comments is that they drift from the code over time because most people do not update the comments - - based upon my surveying production code bases. If they are hidden, it will drift even quicker and become even more useless faster
I could not have said it better myself. I would also add that I keep the slug just as an entirely separate column (or "user visible id") that they can change, had too many systems do things like "invoice id is auto generated" and then a customer coming back and saying "the invoice id has to be this or the auditors will scream!" - don't expose internals of your database to your users and you wont have a bad time.
> Why not "why not" comments? Not why "not comments"

I nearly exploded trying to grok this
In principal I agree with you but if there is one commonly used technology that is actually objectively inferior to the myriad of replacement options and is only still around because its been ubiquitous for decades, its bash.
This is trade-off that a company (and thee employee, too) has to make:

- does the company want to be able to easily get rid of "undesired"/"lazy" employees? For this option, it will likely have to pay bigger salaries.

- on the other hand, for the option to have job security, an employee will have to accept that the expected salary is lower, i.e. the company can save money on salaries, but cannot easily fire the employee.

Both are economically sensible solutions.
Cops Are Testing Apple Vision Pro for Use in Surveillance
> law enforcement subpoenaing you every single time is one way to make it very clear what it is that you're choosing.

That's not what subpoenas are for, and it would be a really stupid waste of time and resources. If you really want to do that, just send them an email.
On the other hand, I know someone from the UK who moved away and lived in places like Qatar and Oman for 20-30 years, keeping their UK citizenship and paying zero taxes to the UK (and extremely low taxes in the gulf countries).

Then they retired, returned to the UK, sent their kids to subsidized state universities (in the UK), receive free healthcare on the NHS, and receive state benefits for retirees.

They receive all of these state benefits and they paid almost no taxes to the UK government for most of their adult life. Is that fair?
So far, it's no HAL 9000.

Uploaded video dialog:

Bowman: You know, of course, though, he's right about the 9000 series having a perfect operational record. They do.

Poole: Unfortunately that sounds a little like famous last words.

Bowman: Yeah, still it was his idea to carry out the failure mode analysis, wasn't it?

Poole: mmm

Bowman: Should certainly indicate... (away from camera): his integrity and self-confidence

Bowman: If he were wrong, it'd be the surest way of proving it.

Poole: It would be if he knew he was wrong.

Results:

"Of course there is recommended getting necessary to have a perfect operational rank i know youre going to be the first to do that youre going to get the best youre going to get the best youre going to get the best youre going to get the best youre going to get the best of yours if you want to rock better sure its well perfect."
Simple. First, bootstrap a new universe...
Agreed.. this " I could not ignore the fact that any "really!!!" bad actor could use the same infrastructure to avoid investigation/prosecution," could be dependant on what you personally see as bad actor.

Would being gay count? In some countries it's a death sentence, so using TOR is how they avoid being thrown off a roof or stoned. Talking about anything LGB is a crime.

What about someone who wants to read 1984.. Would you be okay with them committing that crime?
Current Russian nuclear doctrine says otherwise. I do not want to push on that to see if they're bluffing, thanks.
Just to be clear - I don't think many people have (much) of a problem with ireland's "headline" 12.5% CT rate.

The problem is the selective tax rates that Ireland gave to many multinationals, often as low as 0.005% (effectively in return for ensuring x amount of jobs were created in Ireland). I think these are really very much sneaky schemes.
Processing power, screen size and quality, active monitoring quality, AOD. There are a few things that will hugely impact battery life.

Lower battery life literally doesn't matter if you can charge it in the time it takes you to get ready in the morning. It has zero impact on usability.

The maximum battery lives advertised on sites are literally for doing nothing anyhow. My Garmin definitely does not have a multi day charge when I'm using it to track swimming.

You are doing the tech equivalent to her knees are too pointy.
I got my hands on one of those cheap UV-K5 Radios and the first thing I did was try to listen in to one of my FRS Radios and discovering all their channels & sub channels/privacy codes.

Discovered this list while learning & researching:

https://www.k0tfu.org/reference/frs-gmrs-privacy-codes-demys...
I am the author and used the phrase "Code review is a pretty good idea, in general" in the opening very specifically, because it used be one of the selling points listed on the Phabricator homepage. :) I miss it.
Here is the Blancolirio video on the matter: https://www.youtube.com/watch?v=U95S6dQSga8

Here is the ATC audio recording: https://www.youtube.com/watch?v=xBV8aDIO1bg
I don't think doc comments are warranted in every case and definitely don't think you need to document every single parameter, return value, etc. for every single function, but they sure do come in handy for complicated APIs.
You have to ask yourself if the good is worth the harm.
Correct, Ireland fought very hard against getting that 13B.
When we publish a stack of commits, our ci ensures that every commit is build and tested individually. There is no consistency issue

Squash and merge actually makes the above goal harder. With rebase + small commits, all we need to make sure is that every commit pass all the build signals and tests during ci
"The comment for the code tells you what the author intended it to do."

Not quite.

The comment for the code tells you what the author of the comment understood the code to do when hen wrote the comment.
https://www.google.com/search?q=ny+times+profit+margin

In June it was 10.6%, in March it was 6.9%
Maybe check out the fast ai course. Jeremy Howard has a way of explaining stuff.
Personally I think you're better off putting 'not comments' in git commit information. Git commit comments are like normal comments except they don't get detached from the code.
Same, my coworker used this argument when I tried to get them to write more comments. The number of hours I've wasted due to there being no comments at all is way, way, way more than the very small number I've wasted due to a no-longer-accurate comment. And I usually find that people who write self-documenting code choose variable/function names that might make sense to them at the time, but are vague and confusing to me when I need to read the code.
... which might have estranged him from the church, which would have been a good thing. Win all around...
How hard would it be for a biohacker to use these models to develop novel proteins? Let's say I wanted to take GFP and create another color fluorescent or something.
Yes. I currently work in a codebase where the previous tech lead did that and promoted such behavior (among many other insanity-inducing practices).
Lex Friedman invites guests to just repeat whatever nonsense they write on their blogs without questioning any of the questionable claims, and plenty of people listen to it. This technology would be perfect for his podcast.
I'm really happy about the firmware updates.
When Flipper Zero was crowdfunded, the deal was that the tool will be available once the hardware is good enough to fulfill the promises. And so the software will be updated later.

I'm happy that they keep they promises.
So if such an easily obtainable, and comparatively lucrative (but fully legal) option were available -- and if it's so obvious, one has to presume Apple's people would have been perfectly aware of it -- why didn't they just take that route from the beginning (or if not, at least much earlier in this saga)?

Something tells me there's more to the story here.
From my POV, it's a supplier that is no longer beholden to shareholders demands for profit. A platform and service that can operate using customer sourced revenue and respond to market demand without a profit driven board is a big win for everyone while funding development and maintenance of a great open source project.
I use mermaid.js a lot but not enough that I an fluent in the DSL. So I pump things into excalidraw's AI and tell it to create the mermaid chart. It gets my 80% of the way and I tweak/extend from there. If nothing else its awesome for that
As a US company they are required to get launch permits from the US regardless of where they launch from. Mixing jurisdictions would likely make things harder, not easier.
whats so confusing about open core?

its open source for the masses and commercial for the very few enterprise with paid addons

https://en.wikipedia.org/wiki/Open-core_model

definitely the best of both—sustainability and freemium OSS for hobbyists and small companies
At scale, there are some workloads where it can be a great choice:

* InnoDB (default storage engine in MySQL and MariaDB) uses a clustered index, which can handle an extremely high volume of primary key range scan queries

* Ability to handle several thousand connections per second without needing a proxy or pool (the connection model in MySQL and MariaDB is multi-threaded instead of multi-process)

* Workloads that lean heavily on UPDATE or DELETE have terrible MVCC pain (vacuum) in Postgres, rarely a problem in MySQL or MariaDB due to using an undo log design

* Support for index hints and forced indexes, preventing huge outages when the query planner makes a random mistake at an off hour

* Built-in support for direct I/O is important for very high-volume OLTP workloads -- InnoDB's buffer pool design is completely independent of filesystem/OS caching

* If you need best-in-industry compression, the MyRocks storage engine is easy to use in MariaDB

* Logical replication can handle DDL out-of-the-box in FOSS MariaDB or MySQL, whereas in Postgres you must pay for an enterprise solution

* Much better collation support out-of-the-box

* Tooling ecosystem which includes multiple battle-tested external online schema change tools, for safely making alterations of any type to tables with billions of rows

* MariaDB has built-in support for using system-versioned tables, application-time periods, or both (bitemporal tables)

That all said -- Postgres is an amazing database with many awesome features which MariaDB lacks. Overall unless your situation is very high scale or an unusual edge-case, it's usually best to just go with what you know / what your team knows / what you can hire for, etc.
Telling that there's not an Authoritarian Defiant Disorder, for those teachers who are particularly disagreeably unreasonably authoritarian. Surely everyone has had at least one of those.

Mine was an English teacher. I realized by the second class that I needed to transfer out of his course. The school administrators were completely unsurprised by my request. It seems that I was just one among many who had done the same thing.
And they used this PR for what? This isn't a puff piece. Those guys are the real deal.
We first built interdiffs in Review Board [https://www.reviewboard.org] way back in 2006 (in fact I think I may have coined the term, or arrived at it independently). It's still my favorite part of the product and my process when doing code reviews. And it's one of the things we hear the most nostalgia for when people move to something like GitHub.

I've never felt that fix-it commits are really a proper alternative, since:

1) They don't tell you what upstream changes have been incorporated into a series of commits.

2) They tend to mess up the commit graph, even if temporarily, and make it more difficult to review. If you've been following along with a review, you may have already read the code being fixed in fix-it commits, but if you're coming in fresh, you may start off with a bad sense of what that code's trying to do or how it's structured.

3) Not everyone uses Git or other multi-commit-capable SCMs. Plenty of people are on Perforce (such as in gamedev) or on specialized SCMs like Keysight SOS (such as chip manufacturers). So fix-it commits aren't even an option there.

A proper interdiff-capable code review systems means one reviewer can start off from the first published review request and follow along with every update, seeing only what's changed, while another can jump in to the latest full change and not have to worry about the series of fix-its that led up to it. And it can do this regardless of the SCM.

If done right, it can also exist alongside multi-commit changes.

Let's say I have a small project I've broken up into multiple commits to help with the review process (say, an API handler, front-end UI, and documentation), and have decided this is suitable for posting as one review request (since the commits are largely interrelated and having these as one change helps lend context to the reviewers — if they aren't, multiple review requests in a dependency chain are probably ideal).

Based on review feedback, I may end up making a series of changes to one or all of those commits. When people go to review my updates, it's nice to be able to see how each piece evolved, without trying to do the mental arithmetic of mapping fix-it commits and their changes to their corresponding changes.

So yes, interdiffs are fantastic! More people should use them, whether they're working with lots of small commits or large commits, single-commit review requests or multi-commit.