skysight-inc/HackerNews huggingface dataset:
What do I need to do to switch from an official Nix install to using nix-installer on macOS? Just uninstall the current nix and install using nix-installer?

My config is loosely based off https://github.com/dustinlyons/nixos-config if this matters. Using nix-darwin.
I believe that you don't believe me, because that's what I always got. Except when on rare ocasssions ppl followed me with a car or motorbike. OR I pushed them to ride like they couldn't believe when they rode with me, which was also rare.

Can't do anything about it. Shrug. :-)
They sold it for a reported $180 Million[1]

While chump change to the likes of Google, it demonstrates Squarespace views this business as highly profitable. Migrating an acquired business into your systems makes a lot of sense.

Unless you have some evidence it would have been just simply shut down otherwise, I think you're inferring things that do not exist. Few if any of the other "shut down by google" operations could have sold for anywhere near this amount, as they almost universally lost money and/or were niche.

[1] https://www.theregister.com/2023/06/18/google_domains_shutti....
I think they meant Rust? Rust definitely has that property to an extent; C++ is so far from it it’s not even funny.
I get the need for native apps on media centers, like Roku, Apple TV, etc. I do not understand why anybody would need a native app on desktop. Let alone an unofficial closed-source one from a dev that only has this to say:

> This is unofficial client for jellyfin app. For now macos only. Very early build. Expect any kind of crashes, issues and generally its good if it even runs.

