skysight-inc/HackerNews huggingface dataset:
Show HN: Songcards – Making digital music collectable again
Hi everyone,

This is something I have been working on for about a year now.

It's currently in open beta for musicians who want to sell their music as digital collectables.

I am very much open to feedback on the UI and UX as I want this to be a very consumer-friendly platform.

Looking forward to hearing your thoughts.

Cheers,
Chris
4. Educating yourself and not spreading horseshit.
Tailwind is not worse in this case either, and one might argue the “cascading” part of CSS is useless on such a local scope.

Also, tailwind gives you a pragmatic, limited selection of sizes, colors, etc, which is a very good basis for designing. (You shouldn’t be using a new px value for everything, they should come from a small custom-chosen set)
Has anyone managed to prove that an email address is not "reasonably sufficient to permit the service provider to contact the complaining party"?

I doubt it. I expect that Shopify doubts it, too.
I think that distros with “perfect mirror” DEs could make a big difference in bringing about TYotLD.

Lots of DEs are vaguely Windows-like, but this isn’t enough for non-technical users. It’s still different, and this adds enough friction that anybody who might’ve been interested quickly loses interest.

On the other hand, if a distro could be sold as “Windows but better” (using a modern Win10 like DE) or “like Windows in the good old days” (using a Win2K/XP/7 DE), it’s significantly more compelling. Add in something that’s like Proton but more intelligent and automatic (e.g. it sees you’re trying to install X version of MS Office, and so configures everything to work correctly automatically) and it’s even more interesting.

I know that Lindows used to be a thing, but it made a few critical errors: selling the product (opening them to litigation), not throughly duplicating the Windows desktop well enough, and the integrated WINE not being mature enough. All of that is avoidable now.
What’s a functional medical practitioner? Like a general practitioner or something?

It wouldn’t be that surprising for GP’s to notice a trend in an ad-hoc fashion, right? They have direct contact with the biggest dataset… patients.

Since they are respected professionals with licenses and training I’m sure there’s a way for the research community to hear from them and start systematizing their observations… or at least, I sure hope there is!
Incredible work. Even just aesthetically these images are beautiful.

Perhaps consider selling prints of some of these? Dozens of companies can white-label and turnkey sales and fulfillment from your site (if you’re interested, many of these companies position themselves toward wedding photographers), and I’m sure people would like to support you and your work.
Not really what you asked, but there are lots of tools for markdown to HTML, and lots of HTML parsers.
I think CSS does a good job at separating structure from presentation. Or what do you think was the original intention? Do you think Tailwind fixed the core issue with CSS?
> because they mean things that somebody used to these distinct categories will classify nature according to these boxes.

Very interesting. Could you explain this part in a little more detail?
Looks like you expose your git repo in your web root, rookie :)

geuis.com/.git/config
As a weapon . . system? . . it's hard not to gawk at this awesome assemblage of megadeath. Charles Stross gave the SLAM the honor of fighting Cthulhu in "A Colder War".

http://www.infinityplus.co.uk/stories/colderwar.htm

This also features another nuke engine, the ANP turbojet that would have been installed on the B-36 variant using it (test aircraft was, I believe, NB-36). Stross seems to think the ANP was open-cycle, but the (probably) most likely choice for that program would have been a closed-cycle nuclear turbojet. Any weight/efficiency loss would have been more than made up for by the . . the just general pain in the ass of having an open nuclear reaction fooshing onto the tarmac and everywhere else.
That's me. But for some projects I've had to switch back to yarn, because npm no longer works to install node_modules, and I don't really care why. Yarn works on those projects, npm does not. If npm works for a project, I use that, but there are some where yarn works and npm simply errors and quits.
How does this limit or prevent burnout?
Thank you for your comment! Too nice to read!
I don't understand this position, sorry. A bridge that would fail under expected conditions is straightforwardly not strong enough for its purpose?
Just from what I am using personally Figma and ChatGPT come to mind. The whole AI wave has nothing this side of the pond. Now the success of these AI tools is not yet guaranteed, so maybe I am wrong.
For the record -

There is no evidence what-so-ever that “performance trades with developer time”. 99% of the time, reasonable performance is a skill issue, not a developer time issue.

In actual fact, if you look at “clean abstractions” and other nonsense, you can see that higher developer time actually seems to equate to lower performance. As we all also know, the best indicator of bug count is lines of code, so adding in all these abstractions that adds lines of code not only make code slower, but also results in more bugs.

That is to say, all current evidence points to the exact opposite of their claim:

