Rockslide

Just Dance Vance's shitposting doesn't even qualify as "ideas".

Figuring out what is true for npm v5 is quite the waste of time, given that we are currently at v11. And that's what this ancient stackoverflow thread is about. npm certainly has a troubled past, otherwise we wouldn't have yarn and pnpm and whatnot. But _today_, npm install works very reasonably with lockfiles.

npm install does install the exact versions from the lockfile. Even though this misconception gets repeated in every single thread about npm here on hn. npm install will not randomly update your direct dependencies, let alone transitive dependencies.

That first recommendation of pinning exact versions of each and every dependency is borderline insane. That's exactly what lockfiles are for. Which are used by default.

Well there are other lockfile updates as well, which aren't dependency version changes either. e.g. if the lockfile was created with an older npm version, running npm install with a newer npm version might upgrade it to a newer lockfile format and thus result in huge diffs. But that wouldn't change anything about the versions used for your dependencies.

> You've partially answered your own question here.

Is that the case? If it were ever true (outside of outright bugs in npm), it must have been many many years and major npm releases ago. So that doesn't justify brigading outdated information.

Yes. As someone who's using npm install daily, and given the update cadence of npm packages, I would end up with dirty lock files very frequently if the parent statement were true. It just doesn't happen.

How does this get repeated over and over, when it's simply not true? At least not anymore. npm install will only update the lockfile if you make changes to your package.json. Otherwise, it will install the versions from the lockfile.

Those stackoverflow posts are ancient and many major npm releases old, so in other words: irrelevant. That blog post is somewhat up to date but also very vague about the circumstances which would update the lockfile. Which certainly isn't that npm install updates dependencies to newer versions within the semver range, because it absolutely does not.

Well but the docs you cited don't match what you stated. You can delete node_modules and reinstall, it will never update the package-lock.json, you will always end up with the exact same versions as before. The package-lock updating happens when you change version numbers in the package.json file, but that is very much expected! So no, running npm install will not pull in new versions randomly.

> What's next We're improving the developer experience in three distinct phases: Framework -> Design -> Cloud

So the "cloud" part is where the enshittification will begin. Been there, done that, switched away from next.js :|

You have that mixed up, storage and ingestion is cheap in BigQuery but processing is exactly were they grab $$$

Yes the whole consultancy situation really is the icing on the cake - as the customer you pay for (alleged) experts in the field and get this as the result...

Sorry but that's nonsense. Partitioning is THE central cost controlling mechanism in BigQuery and the docs clearly state this. And it's an easy to use feature, so I'm not sure what makes you think using that would be as challenging as building your own query engine.

I don't have a lot of sympathy for people using their tools wrong. Using partitioning surely would have prevented this.

Adding a contact form to a statically generated website - that's what I use it for (all email goes to a single predefined account)

it literally says "same project" right there

> If that is all you're going to put there, then just leave it blank.

Well, I would love to. Unfortunately neither Play Store nor App Store allow you to do that... so "bug fixes and performance improvements" it is, 99% of the time.

Tradegate is even 08-22...

It was on German n-tv. Although they now state the opposite here: https://www.n-tv.de/wirtschaft/der_boersen_tag/Arger-ueber-F...

Trading has continued hours ago, probably even before this article was even published.

In a first statement, they blamed algo-traders which created (and within milliseconds deleted) a ton of pointless orders, like buying Wirecard for 0,05EUR (which is ~1/100th of the current price). Yes, they explicitly called out orders on Wirecard. So basically... Denial of Service by bot-traders.

GB never joined the Eurozone. So what does Target2 have to do with any of that mentioned in the article?

Is that true though?

The Deluge currently appears to not be buyable anywhere here, and if I bought it directly from them in NZ and add import tax to that, it probably won't be that much cheaper than a OP-1, if at all. And then the Deluge is at its core a step sequencer, so you can't even record unquantized. Might not be important to you, might be the killing missing feature for someone else. But never having owned a Deluge I can't say much more about it.

The AKAI Force is not that much cheaper than an OP-1 here. Is it "way more capable"? I don't know. But it doesn't even have a piano-like keyboard input, so again, at least one very distinctive feature it doesn't have compared to the OP-1. And then look at it. Would you want to take your AKAI Force on your commute to jam? I wouldn't.

The only one that really is significantly cheaper is the MPC Live, which I don't know, so can't really judge. But this seems to be a sampler at its core, so not sure about its synth capabilities? And it also doesn't have a keyboard...

Edit: well, I stand corrected - the Akai MPC Live II costs the same as on OP-1.

Exactly! You worded it better than I did :)

Spending money doesn't "hurt" as much when the goods you spent it on don't lose value, that's all ¯\_(ツ)_/¯ I might regret having bought it if you can get it for 200 bucks in 5 years. I will not regret it if you can sell it used for the same price as today.

Yes it's expensive in some ways and in others it isn't. Can you get a better synth for the money? Sure. Can you get a better sampler for the money? Sure. Can you get a better sequencer for the money? Sure. Can you get a decent synth, sequencer, and sampler for the money? Well, not necessarily. I'm not saying the price is entirely justified. You certainly pay a lot for the "brand". But on the other hand it might not be as overpriced as one might think by intuition.

Plus, as a owner, I hope price will only go further up, or at least stay on that level :)

> Clock hand question is painfully obvious once you look at actual analog clock face.

You see, intuitively I thought this would involve some kind of radian maths (just because it's about angles and a circle) and I don't remember any of that - never had any use for it.

But yes, it is a lot more easy than that. Not sure I would have discovered the trivial approach in an interview situation when it didn't even occur to me at home on the couch.

Well, when you work at Google, at least you must have passed that kind of an interview at one point - which is something I'm fairly certain I wouldn't be able to do.

I have no doubts that _some_ people working at Google are top of their field. But that hardly applies to all of their workforce...

Reading that stuff always makes me feel incredibly stupid (or rather clueless). I wouldn't be able to answer most of those questions off the top of my head. Including this weird clock hand question (which is probably some trivial math that might or might not have been taught to me more than a decade ago and which I never ever actually applied since).

Then I probably have to remind myself that I'm (halfway successfully) running a SaaS platform with tens of thousands of users, so maybe I'm not that clueless after all.

Maybe Google scale isn't for me.