skysight-inc/HackerNews huggingface dataset:
I agree with the overall point but I think you're using the wrong example. Music consumption didn't really change with the ipod, it changed with abundant mobile data that removed the need for locally-stored files (and hence their management). You can argue that the introduction of iTunes changed the game, which it did a bit, but imho mobile data is what fundamentally altered the field. Imho the move really was cd -> mp3 (filesharing/iTunes) -> streaming to mobile.
Could be.

However I'm doubtful that the PC market will move to a closed system similar to Apple's. So whoever comes in with ARM better be prepared for lots of competitions and low margins in a cutthroat environment. That's not a very attractive market proposition, especially since the x86 makers won't just take this lying down.

I think we'll be in a weird place soon.

Apple will be doing Apple things and increasing its market share but never taking over (maybe it will reach 20-25%? who knows).

Many server environments will switch to ARM, especially the big cloud providers that can make their own chips.

Qualcomm will push some more desktop class SOCs but I doubt they'll reach Apple's performance levels so they risk having their lunch eaten, especially by AMD.

So it's possible that the PC desktop/laptop market might be "stuck" with x86 for many more decades.

There is also a scenario where Intel or AMD come up with some brilliant designs and catch up completely or well enough to Apple in which case this will all have been a tempest in a teacup.
They own Ask.com adware?
If yes then probably baning them from store may not do much as I think the extension is sideloaded in most cases, plus there is also search provider set as default.
Back in the day Java runtime installer was spreading it at massive scale:
https://images.techhive.com/images/article/2013/07/java-ask-...
Please don't stop them, I really don't want to be forced to buy an Android phone.
Interesting as well that the actual voyage is pretty cheap, compared with the local transits and the various port and filing fees at each end.
Unlikely, if only because it's actually not easy to do that. You'd have to get the container placed at the edge of the ship when in dock, then get the locks on the container undone while underway, then either hope that the container gets washed overboard in a storm, and doesn't hit the ship on its way out, or get a couple guys to lever it off.

Which is totally doable, except that a container can weigh 30 tons, and you've got the space between rows of containers to use for working in. Admittedly, if it's at the top of the column, its probably a lighter container. But it's still going to be heavy, with the crew working up in the air, in a relatively narrow area.
Yes, it results better code but is a soul crushing practice, it's ok only when those involved have comparable experience level and can tollerate each other presence, that in my experience rarely happens.

Pretty sure it will never become the norm outside of some cookie-cutter shops that churn out CRUDs.
the main feature it is not de-regulation but de-centralization, anyone could run a Bitcoin node and unless you own 51% of the network you cannot control it

Facebook is trying to create yet another world bank
they sell it at newegg.
Loading a container ship is massive puzzle. The weight is one thing, but other one is that the operation really isn't point to point, but series. So starting from China empty(probably not) the ship is filled and then it visits multiple ports. And neither the ship or the ports want to waste time to move containers out and back in so containers going to later ports have to be below containers going to earlier ports. And containers travelling to the later ports can also be added on the way.
But you can have a third party if you want. (Though my personal preference would be NO party. I want total control over it myself with zero privacy leaks. But that likely won't happen.) In any case, the point is that you could buy something other than an Apple phone if that's important to you. I mean why buy a horridly overpriced phone that can't do what you want it to do? I wouldn't buy a Ferrari to haul farming implements around the back roads of Wisconsin.
On a great day I can do about 6 hours of highly concentrated programming work. Most days is probably closer to 4 hours.

If I'm tired, I will definitely not reach the 6 hours.

So I really wonder who in their fucking mind would think that you can pull off 12 hour workdays and be more productive? That is just pure insanity. I think it's time to stop lying to ourselves on how many hours we are actually productive in the 'work hours' that we do.
Mysterious monoliths: What on Earth are they? Here's what we know
This is great. After all these years the venerable and super useful TeX/LaTeX meme has once again managed to propagate into a new and exiting ecosystem. This would be good for the insufferable Rust community as well, I hope. Perhaps as the language they invested their identity in, actually becomes useful and venerated, they will calm the fuck down and start becoming adult members of the useful tool community.

Nice one rustcucks, next do Python.
It's also impossible to use (even for free apps) without IDing yourself, and your travel history (via IP geolocation), to Apple.

The convenience comes at a cost.
This comment alone makes me think twice about using whatever it is that you're "selling", but more importantly, what are you actually selling? The github page looks impressive, but the giant "PRO" links make me worried. They don't actually link anywhere useful, so I'm left wondering if this is another one of those "we open-sourced our backend but if you want to actually use it without a year's worth of reverse-engineering, give us a huge sack of money for the rest of the stack". Hardly comparable to an end-to-end solution.
Drinking is normalized in my entire country, but its still pretty obvious you're literally poisoning yourself with alcohol. That much I understood even as a teen.
I seriously don't understand why this elegant example is a 'clever' code at all. It is just much easier to understand.
Going offtopic here; but this is exactly the problem. There is a cronjob that restarts nginx after a certbot rerun. This makes at least three assumptions, all of which will fail at some point:

1. certbot does not need to stop nginx to renew a cert (some modes do).

2. the certbot run succeeded (all certs have been renewed, no network issues, etc)
3. all certs are written correctly so that nginx config is valid (can reach and parse the certs)

In this particular case, for some reason, one of the 7 sites hosted here had a misconfigured DNS, letsencrypt servers could not reach it, certbot failed, no nginx restart was attempted. This case falls in #1, fixable by force-reloading nginx every day after certbot run regardless of whether a cert has been renewed.

All solutions with nginx are cludges like that. Don't get me wrong: certbot/letsencrypt is miles ahead of automation before they came along (I've built en ran several hosting companies, certs automation is a disgrace), but it remains hacky, cludgy and therefore unstable and somewhat unreliable.
Don't know whether it's intentional but there seems to be a 20 character limit on the username length currently
nobody will fund a technology like Libra, owned by Facebook, in fact they already failed before