Higher dev time = lower performance and more bugs (assuming higher dev time is coming from trying to abstract)
This is exactly what I did. I even participated in the Yarn project a bit before it was fully open, but as npm 6 and 7 brought major speed improvements, workspaces, and overrides, I don't see the need for an alternate package manager anymore. As a library maintainer using the same package manager that most of my users do is a pretty big help.

I'll be very happy when npm's linked install strategy is stable so that there's less reason to use pnpm and we get dependency isolation in monorepos.
Does it not? what's the Pi missing? I assume truenas scale (the linux based one) would work better.
Wash Post: the quarter-zip = "office-guy uniform"; is this true in tech too?
The Washington Post Style section has an article today on "How the golf quarter-zip became the 2020s’ office-guy uniform" -- is this more of an East Coast thing or do we see this ringing true here in Silicon Valley too?
You see the same thing in other areas. In Mandarin Chinese, the sounds represented by "si" in English vision or "r" in English virile are the same sound.

An English speaker (like speakers of many other languages) would find this ridiculous, but it is true that the two sounds represent either side of a completely arbitrary threshold applied to a continuous phenomenon.
Expanded Silverado EV Production Delayed a Year as GM Cites 'Evolving EV Demand'
So that 99.999% percent of folks won't bother them.
My reactions were:

A video might be helpful - one video showing someone use it. The homepage was a bit overwhelming to me with all the gifs. I wasn't quite sure how to process it all. (I strongly agree with the HN commenter who suggested setting up a virtual co-working site for demo purposes - I think all virtual co-working tools should do that, and put some people from your team in those offices, would be a great way to learn from and interact with users, too.)

The wave felt a little 'Black Mirror' to me - like the way someone in a black mirror show would wave and exaggerate a gesture.

I saw the HN comment from someone saying it reminded them of Focusmate and that they thought it looked great, so I decided to check out the website again, and to write this comment, in the hopes that hearing what went through my mind when I saw the post / site might be helpful to you.

Best of luck with everything! The site does look very polished.
TL;DR: where performance actually matters and is a real competitive factor - things are fine - say same video games - if someone created same game giving half the fps on the same hardware, it is dead on arrival and gaming community will pour buckets of shit on it same day. Where it's not, it's not.
Adding new features is what most companies want. There isn't any correlation between software quality and success so companies don't bother.
But think of the lost economic efficiency!
Apparently according to Wikipedia it is a common gut flora.
At the end of the workday, an employee can assess their condition based on two parameters: how tired they are and how satisfied they are, on a scale from 1 to 10.

If the employee notes that the level of satisfaction during the working day is higher than the level of tiredness, then we consider that today did not contribute to their burnout.

If the employee notes that they are very tired but not satisfied, Ploito will count this as burnout (using a special formula).

The situation where the employee is maximally satisfied and maximally tired is also considered a minor burnout.

The employer or HR manager should pay maximum attention to this metric and analyze it comprehensively: what tasks the employee performs, how they comment on their fatigue, etc. In addition to satisfaction and tiredness ratings, the employee can write a comment with their impressions of the past day and mark completed tasks in their to-do list.

Thus, the employer can view the employee's reports and see the situation more clearly. For example, if an employee planned to finish a task but it turned out to be challenging and remained unfinished, the employee's comment might be "Struggled all day but made very little progress," along with the maximum tiredness rating and the minimum satisfaction rating.

This is the first signal to talk to the employee.
I think they are in everyone’s bodies as part of the flora so if you have too much of it like when there is an imbalance under maybe if you have weakened immune that could be a problem. Treat it as a probability like how often you can get hurt driving a car, and don’t worry about it
I'm pretty sure the international agreement on road signaling completely forbids any stop and go light from being on the same place, so that you can distinguish them without depending on any color.

But well, the US never follows any agreement it signs, so yeah, that happens.
weird, maybe you have to send them your blood, fingerprints, and a list of your favorite laundry detergents in order to get through?
At a data-centre scale they might still. Even marginal gains in efficiency translate to large savings in power consumption, heat management, and waste. If tech companies are properly taxed and regulated for these externalities, like say consuming billions of litres of fresh water during a drought in order to train a ML model, there would be a lot more pressure for this sort of efficiency.
It is so commonly the answer languages acquired the specific word "sabotage" to describe it.
1: https://erichartford.com/meet-samantha

2: ...Nope.
In Modern Greek, the voiced plosives of Ancient Greek, i.e. beta, delta and gamma, have become voiced fricatives, while the aspirated plosives of Ancient Greek have become voiceless fricatives.

