skysight-inc/HackerNews huggingface dataset:
Awesome summary, thanks and all good points.
Here is my quick list.

- Linux + GNU: My servers would never have been the same without them.

- Emacs: So many varied use cases over the years. I can type in Telugu (my mother tongue) and Devanagari so seamlessly ... bliss!

- LaTeX: From papers to books to presentations.

- Helix: A very recent discovery that replaced Vim for me in just a week!

- Kitty terminal: I no longer use GNU screen or tmux locally.

- Go, Ruby, Python: They have been paying my bills for so long.

- KDE: The other half of the Linux spirit!

- ffmpeg: Such a boon!

- Homebrew: So convenient.
why is it voted down? This is technically true.

People are polarized on the topic of communism vs. capitalism but the reality is these are just two different colors. Two different aspects, similar to solid or liquid.

When you treat it as a sport team you become biased. If you hate capitalism you become blind to how capitalism produces powerful economies like most of the western world. If you hate communism you become blind to how stories like this can benefit a community.

There are plenty of public goods that cannot thrive under pure capitalism. Grocery stores with razer thing margins are an example of this.
> Every templating language inevitably turns into a very poor programming language over time.

This realization is what initially sold me on React. I just wanted program and build abstractions with an actual programming language!
Can’t take an EV on a road trip. It would make it 3 times as long. And there are no convertible EVs. So I’ll think I’ll keep my oil burner which does about 12mpg, top down while I blast AC on my feet.
The first burst sounds like a grazing animal. Then definitely becomes very human sounding.
It makes a lot of sense to build turbines with a lower expected lifespan while the technology is still rapidly improving. Nobody wants to operate 30 year old 1MW turbines when 15MW turbines are available.
scrolling mindlessly. without watching any thing completely. hoping that I get some great fresh content.
What does it mean for your life in terms of doing things that require durable concentration? For example, driving a car? Can you do that without risking falling asleep?

It seems like such a cruel disease. I hope there will be better remedies ahead.
On the 60th or more shot is not a record, if you throw enough lead down range in the general aim, one will impact eventually.

Something like a 2km repeatable shot done with 338 lapua and 26" barrel high accuracy rifle is much more real world.
Dependency management is a real security concern. There’s no corruption there.

The root comment suggested that somehow this was a smear on FOSS, intended to sell more proprietary software. However, this doesn’t hold up, because FOSS components are widely used by all of the big proprietary software vendors in this space too.
> Yeah great convenience to miss part of the movie

Nobody said a feature implemented as a convenience to the user had to make things more convenient for the user. They're barely even related concepts.

https://chainsawsuit.krisstraub.com/20171207.shtml
> All the students with Linux boxes have some kind of problems, like the user was not a member of the dialout group or the group does not exist at all. I still prefer Linux, but no everything works "out of the box".

This (requiring elevated privileges) is a very niche thing, though (raw access to the serial port).
Anyone experience running Java/JVM apps on Fly?
Anything more expensive available for civilians is generally thermal or night vision, it's easy to spend $6k-8k on a scope with half the zoom but thermal 640x384 sensor capabilities.

People use $4000-9000 thermal scopes at much less zoom and much shorter ranges under 400 yards shooting feral hogs in Texas.
Do you mind sharing your Hammerspoon config?
> Mozilla should stop whining and focus on building a browser that regular non technical people also want to use.

This, they're right you know.

Mozilla has being whining for years despite living off of Google's money and even with that they are still complaining and more websites are continuing to require Chromium browsers over using Firefox for their sites as they know the site breaks with Firefox.

That's why little to no one is using it. Like when you have the choice of Linux distros, you have the many choices of Chromium browsers and it seems that Brave is the recommended one.
In addition to serverless meaning that you don’t have to worry about the compute layer, I take it to mean also:

• I don’t need to manage the infrastructure for each of the services I depend on
• My compute and other services are billed based on usage, not for being switched on
• Everything scales up as needed, and just as important, down to zero
If you have nine grand available on a visa card you can buy a Barrett m82a1 online right now, ship to local FFL, fill out a form, pick it up in a week or two.
Indeed.

I'd be interested if Wave Swell Energy have any plans to develop the idea more along the lines you've described, now they've somewhat proven the concept, or if they're planning on sticking with the current design, which would seem to have only niche use in remote areas that are underserved by grid supply, and suffer poor wind / solar viability for at least some part of the year. So probably nowhere.
The biggest unknown right now is how FERC 2222 is going to play out. It essentially allows consumer solar to be aggregated and sold on the wholesale markets. As aggregators come online and prices fluctuate there are going to be even more regulations as federal and state officials find flaws and gaps in how the system works.

