skysight-inc/HackerNews huggingface dataset:
> what if the sun and wind stop simultaneously for 2 months

Forget about two months, the cost to battery store just for two or three days is enormous. At the same time, it does not happen often enough to justify the cost over just using natural gas as a backup, so that is how it is done.
wow super cool, thanks for sharing!
Jason Cohen built a one SAAS. his blog [1] is a must read and pretty much a free MBA in the business of software.

a lot of manual work is involved which means emailing and reaching out to customers directly

[1]: asmartbear.com
Damn. That's an interesting fun fact.
> The rest is Mac OS, which uses a BSD userland and hence BSD make by default.

No. Just a really old version of GNU Make

make --version
GNU Make 3.81
Copyright (C) 2006
Okay, no, we don't have to go down this nobody-can-afford-anything rabbit hole.

There are people out there that will pay. The issue is not that there isn't willing consumers to pay for it, it's that you're undiscoverable until word-of-mouth builds around your product among people(like those in this very thread) know and talk about your product going against the grain.
According to https://www.which.co.uk/news/article/which-food-storage-cont... the Ikea 365+ ones are some of the best and they are stupid cheap.
It's mostly so I can immediately see which targets are phonies. Every phony has a line directly above it adding it to the list of phonies. When a makefile gets complex enough we need all the help we can get.

I use phony targets so much I wrote a shell script to parse the makefile database dump into some sort of help text. It doesn't depend on that variable at all.

https://github.com/matheusmoreira/.files/blob/master/~/.loca...

Prints output like:

phony1
phony2
dependency1
dependency2
So spend on that infrastructure instead, or mandate it. Honestly, spending resources on anything ICEs (outside of special industries) in this day and age is just wrong.
Idiots here always have to take it to the next level right?
Ernst Häckel created some of the most beautiful art ever and a conversation about his work is funnily enough how this whole little diatom post project got started :)
I'm not sure there is much more relations to actual chemistry than what I put in the "Prerequisites" section. You can also look the Belousov-Zhabotinsky reaction, which is (at a very basic level) a real world instance of a reaction-diffusion system that acts similarly to this model.
I also like Makefiles, but some design choices are really dated.

My latest gripe with it was its extremely poor support for filenames with spaces and special chars (;) in them: I just wanted to convert a flac library to MP3 files, it seemed well suited for the job at first glance.

I don't know what tool could be a proper replacement. scons perhaps? ninja files are too verbose. just doesn't do dependencies, job control, etc.
Yes, but the article is not talking about your scenario. It is talking about commercial software, where people would need to be paid to ensure that the software is supported on the platforms they like.

You have the privilege of being able to develop open-source but that's hardly a sustainable model.
Do you know if the shells are still intact? Maybe it's an easy way for people to gather lots of diatoms to make more arrangements :)
The battery can be recycled in Germany if Poland doesn't have the facility.
This is very cool. Though personally I don't watch YouTube in this way. Would be cool if it supported game blogs (eg. Lucas Pope, myself, etc) and social media (eg. Walaber, countless others, etc)
Because it’s a dead-end tech that’s holding us back and destroying the place where we all live. If you insist on pursuing it for your own pleasure, knowing what we all know now, you may be a villain.
I was speaking more generally than reviews or classification sites. I really meant virtually any application. It's just that it's a long, slow grind to build the reputation and differentiation from the big tech products you're competing with.
Battery arrays aren't primarily rated for their storage capacity but for their ability to provide/consume power.

At the moment the goal of battery storage additions to solar plants is to soften their peak power production and broaden the time they provide power to extend to the morning and dinner time.

690 MW.
Just fyi, I would recommend posting in r/blind, for a better community, and not here, since there's already so much death crap in the comments, not what a parent looking for advice came to see! Oh, sorry mods if this isn't allowed.
Yeah, that element should be 'textarea' instead of 'div' or at least the 'contenteditable' should be true.
if you want to measure success by how genetically varied your offspring is, go for it man. just a pretty fringe view. to most people, it's just extremely comical to use in this context.
While these npm examples are easy to grasp, they do not reflect any strength of Make. With same success one could use package.json's script property, code would be pretty much identical.
> It explains all it does behind the scenes if you enable the developer console. It can help one learn so at a certain moment one understands and automates with scripts and specs.