Source: https://github.com/avdept/JellyBox
Yah, it's nice reading some balanced takes.
There are a lot of nice tui s for this, but saidly helix does not support opening new files into an existing session :(
Liquid oxygen as a hypergolic propellant? No. Rockets do not use liquid oxygen as a hypergolic propellant.

Merlin engines combine TEA-TEB with liquid oxygen to start the engines but do not use TEA-TEB as a propellant. TEA-TEB also spontaneously ignites with air; that shit is insane but you deliberately chose not to mention TEA-TEB because you know TEA-TEB would fuck you up (presuming you could even consume it without catching fire first!) Leaving out such a pertinent detail leaves it hard to believe you're not arguing in bad faith.

Why are we even talking about hypergolic propellants? Because a fear mongering comment upthread suggested that rocket propellants are extremely toxic. Scratch hyperbolic propellants off the list and what are you left with? Kerosene, methane, hydrogen, and oxygen. None of these present a significant toxicity threat, the worse of them is kerosene which can contaminate the soil and groundwater but all of the others vaporize harmlessly. So the fear monger was trying to cash in on the toxic reputation of hypergolic propellants to insinuate that Starship presents such a threat itself. This is complete nonsense, a bad faith argument that even a single minute of research can refute.
Ssshhh keep it quiet...
Present evidence it was forced vs. shut-down or stop spreading a made up rumor.
Maybe transition away from private car ownership. Public transport for 80% of cases, car share for remaining 20%
Isn’t the Space Coast launch site in Florida in the middle of protected wetlands?

I don’t think the area around Boca Chica is very important and the land around is not special or worth more than having a launch facility.
Keep up the good work! I feel that your content is bringing a lot of educational value to the tech community. I would even say that the visualisations extend the understanding of tech averse people and leads to more people understanding our rather complex ecosystems.
Thank you
No, URL's don't make sense because your application shouldn't care where on the internet your dependency happened to be hosted when you integrated it. It's location has nothing to do with what it is.

By the time you're going to production, your vetted and locked dependency should be living in your own cache/mirror/vendored-repo/whatever so that you know exactly what code you built your project around and know exactly what the availability will be when you build/instantiate your project.

Your project shouldn't need to care whether GitHub fell out of fashion and the project moved to GitLab, and definitely shouldn't be relying on GitHub being available when you need to build, test, deploy, or scale. That's a completely unnecessary failure point for you to introduce.

Systems that use URL-identified packages can work around some of this, but just reinforce terrible habits.
I guess active users counts anyone that opens Facebook for even one second. Not necessarily people who are using the app in a meaningful way.
Using brew on Linux is generally not a good idea because distros have better package managers.
OK? Not sure how this relates to TFA.
> "The richest 1% is responsible for 49% of lifestyle emissions. [...] luxuries like meat consumption or fast fashion"

How many megatons of meat do you think Musk eats a month? Does Bezos put a billion burgers into his belly? The vast majority of meat is consumed by people in that bottom 99%. For that matter, how many fast-fashion trendy patterned stockings do you think these men wear? It's really disingenuous to act like you're against luxuries for the 1% and then use meat and cheap clothing as your examples of great evils to be eliminated. Who would be sacrificing if large scale production of these cheap goods were banned? Not the 1%. What you are proposing is not to tear down the 1%, but to suppress the standard of living for the 99%.

Maybe you just chose bad examples by accident though, do you have any proposals that would actually limit emissions from the 1% instead of capping the quality of life for the other 99%?
It doesn't help with the failure mode of dependencies disappearing, which forces people that care about it to vendor, which in turn brings its own set of issues.
GraphQL query to automatically send emails from InstaWP to Mailchimp
They pay as well as any company in Silicon Valley and better than most.
Support couldn't fully fix it even with hours of effort. Something is very wrong and worth warning about there. Those are not reasonable consequences for buying the wrong thing.
Maps/Waze can also shape traffic by suggesting different routes.

One interesting half-way-there solution (and this is a technical solution involving cars, not reducing them as I'd much prefer) would be to have nav apps be able to read the traffic light timings for the intended route, and give you a suggested speed to travel at to maximise green lights and/or traffic throughput. It would piss off cars that want to go exactly at the speed limit, but would probably end up getting them to their destination faster.

In both cases, cities could offer incentive schemes (e.g. points -> $ or discounts off licence/registration fees) to encourage people to 'follow the computer'. Would probably be cheaper than building infrastructure.
That's weird, I had a different experience: I definitely heard about Plex the most, but often in a negative light. The alternative presented (again, in my experience) was always Jellyfin.
Latitude and also having ocean to the east so if something goes wrong, you can abort and not worry about debris falling on people.
Samsung has their own "offline finding" as they call it, if enabled other Samsung devices/wearables can locate it somehow, brief on how that's done on their site
Only took them this long to come to some common sense.
How long before they rename and back again this like they did with Intune.
It’s called Rayon for anyone who wants to know.
This is how being 2m tall feels all of the time. :]
if it were that simple, I'd take the "billing time" payment every time. Engineers' time is the greatest cost for just about any tech business
> Scala isn't a language I can use here, we have too much Java tooling and are conservative on new languages.

Most Java tooling works with Scala out of the box or at most needs a plugin added, and interop when calling Java from Scala is very smooth. Even if it wouldn't be acceptable for production code you might consider trying it for migration scripts, admin tools, testing etc. (though personally I'd stay away from ScalaTest et al) - that's how I got my start with Scala many years ago.
And others would interpret it as "We could safely fire our nuclear weapons." And I'm not counting on the guys responsible for building the weapons to decide the more altruistic interpretation.
Gatekeeping? Nice word to hide your blatant bigotry.
oh, this is great. i've never thought to even try bookmarklets on mobile.
That doesn't jive to me with my read of their text.
Phind co-founder here. Phind gives you 10 free GPT-4 searches without an account and 10 free daily GPT-4 searches with an account. On top of that, we have plans that support higher GPT-4 uses as GPT-4 is expensive for us to run.

Furthermore, all users have unlimited searches using our own Phind model (which has similar coding performance to GPT-4) using the dropdown menu.
as is: provision isolated resources for each customer
I wonder how cheap and low power we could make tracking beacons if we didn't actually have to send any data and could accept some privacy risk.

Imagine like, an airtag, but the ID only needs to be 1 byte long, or even just a simple presence signal.