To deal with the voiced plosives that are present in many modern loanwords, from languages like English, they had to develop ways to write them, using the existing letters of their alphabet, and the solution was to use digraphs, like "mp" for English "b".
That's what I mean by foamer logic, most of that American passenger rail stuff went defunct a hundred years ago. Fresno has 20mph vegetable trains and now a 20 mile long HSR viaduct to "revitalize" (blight) their pathetic downtown. There's no money for all the tunneling they want to do. (Take a look at the EIRs.)

The French came here and recommended a greenfield route, which is what they built in France, you can see the bypasses on google maps. They concluded that California is full of shit, and built HSR in Morocco instead.
Intentions are useless in this case. What matters are the incentives.
The implication is that self-editing of genes is much more common than we suspected?
It does, but it is pretty bad. Loads very slowly. Randomly disconnects. Just overall a janky experience.
Chrome Site Engagement Feature Leaks Frequently Visited Sites
the judgment here is funny, but there is no algorithmic way to validate "suspicion", is there? presumably it requires "judgement" -- so the idea that we can make a list of specific "suspicious behaviors" or a list of behaviors that cannot be considered suspicious is ridiculous
When the networking stack got worked out by Windows 98, everything was pretty smooth sailing. Until the drive-bys started. Then we moved to Windows NT and complexity, and albeit security, increased significantly. Windows XP was stable as fuck until the root kits started flowing. We moved through Vista, hopefully avoiding it all together until we landed at the fucking dream that was Windows 7. I would have stopped right there and been happy.

Then something got pushed over the cliff. Windows 10 and the UWP...like seriously WTF!? Satan's very own dumpster fire.
What this says to me is that a total rewrite is ALWAYS incentivized, and I consider that a good thing.
https://en.wikipedia.org/wiki/Blue%E2%80%93green_distinction...

Color in general can be subjective, even between people of the same culture and language group. There's an interesting experiment with color in this video around yellow lasers that might help get the idea across.

https://youtu.be/XQnmMjYHgcM
I think it is the consequence of reusability. We do not want to write everything from scratch understandably but the issue here is that every library you use, would not have exactly the amount of features that you need so there's lot of stuff that would be shipped regardless of how much of that reusable library you're using. I might be wrong on that part (maybe static linking does not work that way and does cherry pick portions)

Or at least that's how it works for some languages. You cannot have just a portion of a jar included as your dependency. It comes all or nothing.

Tree shaking etc does exist for the frontend world but I am not so sure how much efficient that is.
I've been using Roam (https://ro.am/) which is much less video focused (but still has video rooms). The helps those on our team who are camera shy. Plus it has a 2D overhead map of the different "floors" and "offices". See this for a screenshot: https://i.imgur.com/zFmedvl.png
You will be more effective if you deploy your words more carefully.

Loose coupling vs tight coupling has an established meaning ≈ “if a change to module X causes a failure in module Y, then we say X and Y are tightly coupled.” This has some “knock-on” effects that you are trying to gesture at, like, “If two modules are tightly coupled then because of that tight coupling we usually have to coordinate deployments between them both.” And then you're like “I can ship new CSS without having to coordinate a deployment of HTML, that must be loose coupling then!”

But this is a sloppy way to use the language, because in the one case you have one module, and in the other case you have two: there is no coupling in the Tailwind case because there is nothing to be coupled because it all ships as one module, then you construct a more modular approach, one with two modules in fact, and these modules are (depending on how you squint at it given that we are doing decorative programming and there are no explicit errors) in fact “tightly coupled”—the semantic HTML essentially provides a customized API which the CSS uses by hooking into; this is a common form of tight coupling in microservice deployments for example.[1]

So you are actually looking at, one module plus a static asset that defines a common language, vs. two modules that are tightly coupled, and declaring that the two modules are “more loosely coupled” and this is somewhat of a nonsense thing to say. Like I get what you were going for, I didn't write this as a top level complaint because I understand what you meant, but here in the thicket of comments I see that you are not communicating well with your interlocutor because of this sloppiness and language, you might want to pivot?

[1] This point about microservices is likely to outrage a random passerby, look I am sure that your microservices use RPCs against HTTP APIs in a way that doesn't cause you much grief in having to update multiple modules in one commit (if monorepo) or stage “topics” (Gerrit’s term) where you carefully have to merge 2 or 3 pull requests to different repositories all at the same time (if multi-repo). But even though your microservices are loosely coupled, I have worked on very similar architectures where we did have to stage topics and if you didn't then changes to service X would break service Y, “We’ll ship a new value for this enum, that requires changing the common schema repo, which requires updating every microservice that looks at that enum so that it doesn't have a deserialization failure ‘this is not an allowed value for that enum’ when the new values start rolling out, the ones that actually switch() or if() on that enum need to be updated to do the right thing, oh, I missed one because it relies on the contract that if enum == x then fieldA is set but if enum == y or z then fieldB is set but now when enum == q neither fieldA nor fieldB is set...” and I am happy that you haven't had these problems but yeah, some microservices are tightly coupled by this definition.
For a second I thought it was Magic Seaweed 2. RIP.
This looks like a very well-designed and functional product. From an engineering standpoint, I genuinely applaud your work.