An excellent way to learn indeed! Good luck with your project.
termux -> "sudo su" and then

ls /sys/module

(it gives an output similar to lsmod)
Installed solar on my roof 2 years ago (Croatia).

Panel price was 40 cents per W, but that was only 30% od the installation cost, and only 20% of total cost (with permits, etc). EU subsidies covered ~30% of the total cost.

Expect to break even in 8 years at current prices (sure to go up because they’re currently subsidized, so ~5 years more likely).
> Application/service dependencies are no longer tied to the server it is running on, mitigating the worst parts of dependency hell.

Until you decide to optimise for resources, and do crazy things like “one postgres instance, one influxdb instance” instead of “one instance per microservice”, and then you get back into hell pretty quick.

Winds me up how massive tiny applications become, and how my choices are to throw money (RAM) at the problem, or money (time) at the problem. I wonder when someone will do the math and prove that developer laziness is having a substantial drag on global efficiency. The aggregate cost bourn by users has to be orders of magnitude larger than the cost savings made by developers at this point.
Model 3's didn't exist in 2012. Did you mean something else? I've driven an M3P for 5 years, and I wouldn't call it sterile.

I haven't been cross shopping it with vehicles that cost 3x as much and get only 15% of the mileage, so maybe I'm missing something? But weighing 10% more and taking 20% longer to reach 60 doesn't seem particularly compelling.
Intel networking used to have the expensive and works traits. Not confident their current products would be as good.
I’d be more surprised if the effect was immediate. Addiction takes years to develop, and years to recover from. I would also expect marijuana legalization to have more impact on (potential) future drug users than people already addicted to opioids.
Until somebody comes up with a replacement technology that so the same or more there will be a place for it.
Military contracts can make anything make economic sense.
All that is true, but food containers still sell. People have lunch boxes etc.

Tupperware has not innovated, patents have expired. Same injection mold plastics that eventually gets color stains from the food.

Cheap knockoffs everywhere.

Higher quality plastic containers available.

Tupperware brand is associated with grandmothers and valued only by them. Younger people don't buy them.

People who are ready to pay more use metallic containers or borosilicate glass containers with plastic lid. Buy one with good silicone-rubber seal lid and they last forever.

There is nothing going on with Tupperware.
I'm lucky enough to be employed full time to work on open source, but I still build my own OSS in my own time because it scratches a different itch. My work on Astro is fun, but it's my job, with Linear tickets and standups and 1:1s and quarterly planning. My own OSS is where I build whatever fun stuff I feel like without pressure. It has enough users that I do get issues, but not too many that they're overwhelming. I think the very fact that I have a job in OSS makes it easier for me to dismiss the entitled users who come to my personal projects demanding support. I build that for fun, and I owe you nothing.
That's interesting because I find the commenting itself to be flame war baiting, not the voting parts. But maybe there should be a manually settable comment reply cooldown period, which I believe HN does automatically for some accounts who post a lot of flamebait comments.
A framework for quantifying software engineer performance
You can overfill the cylinder for the first stroke, because the unspent fuel will burn on the next cycle instead of being exhausted.

High power engines exhaust a lot of unburned fuel, because you can't guarantee an exact 100% fill for the cylinder, and there's more power to be had at 120% fill than 80% fill. Oversimplified of course.
If I may disagree: I live in a flat with a fully electric vehicle. It's just a matter of planning around charging a bit. Once you think ahead (and it's not dramatic), you don't notice anymore.

I find plug in hybrids make no sense: electrification is the future.
Reflecting the interwar German society more broadly; agricultural mechanization was decades behind the US and UK.

