skysight-inc/HackerNews huggingface dataset:
I'm talking about the same skill you are. You (and many others) think that the third picture requires a lot of artistic skill. As far as I see, the third picture is a prototype with a lot of technical debt.

I don't think we can meet on common terms because our definitions of art are different. I do not subscribe to the opinion that art is about challenging our thinking. Instead, I consider good art to be about immersion. You do not have to convince yourself to like it. You do not feel the need to like it ironically. Yes, you can get used to it and it loses some of it's power, but the greatest art is the art that you can keep looking at (or listening to etc.) without feeling the need to justify it. (I cannot remember which philosopher I borrowed that idea from.)
Sounds like a good place to open a lithium & rare earths mine.
> his initial credited work being '2001: A Space Odyssey.'

It's amazing how derivative Star Wars appears after going back and watching 2001.

Similarly go back and watch Westworld (the movied) and see how it makes you feel about Terminator.
I've seen this often as well, typically some library will get flag by programs like snyk giving you a "high" score. The way snyk scores packages is completely asinine. It favors libraries that are constantly being updated compared to say some library that is feature complete and in maintenance mode. One way around this is to literally pull all the source code and paste it into your repo.
Second developer that touched it might be new to the company, or in a deadline, you never know
Kafka special cases the "tail" of a partition - the open log segment (i.e., the very end of the partition that's still being written too) is never evicted, and log segments closer to the tail are evicted last, IIRC.

It definitely prioritises tail consumption over read from 0.
You should get them some full body Kevlar and chain mail as well. There are more shootings and stabbings than bicycle head injuries. Just to be safe.
> The people arguing for decreased protection are doing it with no intention of starting businesses

Is the only possible social value of creative work the generation of a business? Maybe some things are simply better as a universal social infrastructure-- the benefit is that it exists for other things to be built around it, rather than as a direct business.

> Most of these detractors want to create one-off art pieces for the fun of it. That doesn’t bring food to the table or build a long term foundation upon which more advanced works be built.

To me, the big benefit is to move creativity from "the artist with his unsullied vision" versus "iterative multiplayer development." It's a principle I'd love to see not just in software, but all creative endeavours.

Yes, no individual hobbyist is likely to be able to spit up a project with the scale and scope of Windows XP, but a thousand hobbyists, each working their own fixation and interests, can potentially take an existing product and add real value to it-- or, eventually ship-of-Thesus the whole thing into something fresh.

Maybe you've got someone fixated on the device driver so he can keep using his one specific printer, or a student who wants to do his Ph. D. thesis on scheduler technology Another person just wants to replace every use of the world "whitelist" in the code.. Some of this stuff will be self-indulgent "art projects" but others are motivated by real productive aims.

You can't stop them, but now you also get the opportunity to cherrypick it. A new value centre emerges in curation-- like the role a Linux distributor plays. People will support a strongly opinionated project like Debian or Clear Linux because they trust the choices they make in curating and packaging other people's work, even if you could manually assemble the same elements from scratch yourself. The curators can then bring on professional developers to ensure that their interests are represented in future development.
I did some research and Wikipedia pointed to the whole language method (https://en.m.wikipedia.org/wiki/Whole_language) as opposed to the phonics method (https://en.m.wikipedia.org/wiki/Phonics) which focus more on how words are composed from syllables.

As a non expert, my analysis would be reduced to :

- whole word would focus of growing the list of words you would be able to recognize.
- phonics focus on the link between speaking and reading, which I guess could build up self confidence for being more eloquent, and in my opinion would help with learning foreign languages.
I'm sure you know this story already, but nice example: https://gizmodo.com/one-mans-nearly-impossible-quest-to-make...
On the Suboptimality of Human Life
US 10 year bond rates are 3.1%.

The one time in history they have gone beyond 10% it took 2 years to go from 7.32% in Sep 1977 to reach 10% in October 1979, and then peak at 15% in 1981.

It's not impossible bonds will reach 10% again. But it seems unlikely, and it seems safe to think it would take 3+ years to get there.

https://www.macrotrends.net/2016/10-year-treasury-bond-rate-...
I think they were discussing rebalancing replicas when you increase partitions. Cruise Control is great here.
Commonly called a folksonomy.

Yeah, it's not, really. And thankfully.
This only works if all devices are PCIe 5, though. There are still a lot of PCIe 3 or even PCIe 2 devices that could make do with very few PCIe 5 lanes but need a lot of lanes regardless.
> it's what makes it possible to write a C compiler at all for those weird architectures.

Only if one is pedantic. There's no practical problem at all customizing C compiler semantics for weird architectures. After all, everybody did it for DOS C compilers.

> I even thought D might work but now I understand why it wouldn't

People do use it for embedded work. I don't know why you wouldn't think it would work.

> I wonder if you're aware of the standard sized type aliases int8_t, int16_t etc

I am. After all, I wrote stdint.h for Digital Mars C.

> and what's your opinion of them.

There are three of each:

typedef long int32_t;
typedef long int_least32_t;
typedef long int_fast32_t;

1. Too many choices. I have experience with what happens when programmers have too many choices, with the differences between them being slight, esoteric and likely not substantive. They blindly pick one.

2. People have endless trouble with C's implicit integral conversions. This makes it combinatorically much worse.

3. int32_t makes sense for the first hour. Then it become annoying, and looks ugly. `int` is much beter.

4. `int` is 32 bits anyway. No point in bothering with stdint.h.
What an absolutely absurd comment. It strikes me as fairly offensive to a lot of people to suggest that rules about maintaining your yard and not trashing your property are inherently associated with "whiteness".
Ask HN: Solo founders, what’s “stuff breaks while you're unavailable” strategy?
There is a current post with a similar title asking about your "get hit by a bus strategy" and I think the answers are missing the mark, so I'm posing a slightly different question.

There are times you are absolutely unavailable (sick, on a plane, off grid, dealing with a personal emergency, etc). What's your strategy when all hell breaks loose and you just can't step away.

In other words, being on call 24-7-365 is not realistic. Do you have a plan?
My stuff would end up being dormant or shutting down. I don't feel the need for continuity with my LLC nor my Android apps. If I'm dead, oh well. The Android apps are open source, so someone can recreate them.
I just posed a slightly different question here: https://news.ycombinator.com/item?id=31474258
Sounds like you may have dodged a Meta-bullet.

Congratulations!

I've always wondered about one thing -- with VR, your eye convergence distance is whatever the software wants it to be, whether that is something in your virtual hands, or something across the virtual yard. But your focus convergence distance is just millimeters away from your eyeballs.

But for the millennia that human beings have evolved, our convergence distance and our focus distance has always been the same. If it's in your hands, then the distance is about three feet, or whatever. If the object is in the yard, it might be thirty feet.

So, how do you deal with this problem in VR?
we're always listening
Giving away biometric data like this seems like a very poor trade-off compared to just pulling out your phone or card.

More secure? More hygienic? Come on...
You aren’t tracking the whole market. An index is a subset. Even total market indices have weightings which embed biases. And the whole game has been reverse engineered by charlatans to dump crap into rivers of blind money. If think capital offerings aren’t designed explicitly to target index inclusion criteria then you aren’t in on the joke.
I have accepted the chaos. Be one with the chaos of the universe.

I rarely delete email and files or close tabs. I come up with some inefficient but workable system to find what I need.
You can become a statistic just by walking outside.
> Crypto, by-in-large, is not predatory.

I disagree and believe crypto is by-in-large predatory. The crypto handbook seems to be:

1. create coin

2. promote coin and get people to 'invest' in it

3. move the 'invested' money ("rug pull") into your personal account

4. disappear or do it again

> there will always be people who don't value risk properly

This is true. But we cannot compare making a wrong call on the direction of highly regulated Microsoft stock with 'investing' our money with people who are almost certainly going to steal all of it with zero consequences.

> will affect your gambling experience

You call this gambling. But the crypto creators promote their coins as investments with 'exchanges' and so on.

Financial investments and gambling are both highly regulated industries but crypto is subject to regulations from neither.
It's your job and your career. Good luck with that choice.
What's the human right angle on me assigning the copyright of my work to the public domain?
Ask HN: Thoughts on the other 5-second rule?
The Other 5-Second Rule

> If it's something a person can't fix in a minute (food in teeth, shirt untucked, etc) then don't talk about it.
That's true. I should have included a proviso.
Printing a website & adding a $ on it, we are living in crazy times.
Exactly. It's also easy to demonstrate that if it changes we just change the code, duh!! Simple concrete code is far easier to change.
I think this could be a decent alternative to Isotope's filter & sort magical layouts:

https://github.com/metafizzy/isotope

It was so popular back in the day but hasn't received any recent updates.
Redwood materials is run by the co founder and former cto of Tesla, presumably formed to head off the point where if BEV volume manufacturing ever does take off at scale there is a fig leaf of 'recyclability'.

BEVs are extremely heavy and rely on lightweight hard to recycle plastic and alloy body components to lighten kerb weight. Tires produce far more pollution than 'tailpipes' (BEVs just move the pollution somewhere else of course, they are wonderful for affluent cities).
https://www.tiretechnologyinternational.com/news/regulations...

The other worrying aspect of BEV battery module recycling is fire risk- as the current generation of BEVs age we can expect to see more trapped energy thermal runaway events from faulty batteries.

I'd say we have a way to go solving these realities before increasing BEV volume manufacture - hybrid cars are the best solution IMO for the foreseeable future especially given the perilous state of western world electric grid reliability
The first example on the page is actually decent I think, visually showing the two elements swapping so you see where they moved to, but making it so automatic is going to be an irresistible temptation for many people.
The best thing you can do is leave the idea that you will time it correctly. Take profit when you are comfortable. Feetr provides stocks almost every day and, to me, the goal is compound interest.

The metrics are as they are because, right now[0], there are no better options to validate how Feetr performed. These values are, like you say, theoretical maximums and have not been matched by humans in almost a year. You get the top every so often but not consistently.

However, I wouldn't say that this makes the service less useful than people think. I have made 700% returns and this allowed me to quit my job and work on Feetr full time. Other beta testers have made more than their salary using this.

[0] As above, there will be an investment service offered at some point
That's a good summary of things to consider.

With that in mind, it seems pretty nice if a library can make simple animations much easier.

The demo shows some promising examples that tend to be common polish on, say, iOS. The simple sorting/delete ListView example is pretty nice compared to the instant changes with zero feedback it's compared to.

Meanwhile, web animations by hand can take quite a bit of thought even for basic things, like fiddling with CSS `transition` and ensuring your component lifecycle sees it through. Always ends up being a bit brittle, like having to duplicate CSS time durations with your JS components.

I'll have to play with it.
Where I live, they only prohibit keeping roosters, though there are restrictions on chickens as well I think -- though theres no enforcement. A couple of my neighbours have them (and they escape and wander around the scrub land behind my fence and make friends with the local brush turkeys, which I find cute and endearing). Its quite fun to live basically in the centre of Brisbane's city, but have chickens wandering around. But that's also part of what makes this place neat, in my opinion, while I'm a kilometre from the CBD, the townhouse I live in is in a suburb filled with old Queenslander houses, newer builds, townhouses and small apartment buildings.
I was stumped on how to integrate Postgres schemas + TypeScript types, so I visited HN, and this thread helped me move forward.

My project is a game, the client/server uses WebSocket rather than a normal REST API.

I have used Prisma, Knex, TypeORM. Seems to me that ideally, we would write types in TypeScript and have a DB schema generated from those, including automatic migrations based on schema diffing like Prisma. Then we only need to know TS, not another DSL.

We don't want to generate TS types from the DB because then we have no way of versioning the DB schema (except by writing SQL or DSL migrations).

I ended up finding https://deepkit.io/library/orm and I'm going to try it out. (Not associated with project)
Can you use Google Sheets? There a plethora of solutions to turn a Google Sheet into an API. The Google sheet will update automatically on it's own.
Biometrics have to be the biggest meme in security maybe behind anti-virus software.
> If something is used once, ignore any abstractions. If it's used twice, just copy it, it's better. If it's used 3 or more times, look at writing an abstraction...

That is a good rule of thumb, and I often follow it too. But it does take some discernment to recognize cases where something would benefit from an abstraction or some common code, even if it is only used twice.

I used to work for a company that imported airspace data from the FAA (the US Federal Aviation Administration) and other sources. The FAA has two main kinds of airspace: Class Airspace and Special Use Airspace.

The data files that describe these are rather complex, but about 90% of the format is common between the two. In particular, the geographical data is the same, and that's what takes the most code to process.

I noticed that each of these importers was about 3000 lines of C++ code and close to 1000 lines of protobuf (protocol buffer) definitions. As you may guess, about 90% of the code and protobufs were the same between the two.

It seemed clear that one was written first, and then copied and pasted and edited here and there to make the second. So when a bug had to be fixed, it had to be fixed both places.

There wasn't any good path toward refactoring this code to reduce the duplication. Most of the C++ code referenced the protobufs directly, and even if most of the data in one had the same names as in the other, you couldn't just interchange or combine them.

When I asked the author about this code duplication, they cited the same principle of "copy for two, refactor for three" that you and I approve of.

But this was a case where it was spectacularly misapplied.
Why SR and not the approx. 200kg heavier LR?
In D it is ridiculously simple:

byte = 8 bits
short = 16 bits
int = 32 bits
long = 64 bits

add `u` prefix for unsigned version

22 years of experience shows this works very, very well, and is very portable.

The only variable size is size_t and ptrdiff_t, but we're kinda stuck there for obvious reasons.

There have been some issues with printf formats mismatching when moving D code between systems, but we solved that by adding a diagnostic to the compiler to scan the printf format against the argument list and tell you how to fix the format.
With either an in-memory db or using zstd compressed ramdisks the limits are ridiculous.

Who needs durability anyway, right?
Another complaint I have is that if you look really close at most typefaces the letters and numbers seem to not just not come from the same typeface but not even from the same planet.
Thing is, cyclists don't need to rack up as many kilometers as drivists. If you're riding a bike, you probably live in an urban place and you need only bike short distances.
You can use money or housing as a fun collectible or you can use them for their intended purpose, exchanging goods and shelter. As far as I can tell we prioritize the former well above the latter. The concerns of the collectors override the basic needs of the poor.

When you consider that money is representing a claim to someone else's time then treating that person's time as a collectible forces helplessness onto that person. You run into the paradox that a person that is capable of helping themselves is banned from doing so, yet is simultaneously reprimanded for their forced upon helplessness by the very people that forced this helplessness upon them.
> Nonverbal autistic people are still quite rare. I know a few (actually, I know their parents, and, through them, their children). Tough gig.

Know a guy who’s son is non-verbal, definitely a tough gig.

My friend is highly creative as a writer, and definitely anal in terms of rewriting until a piece is perfect in word choice, tempo, etc. He struggled his entire life with close emotional connections, only after a divorce sought some introspective counseling which led to his understanding of where he sat on the spectrum. When he told me, it was like blinders were lifted and I spun back through dozens of interactions that we had had over the years and it was an *of course!* moment. Made perfect sense in hindsight.
> My next realization was that it doesn't matter if I have the right of way and am dead.

This is a good realization for others to have before it takes a near death experience to change the view.
Absolutely correct. Feetr doesn't invest on people's behalf at this point, it's purely stock discovery. The idea of showing the difference between the open price and the highest is that this is how much profit could've been made that day.

The concept that I try to push is to focus on compound interest. To start with a small amount and just keep rolling it over into (near) daily profits. Don't try to time the top, sell when you're comfortable.
I hate ORMs.

After days of fumbling in the dark you finally isolate the problematic query, post it like "guys I found it," and still nobody speaks up. So you hack the ORM to attach tracebacks as comments to each query, retest everything, and finally git-blame your way to somebody who owns that bit of code and they're always like "wait, the ORM did WHAT?"

I'd rather grep code for SQL any day.
Right so let’s have thousands of variations and none of them interchangeable. Great for the environment.

Now imagine if you can only fill up at an Exxon. Not because the fuel is different but because the pump nozzle size is different. Only a true libertarian capitalist would come up with such an idea.
I haven't been following the Node ecosystem closely. However Fastify is really interesting. Why choose Fastify over Koa? I've never understood why Koa gets so little love from the Node.js community.
A painted bicycle gutter is not dedication, it's lack of dedication from your local government.
Neat! I wonder how it compares to tiddlywiki? e.g. search doesn't seem to be supported at first glance...
> In one set of studies, participants answered three multiple-choice questions about their lives; half then saw their partner’s responses to the same questions and half did not. All participants were then told that their partner was trying to guess their own answers. Participants who saw their partner’s responses believed that this stranger understood them better than those who did not.

This seems perfectly rational to me. The participants thought their partners had a symmetrical role to them by the design of the experiment. So they assumed if they received information about their partners then their partners must also have received information about them. They are making a reasonable inference based on a false premise that they were deliberately misled into accepting.

Perhaps if I read more I would see the experimental design has been glossed over and it isn't as simple as this, but this is what stuck out to me.
Your main resource contention there would be network throughput, then broker CPU time in iowait if there's a lot of concurrent large disk reads happening on the same broker (although Kafka's optimised for sequential reads).

Partition count only limits concurrent consumption within a single consumer group. One consumer group won't impact another unless its consumers are doing sufficiently bad things to bottleneck the network or disk.
Agreed. Great read. Thanks OP!
I must say I am mildly amused that the author went to the effort to specify six SKUs based on size when the largest is only 10% larger than the smallest. And this approaches 0% as you add content to your wiki. But I always love seeing some blazing-fast web pages!
Are you sure this isn’t because of the tightened electrical tolerances for PCIe’s physical layer, not the protocol it’s self?
https://archive.ph/cvcFI
A human being's weight hitting the ground at 30 mph (already a generously high figure) is far less serious than a multi-ton vehicle hitting them at 30 mph (already a generously low figure).

So, yes, physics.
I don't like this authors approach. Always ask the question, but never add complexity because you assume you know the answer. If you have "multiple layers of indirection" that is "unused" because of paranoia that you might have to refactor your code, then you're doing it wrong. Write code such that you never have to be afraid to refactor it. That's not write code that never has to be refactored. In fact, refactor often and liberally. And if things break when you refactor, then that code is bad code. But don't add worthless layers of indirection because you write code that can't be tested, full of side effects, requiring entire components be rewritten from scratch, etc.

The top commenter says good code rarely needs to be changed. I think thats foolish. Good code is constantly changed, because its good enough it can be.
For example, a Server's:

- disk fails (ZFS with hot spares)

- power supply fails (each server has two)

- someone cut the power (there's another server)

---

Most issues will be caused by me, so the general answer is don't leave before testing.
America's Pager Giant
> In ordinary usage

Sounds like you are referring to a connotative value which is common to a subculture of English speakers. I learned to use the dictionary definition from sociology 101.