skysight-inc/HackerNews huggingface dataset:
For years, the bane of my existence was always lodash. Import one tiny utility and it brings along 15 of its closest friends. You can't get away from it. It was built so incredibly modularly, that it has to import a bunch of other things. Now most folks will quickly rush to its defense and tell you that Webpack should be able to tree-shake it well enough. My actual experience is that it was a tremendous waste of my customers' bandwidth. Seeing LoDash as a dependency of anything I use is an immediate NOPE for me. I've yet to see anything it provides that I couldn't just do myself.

It's an unpopular opinion for some silly reason. It's like when Guava or Apache Commons was included on every single Java project in the 2010s. "It's just so much easier to use a well-tested library". That line of thinking is what got us here.
Quick note: It's still classified as an "abortion" even when the fetus is dead. An abortion is an abortion, regardless of the status of the fetus.

It's why you will hear of mothers suffering and dying from sepsis due to a dead baby rotting in their wombs.

That's one reason why it's not binary.
I mean the problem is not only poor people. It is that access start at 250k a year which is really hard to get even in tech.

The reason it is harder in tech to get funding for these good ideas that could be profitable has multiple factors

1. As pointed, decoupling of relationship between entrepreneurs and "old money". This could be rebuilt even a the local government level with reach out actions

2. The untangibility of tech assets make banks loans near impossible to get

3. People cannot afford the risk. Better safety net would help. Obamacare was a good first step. Far more are needed.

4. The winner take all model has failed to generate profit. It generated capital returns but as pointed out by OP, pretty bad one. But it needed a lot of capital and LPs had a lot of money to throw around. The current inflation and folding back to Value investment will help. But we need to make the point.

5. The rise of passive investing has reduced the amount of money available to these kind of "semi anateur small rounds". The return to a less bullish market may help.

6. Housing. A lot of money and security rn for young people is sinked in rent

7. O'Reilly had amazing result with Indie.vc. The LPs refused to invest. There is a story that need to be told more. We need dozens of people banging the drum on this.

In the end... i don't have a solution sadly. We need a return to fundamentals to make the story of these models work. Focus on real possible profit and not some "we will control the world". FAANG are the exception. Not the rule. LP need to realise that.
I don't write C at all and the *++argv thing is obvious to me?
Look at the pointer of argv, then look at its sibling?
IMO that's not a good replacement (and I'm definitely in search of one!):

- You lose all asynchronous aspects to work.

- Screensharing is basically one screen at a time and usually "zoomed in", not representing your actual screen. You can't sit side by side and compare laptops. You lose a lot of those subtleties about how you physically do the work.

- Open audio is, I wager, very atypical. For me, it's almost a faux pas.

- This can add up to a lot of lost time for senior devs, so it's going to be avoided. Meaning you'll need to push uphill to make it happen.
Sad news. I've been waiting for a chin-less upgrade for a while, it made for an amazing gaming/music device, and also a cheap high-quality touch screen remote for random hacks.
> You can do this in things like Java too with interfaces if you can tolerate openness

Java supports sealed interfaces now, so this is not true anymore.
You’re not expressing what you mean by %..
I’m all against these packages, but in Ruby we have a good standard library.
one of these will finally stick, and more people will be able to build apps
Can you please source this? A react project can be so many things...do you mean create react app? A custom react app?
Bezos has zero control or sway in any editorial decision made by the newsroom.
Reminds me of talking to a VC who said that one of his investments 'turning into a $20MM company is the WORST outcome'.

The reasoning was that if the company just tanked, he had no ongoing issues, it was gone. Now, he still has his time & resources occupied by an ongoing company, even if minimally, it's a distraction...
I feel like "Note the Precision" is one that I most see missed.

Partially, this is on engineers. They'll say "That'll take 36 days" and not realize that they're implying a higher level of specificity than they intend.

Partially, this is on consumers of estimates (managers, etc). They'll hear "It'll be about 36 days, but that's just a super rough estimate, we haven't planned it out yet, it could be way more..." but they stopped listening and wrote down "estimate: 36 days."

My current eng team has fixated on two distinct levels of eng estimates. The first is super high level: "minutes to hours", "hours to days," "days to weeks", "weeks to months," or "months to quarters." The second is a number of hours. We give out the high-level estimates freely - they're super helpful for project planning. We give out the second number only when we have a pretty solid plan with estimated tickets.

It's worked pretty well because engineers can always be clear on which estimation type is called for. It's also helpful because non-engineers can get used to hearing the high-level estimates pretty quickly and know to treat them as super vague.