The industrial and economic "miracle" of the pre war Nazi regime wasn't spent on tractors either, but on weapons.
I’d walk that before talking. Take any complex makefile system and turn it into a single “not really difficult” makefile without sacrificing anything important. Wins this argument and helps those who “use it wrong”.
I am not here to shill for Google, but they publish a staggering amount of liberally licenced software. We can much less of that about Microsoft, Apple, and (my personal most dreaded for open source) Amazon.

Also, I stand by my previous comments from other similar discussions: Almost all big corps use Redhat. They are indirectly funding open source. Redhat probably employs more programmers that contribute to a base Linux install than any other company on the planet. (Yeah, I know they were bought by IBM, which gets no love around here.)
¯\_(ツ)_/¯ Fundamentally, I don't think it's bad to require that wealthy citizens pay taxes. I don't think I'm being "robbed" - I pay higher taxes where I'm resident, so I just fill out some forms to tell Uncle Sam what I've already paid and it zeroes out my US tax liability.

Far from being unjust, I think it's good and proper that you can't run away to Dubai to skip out on your obligations.

The US government does plenty of things I consider unjust. To take one obvious example, it has, without due process, killed its own citizens in drone strikes. I just don't consider making wealthy business owners do paperwork among its crimes.
As long as you're scanning over a perfectly flat, if tilted (relative to the microscope's focus plane) 2d plane, you don't need to autofocus much. Just measure the focus at a few points and fit the plane, then run the scan and apply the focus parameters from the fit.
You are now aware that you have forgotten something important.
The same reason people still do R&D for vinyl records: There's enough customers who want to buy the old thing, for ideological, emotional or other reasons
> I find plug in hybrids make no sense: electrification is the future.

They make sense depending on how far away that future is, and I think that 'future' is way different for different parts of the world.
Ig Nobel is a pun on Nobel and ignoble, so how about a Tor Turing award?
The worst build systems are the ones centered on a particular programming language. Since there's N>>1 programming languages that's N>>1 build systems -- this does not scale, as the cognitive load is prohibitive.

The only general-purpose build system that spans all these languages is `make` or systems that target `make` (e.g., CMake). And this sucks because `make` sucks. And `make` sucks because:

- it's really difficult to use right
(think recursive vs. non-recursive make)
- so many incompatible variations:
- Unix/POSIX make
- BSD make
- GNU make
- `nmake` (Windows)
- it's rather ugly

But `make` used right is quite good. We're really lucky to have `make` for the lowest common denominator.
In contrast, the Treo 650 battery was considerably smaller in terms of capacity and significantly bigger in terms of physical size, leading to a bulkier device that had a significantly lower resolution, colour and physically sized screen. Lets not pretend the state of the art has not moved on.
We have no idea what's under the surface of the moon. We literally know nothing. It could be that the moon is secretly a gold mine of rocket propellant 5 meters under the surface, but we simply never looked deep enough.

We built the first railways on earth 200 years ago. We could build railways on the moon this century. Think about this. The time between the beginning of industrialization and a space civilization could be just 300 years.

Your grand kids would experience the space age, but only if you start working on it today.
GitHub Sponsors seems promising... If one somehow gains a large amount of fans. I gained one last time my work was posted here and I'm really grateful for it. I refuse to advertise my projects though. Simply because I hate ads myself.

I think the best option is to just AGPLv3 everything. You maximize freedom but still own the copyright so if corporations want your software they can simply pay for permission to use it. AGPLv3 gives us our leverage back in an ethical way.

Even asked Richard Stallman what he thought of it. His reply:

> It is my understanding that as the copyright holders
> they have the right to do it without any problems.
> They leverage the AGPLv3 to make it harder for their
> competitors to use the code to compete against them.

I see what you mean. The original developer can engage
in a practice that blocks coopertation.

By contrast, using some other license, such as the ordinary GPL,
would permitt ANY user of the program to engage in that practice.
In a perverse sense that could seem more fair, but I think it is
also more harmful.

On balance, using the AGPL is better.
Let's completely remove them from your feed
I am the last person who would defend Elon or Tesla. They have enough sycophants in this thread alone.

