skysight-inc/HackerNews huggingface dataset:
It's crazy how people forget the past. Back in the day, git was "rewrite, rebases modify past to make beautiful commit" vs hg "rewriting past is bad, beautiful commits are lies about history". Turns out people don't care about truthful history.

(Nowadays mercurial can do rebase/amend just fine.. But it is too late)
Cost per unit is displayed on price labels in the US, at every store I can remember being to. Smaller text than the price, which makes sense.

Sometimes the units are screwed up, and it shows “$3.49, $3.49/ea” for something that should be in ounces, but that’s rare and is clearly a data problem.
Can you link to info about this? I can't find much in a quick Google search
I recently[1] learned that you can telnet to a NASA machine to query various information
about astronomical bodies, including man-made satellites.

> telnet horizons.jpl.nasa.gov 6775

The interface is pretty difficult to use, but there is a python wrapper for it. I forced myself
to stumble through the telnet interface.

> Voyager

(no semicolon–othewise it'd look up in the small-bodies table)

That tells you Voyager 1 is ID 31, and Voyager 2 is ID 32.

> 31

> E

> <Enter> x2 (take defaults)

> 2022-06-18

> 2022-06-19

> 1h

> <Enter>

> A

Spits out this data:

https://gist.github.com/connorjclark/de205ce62a7f1d4fda6d8fa...

I'm not knowledgable enough to know how to utilize this data in an interesting way, but I assume this "Ephemeris" data can be utilized to determine where to point your telescope for any given object.

[1] https://twitter.com/cjamcl/status/1536609292572184576
Technically correct, the favorite of pedants.
IBM has made lots of not black things. Were any of their typewriters black? The IBM PC sure wasn't and many models after that weren't. I think the ThinkPad was their first black computer at the very least. IMO ThinkPads look great and they've done some really cool things like the butterfly keyboard.
teach recursion not "How not to teach recursion (2021) (parentheticallyspeaking.org)"

(trees,permutations,graphs..)
My rule-of-thumb is that if you have less than a terabyte of data, you're better off processing it locally, and even that is pretty conservative. Big data is for when you have problem sets that simply will not fit on a single machine. With 4TB hard drives going for about $60, a lot of problems are better solved by simple algorithms in efficient programming languages on a single box.

There are some data sets where you really do need big-data tools, but it's for when you have petabyte-scale data, not megabyte/gigabyte-scale data.
I run a Mastodon instance and to be quite honest the fact that it’s kind of hidden and obscure is part of the appeal for me. It’s a nice quiet little place for me and some people I like to hang out. It’s never going to be huge, it doesn’t need to be huge, it just needs to be a place for me to talk to my friends. Not every social space needs to be planet-scale.

RTC’s pitch doesn’t make me want to learn more but there are probably people here who are totally into what it’s offering.
I agree that symlinks cause more trouble then is needed on any platform. Sadly, only Node really likes to use them to optimise the store of packages

Personally, I don't have major issues compiling things on Windows for other platforms (macOs, Win32, Android, Linux). Only awkward thing is designing UIs
This hobby attitude is exactly why Google kills so many products. Google Reader is a hobby; leadership can't ever imagine it being a billion-dollar business so it doesn't justify any more maintenance effort. HomePod is certainly going down that path.
I think the parent comment meant doing very little from an evolutionary perspective.
The SVN implementation worked pretty seamlessly, almost like a regular subdirectory.

There was no gotcha of a non-recursive clone/checkout. If you've used this feature, your users wouldn't keep getting "broken" checkouts.

There was no gotcha of state split between .gitmodules, top-level .git state, and submodule's .git, and the issues caused by them being out of sync.

There was no gotcha of referencing an unpushed commit.

Submodules are weirdly special and let all of their primitive implementation details leak out to the interface. You can't just clone the repo any more, you have to clone recursively. You can't just checkout branches any more, you have to init and update the submodules too, with extra complications if the same submodules don't exist in all branches. You can't just commit/push, you have to commit/push the submodules first. With submodules every basic git operation gets extra steps and novel failure modes. Some operations feel outright buggy, e.g. rebase gets confused and fails when an in-tree directory has been changed to a submodule.

Functionality provided by submodules is great, but the implementation feels like it's intentionally trying to make less-than-expert users feel stupid.
Citybound – A city building game using actor-based distributed simulation
Sorry, I don't fully understand what you mean by that. Are "early returns" easier to miss when reading code (easier to miss than goto statements achieving the same effect)? If that was your intended meaning (sorry I am missing some sleep today) I don't share that view, I think both statements are equally obvious in that regard.

Examples I was thinking about:

* an early return can only go back to the call-site

* all returns in a function or method return to the same place

* an early return terminates the context it is in

* an early return does not create an entry point for nearly arbitrary other code points as labels for gotos do
Microsoft's own machine learning repo "Project azua" (https://github.com/microsoft/project-azua) runs on JAX. Let that sink in.
> A related question might be "why are we fooled by such simple tricks?"

Yes, and to poke at this a bit further, we could ask "What is it that humans are doing when talking that isn't just simple tricks?"

If I had to hazard a guess, I'd say the answer to that is some sort of persistent world modelling, which means an AI may need to have a sense of self before it can move beyond simple tricks.
Patreon is a relationship processor that handles some elements of some relationships with content hosting and payment processing.

I don't think it's unreasonable to distinguish between what Patreon does and basic PP. Users are paying for access to the package - which includes removal of PP friction - not just for a basic PP service.
> Something about cryptocurrencies attracts, not just starry-eyed naïfs, but the sort of starry-eyed naïf who thinks that Ponzis, chain letters and other blatantly fraudulent financial schemes are actually a good idea.

And where there are naïfs with stars in their eyes, there are scammers to prey upon them. It’s a new paradigm!
If you want to build binaries for a distro, build in that distro. If that distro has a Docker image, it's as simple as:

docker run -v "$PWD:/src" olddistro:version /src/build.sh

$dayjob supports distros as old as CentOS 7 and as new as Ubuntu 22.04 this way.

Compiling on one distro and then expecting it to work on another distro is a foolhardy errand. Libraries have different versions, different paths (eg /usr/lib vs /usr/lib64 vs /usr/lib/x86_64-linux-gnu/ vs...), and different compile-time configuration (eg openssl engines directory) across distros.
The criticism re: purity is silly. It can still be useful to design a language that is “mostly pure” because you’re mostly not trying to fuck your self over. For example OCaml is “mostly pure” and it’s tremendously beneficial in terms of writing correct software, regardless of the IO escape hatch or the ‘a ref explicit mutability etc.

(I don’t care for V one way or the other though, and most of the results in the post are clearly bad, I just find this particular point to be absurd).
>> The PVs absorb a lot of thermal energy, too, more than the shingles themselves do. So they make the roof hot. You can actually feel the difference inside the house - the rooms that are underneath the solar panels get warmer in the summer than the ones that aren't.

I've actually read the opposite: most PVs don't sit directly on the roof, but rather a few inches above it. And that air gap further limits the amount of solar energy that makes it onto the roof and into the attic.
I'm talking about my needs, ditto with the XKCD guy. Basically I just need to be able to create a PR from my local changes. Not much more.
My personal hell is having some nested objects/dictionaries and wanting to either add or remove a layer. Good luck and God speed in your attempt to simply find every single line of code that needs to be updated.
The 238Pu used in radioactive batteries is a lot more active than the more common 239Pu used in nuclear reactors/weapons.
well, there is the classic for one -> https://www.oculus.com/experiences/quest/2719294624823942/
There's tooling that mostly avoids this. https://github.com/Jake-Shadle/xwin

This is a utility that fixes a lot of the cross-compiling issues for windows by giving you a portable, unfucked naming, and not-massive SDK. It's the same SDK you get when you install MSVC but it's only a few hundred megs and the names are consistent even with all of Windows' fucked up tooling.

The only caveat is you need to provide your own compiler, in this case clang is often the best option.
Why Does Science News Suck So Much? [video]
Australian government lobbying behind the scenes for Assange's freedom
I've toured power plants, both hydro and coal, which are dangerous places. On a scale of 1-10 with a corporate office being 1 and a power plant being 10, I'd have rated a data center at 1. But now having seen the inside of one, I'd rate it more like 3 or 4. The biggest danger is the high voltage, but there are more mundane dangers like hearing loss, heavy equipment, heat, room-pressure, holes in the floor, etc. It's an industrial facility for sure, and PPE and safety procedures are a BIG DEAL for the workers.
Many push notifications are spam that developers want to send and users don’t actually care about. But more than that, the fact that you actually downloaded an app is much higher proof that you want to get notifications than just going to a site and clicking yes on a dialog. Dialogs basically mean nothing because users will just click yes without thinking about it.
I have done multiple times both refactoring of untyping JS and JS fully typed with Flow. With the latter after the Flow compiler stopped complaining one can expect things to work. With the former despite extensive tests sometimes it took weeks to fix bugs caused by the refactoring.

Granted this is personal experience and I may be simply not careful enough to do untyped refactoring, but few people I talked about that shared the experience.
Document Your Documentation
By "their country," I meant the state of Russia. Millions of Russians suddenly found themselves, not by choice, disconnected from Russia.
The point of this article is that unicode isn't a "basic thing".
Yeah, that's enough to visualize the idea. If you have a mx2 matrix, and you take each row as a point in 2D space, the compression means projecting all the points along the long dimension of the ellipse. If all the points are along a line, then the matrix is perfectly compressible.
What I’m saying is the delta between a very cheap hdd and an ssd is 20 bucks.

This whole assuming everyone is destitute is getting rather tiring.
Carter taught me that there are four ways to pronounce pecan.
For these people that claim taking cold showers, I want water temp. Out of the tap, in summer, my water is 53 degrees (f), upper 40s in winter. I'm not sure I could get through a whole shower sans hypothermia.

Edit: looked it up. 30min-2hr for hypothermia at that range. Typically I take a 15-20 minute shower, so only flirting with hypothermia.

I love a hot, hot shower. Best advancement in technology in the last thousand years
I think there's even a problem of expectations. What would it accomplish if we did that? Because there wouldn't be a reduction of climate forcing if we did this, it would be a (slower) increase. It wouldn't cool the planet, it would merely slow the increase.

Since we definitely want that to happen, we need other options than the options currently discussed.

If I look at this I always come back to the same point: humanity will need to take control of earth's climate. And while limiting CO2 (and, more importantly, methane) emissions will be a component of that, it's not going to be the only one or even the most important.
How did you find a Mitsubishi installer? I like the product but couldn’t find a contractor in the Portland Oregon area.
back in the original dotcom 1.0 crash the furniture ended up at various office furniture liquidators and auction specialists, I knew a number of people who bought aeron chairs for like $150 a piece.

most big cities have a few warehouse-like vendors of used office furniture if you do some searching and visiting locations in person. can usually rule in or out if a place actually has a lot in stock by finding it from google street view and checking the size of the building from aerial view.
> Any wavelengths which were gonna heat the air by absorption, were absorbed on the way in and didn't reach the roof in the first place.

What is the basis for this? Intuitively (I am no expert) it seems more likely that the amount of thermal energy produced would be a function of the distance light travels through a medium and the amount of energy carried by the light in the first place. So I would expect that the "inbound" light would produce more thermal absorption energy than the reflected "outbound" light, but it wouldn't arbitrarily all be absorbed on the way in.

Reality seems to be more complicated: https://www.sciencedirect.com/science/article/abs/pii/096016...
I don't doubt that unlikely clustering can innocently occur by chance. But you asked if hiring discrimination is alleged to have occured and it was very clearly alleged when the author uses the word nepotism in their original blog post:

>Cronyism and nepotism is not uncommon, especially in my line of my work, but it was unusual on this scale

You may say the author has jumped too soon to that conclusion but they nonetheless made that allegation. My comment stands.

You should also be aware that accusing someone of not reading a comment or article is both rude and against site guidelines. A more productive way of going about this if you think someone misunderstood or indeed overlooked or skipped part of something is to simply quote the relevant portion. That at least gives them the benefit of the doubt. It also goes a long way towards preventing responses that go on the defensive before even considering the merits of an argument.
Podcast with the creators of DoWhy https://thedataexchange.media/an-open-source-and-end-to-end-...
At this point Windows as a primary development platform is essentially dead. With a few exceptions (DX) nearly everyone writes code for Unix/Linux and then cross-compiles for Windows.

Windows is the afterthought.

Let that sink in...
> What about git submodules is "flat-out bad"?

Do you want me to grep the changelog for fixed mistakes?

Do you think they fixed all of them, just now, june 2022?

There are mistakes, which are flat-out bad. Trying to fix them is a continuous process that is not complete. And there are probably bad decisions that will be baked in forever, but that's not necessary to prove my point.

> It's ironic that you're criticizing others' comments on being vague and providing non-answers while you've contributed nothing to the discussion.

It's not ironic. One person asks for input. Another person gives a vague answer. I call the answer too vague to be useless. That doesn't make it my job to be specific now. I'm not answering OP. I'm giving feedback on a different answer.

Which is what you were originally doing too, so don't complain that it's not "of value".

And I'm not criticizing submodules here either.

I'll make my argument more clear. The idea that any software has "nothing bad" about it is ridiculous. That's a generic argument for all software. If you really want examples, look at the changelog. But I think it should be obvious. If you think it would even be useful for me to provide an example, then there's probably been a terrible miscommunication.
No, they're not really. And IIS is not that bad either. My main gripe with windows and why i won't develop on it anymore is simple that their system is too complex. I suppose this is the gripe of the article author as well tbh.

Windows is horribly hard to learn. In a day, i learned how to create file, directories, change the stats on those, execute diff and patch, an do weird string modifications with grep and cut (and learn to commit and push with git). First day on an UNIX machine. First work week on a windows machine (at that time, i had already built a LFS): we have those two project with two different version of (proprietary JS front framework) and (weird php framework). Those don't use the same version of mycrypt.dll (and others, but this one i will remember for at least two dozen year). With the support of non-intern engineers including a windows DBA, it took us a week to manage to install the two different versions.

A week prior, i was linking to a previous version of Ruby for my RoR app (it was around 2013).

But since, i really respect windows sysadmin, they are the best of us. I will just never, ever want to work on a windows server again. I like learning, but putting that much effort for this little rewards? not worth.
Hard to measure, the javascript I worked with was mostly front-end, which is harder to write automated tests for. Not impossible, but the higher friction naturally leads to less tests, especially given how frequent the front-end changes. "Level of safety" would also need better quantification. Something that a peer-reviewed study would be better suited for
Putting software design under the hardware design folks after Forstall was outed was and remains disastrous IMO.

Dye and his team continue to make beautiful hardware but fuck me hiding every function of a program behind a hover state or overflow menu absolutely kills usability. Productivity is being sacrificed for some weird notion of “cleanliness”. We’re all running displays with millions of pixels, we can afford buttons for stuff.
Any company working on this at the moment? If it's bound to happen, I assume the research has already started.
I would love to hear from people who've been using the "git subtree" command instead. Any good experiences?

---

My colleagues and myself lost work a few times when working on a project whose top-level Makefile / build script ran some "git submodule" commands from time to time, when they detected that a submodule appeared to be out of date.

Those commands wiped work in progress, because of submodules' tendancy to leave junk around when switching to-level branches, or the set of submodules changed, or the same with recursion over vendor submodules. That junk caused a few end-users to end up building and running incorrect code, or to get unexpected build errors, so the policy was for the build scripts to wipe it.

In other words, policy was to prioritise the experience for end-users who cloned the repo and occasionally updated or switched branches.

Unfortunately that meant it clobbered work in progress by devs occasionally. If you were careful it wouldn't happen, but if you left a trail of small changes and forgot about them, and did a git pull or such to get on with other work, intending to still find those work in progress changes later, they'd sometimes be gone. Such changes were things like those which needed to edit inside and outside a module (e.g. for API changes), or improvements to a submodule's code that there was no hurry to finish or commit, changes to add diagnostics, spotted improvements to tests, etc.

Often when those changes were wiped, the dev wouldn't notice for a while. Then later, "eh, I thought I had already done this before...".

My solution was to stop using the standard build target, and remember to use "git submodule" myself at appropriate times such as when switching branches and updating. That way I never lost any work, but it was not how I was "supposed" to work.

The team discussed improvements to the auto-update-clean-and-hard-reset commands, to make it check more carefully so it wouldn't run as often. But the problem remained, and that refinement made the build options rather ugly, a kind of "make REALLY_REALLY_DONT_UPDATE=1" sort of thing. Sensible defaults that Just Work™ for everyone were never found.

I also found submodules annoyingly time-consuming when making many changes that spanned inside and outside modules or across modules. The dance backward and forward to make a PR in the module to something that's compatible with before-and-after, then a PR in what uses it, then a PR clean up the module, perhaps multiple iterations needed, with each step having a potentially slow review cycle in between, over GitHub's slow web interface as well. Understandable for stable APIs shared among multiple projects, but pointless busywork (and worse commit logs) for small changes that could be a single PR in a monorepo.

(ps. Please see first line of this comment.)
At this time last year, this region was subjected to a 'heat dome'. Luckily this building has a 'cool dome' in the basement. Spent a few days listening, reading and solving down there (12-16°C cooler).

Much cooler temperatures (13°C) are found just a few feet below ground. (Memorable to those who've visited 'root cellars.) Before long those mysterious 'underground cities' in Anatolia may not seem so mysterious. It's a low-cost, low-tech, zero-energy solution, used by native communities in many regions of the world.
What heat pump do you have?
This is the port.

https://images.app.goo.gl/n3TFrbnZ8JbjzVyp9

It expands to support a standard Ethernet jack
> "Each project, even small ones, is a chance to add new techniques and tools to your toolbox. "

Love this. I recently started a collection of notes all named "learned-from-X", which is the compilation of all the small things I learned (essentially knowledge obtained from a google search) while working on projects.

I am a believer in focusing on a problem you want to solve and learning as you go. However, to cement what you learn and to have a higher level understanding, reviewing what you've learned is a good idea.
It doesn't, no. If you are only working with libraries designed for Windows or are linking against binaries, most of the dev issues listed disappear. The point of the article is that the Windows push for open source introduces friction because the way of doing things with established OSS projects is so different.
It’s a single computer that allows ssh and tmux with irc, email, and other text based commands to communicate with each other.
I'm not aware of any stats, but I've experienced the difference between hot neighborhoods and cooler neighborhoods, right next to each other in Houston. It would be great to have a quantitative measure for this effect, similar to a walk score (which isn't perfect, but can be occasionally useful).
Why can’t you stir fry?
This makes sense if the buyers totally bought their rigs outright, which isn’t usually the case. They usually buy rigs on credit which assumes a certain amount of profitability to be able to pay it off.

Why? Well, imagine you have the capital to buy 3 rigs outright. You can use this to make a profit of $X / day on your outright owned rigs. Well, maybe it’s smarter to buy 30 rigs on credit, pay interest, make $10X/day in profit (before your loan payment).

At some profit $X you should go the credit route because you’ll earn more, in fact a lot more. However if you buy assuming $X and the profit craters you could be in deep trouble