* We actually deliver all hour estimates as 30/60/90 estimates: "we're 30% sure it'll be done in 36 hours, 60% sure it'll be done in 50 hours, and 90% sure it'll be done in 80 hours". There's still a tendency of people to just use the 60% estimate as "The Estimate," but it's better than nothing.
4-5 years ago (when the popularity of node was skyrocketing but es6 was still relatively new) I remember some people arguing passionately that it was good to maximize code reuse, i.e. better to pull in a package with one utility than to write 5 lines of code in your own application. I think it was mainly a symptom of the gaping holes in javascript's standard library... thankfully that attitude seems to have mostly died off.
>"After those modems were knocked offline it wasn't like you unplug them and plug them back in and reboot and they come back," the U.S. National Security Agency's Director.

"They were down and down hard; they had to go back to the factory to be swapped out."
Discipline, leadership, organization, and, most of all: coherency between developers.

Most orgs do not have these things - especially not at the level of the Linux team. Also the motives of OSS are completely different than that of your typical business - I personally think this keeps OSS team coherent/productive for far longer than your typical corp can.
truly... those are just modulo operations
You mean "duplicate"?
Oil Giants Sell Dirty Wells to Buyers with Looser Climate Goals, Study Finds
You don't need it as much or have that much problems if you make a profit.

And sorry but as upper middle class, my family cannot fund 500k. 100k max. And young people do not have a home.

Welcome to the real world.
The point is that low participation is a symptom of pointless poorly organized meetings (often that should have been emails), not lack of engagement. The rudeness of it is on the part of the organizer not the attendee.
At risk of criticism, I'll bite. I used to think this way and include a lot of small dependencies in most projects I worked on.

The thinking was as follows: Of course you could just copy the code, but then that increases LOC in my codebase that I'm responsible for. More code is more work. Lines in a dependency are the responsibility of someone else. If there's a bug, even in a small function, the community can identify it and fix it. I can get new features I might not have known I needed. I can benefit from all of these fixes indefinitely into the future without ever having to have any mental overhead about that code. So can everyone else; it's good to maximize code reuse.

I don't think I've ever used something that could be an obvious one-liner like `isOdd` but for lots of only slightly more complex stuff like left-pad, email format validation, GPS coordinate math functions -- all stuff that's really less than 30 lines -- it was really nice to just not have to think about the implementation details of that and get back to solving your problem. I could have reviewed the code or written it myself but it's just more work when remaining at a high level `leftPad()` call let's me stay focused on my original task.

That said, I've since realized I was wrong of course. Trying to maintain projects that haven't been touched in more than a year led to hours of fixing dependency issues. We switched to using dependabot, which is better, but just makes it obvious how much work it actually is to keep dependencies up to date week-to-week. Then there's all of the security issues. These days, for small packages, I advocate for reviewing the code from these packages, ensuring we understand it, and then copying it in directly with a comment for attribution. We generally try to keep dependencies low; still more than in other languages but at least some thoughtfulness about whether it's "worth it". I think a lot of the community has shifted similarly, but there's still a lot of older projects with older dependencies.
You're either trolling or completely clueless. I suspect the former is more likely but I'll try to give you the benefit of the doubt.

> You'd be dead in a social society because as a lone, greedy individual …

You're obviously reading way more into my comment than I actually wrote, which says more about you than me. I am 100% in support of groups working together voluntarily and looking out for each other. The system you advocated for is not that, and opposing it does not make one "lone" or "greedy".

> … you're weaker than a group where the strong care for the weak.

Imposing a "choice" of compulsory payments or eviction is not the strong caring for the weak, but rather the strong preying upon the weak.

> … the parts you didn't answer to speak for themselves.

I didn't address the rest of your prior comment because it wasn't worth a response. But since you insist:

> Don't you pay for taxes or Government services too? This is how a civilized society works.

Civilized society persists despite taxes, not because of them. Theft is not civilized, and treating it as legitimate is corrosive to any civilized society.

> What do you expect people to do which can't afford to pay their health bills because they've been unlucky or something like that? Are they supposed to just die?

Obviously they aren't supposed to just die. That question was not asked in good faith. Taking other people's stuff isn't the answer either; the products of their labor are not for you to spend. People are expected work to provide for themselves and to plan ahead for the future, setting aside a portion of the surplus during good times to sustain them through the bad times. Working together with others makes this much easier but it is first and foremost an individual responsibility. For the truly unlucky cases there is plenty of honest, actually-voluntary charity to go around.
> In Factorio I just let things buffer on belts and eyeballed things as I went along.