But when you are an employee, especially in current market conditions, you may be subject to working for companies you personally despise. I know I have.

Regular people have rent to pay and mouths to feed, they may not have the luxury of damaging their own well being to defy the retarded billionaire in charge.
but the grandparent poster's problem isn't with ICE itself, but with "emotion, driving as an experience" etc.

In other words, the grandparent poster's argument is merely that people shouldn't be basing decisions on their (flawed) emotional attachment to driving as an experience, and would like such to be shamed and vilified.

This is a moralistic argument. It has nothing to do with environmentalism, but is using climate change as a platform to push a personal agenda or world view. In other words, it's a woke argument.
If you took a list of every open source project that FANG-type companies depend on, there are small libraries that don't draw benefit/attention from large companies.

Outdated, less optimal, almost-famous code/libraries/frameworks that businesses still rely on for money and don't want to spend money migrating away from that need various updates for new OS versions, security patches, and those are the maintainers that are underpaid and struggling.
As a guy who doesn’t write code, but reads a lot of it, Makefiles have always been a PITA to deal with. But less so than cmake or other build systems.
There is a whole spectrum between AGPL and permissive. MPLv2 or the EUPL [1] basically say "you can use it as a library (and link it without the concerns of LGPL) but if you modify/extend the library, you have to distribute the code of the modified/extended library".

I don't understand why an OSS author would select anything more permissive than that: big corps can use MPLv2/EUPL libraries in proprietary software just fine.

[1]: https://joinup.ec.europa.eu/collection/eupl/how-use-eupl
They're called sports cars for a reason. They're driven far less than everyday cars. They're fantastic fun.

I'm an enviromentalist and I'd still buy an ICE Porsche.

No EV has come close ... only the Hyundai ioniq 5 N seems to be looking interesting.
I actually really wanted to buy Tupperware,specifically because it lasted.

Imagine my surprise when it turned out I'd need to go to a Tupperware party to do so.
Aight so I gotta improve my 5k pace by about 1.5min/km and then keep that up for an entire marathon.

Though perhaps I'll stick to attempting a 25min 5k first. Catch Boston some other year weep
> Words mean things. Please use the right words.

What the ... You are ignoring what I wrote while not contributing anything. What did you fail to comprehend? You should be addressing what I wrote. Apparently many other commenters did understand me. What does that tell us? You are just being a jerk.

> Stop it.

Seriously. You are not discussing things, and you are not sharing an opinion here. You should be the one taking a break and consider your behavior.

How does it feel defending one of the richest companies in the world, and realizing they wouldn't care if you dropped dead?
> paid a support fee and get support

I cannot prove it, but I am convinced this is an important revenue stream for Redhat. They will patch an ancient Linux kernel forever if you pay them. I have worked at multiple companies where we were running ancient Linux kernels than received regular security updates, courtesy of our Redhat subscription!
> [Linus] also said it's far too early to give up on Rust in the kernel as it's still early days.

Did I miss something? This sounds like they’re thinking about giving up on rust.

Edit: this from the lead working on it:

> "I am retiring from the project," Filho declared. "After almost four years, I find myself lacking the energy and enthusiasm I once had to respond to some of the nontechnical nonsense, so it's best to leave it up to those who still have it in them."

It truly is the most toxic community. I’m just glad I’m not to feel like the only seeing / be affected by it.
> Also genetically varied offsprings from point of view of nature is probably the only measure on how successful your life is.

For a farm animal.
Can someone explain why it's going to take so long to fully decommission TMI-2, the old reactor?

Reading the commission report, they have about $733m in the decommissioning fund, while decommissioning is projected to cost $1B. Active demolition projected to start 2046, completed in 2052. They've started some work on debris demoval, but it looks they're going to take a break 2030-2046 to let the fund accrue (at expected 2% real RoR) enough to get the fund to $1B.