the main point is that Bitcoin is decentralized, there are many nodes in China, Iran, etc. that is why it has so much value
Right -- if you assign everyone on Earth a 33-bit number, the questions would just be "what is the bit at position i"?

It seems impossible for any question to be replaced with an interpretable meaning.
It should actually be a banking service and it should be portable between banks. There should be a banking standard for this.
Taking that argument to its extreme, if someone hands you a gun and says "shoot this person for $100 or I'll do it myself", whether you do the shooting has "ultimately the same effect" of that person dying. Still, most people wouldn't.
Might have mixed up Chime & IVS a bit.

To clarify, the 4-5s delay I'm talking about is for IVS, which is a live streaming solution, and doesn't have anything to do with video chat.
It has a RTMP input on which you send a video stream, re-encodes it and then distribute it as an HLS stream.
And getting sub 5s latency on an HLS stream is pretty fast.

I brought up Chime and video chat mostly as an example on how AWS is pushing for RTMP to connect those services.
There's now an official Cloudflare Wordpress plugin that makes sites hosted this way incredibly fast.

In the confidence it caches the HTML, and the plugin triggers a CDN purge when the HTML changes

Coupled with Cloudflare's standards support (TLS 1.2, H2, H3), and their image optimisation services it's really great for performance.

Just got to remember to disable many of the WP 'speed optimisation' plugins that may be installed as they actually can cause more speed issues.
I'm from Detroit.
That sounds miserable. I think, as a reviewer, it's important to keep in mind that most problems have many solutions. You have to be flexible and work with the person that did the hard work of implementing it. Everyone messes up and lets a bug slip through every now and then. That's what multiple layers of thorough testing is for.

On my current team, I'm considered to be the most thorough code reviewer. Folk usually thank me rather than scorn me, though. Some are afraid to send me their PRs not because they fear my feedback, but because they think reviewing their code will take up too much of my time. Reviewing code thoroughly doesn't take much time at all, though, if you make it a habit. If it's a bug, I explain my concern and suggest a fix. If it's a style nit, I link to the relevant style guide section. If it's a suggestion or personal preference, I explicitly say that, write out my rationale, then offer to chat more. If it's a weak suggestion, I tell them right off the bat that I'm fine either way. If it's a strong suggestion, I try to give them an "early out" by suggesting they simply add a // TODO comment. I'll let a coworker get away with murder as long as they leave a TODO comment.

For new team members that send me a PR for the first time, I typically send a message at the start describing what they should expect. That helps a lot, because everyone's first few PRs are going to be rough until they've gotten up to speed on the existing team's expectations.

I will say that there are some engineers that just don't take technical feedback well. When they join an existing team, they can be stubborn and refuse to adapt to the established culture. Instead, they either misinterpret criticism as personal attacks, or get frustrated and insist that the team conform to their preferences right off the bat. Team culture can and should evolve over time, but it requires respect and understanding of the status quo. It's possible for an open minded engineer to join a team, embrace its current culture, then radically change it all over the course of a few months. It's possible for a close minded engineer to not get more than a dozen PRs approved over the course of a year. Not to say that such engineers are good or bad one way or another, but rather folk should seek out projects that are compatible with their personality.
Yeah, I’m not doing a great job of explaining it but that’s more or less how it works. I think the way it actually happens is that the banana guy pays $499.50 and gets his bananas back, but that’s effectively the same thing. Also there are administrative costs and the value of this ship is also involved in the calculation, but that’s a bit in the weeds.
I have written my own tool, StaticMarks[0]. I maintain my bookmarks in plain YAML files and generate a static web app on every change.

