skysight-inc/HackerNews huggingface dataset:
The game does a lot of plane-like physics instead of space-like physics as far as flying goes. Some of it is explained away by the ship "simulating" things for you, like drag. In practice it's just more fun/intuitive that way. Humans have a hard time with real space physics. Not that dogfighting would ever be a thing in space anyway.
Am I crazy to think this might raise legal alarm bells? Mirroring content is commonplace but I haven't heard of sites with an explicit path to take users from another site. One is grazing on their land, the other is an existential threat.
They're basically saying:
a) you are safer with a password manager than without, in general, despite it not providing any additional security for this particular attack; it is also not any more vulnerable. having a password manager doesn't make you more likely to be caught by this attack (because the last thing they want to do is accidentally convince people to stop using them, in favor of 'newpassword2')

b) you are safer yet if you turn off automatic autofill and instead use a hotkey or some other form of user interaction
I've not actually done it, but from what I understand using two GPUs is the way to go - you use one for your actual display etc., and the other is just passthrough to the VM.

(I was looking into it in the context of running Fusion 360 in a Windows VM though, not Stable Diffusion or any ML.)
It was easy for me to spot the why, so I'll distill it.

Once a market is saturated and business growth can't continue by selling more of the product(see microwaves), growth occurs through M&A(consolidation) or reducing costs(eg: removing the moisture sensor). The author reflects on the microwave market having single supplier Midea as an example of the former, and their removal of the moisture sensor as an example of the latter.

Naturally, the author asks, "what are the incentives that create these behaviors?" They identify the economic structure as the proximal cause of these incentives. Thus concluding that the economic structure that creates microwave markets ultimately concludes in the creation of the shitty microwaves.

The author extrapolates this to the multicooker market a la InstantPot - a bonus predictive why InstantPot will get shitty soon.
Google very clearly stated in no uncertain terms that Stadia was a real product that they were committed to for the long term. Stating, after the fact, that it was "actually" an "experiment" or a "random little thing" is not just dismissive - it's pure revisionist history.
I have a Panasonic "Genius" microwave that I actually like quite well. The "inverter technology" does seem to cook more evenly than previous microwaves I've had, and the "air fryer" (not really) mode works very well for a bunch of frozen things that should be a bit crisp on the outside (e.g. samosas or taquitos). Day old fries often come out better than they were when fresh.

Is it an amazing indispensable life-changing invention? No. But does it suck? Also no. The premise of the article is seriously flawed, and comes across as somebody who just didn't like anything but old-fashioned stove cooking (probably by someone else) in the first place.
Not to nitpick but I think you mean trilaterate ;)
I think you're equating political intrigue with loyalty, whereas for many people it just means relatively selfless identification with the goals of your employer, ie diligence.
Two lane roundabouts are pretty good. More than two lanes are very questionable. And roundabouts which include... stoplights!?!? are just stupid.

I live in the Netherlands, where roundabouts are very common. In many cases, they are an improvement.

But NL is also a huge bike country. And at most roundabouts, bikes have right of way. So as a car driver, you have to worry about other cars as well as bikes which may turn (go away from the roundabout) or continue (cross the adjacent road circularly around the roundabout.

In good visibility conditions, it's ok. And by OK, I mean it can still really f* up car traffic, especially when it is a high traffic area not far from a school. In lower vis conditions, and/or when electric higher speed bikes are concerned, it becomes a whole new kind of danger.

I would argue that the benefits of roundabouts diminish or fully disappear when the number of lanes exceeds 2, or when traffic lights are added to roundabouts, or (and!) especially when bike paths intersect with and circulate around the roundabouts.
I've been enjoying this thread. I have a company that does this (Eion). We are recruiting for a data engineer role to implement the algorithms for quantifying carbon removal, if these questions are interesting to you. Touches on nearly every aspect in this thread.
> Imagine like, an airtag, but the ID only needs to be 1 byte long,

Well, then you could only ever track 255 different tags :)