I tend to lean toward battery storage as being the piece that will tip the scale. As more efficient and longer lasting batteries come online, grid ops will become a bit easier and some of the DER capacity that would typically be shed could be stored for later needs.
I’m proposing that cuts like this are unnecessary for companies this flush with cash. It’s an excuse to cut staff with some reason to point to for doing so.
Damn that guy has an annoying voice.
Oh fun! At my employer the "security team" misunderstands that criticality score and takes it as a "vulnerability score". Everything scoring high is a security risk, everything scoring low is secure.
> 2. Server serializes root component element to JSON

That's what I'm talking about.
Municipal-owned utilities and businesses have long existed, in many countries, of all political stripes.
>Then Putin cut the oil and gas supplies to the world

It was (most of) EU and US that decided to stop buying oil from Russia. Everyone else keep doing it. EU and US can do too, just don't want to.
The study presupposes everyone is going to drive in to the office every day. I haven't worked in an office since Mar of 2020. If I can help it, I'm going to stay remote. I'll need to charge my car at home, should I get an EV.
Yeah, more or less! This closes some paths and opens brand new ones, like more of the former and less of the latter. For example, let's consider this code.

void f(void) {
obj *a;
a = calloc(1, sizeof(a));
g(a);
}

void g(obj *o) {
if (o->callback) {
o->callback();
}
}

it's contrived for simplicity, but suppose obj had a function pointer in it and just after allocation the object is passed to another routine which does some work on the object and checks if the callback exists and calls it if it does. In a single threaded application, you would not be able to target the function pointer here because nothing interesting happens between calloc and the invocation since the if check will always fail due to it being zero'd from calloc.

Now, as you mention, if calloc didn't zero, an attacker could scribble over what they think will be the next allocated slot in the heap (either by targeting a partially used page or an entirely unused page that's just being kept in malloc's retainer) and write a value into the callback pointer field. Now when a new object is allocated there, we end up using the corrupted data and invoking the evil pointer, and the rest is history.