You'd put it on everything you own that's portable and easy to lose. When you want to find it you just search for signals. Maybe it could have an NFC silencing feature.
Perhaps it could only activate after 10 minutes of not detecting movement, while also not being near a base station (The base stations would mark a location as the "safe place you won't forget").

So you won't get any interference from anything people are carrying. You won't pick up anything safely stashed where it actually belongs.

But you can quickly sweep an area for any lost property (Which could be good or bad, depending on if it's a helpful security guard or someone who believes in finders keepers looking...).

You wouldn't ever have to receive any data, except to detect base stations, which would only need maybe a 2ft range.

But it wouldn't solve the big issue with losing stuff, detecting when you leave a location without a thing.
#2 seems like a ludicrous misalignment / conflict of interest. Why would I as a taxpayer/voter want CO2 emissions to decrease if I'm essentially getting a monthly bonus for their existence?
My understanding was that Chinese consumers (generally) prefer cars with much longer wheel-bases than American consumers. While it is true that SUVs popular in the US may be taller than a long-wheel-base sedan, I am not sure the GVWR is that different between the two. Besides, the batteries are the biggest source of weight in an electric car by a lot,

What I can see as being a difference maker is the need (real or imagined) of a lot of American consumers to tow something. Towing _does_ require a lot more energy and thus batteries.
And they're also shutt- I mean deprecated their enterprise version? (https://cloud.google.com/domains/docs/deprecations/feature-d...) That doesn't sound like "oh, we're selling this because it's valuable money" but more of "we don't have the energy to maintain this".
Yah, but that's definitely not the default in Rust land.
> "We're pretending security is not an issue." has been the feedback every time this is raised with the Cargo team.

Literally nobody has said this.

> The attitude of "Rust is memory-safe, so we don't need any other form of security." is not a good one.

Fortunately it's an attitude that nobody in the Rust project has!
Every time I try to skip the glue code, it bites me. You need the glue layer to allow for indirection, tight coupling through codegen or reflection will work early on but eventually a dependency will need to be shimmed, proxied or otherwise modified- having the glue layer gives us a way to make that change.

In software eng, the one true metric for delivering is how fast can you iterate on a piece of software. We already have constructs to deal with code duplication (classes, etc).
The us is 4% of the world, fb is the internet in many countries.
Isn't the goal to offer a good experience and a one platform rules it all approach?
A massive downgrade for the GCP platform.

If the onion released an article that states "Google sells it's domain business, who needs domains in 2023 anyway" this would be a great joke.
> 6. You can bind any menu item in any application to a keystroke. E.g., you can rebind menu items to other keys, or adding key bindings to menu items that don't have keyboard shortcuts.

This is a macOS feature (either globally or per app) and doesn’t need a separate app. For example, I have ⇧⌘M mapped to Window > Zoom (the inverse of Minimize).

This is now hidden deep in System Settings > Keyboard > Keyboard Shortcuts button > App Shortcuts.
Repochat
Mostly yes and good.

One thing I don't appreciate is nonorthogonality of certain uses and control structures that cannot be refactored into a function despite structural equivalence without introducing a multiple borrow conflict.
Walk around shouting Hey Siri
For my next project I prefer:

1. Create MVP (0-100hrs work max) without talking to customers (too much) avoids paralysis. Avoids mum-test type issues too. Have some basis that it is a good idea (e.g. competitors, solving your own pain, a pain you see mentioned alot online)

2. Get MVP in front of people then talk to users.

3. Iterate based on that information: talking to people who are taking time to use your service.

It is a nice filter to talk to people who use your service (proof of work!) vs. just interviewing a bunch of people who look like they might be in your persona.
> Do you need memory safety?

I think that’s an unusual way frame that requirement.

All programs need to handle memory _correctly_. Very few seg fault as part of expected operation.
Love the hustle, dude! This is the way!
It's pulp. People like pulp. I do too.
> The "gotcha" is that at 83 microns, this study showed only 0.15% of the theoretical CO2 capacity absorbed in the first year

According to the study [1] (and the article), that's because the experiment was purposely conducted in a dry climate (inland northern CA) and during a drought to determine a lower bound on the CO2 absorption capacity. More well suited (wetter) climates are expected to result in more CO2 absorption.

"Given that climate change impacts such as heatwaves and droughts are already widespread, knowledge of the robustness of enhanced weathering under extreme conditions is essential to understanding its future efficacy. Here we show that enhanced weathering maintains modest carbon dioxide (CO2) removal in a multi-acre field trial under an extreme drought in California, one of the largest agricultural producers globally."

1. https://iopscience.iop.org/article/10.1088/2515-7620/acfd89
I am very familiar with Portland ;), the green ways are cool for sure. Except if I am on Salmon or Clinton and want to go to Fred Meyer, I need to ride on 39th or Hawthorne at _some point_, which to a lot of people is a non-starter due to danger.