AirTags are already pretty minimal. Their battery lasts about a year, and I imagine an open source equivalent should be possible to build for under $5.

This is purely guesstimated based on the fact that I have a couple of Bluetooth LE thermometer/hygrometers that cost me about $3 a piece that last about a year on the same battery (CR2032) – and these run custom firmware and need to run a display and data logger (to on-chip flash) as well!
You can, though. From a random Cargo package I have downloaded to my computer:

[dependencies]
uniffi = { git = "https://github.com/mozilla/uniffi-rs" }

You can also specify revision/branch/etc.

Alternatively, you can do:

[registries]
maven = { index = "https://rust.maven.org/git/index" }
[dependencies]
some-package = { index = "maven", version = "1.1" }

Obviously Maven doesn't host any Rust crates (yet?), this is just a theoretical example. Very few projects bother to host their own registry, partially because crates.io doesn't allow packages that load dependencies from other indices (for obvious security reasons). The registry definition can also be done globally through environment variables: CARGO_REGISTRIES_MAVEN="https://rust.maven.org/git/index". Furthermore, the default registry can be set in a global config file.

In theory, all you need to do is publish a crate is to `git push upstream master`, and your package will become available on https://github.com/username/crate-name (or example.com/your-package if you choose to host your git repo on there).

Personally, I don't like using other people's URL packages, because your website can disappear any moment for any reason. Maybe you decide to call it quits, maybe you get hit by a car, whatever the reason, my build is broken all of the sudden. The probability of crates.io going down is a lot lower than the probability of packages-of-some-random-guy-in-nebraska.ddns.net disappearing
Hah, I didn't know Silicon Valley's "hot dog, not hot dog" app had IRL roots!
This is a deeply weird take IMO. Nobody "embraces risk" because they have a risk fetish. You take on risk because you believe you can be paid for it, and perhaps you are better equipped to mitigate the risk than the people paying you to take it.

There is no payoff for using a Google product versus one of the competitors, so a rational person would not accept the risk that Google pulls the plug on a product, or some contractor gets banned by Google and gets your whole account frozen, etc. There's no upside. It's not even gambling because there's no "win" possible - it's more like shooting an arrow straight up into the air and hoping it doesn't land on your head.
Linux Foundation Adopting Terraform Fork Provokes Ire of HashiCorp CEO
The Samsung microwaves, although with good build quality, are notorious for having a very bad UX.

- The buttons don't give have tactile feedback.

- Setting time is very confusing.

- You have to press multiple buttons just to start.

- If you want to cancel/clear timer, you have to press multiple buttons again.
I think adjusting the prompt makes sense. We have to keep in mind that this implicitly happens on the human side as well. The person creating the initial question will consider how understandable it is for them and edit until they're happy. Then the questions will be reviewed by co-authors and possibly tested on a few people before running the full experiment. They'd probably review the explanation again or change the task if they realised half the people can't follow the instructions.

We just call it "editing for clarity" rather than "prompt engineering" when we write for other people.
Crushing rock is very energy intensive, transporting rock to farms is energy intensive. Placing rock in the soil is energy intensive. Its hard to see how this passes the B/S test.
Why not user owned, or a nonprofit, instead of worker owned? It's too easy to imagine a worker owned advertising company that still wants to control everything.

Engineers typically already partially own their companies via equity grants, but we still have the whole landscape of enshittified tech
I got rid of my microwave several years ago and don't miss it anymore. (It took a while to get used to its absence.) I still have an Instant Pot but use it very rarely, maybe once a month. Investing in a high quality set of pots and pans has made up for it: copper pots for things that need to be heated quickly (e.g. boiling water, which is almost as fast as the microwave in a copper pot) and high-quality cast iron for things that need to be heated thoroughly (e.g. frying, baking). I also own a toaster oven because I'm too lazy to toast bread in the frying pan :) That one is electronic, but you can still get analog toaster ovens I believe.
I go to threads here and there. It's okay, it's definitely a different feel than what I get on Twitter and I'm okay with that.