Isn't that insane? So from 2030-2046, it will just sit there "mothballed" with a minimum spent on security and so on, just for the fund to gain value?
I'm not sure that follows. Prior to Android we had numerous options, since Android we have two. Prior to Linux we had Solaris, Next, Xenix, HP UX, AIX, BSD, etc. Now we have macOS and Linux. Browse through early issues of Byte or Dr Dobbs and see how many C/C++ compilers were available, now we have gcc or clang.
I do this with kubectx to switch and kube-ps1 with ohmyzsh to display cluster/namespace in my usual prompt
Did you pay for the software? Do you have a contract? No? Then they owe you literally nothing. You are lucky that they give it to you for free. You can open issues if you find a bug, and hopefully the maintainers will fix it, or somebody else will. But if they don't, then you are lucky that it's open enough that you can fix it or pay somebody to. But they are under no obligation to do anything.
We’re excited to share the latest updates to phx.tools, the complete development environment for Elixir and Phoenix.

Most significant changes:
- removing unnecessary dependencies
- switching from asdf to mise
- using existing shell instead of forcing Zsh installation
"we're the dot in dot.com"

No wait ... the other one ...

"the network is the computer"
I already don't like, and would not want to meet that person in public! So yeah no!
Makefiles become a horrific technology the minute dynamic variables and the ensuing escaping games get involved. Massive footgun. Bash is already a fairly bonkers language (think from a junior engineer's perspective) and Makefiles so frequently compound that by an order of magnitude.
"I usually move more complicated script put of Makefiles."

We probably all should. But it is valuable a few different ways to have everything in a single file.

Even though it's an ugly mess having a script within another script, with make variables mixed with shell variables mixed with make logic mixed with shell logic mixed with child proc output... the task at hand wants bits from both worlds at the same time, so the mess is also the value.

You can rig up alternative answers for each of those, but really it just means make should probably have a more generic scripting language itself so you don't have to leave it to get something done, like how you don't have to leave awk to do non-record-processing stuff. People don't, but you can basically write anything you want in awk just like in shell or python.

Or it should have less, be intentionally so limited that you can't embed any significant logic in the makefile and so it all lives somewhere else, either way, so long as it's all together, either all in the makefile or all in something the makefile runs.
Companies that depend on FOSS would contribute if the license did not explicitly tell them that they don't have to.

MPLv2/EUPL come to mind: they are compatible with proprietary products, but they make it mandatory to distribute changes/extensions of the library, not the whole product.

FOSS authors have a responsibility when they choose a permissive license.
I will get downvoted for this answer. I have similar experiences with open source contributions, including big reports. My solution: Don't do it; it is a waste of your time. It is best, if possible, to run your own open source projects, then you fully control to whom you listen and accept input.
Sadly no sigrok and pulseview support. See https://forum.redpitaya.com/viewtopic.php?t=22866
> I'll miss the closed loop payment card support from iOS

I was definitely hurting for a while for lack of this (and iMessage) on Windows. While I haven’t gotten over iMessage (and use a KVM with my iPad to resolve that), the additional friction for payments has actually been a boon for my bank account.

The more friction we feel with payments, the fewer payments we make. Cash is higher friction than cards. Manual card input is higher friction than password manager autocomplete. Autocomplete is higher friction than apple pay. I haven’t found anything lower friction than apple pay.

By switching back to password manager autocomplete (which is unreliable at best), I’ve found my spending has gone down, because the cost of friction in payment is higher than the value of the item.

(I clearly also have too much disposable income, but that’s a whole other tangent)
nobody likes makefile
Yeah, the grid is the part of this that doesn't get discussed enough.
Sending mass from the moon to earth is energetically positive and you can build mass drivers and space elevators on the moon that are only powered by electricity. So assuming an ambitious space program, there is every reason to do this, except that it costs money.
Qwen2.5-Coder Technical Report
Vedit ⧸ VEDIT‑PLUS for CP/M v2.33B (04/27/87) source code
Underrated? The flip side is that hardware failures are still your problem like they would be with rolling your own hosting. I think they’re correctly rated for the position on the scale of traders that they provide.