Besides, suburbs exist, and someone living in Sherwood who works in Portland, at this time, requires a car. And public transit would need to be either faster, cheaper, or more convenient (wifi, coffee etc) than driving for (most) people to adopt it over a car.

And Hawthorne is _super confusing_ now. Turning right from Hawthorne to 10th is a nightmare, you have a bus lane, a bike lane and a sidewalk to the right of you, all of which could contain someone. It is hard to accurately see all three "lanes" that you need to cross. Another example is the Hawthorne bridge onto 99E, the angle is below 90 degrees so you end up with a massive blind spot. I start looking for bikes/peds way before the off-ramp because I am used to it.. someone from out of town or who rarely drives in Portland is going to kill or injure someone.
The ocelot concern is a transparent farce.
Not possible in your typical Rails setup where remote console spawns a separate process so you can't inspect what's going on with your actual servers. Even if so, the amount of observability is not remotely (pun intended) close. You don't appreciate it until your production puma workers start going haywire and you have no idea why
"Rust screams at you all day, every day, often about things that you would have considered perfectly normal in another life."

A good C compiler does this when you turn on all the flags. I like languages/compilers that let you selectively disable the screaming and let you write bad code on purpose. Bad code that works but can be written fast is often better than perfect code that takes forever to write. Once you have a bad but working POC, you can make it less bad.

"It’s got no problem attracting new users, but it’s not resulting in dramatically improved libraries or tools. It’s resulting in one-off forks that handle specific use cases."

Age has nothing to do with that. Attracting core devs is hard, and putting lots of effort into making it attractive is necessary. On top of that, cultural conventions are set by the early adopters, and a lack of convention is often just as sinful as a bad existing convention.

Take Python for example. They took a lackadaisical approach to development and runtime environments, and as a result there's 50 competing ways to develop or run a Python program. Their most-used package repository, PyPI, has been a mess for years. Nobody builds on top of existing packages, names make as much sense as a random word generator, the ecosystem is rife with malware, you can't even search for a package on the command line, etc etc. None of that is the language's fault, it's the community and core team's fault for sitting on the sidelines rather than leading. Culture matters more than the tech it's centered around.