It's a bit of a weirder exploit path but honestly with how ridiculous UAF flows have gotten with modern mitigations on iOS, it's hardly the worst thing I've ever seen and I suspect someone will get decent mileage out of it
I think it's because despite the fact that programmers have to deal with complex problems, we fail to see complexity in a lot of things. So it's very easy to dismiss things or ideas as useless and apply cynicism to everything. For instance,when I started managing people, I thought that the journey from ' I don't know it' to ' I know it' is as simple as getting from A to B. So I was always very surprised when someone would come to me asking 'why is that?' or ' how do I do it?' or simply saying ' I wasn't trained on this' or ' nobody told me about it'. At first I was perplexed why people don't just read about the problem and they'll figure it out. But for a lot of people it's not from A to B. It's more like A to G to F to B to R to A and then to S. Or not even moving from A. Things like motivation, hunger for knowledge kicks in and so on.
I often sit in meetings with people that have very different backgrounds, positions and usually approach things differently. It's fascinating to see how some subjects get discussed and I end up seeing way more angles than I initially thought about.
> electrified. (they're close to 100% of people with access to electricity) Get a heatpump and move on, you say?

Yes, electrification is a solved problem. Look how quickly the US electrified rural America, and that’s when it was a new concept. For a more recent example of using known technology, look at how quickly China electrified from the 80s-00s.
Exactly, I was a bit undecided back in the day thinking React and Angular might be similarly valuable, and I don't remember if there was even Vue yet or not (I believe not yet). Angular had just split, and I had to help contracting for a company using Angular 1, and OH BOY the page was horizontal and most of the programming statements happened within those nightmarish ng-if, ng-repeat, ng-{please-kill-me-know}. I believe there were parts up to 350-400 columns wide.

That's exactly when I learned that same realization, and decided never to use (if I can avoid it) a programming environment that defines its own templating language.
I'm quite sure that screws are indeed something that, if made in a shoddy way, would have legal repercussions for those producing them. That's the norm - it's software that's weird for not having that. I would actually expect screws are even rated for specific work. Also, people sell screws, so the analogy really makes no sense.

I'm not suggesting that software developers be required to do anything if they're just writing code, and I'm not suggesting that they do things to some sort of extreme, as you seem to be implying, if they do distribute their code for use.

> explicitly hobbyist-grade or inadequate for purpose that poses a problem

Well, no, they're not explicitly hobbyist-grade. That would be fine if someone were just publishing code and saying "don't use this", but they are publishing code for distribution to package repositories. They don't have to do that, they could just leave it as open source code that isn't distributed, and note that it's not production quality explicitly as you suggest.

Perhaps a more appropriate analogy would be if you were making dinner. You go to the farmer's market and someone with a booth their says "I'm giving away some free fruit, here you go". You would hope that someone who set up a stand at the market would be giving you fruit that's edible. If you went home and ate it, and then you got sick because it didn't meet food quality standards, you would not be the one liable, the vendor would be. "But the vendor gave it away for free!" Yes, but other than software the person giving you something is in fact liable for its quality.

Anyway, analogies suck, I'm sure this misses plenty of important bits. Rather than argue about analogies, let's clarify the actual argument.

1. No one forces anyone to publish their code for distribution purposes

2. When you publish code with the intent for others to use it there should be an obligation to provide basic quality standards to avoid that code doing others harm
You should cut down on Indian govt daily prescribed propaganda consumption. Both countries live in completely different geopolitical realities so their budget allocation reflects that.
I would say fear mongering is worth it if it helps reduce crime. There is now a large swath of people (many of them politicians and prosecutors) that seem to care and talk more about criminals than the actual victims.
Artemis' Lunar Terrain Vehicle will be vastly more capable than the Apollo rover
Trazodone works quite well for some people, is generic and isn’t particularly valuable.
> Dang claims that users flagged it and linked to the FAQ.

I am not defending dang, but that does appear to be a weaponized tactic being utilized here on HN.

Flag something, downvote it en masse, get a user making a dissenting opinion on a "you are commenting too fast timer" which appears to be triggered by mass downvotes, and then hope the flagging carries through.

The problem is with HN - they are permitting this type of behavior, and not realizing (or not actively intercepting) the use of this tactic to silence dissent.

While some time ago the idea that IV injection was problematic with the vaccines would be called fringe or, more aptly, cutting edge research, nowadays we know there is a legitimate issue, many countries are now banning these vaccines in persons under specific ages, and the body of research is more developed.
Could that pick up a transmission from a device designed to emit RF stored in the overhead above?
The Texas grid is running fine. Rolling brownouts a few days a year is completely livable and is only an inconvenience if you’re already used to a super stable grid.

Anyway, my two examples were Boston and Phoenix, which are on more stable major grids.
They're using US numbers both for iPhone count (which they overestimate by ~40 million) and total electricity. That should bias their estimate against their point, as the US is particularly consumerist. Correct me if I'm wrong, but I would think that measuring as a fraction of total usage would also bias their result upwards- x/avg(y) > x/max(y).
The Wire is a great story. Star Trek is a great story. RomComs can be very entertaining.

But taking life lessons from fiction is a serious mistake. I made those mistakes many times. They're fantasies dreamed up by writers, and being fantasies, those imaginary worlds work in the way the writer thinks things ought to work.

The real world doesn't work that way. Real interactions among people, if they have any relationship to movie plots, is simply accidental.

This is a large reason why I have slowly gravitated over the years towards reading history books rather than fiction. History is real, and it doesn't work like fiction (a beginning, a middle, an end). The life lessons in them actually work.

For just one example, Star Trek is the fantasy of the benevolent dictator, embodied by Kirk, and his idiot savant advisor, Spock. I love ST as much as anyone, but the benevolent dictator is a pure fantasy.
Hey, author!

I also remember something, and you forgot to mention it: other frameworks were honestly saying that they took some ideas from React (or improved their solutions being inspired by React’s ideas).

I don't think it was a good idea to use such a hostile style of writing - it is ok for web frameworks to evolve. It is more than ok to share ideas. Every time I see that some new framework took some idea of React (or Ember, or Angular, or PHP) - I see the “credits”, the authors are not trying to hide it.

Some people are criticizing some frameworks - it is ok, no need to start holy wars because of that. Valid criticism will help, pointless toxicity will just shade away.
Automatic generics is how c++ templates behave. It is universally agreed upon to be absolutely horrible, now being remedied with what they call Concepts to constrain the generic signatures at least a little.

The issue is that when you have errors, it is impossible to determine if the error is at the caller, the callee or at the type signature. Essentially you have an equation of 3 dimensions with 3 unknowns. Same issue propagates into code navigation and refactoring.

It’s like regressing into a dynamically typed language except the errors are given during compile time. For small simple functions like the addOne example, it’s great to reduce boilerplate typing, but once you start relying on it for more complex types it can easily go out of hand.
That's just the most obvious smell. But this also happens if you start passing indices around, using them much like unchecked pointers.
You seem to be reading me as implying any use of FOSS is equivalent to having a support contract; it's not. I was claiming that having a support contract for FOSS is equivalent to having a support contract for proprietary software. If you need "support contract" level support you should probably be paying for a support contract. At least with FOSS that can be competitive for the same piece of software (although that probably also means that some of the services on offer are quite a bit worse, having not had to organizationally have passed the hurdle of "actually making the software" at any point).

Finding out that you have a problem when you don't have a support contract and then looking around for someone to work on the thing is not the same thing as having a support contract, although in some cases it can be a sufficient substitute and it's certainly cheaper in the best case (like any other form of skipping insurance).

Depending on context, providing the "support contract" internally is also an option.
I think it’s great too. It’s just a show that people are complaining about non-stop on YouTube, Reddit, and Twitter.
This is true, but the meta point is wrong. It’s far less energy to air condition 110F down to 80F than to go from 0F up to 65F. The energy required in cold climates for heating is far far greater than what it takes to air condition in our hot environments.
There are people who have their personal passwords in iCloud Keychain, and have work credentials/keys in 1Password.
I did a quick dig on Plasmic's AST and not found its spec. Is there a repo for its specification?
I'm open, as always, to refining my understanding of what structured concurrency is, what various forms it takes on, and how it came about. I don't think it's so obvious that the article has misstated, however.

I was not-quite-intentionally using a broader notion of structured concurrency, including not only the initial concept (tie task hierarchy to code structure, propagate errors up the call + task stack), but also critical pieces that are built on top of that, notably cancel/timeout scopes [1]. I don't think these pieces had been assembled to form something powerful enough to make concurrency manageable, until about the time of Nathaniel J. Smith's articles and Python Trio.

I'm revising the text slightly, and adding a footnote:

> It achieves this in ways that seem subtle to us-- clearly so, since its utility didn't reach critical mass until around 2018†

> † While it's argued that the core concept of structured concurrency has existed in some libraries and languages prior to the recent boom, these lacked significant parts of the story for making concurrency manageable. One is powerful, ergonomic control of timeouts and cancellation-- itself dependent on structured concurrency. Another is striving for a program that follows structured concurrency as a whole, including direct and transient dependencies. Nathaniel J. Smith was first to piece this all together, with a set of articles, and corresponding Python Trio concurrency library.

Though I suspect this will welcome more controversy ;)