Same. I'm surprised how many people talk about spreadsheets with Factorio.

I cover a resource patch with miners, then keep building smelters until I end up with an idle one at the end of the line. When I discovered a new item I'd need to produce, I'd just built a small line of assemblers and see what my output looked like, and go back to fix any supply constraints.

Was it optimal? Almost certainly not. But I definitely enjoyed not playing it as a spreadsheet.
That's why cell phones bill aren't accepted as utility bills, for many cases. Electric, water, sewer -- these things have a physical connection, and that's what they want to see.
Very cool. I became fascinated with bells after watching this [0] documentary on how they are made a few years ago (it's in German, but that hardly matters, just watching the process is extremely interesting).

The whole process is a combination of extreme sophistication and extremely simple tools and materials, something that has become quite rare nowadays. And despite an exact calculation of the bell shape and thousands of years of trial and error, tradition, and experience (the foundry in the video has been owned by the same family for 300 years), the cast is still highly dangerous and it still regularly happens that the bell just doesn't come out right and cannot be saved - months of work for nothing.

I think that explains why on the day of the cast (which is just 1 or 2 times per year), everyone involved is extremely nervous. The bell founder and the customer all join in prayer, and the cast traditionally starts with "in God's name" [1].

[0] https://www.youtube.com/watch?v=OQ8ZZV5UjcI

[1] https://youtu.be/OQ8ZZV5UjcI?t=1918
That mug-tapping demonstration in the "Doublets or warble in bells" page [0] is neat! I'll be looking for an opportunity to show that to someone, ask why they think it happens, explain pedantically, and yell "Science!"

[0] https://www.hibberts.co.uk/doublets-or-warble-in-bells/
I recommend not.
No single piece won the award. A collection of videos, photos, texts, graphics, and other things did it.
> Yep I remember how everyone thought COVID would lead to a depression.

I don't think we are in the clear already. Just take a look at the markets right now.
PowerShell does this too, at least for URLs. That said, it’s a true pain in the ass when it kicks in incorrectly, which unfortunately does happen.
That's certainly one way to use YouTube. It sounds pretty much like cable TV (but with a very low entry cost for producers).

Very often a channel has a really interesting video that I like, but the other 250 videos are 'junk' to me. Subscribing based on that single video would not give me good quality recommendations at all.

I enjoy discovering new videos, channels and topics, not just watching the same people or staying within a bubble of my own making. That's where a recommendation engine is supposed to shine, not fail miserably as it currently does. I always assumed this is how the majority of people use (used?) the platform.
An interesting podcast on bells form Planet Money:

When you've got two companies down the road from each other making the same thing, you can almost guess the history. Originally there was just one company, but something happened. Maybe someone got angry, somebody left, and they started a second business, a competitor.

Today on the show, the rivalry between two companies that make nearly all the world's handbells. And how they eventually made peace.

https://www.npr.org/2021/12/23/1067333584/bell-wars-classic
But I have an impression that Common Lisp doesn't have a type system, whereas this languages strives to have all "levels" of it's metaprogramming typed, so it's not like this language doesn't have any novelty.
Thank you for kind words man, I appreciate it a lot
80-1 shot Rich Strike races to upset in Kentucky Derby
This is exactly what OP was talking about. Ironic
They do it for much less. See Waco and Ruby Ridge.
No matter what your stance is on many issues, the legislative branch has spent the last two decades trying to do the least amount of work possible. Executive Orders and judicial decisions have taken over from laws actually being passed, while the legislature concerns themselves with budget resolutions and new national holidays.
I think the type of industry here matters.

A big chunk of the classic Middelstand is something physical, not knowledge work.

And startups turn that effect up to 11. Either it works or it doesn't. It is by its nature not conducive to middle ground.
Right, it should be "isUserInputEven" /s
So is every piece of large software a 'special case'? Besides the Linux Kernel, there's every other OS ever written, office tools, browsers, video games, all sorts of SaaS apps. The idea that microservices solve some problem in that space is bogus.
For literally centuries European bell tuning was all done by rule of thumb, with results varying from to sublime to abysmal. It was all finally figured out by Canon Simpson in 1895/6 who described the relationship between the 5 main components of a bell's strike note - the hum, prime, tierce, quint and nominal.

https://www.hibberts.co.uk/building-a-bell-sound/
This post is describing a structural issue on the funding side of new ventures: -

- bootstrapping is very hard

- traditional credit/loans aren't structured well for the "mid" type risks of starting software businesses (not much collateral)

- and on the VC side there is much less opportunity for the Unicorn 1 in 10 exits.

Tackling this problem are two funds that I didn't see mentioned in either the article or the comments so far: TinySeed and Calm Fund.

https://tinyseed.com/thesis

https://calmfund.com/shared-earnings-agreement

Broadly both invest much less than a traditional VC would and are compensated differently. The details are different (and matter) between the two but it's more along the lines of profit sharing than looking for big exits.
Have you ever questioned if "pro-life" was merely propaganda by the religious elite to enforce a certain lifestyle that gives them control over people?

Ex: "Right to life" disguised as "the obligation of people to live the lifestyle we want to force them to live"?

Fundamentally, the pro-choice side of the aisle is the side of individual sovereignty and freedom. That includes preserving your right to live a more traditional, conservative life if that's what you so choose. I'm personally of the opinion that many, if not most, women when given sufficient information and life experience, would choose the more traditional, motherhood/housewife lifestyle.

Conversely, the pro-life side of the aisle is one of coercion and slavery. It's the side that attempts to force people (specifically women in this case) to serve the role that the conservative elite want them to serve, regardless of whether or not they consent to it.

In my opinion, the pro-life/anti-abortion ideology is fundamentally un-American, undemocratic, and has no place in a free and open society that values individual sovereignty.
I wonder if anyone who wants to bring back the monolith has ever worked on a true large monolithic codebase? Not something that's like 5-10k lines of code excluding frameworks, but monsters that are 100k+. Where test suites take an hour to run end-to-end and you've got 50+ devs all issuing pull requests in the same codebase? I feel like webapps usually have a sweet spot in terms of size and logical reach. This whiplash hype cycle of "X" and "anti-X" just exposes the ever lingering problem of letting blog posts on HN determine your architecture decisions.
I have this exact problem on YouTube and spotify.
> JSON Patch is not REST. It is not representational state.

This is a perfectly reasonable take, although it fits well in systems otherwise generally more inclined to use HTTP semantics. I know that’s not REST, but it’s certainly easier to reason about and clearly document (eg OpenAPI) than its RPC analogues.

> But it's also not the way any sane person has ever done RPC over HTTP.

Why not?

Aside: I’ve also used it as a format for internal calls and change tracking. It’s surely not ideal, but it was already in the service and trivial to repurpose. Turned out to be an extremely lucky decision, as it also became a crucial tool for forensic analysis in a major recovery effort.

> I work in an industry of idiots.

You could just… not be a jerk. You have that option.
I do think there are valid arguments in favor of in-office work, but "empty office space" and "office rent cost" are not valid. An old employer of mine had a company car that got shared when people had to go to remote sites for same-day work. That wasn't getting passed around during COVID just because they were paying for it, it just sat there unused.

The cost in particular is just a sunk cost fallacy. You're paying for the office regardless, so because of that you're going to force people to pay out of pocket for gas and other incidentals just so they can sit there and (at least for most software engineers) be less productive? And you've also just increased your own costs because you probably could have left the lights and HVAC off? Nonsense.
The iPod touch was so great for me as a kid, it provided an accessible (read - cheap) platform I could plug into a Mac and deploy iOS apps to at a young age.

Now there's really no reason to keep it around, as you can get an off-contract used iPhone that is better in every dimension for less money. Still feel a bit sad to see it leave.
How about when it’s viable outside the womb, which is earlier in the western world and later elsewhere (given the effort required to deal with preemies). Before this time, it’s a cellular construct. And, similarly, I see the commandment as thou shall not kill. There’s no asterisk that I’ve seen, so people are bending a commandment as they wish to have capital punishment. Various quotes in the New Testament about judging and vengeance suggest against capital punishment as well.

Women aren’t brood mares at the beck and call of others. There is no right to inflict one’s progeny on another.

And, if the unborn are so vital, then they should be protected before and after birth, possibly until they’re an adult. Don’t see anybody saying that they have to provide medical care to the mother and unborn child. Or, are others allowed to kill the child (pr permanently cripple it) just not the mother?
You're right, I confused it with USDT. Sorry!
The only remaining dedicated bell foundry in the UK is in Loughborough - https://taylorbells.co.uk/ You can visit :-)
So long as the fetus requires the woman's body to survive, let alone come to term, it absolutely has to do with the woman's body. The fetus can also kill the woman whose body it's inhabiting.

Not considering the woman's point of view is treating her as if she's nothing more than an incubator, which comes back to "enslaving or murdering women".

And flushing her body of a fetus (or an embryo) is absolutely an action a woman may take upon her own body.