(I'm not trying to pick on them, I just know their problems better. C has been around for a half century and its community never really put together half the solutions more modern languages did)
That article starts with the premise that “it’s a feature, not a bug” then goes on to describe a whole bunch of things I consider to be anti-features of a packaging system that has a flat namespace.

The first section says it discourages forking. I consider this to be bad. Nobody’s code should be more important purely because it squatted a better name.

The Identity section actually makes the case that flat registries make naming harder.

The section on Continuity is “we’ve tried nothing and we’re all out of ideas”. Make up an org name and grandfather all packages in the flat namespace into that special org. Also this is already a problem because packages in the flat namespace do get abandoned, then forked, and then we have the associated issues.

The section on Stability seems to take it as a given that crates.io should be the only registry. I don’t. It also seems to conflate cargo with rustc for the benefit of the argument.

The squatting section describes only anti-features and I don’t consider the author’s legitimate use cases to be legitimate reasons to squat.

I think the only legitimate problems that need addressing are the ergonomics of accessing namespaced packages throughout transient dependencies and backwards compatibility with non-namespaced code. But the fact that these are real problems does not, to me, make a flat namespace a “feature”. It’s just easier to implement.

It’s okay for it to be a mistake that takes effort and time to fix.
They do it so that the coffee stays warmer longer during the winter months
we are all dang on this blessed day
This isn't something I made up, nor is it even controversial[0]. Antisemitism was a common cultural and political element of the early Church and its establishment of self-identity as separate from Judaism, and the belief (sometimes codified into Church doctrine) that the Jews were cursed by God for their rejection of Jesus as the Messiah, and the villification of Judas as the symbol of that curse is almost as old as the Church itself[1].

[0]https://en.wikipedia.org/wiki/Antisemitism_and_the_New_Testa...

[1]https://en.wikipedia.org/wiki/Antisemitism_in_Christianity#C...
While they don’t say it, I expect this is solely to prevent ripped disc images from being presented as a disc drive to the console using emulation hardware.
What's the difference in signal strength between bluetooth and wifi? I had assumed since they use the same frequency, and usually the same chip and antenna, they would be much the same (perhaps there are regulatory differences between them?) If anything, I'd guess that BLE would be more useful in this case as there is less handshaking, which means on a very poor connection you've got more of a chance of getting some data through.
Yeah, blaiming the compiler for pointing out potential runtime bugs is just shooting the messenger.
Wised up so they can make sure companies only focus on profit.
A recent thread with some good ideas: https://lobste.rs/s/d5qwzs/what_is_your_mac_os_setup
No idea, it was super annoying as a Turo customer though.
Tolerance for Non-Determinism in AI-Assisted Incident Management?
UnStruct AI founder here. We all know that AI can be a double-edged sword. For instance, I've developed a feature (in beta) that suggests tasks/follow-ups based on what people say in Slack. While it offers convenience, it can occasionally become spammy, and during high-pressure moments, might even prove distracting.

How do you feel about deploying such tools, especially in high-tempo situations like incident management? How do you strike a balance? I'm wondering if these tools might be more appropriate for after-action reviews once the dust has settled?
The current party in power repeatedly said that rioting != valid protest and nominated an aggressively boring candidate for president instead of a left-wing ideologue. The current party in power is still fundamentally controlled by its centrists; the other got taken over by its fringe.

And nothing that Democrats have done comes close to Republicans failing to impeach Trump, supporting his efforts to overturn election, etc.

I'm insulted you think the rest of us are too stupid to easily spot the differences or something

edit: what does "in power" currently mean anyways? One party controls the executive branch, the other the legislative.
> maintain a steady-state ecosystem in perpetuity

Impossible. It's not how the universe works.
Can't scala, haskell, (kotlin?) you just lift functions into Async?

You can convert colors simply but only one way, and practically that works, functional core imperative shell, etc.
Sometimes billing time is your customer's patience, their phone battery, or other things like that which make your product worse and give your competitors an edge.
I’d have to disagree given all the adults who have bad opinions of AR / VR, yet ironically have yet to try anything modern; with their only experience being Google Cardboard from a decade ago. It’s easy to find these posts on HN and elsewhere online.
> It also looks like (soon) you’ll finally be able to configure global lints for a project. Until now, you had to hack your solution to keep lints consistent for projects.

> I questioned my sanity every time I circled back around to the Clippy issue above. Surely, I was wrong. There must be a configuration I missed. I couldn’t believe it. I still can’t. Surely there must be a way to configure lints globally. I quadruple-checked when I wrote this to make sure I wasn’t delusional.

You create a .cargo/config.toml in the workspace root so it covers all your crates.

inside the file:

[build]
rustflags = ["-Wclippy::lint_name_to_warn", "-Dclippy::lint_name_to_deny"]

The only limitation is that rustflags are not additive, so if you have other sources of rustflags like the RUSTFLAGS environment variable it will overwrite this setting.