[1] https://vorpus.org/blog/timeouts-and-cancellation-for-humans...
Problem is, lots of users have work and personal passwords in different apps.
The town's meeting notes are online here[1]. I think they're pretty interesting.

[1]: https://erieks.com/agendas-minutes/
Thanks for mentioning this. It looks interesting
Build, Baby, Build: End scarcity now
Poe looked the most Star Wars a Star Wars character could look. He and Boyega would have been perfect if the writers had been interested in developing their characters.
For me it's the community, half of the time I'm more interested in everyone's take on a submission than the submission itself
> An actual, good-faith bill that seeks to address these issues would attempt to incentivize/punish orgs that use FOSS without making meaningful contributions to it.

Holy shit this is a terrible idea. I can’t think of a better way to discourage people from using open source than to punish organizations for “not making meaningful contributions” to it. As a heavy open source user, contributor, and author, I’m begging you to stay the fuck away from regulating users. That’s the fastest way to destroy open source.
Glad you were able to make the connection. Too many folks passionate on reforming transport focus primarily on the moral/technical problem/solution Vs the actual "job to be done" for people of owning a personal car.

Where I live, I don't own a car largely because the "jobs" for which having access to a car is critical is handled by a reliable, efficient and safe cab/taxi on demand system (you need to get somewhere quickly, carry a lot of stuff, take your family/friends to A&E at night etc). So then I can rely on the very good Public Transit system for the bulk of my regular commute needs confident that I can get a cab when I need to.

If the reliable cab/taxi on demand didn't exist (which was indeed the situation before Uber and it's ilk), I would buy a car irrespective of how good the public transport system was (it was good even then) and irrespective of taxation dis-incentives. Once you own a car, for many use cases it becomes a lot more convenient and has low incremental cost to just drive.

As you may note, these "jobs to be done" vary by geography, lifestage and income - so while general principles can be drawn up, they need to be locally customized.
Stuff like that is turning into one of our running gags at work. You have all these machine learning processes and our legacy java applications gobbling up memory by the dozen of gigabytes, or our newer java apps being a bit less greedy but still gigabyte sized - and it's never enough.

And then we have something like our zabbix proxies, and when they passed a couple tens of thousands of items, we had to increase it's cache memory... from 16MB to a glorious 64MB. Such a splurge. And the server is using a whole 128MB for its write caches. Or our Grafanas are using a total of about 500MB of memory server side total to chew through oodles of data.
>algae cells whose surfaces are speckled with antibiotic-filled nanoparticles.

They are calling algae a robot.
“The orange site” is some weird euphemism twitter users use when complaining about HN. It’s also a great search term to chuck in to twitter for some entertainment.
Thanks for helping to contextualize the parent comment.
Except pushing too hard is also common sense to be a bad thing.