[0] https://darekkay.com/static-marks/
how is this widely adopted, think in the scale of Linux or Gimp.
Paperless edition: Redact ---> convert to image ---> convert to PDF ---> distribute.
As an ex-Googler who's done a fair bit of interviewing, my bar for "will I use this coding question" is to look at the problem statement, do a from-fresh implementation in a suitable language, and if it took me more than 7 minutes, it is not suitable for a 45-minute interview slot (I would expect the candidate to have a solution in ~20 minutes, then maybe 10 minutes of follow-up questions, then flip to "do you have any questions for me").

I thus gave the candidates roughly three times longer than I needed to solve the problem myself, which should pretty much account for the interview situation.
> Regexps are not great in general

…not great for sensitive data detection in general, of course. Hopefully clear from the context (ha!).
This is a dilemma that often rears its head (exemplified by the classic "42").

Intuitively difficult situations usually end up "conserving their difficulty." An easy solution means a difficult problem (hard to formulate the problem or the formalization of the problem is usually inapplicable). An easy problem usually means a difficult solution.
> Anyone in the market for an ultrabook will care.

My current ultrabook is 12 years old and falling apart, but the new Apple designs aren't even in the picture as replacements because they're simply not general-purpose computers. They are appliances.
Laravel Breeze – Authentication Scaffolding
Registration-Form for Austrian Covid-19 Bulk-Test Runs Google JavaScript Apps
The online-registration-form for the Austrian COVID-19 Bulk Testing runs Google ReCaptcha which intercepts (all?) keyboard and mouse events. The registration requires personal data such as the full home address and social insurance number.
(https://xn--sterreich-testet-lwb.at)
Should I be worried?
For stylistic reasons.

It looks less jarring when pixelated compared to being blackened out.
Not just what people want to write, but what they are actually ready to pay for. Despite the mobile revolution altering some equilibria at the hardware level, software-making is still fundamentally led by business requirements, by the capitalistic research for efficiency gains in money-making. This can be observed in the disconnect between educational software-making (scratch etc) and "real" software-making.
> I love how the assumption is always that confirmed covid death that were actually unrelated to covid are more frequent then covid death that were not confirmed.

There is no such assumption. Read my post again: millions and millions of people died from the common cold before 2020. The media never reported those deaths as 'common cold deaths', though, even though it would have made just as much sense as reporting 'Covid deaths' does.
> horrific conditions while incarcerated within a Bangkok prison after getting caught smuggling in heroin

good, that's how it should be. if there is no punishment, there is no reason for people to stop doing shit like this.
It’s not a bug, in this case. It depends on the behaviour the library is specified to handle, but if you ask me to remove a specific item from a list, and that item isn’t in the list, what should I do?

I can fail so you can catch it, or if you don’t catch it, you’ll at least see exactly what went wrong. You expected the item to be in the list and it wasn’t. Your preconditions were wrong from the beginning and you have an (unknown) bug in the code.

The alternative is that I can’t find the item and I silently suck it up and don’t notify you. If that’s the api we’ve all agreed on, that’s fine. It was on you to check for the thing in the list first and then remove it. But it’s a bit weird if you think about it - now you need to traverse the list twice. Once to check for the existence (and fail out yourself) and once to remove.
Great points, good article.
What Happened to India's National AI Strategy? (Asia AI News)
Can only apologise. As a Brit, I'm ashamed not to have caught the sarcasm.
If you want something practical / simpler, have a look at https://www.youtube.com/user/MusicTheoryForGuitar (it's guitar-oriented, but contains general content) - they're not in a specific order so you'll have to pick and choose your topics. It's a bit better than a book, because you'll hear the examples in most cases too. Then you could go to more advanced ones like 12tone or Adam Neely's Q&As.
Twitter is a truly terrible blogging platform.

- Me, 2020
Well they could be marginally interpretable, but yes they'd all still feel really artificial, extrinsic, and prone to change.

You could for example, have each of those questions be a series of geographical questions that eventually narrow down to a single point in space (you'll need to include z-axis questions as well). But the geographical regions cut out by each question will be insanely artificial.

Intuitively "satisfying" questions would probably require intrinsic questions, i.e. ones that could pick out individuals from the entire sea of hypothetical humans, living or dead, real or imagined.
IMO harder to initially acquire but easier to grok at scale. Imagine combing through the behavior of blocks of code with conditionals in a larger system.
I'm arguing that we should use asserts or similar defensive coding mechanisms to ensure that preconditions are met instead of merrily continuing to run our program with cascading error effects.
> Patrick McKenzie wrote a blog post called “Identity Theft, Credit Reports, and You."

This one mentioned in the article is one of the best blog posts ever written, IMHO. I re-discover and re-read it every ~2 years.
What's your take on how everything works these days?

Do you miss p2p?

Do you think we could ever get back to it?
> I think, often, those folks solve problems by adding more code.

Indeed I think this is a big component in differences in how many lines someone is adding. Some people solve problems by copying code and them modifying it, while others try to come up with general solutions to remove duplication. It's two different styles, both with their advantages and disadvantages. I think duplicating gets you to an initial prototype more quickly, while general solutions are more maintainable as you only have to fix a bug at one position.
Jesus this explains so many intermittent issues I've been having over the last week.
Of course Bitcoin was ideal for this but it went off the rails for the banking the unbanked dream when it refused to scale from a blistering 7 transactions per second and the associated high fees.

You can check any bitcoin dashboard (such as https://bitbo.io); the current transaction fee is 1 satoshi/vByte for a transaction. The average bitcoin transaction is ~250 bytes. 1 satoshi = $0.00019273. A transaction that can wait an hour costs about $0.05.

The "bitcoin doesn't scale" thing really isn't a thing. Lyn Alden addresses this in her "7 Misconceptions about Bitcoin" article [1]:

"In other words, suppose that the Bitcoin network is limited to 250 transactions per minute, which is low. Those transactions could average $100 or $1 million, or any number. If they average $100 each, it means only $25,000 in transaction value is performed per minute. If they average $1 million each, it means $250 million in transaction value is performed per minute. If Bitcoin grows in use as a store of value, the transaction fees and inherent limitations prioritize the largest and most important transactions; the major settlement transactions.

Additional layers built on top of Bitcoin can do an arbitrary number of transactions per minute, and settle them with batches on the actual Bitcoin blockchain. This is similar to how consumer layers like Visa or Paypal can process an arbitrary number of transactions per minute, while the banks behind the scenes settle with larger transactions less frequently."

Lightning Network is a layer 2 protocol on top of bitcoin; transactions settle in seconds and the fees are tiny—about 1 satoshi—(a fraction of a penny) per hop. Not only are they cheap, they're private as Lightning runs over Tor.

The UI/UX of the current crop of Bitcoin/lightning wallets for iOS and Android, such as BlueWallet (https://bluewallet.io) is quite good.

[1]: https://www.lynalden.com/misconceptions-about-bitcoin/
Maas investigates Hosaka.
What useful information could solid color and random text leak even if depixelized? I assume the average solid color is just so the new pixelized region doesn't stand out against the rest of the non-pixelized ones, being an average color.

Applying it to an HN comment the result would be a solid average of #F6F6EF (beige background) and #290027 (text), so a solid darker beige with some random black text over, all pixelized. How can any of this be used to recover the original text?
This data is also be highly unreliable. Some students might connect remotely to devices through labs or a dorms. I did that very often while I was in university.

That said, the obsessive desire for surveillance should be stopped. Best day to start with that would be yesterday. People are getting crazy, which reduces overall security.
I know I've been testy with a coworker or junior before but its so counter productive to have a workplace with fear. Process can lead to trust and confidence so I try to focus on identifying and improving that (as well as mentoring around risky patterns and such.) Test, reviews, tooling etc. If simple mistakes are effecting the team, its really a process failure.

Fear driven development is toxic.
It was ages ago, but I did see that you could install just the ChromeOS shell as a session for other distros. If its still possible, it could be an option for people not wanting full fat Google OS
If you want systemd integration, use podman. It has a docker compatible CLI and runs OCI images just like docker but unlike docker it runs daemonless and has systemd integration
I think the short answer is nomenclature. Much of what makes music theory difficult is that the terms and notation systems have built up over centuries, and they come from musicians who were concerned with what's useful, not from programmers who understood the math. So pretty much everything has nine different names, and pretty much every term gets used to mean nine different things.

That said, for modes, AFAIK the names are all 100% arbitrary and used for historic reasons. For scales with varying numbers of modes, the first thing that jumps to mind is that some scales have modes that are identical to the scale, or to other modes, so references probably leave them out (e.g. consider the modes of the whole tone scale!). But there's probably also cases where this or that mode might get omitted because it whoever wrote the authoritative textbook about that scale thought it sounded awful, or felt it shouldn't be considered a mode for whatever reason.

There could be other stuff going on I don't know about - when I was learning this stuff I ignored big swaths of material that didn't seem useful for programmatic music.
I post online in very rare occasions, and this is one.

Dang, you deserve an heartfelt thank you for keeping healthy this community.

In the course of some years hn has become gradually my main source of news and many times the comments are actually more interesting than the story itself!

Considering the present state of the web, this is almost a miracle.

There is no place like home: thanks to your efforts hn is a safe place for me.
I guess that's how we get to see videos like this one: https://www.youtube.com/watch?v=dQ983bvP5YU
Or Adobe XD?