As someone who works remote, this seems like a nightmare and I hope my company never adopts anything like this.
:)

Some breeds have different drives.

Virtually none of them have innate drives to attack or harm humans, but for some, they can definitely enter what I will call almost akin to a fugue state where they revert to much more primal instincts.

For example the greyhounds are like this if you wake them from sleep. My first greyhound slept on my bed precisely once -- when I kicked her in my sleep in the middle of the night I got woken up by a dog clamped on my leg, fortunately through a comforter so there was no real damage. Within seconds she was incredibly apologetic. But, it's a known thing with that breed.

Dogs absolutely want to please their owners. Most of the training I've done as a dog owner is around communication to let my dog know A) what I want and B) that they did it right. For the vast majority of dog owners, if they are just careful with selection, it's not a huge amount of work to train yourself and your dog.
> If its not done its because there is no money in it. In fact the opposite

This bears repeating. It's the disease that has consumed software and is making all modern software the worst possible version of itself.

I think it's the VC funding model which has driven the industry this way. Startups get millions in funding, then it's a race to make enough money to pay back those investors which leads to this. The companies have to squeeze dollars from their app as fast as possible which means anything that doesn't have a ROI metric attached to it will not get a second of anyone's attention.
Thanks for translating. Hard to disagree with that take, but also hard to imagine someone being so angry that a mature market has matured.
I think the thing people are surprised by is that auto-complete searches count as defamation, not that Google didn't take them down.
Then they could also have used that technique without the patent system. What is the value in holding an idea hostage for 20 years?
Arguably Xi was a design-bloat. I mean - it was a research project. Nothing wrong with it, but the community got super-excited about it, ignoring ... well, the pragmatic reality. Any time it was mentioned it talked about efficiently editing > 1GB files. Super over-flexible plugin system design.

For a lean and pragmatic text editor look at Helix, Kakoune, even NeoVim or Emacs.
It's not just about being measurable, it's about being profitable. Capitalism results in efficient production, not efficient products, because it's only interested in extracting profit from the production system.

Cars were optimised only after external (oil) shocks were applied, and even then very unevenly (American cars continue to be very inefficient). In fact, inefficient products are often more profitable in practice, as customers have to replace them more often; the crappy iPhone cable that splits after a year means Apple can charge you again (and again) for its replacement. White goods now break more often, but they're built more cheaply so they can make per-unit profit higher than it would otherwise be. What matters is efficiency producing, not after-sale use.

Capitalism in software means churning out new automation as quickly as possible, letting consumers pick up the resulting waste of energy and time. The production chain gets more and more standardized and optimized: you can now swap React developers, or Kubernetes admins, like you can swap warehouse workers, with all that it entails in terms of salary pressure. Some of that automation is effectively self-justifying, in the same way accountants make accountancy terms obscure so they can justify their jobs; but that's about it. Everything else is about profit.
Which leafy greens are healthiest–and which might make you sick?
Probably not. In general, this sort of thing is buried in the often unchangeable microcode of an RF ASIC. (Which makes sense, after all, the vendor is selling an RF modem for a specific band/modulation capability - they don't expect it to change, certainly not after they've built/configured it.)

If that's the case (as is common), then there is really nothing to update, short of scraping off that chip or module and replacing the hardware.
I can't find it in the docs, so maybe someone here can answer:

Does this allow you to save your steps and "re-play" them on a different dataset?
They are green. Japanese people just call them blue (青). The colors we call green and blue are just ranges on a spectrum. Where you draw the line between them to call one green and the other blue is partially a matter of personal perception and maybe more a matter of culture but there is no absolute right answer.

I'm not sure if there's any connection to why Japanese tend to lean towards blue rather than green but the Japanese word for green, midori (緑) is linguistically different from most other colors. It doesn't have a true adjective form and is instead used as a noun or "adjectival noun". Does this difference create a subconscious aversion to it in the Japanese psyche? I really have no idea.
Oh the downvotes for asking questions…
Thank you for your comments! This is very valuable feedback. Now I’ll discuss it with the developer and designer!
A typology of Chinese sabers (2020)
If that really is a problem we can just still count it as a single company for the tax office. Or make it illegal for companies to own other companies. That would even encourage competition and break down monopolies! All things capitalism thinks are good things.