I don't think this is an app that requires a huge amount of resources to be run so as long as they keep it up it can carve a good niche. Not everything needs a billion users, though I guess there was a lot of hype around it in the beginning.

Also, we don't know what will happen with Twitter in the long run. I mean, having to pay for basic features seems like a really bad idea to me and people might want to migrate.

In any case, where is the promised activitypub support? Still waiting for it. Hopefully it's not been forgotten.
It wasn’t so much a question of skew but visibility: people saw celebrities opposing vaccination a lot more than, say, the Christian homeschoolers who were doing the same things but not holding press conferences back then.
Another option would be to grandfather all packages into their own org. So serde becomes serde/serde. This way you don't need to manage permission rules in the legacy "all" namespace.

You get some oddities such as serde-derive/serde-derive but the package owners can choose if they want to move to serde/derive or leave it in a separate namespace.
The proper way would be a bookmarklet that renders a list of bookmarklets.
He’s not taking about the richest 1% of Americans.

Even if he was your examples are disingenuous. Musk and Bezos aren’t representative of even the richest 1% of Americans.
”what can we learn from this? i don't know. capitalism will destroy everything it touches.”

Microwaves are better in countries with less capitalism?
> Technology isn't a weakness with Google... never was. Most of their stuff is top-notch technology-wise. The problems are from a business-angle and being their customer.

There's very little technologically impressive with GCP. It's the same products from all three vendors with few exceptions.

What's a clear weakness with GCP is Google's lack of seriousness as operators. Regions in the same data center, outages that take down a whole region for 3+ days. It's not good.
So, do we have a replication crisis?
> conflation of free Gmail/etc. consumer products with GCP.

* Google Domains

* Google Cloud IoT Core

* Jamboard

Also they increased Google Maps pricing by like 10x at one point, and they increased Cloud Storage prices pretty substantially last year too. Price increases can be just as impactful as killing a product. I don't think AWS has ever increased any prices or shut down any service (though quite a few are essentially zombies - SimpleDB, OpsWorks).

Then on the consumer side, Google have killed quite a few paid products. One that bit me was they shut down Google Cloud Print which killed the ability for me to print to my (cheap) printer from my phone. Besides that, there was Nest Secure, Stadia, etc. etc.

Google's reputation problem isn't just coming from their free consumer apps.
Good Stuff,

About GraphQL, I read that GraphQL is versionless, is it really versionless? If so, how? The link below says you will still need to version but we have some Graphql fans at work and they insist that it does not need to be versioned.

[0] https://medium.com/swlh/no-graphql-doesnt-magically-fix-api-...
I'm honestly astounded at how badly many languages have implemented dependency management, particularly when Java basically got this right almost 20 years ago (Maven) and others have made the mistakes that Java fixed. With Maven you get:

1. Flexible version (of requirements) specification;

2. Yes, source code had domain names in packages but that came from Java and you can technically separate that in the dependency declaration;

3. You can run local repos, which is useful for corporate environments so you can deploy your own internal packages; and

4. Source could be included or not, as desired.

Yes, it was XML and verbose. Gradle basically fixed that if you really cared (personally, I didn't).

Later comes along Go. No dependency management at the start. There ended up being two ways of specifying dependencies. At least one included putting github.io/username/package into your code. That username changes and all your code has to change. Awful design.

At least domains forced basically agreed upon namespacing.
I thought that was a roundabout. At least my UK family would call that a roundabout.
I would claim that most people are very bad at communicating in a way that can be interpreted, by human or AI, with a single shot. Most of the time some back and forth is required to clear things up. I think it's unfair to expect gold from garbage input, since meat brains can't do that either, without some back and fourth.

Those prompts should be available. It's ridiculous that they're not.
They shut down Google Cloud IoT Core. Y’know, the thing you need to update all of your field devices to be aware of?
And trade school enrollments are up. https://thehustle.co/04242023-trade-school-enrollment/

Universities will need to get used to smaller enrollments.

https://www.bestcolleges.com/research/college-enrollment-sta....
Ha, last winter I lost my phone while snowboarding in the last 300-500m before mountain base. I noticed because I was listening to music with my airpods when I got to the bottom the music had gone silent. Thankfully I had my Apple watch with me, so I immediately got off the board and start running uphill while incessantly spamming the "ping my phone" button. At some point I saw in the watch screen it briefly connected and then immediately disconnected again. I realized somebody had probably grabbed it and skied by me. I went back running to the chairlift while still spamming the button and finally found the person who had grabbed it, a few seconds before he got into the chairlift. I felt that day that the watch investment had been worth it hah.
To me, GCP does seem easier to use, but I've recently had some instances where I had externally-hosted services (Zaps) make calls to my cloud functions there and inexplicably fail, with no logs whatsoever. While I was trying to figure out what went wrong, I found some other people online who said that their Google rep had mentioned "service instability" or something of the sort to them. Thinking that must've been the case, I went to reach out to GCP support (as nothing was mentioned on their outages page), only to find that it costs $30 / month to get help with anything other than issues with billing (and their pricing page threatens to ban you from support access entirely if you are caught buying it and canceling it after use).
Wow, interesting. Now that I think of it, in those dot-com days, hype was flowing freely from most players' mouths and keyboards.
Besides, it's mostly the programmers doing the abusing.

People do sick things with lifetimes and generic associated types. Sick, sick things.
If we're being nitpicky it was probably neither – multilateration requires taking multiple measurements, drawing circles/lines of equal signal strength (or timing advance) and then intersecting these.

If you just want to home in on a transmitter, there's a much simpler algorithm: Try walking into various directions and keep heading into the one that makes the signal strength nunber go up :) Not sure if there's a name for that.
The answer here is almost certainly one of these:

1. Fix rhai::Engine so it is Send (if !Send is unintentional)

2. Use tokio::spawn_blocking or normal threads to run the rhai::Engine bits

3. Don't hold the rhai::Engine across an await point.

Which one depends on rhai Engine details and what you want to accomplish.

Doing a block on inside a new thread seems unlikely to do anything useful (unless there's some undisclosed detail that makes it reasonable).

I encourage you to ask about this in the rhai repo in a discussion or issue.
So when they get bored and sell their relational databases off to Oracle, what then?
Full-fledged APIs for slowly moving datasets without writing code
Yeah I find this fashionable statement often meaningless when used.

They literally gave an example of how when people were buying them, there was a lot of innovation. That was capitalism too, right?

In fact, if there is any innovation do be had here, it’ll only happen because of monetary motivations.
I just want a microwave with an analog dial for time and a switch for low, med, high. They can keep the computer.
I think you're gravely mistaken about that. I have absolutely heard people quoting this to justify demands of rewards, whether monetary or status; an even pithier version is 'if you don't ask, you don't get.'
You might not want to mount your phone on the handlebar. See: https://news.ycombinator.com/item?id=37230198
> 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.

In the Go world this would be "vendored" dependencies, that is, the dependencies are within your source tree, and your CICD can build to its hearts content with no care in the world about the internet because it has the deps.

The URL is useful for determining which version of a specific project is being used - "Oh we switched to the one hosted on gitlab because the github one went stale"

The advantage of using gitlab, or github, or whatever public code repository is that you get to piggy back off their naming policies which ensure uniqueness.

But, at the same time, there's no reason that the repo being referred to cannot be in house (bob.local) or private.

Having said all of that, the Go module system is a massive improvement on what they did have originally (nothing) and the 3rd party attempts to solve the problem (dep, glide, and the prototype for modules, vgo), but it's not without its edge cases.
Initial post on THN was great in terms of feedback, traffic, etc. but back to dribbles and depression (dead pan facial expression). I feel like a techno thot waiting for the next rush of "attention"... but is it the same... I wonder? All that aside, I'm really wondering what the smarter individuals that me out there would do to grow this "idea" or simply dust bin it?! I mean it's useful for me, but... maybe I'm the weirdo in the room... I probably am... no doubt.

https://blog.june07.com/clippings-emergency-alerts/

https://blog.june07.com/introduction-clippings/
<misread the code, please ignore>
I just want to call out the how nice it is to have a global view of all the keyboard shortcuts like this. Including for applications you might not have open. It makes it a million times easier to fix up situations where two applications want to use the same keyboard shortcut and that causes some kind of issue… which is usually not a problem but can be a major pain when one or more of the conflicting shortcuts are global shortcuts that don’t require the application to have focus or be in the foreground.

Being able to jump into this settings pane and find the issue then simply remap one … infinitely easier than fixing this kind of thing on Windows… where last time I tried literally none of the “list keyboard shortcuts from all open applications” tools I could find worked at all on Windows 10.
What happens if (6) Did someone see it fall is No?
I'm afraid of them buying up US companies and workers, the way they've bought up much of Hollywood and gaming. Our system of capitalism means they get to use our own weapons against us.
Vultr
I used next 12 for a frontend with a Django backend and I was fairly pleased with it. Little slow on the build but tooling I could give to a fairly novice engineer and be pretty hands off.

Then recently, for another client, I tried nextjs 13. What a POS. A lot of the patterns I had learned were tossed replaced with something more complicated.

My first client is still happy but I will never use the stack again. Waste of time.
While I think that's a valid point, for the purpose of the paper having a competent prompt writer would be needed to make a fair comparison.

I think the researchers would know how to get the best from their own AI bot, so that's a level of competency that should be extended to comparisons, otherwise user competency becomes a source of bias. I do feel you're correct in your concerns though, the systems shouldn't need experts to use them, nor should they need the user to already know the right answer, which leads me to my next point:

When it comes to real world expectations, perhaps instead we need a large group of random people (with no prior experience) working with each bot to complete a set of tasks in order to determine how it truly performs - something that could be enhanced if the answers weren't easy to check.
Technology Connections covered microwaves: <https://www.youtube.com/watch?v=UiS27feX8o0>
Web Scraping with JavaScript for Beginner
Thank you for your comments. I appreciate it.

I will be sure to get in touch if I need anything.
BTW - I think my next door neighbor was a customer in those first 4 months. I remember helping him pack for a small move one night and we decided to see if There Was An App For That - and there was! I remember our both being surprised that we made the request at like 10pm and one of the co-founders showed up.

So, um, thank you and sorry! (We didn't order at 10pm to be inconsiderate - we just saw the option and took it). Glad things have worked out since then - I still remember the experience and use it as a reference when I'm telling people about this exact sort of hustle.
My friend was able to retrieve his phone that had just been pickpocketed out of his backpack that way!

"Hey, did you just grab my phone" can take some courage to say to a stranger; "Hey, I can hear my phone ringing in your bag when I press this button!" was much more convincing.
> I don't know where you are quoting "extremely toxic" from but even small quantities of toxic chemicals can be cause for concern.

Look up a couple comments in the thread. "I was under the impression that regular use of rocket fuel made a lot of land extremely toxic."

And we can't just assume there are harmful additives in meaningful quantities.

> Just because a square's a rectangle doesn't make a rectangle a square. Hypergolics are toxic does not equal non-hypergolics are non-toxic. For example, hydrazine monopropellant.

Okay, technically it spontaneously decomposes upon contact with a catalyst. That's so close to the definition of hypergolic.

Also it was pretty clear what they were saying. You can nitpick the wording, but their underlying point is still valid. SpaceX isn't using toxic fuels.