skysight-inc/HackerNews huggingface dataset:
> Personally, I like to put a single song on repeat for hours and hours, days even. It helps me zone in.

I'm pretty sure this is a form of torture. It would be for me, at least.

I think this advice is okay, as long as you've defined parameters for what "finished" even means. If your goal is to make an app, publish it to app stores, and maintain it in perpetuity as a personal income stream, then great. Go for it.

Bringing a piece of software to production is almost never my goal with a side project. Usually, my goal is to explore a new concept. Maybe I want to get a feel for how "problem X" may be solved in the real world, whether or not my program is one of those real-world solutions. Maybe I'm revisiting an old project with new wisdom.

Take this for example: I have created no fewer than 4 visual novel engines, none of which are production-ready. A couple years separate each one, and all of them are wildly different under the hood. One of them is made entirely out of Nim macros. Another one uses Nim to do the drawing, animation, "game-enginey" stuff, but embeds the entire Ruby MRI with a custom DSL that the developer uses to write their game code. Another one is built on pixi.js, and the first one was just an enormous abstraction on top of ren'py.

All of these approaches are wildly different. All of them taught me new software design principles. None of them needed to be "finished" in order to do that.

The goal of side projects doesn't have to be "publish a production version" or "turn a profit." Cut it out with that hustle culture nonsense. Go make art.
Probably.

However impressive LLMs are, they're not AGI.

For example this morning even, I was working together with a coworker and he used ChatGPT to ask for some examples. Unfortunately they didn't work, after reading the actual documentation it turned out that the structure had to be slightly different.

This is the impression I get from everything that has been generated with "AI", on the face it looks great, but as soon as you start going into detail it's not right or just plainly wrong. The generated code had six fingers. They might be able to improve this eventually but I don't think it will ever be fixed because of the nature of LLMs.
It's a little much to say almost everyone does it wrong. More likely, since it's something that catches your notice, you probably have a bias for noticing/remembering when it's incorrect and not noticing when it's correct. It could also just be a simple typo or an autocorrect error for any given occasion
Reading destroys the stored value; it doesn't necessarily destroy the physical material.

Reading from memory is already destructive in DRAM (capacitor gets discharged), magnetic core memory (need to alter the magnetization state to read out how much energy was needed), and probably other technologies as well.
Of course I come into work the next day and now I can't run my custom built one either...
Sure, but it's even easier to not have to worry about deploying at all. The largest structures we've built were built in-situ.
Title is "Winamp Legacy player source code is now open". The usage of the word "open" in conjunction "source code" alludes to the long established "open source code" phrase, which implies a set of licenses, and the associated open source culture.

A better choice for the title would have been "Winamp Legacy player source code is now available".
Ah, piping, all about moving something from A to B. Has anyone else read Leslie Claret's classic text "The Structural Dynamics of Flow"? I got the chance to hear him speak, once. It was riveting: "Hey, let me walk you through our Donnely nut spacing and cracked system rim-riding grip configuration. Using a field of half-seized sprats and brass-fitted nickel slits, our bracketed caps and splay-flexed brace columns vent dampers to dampening hatch depths of 1/2 meter from the damper crown to the spurv plinth. How? Well, we bolster 12 husk nuts to each girdle jerry — while flex-tandems press a task apparatus of ten vertically composited patch-hamplers — then pin flam-fastened pan traps at both maiden apexes of the jim-joists."
Man, this could have been written just for me! :)

I'm so guilty of abandoning projects in the past before they're even remotely done. It's mainly due to losing interest in the subject itself rather than dealing with the bugs and legacy and bad code decisions as you get further along the journey.

I used to get bent out of shape about it and criticize myself for it but I came to realise that it meant I didn't really have enough interest in the thing I was building in the first place.

Case in point (and a bit of a shameless plug tbh) just this morning I finished, end-to-end my current project I've been working on for 4 months: a .NET hosting site like tiiny host where you drag your zipped .net project onto the page and it gets automatically hosted with a unique url and whatnot.

For the last month or so, I've been at the really fiddly stage where all the moving parts came together and they all had bugs that had to be fixed both independently and together with other bugs and finally it worked this morning (still to polish it though).

I usually don't get to that stage and have abandoned a great many things over the years but this project has captivated me from the start with only a minor loss in productivity (due to a health issue with a family member tbh).

I'm now at the fear stage the author mentions - will anyone want to use it? We'll soon find out!

The long and short is that I discovered that I abandoned things frequently in the past but I realise I just wasn't that into the ideas! I don't worry about it as much now.

But, great article :)
The HN headline did
Durable artificial photosynthesis setup chains two carbons together
Or you can try neither and use a year format that does not confuse us plebs.
Places like HK and Singapore had free markets and not much unions and became pretty prosperous, during my lifetime having GDP per capita go from something like a third of the UK to nearly twice it in Singapore in spite of us in the UK having the benefit of unions fighting to keep everyone coal mining and the like.
That still contradicts the license as written.

> No Forking: You may not create, maintain, or distribute a forked version of the software.

There is no meaningful difference between the words "patch" and "fork"; and the act of creating an edited codebase is explicitly disallowed.

If that isn't what they want, then they had better write more clearly.
“fully-managed, cheap metrics, ideal for serverless applications”
> ...but that's not really what I've been speaking to, and it's not what people were angry about or protesting that caused me to post in the first place.

You literally said:

> Shading this as being a blog post about weapons is a deep misservice & actively deeply harmful to the author & discussion. ... Focusing on the weapons part seems not the point of the article to me & shades a bad light/gives the wrong impression.

It doesn't matter at all how angry people are about the article being about weapons manufacture, nothing justifies claiming that that's not what the article is about. While I'm sure you believe you were well-intentioned, claiming that it is NOT about weapons manufacture in an attempt to placate angry people is harmful in the same way that -say- systematically yanking the teeth out of wild cats is.

If the people who get angry about frank and direct talk about weapons manufacture get angry about the article, then that's __good__. It means that the article is doing what it's intended to do, which is to start a frank and public discussion about just how easy it is to build remotely-activateable booby-trapped batteries that are indistinguishable from normal batteries, and that doing so at scale might really actually be a bad thing.
Yes, that's fair. I wouldn't be trying to use Nix at all if I was wanting to depend on stuff outside of it— fortunately nixpkgs already has decent coverage in the scientific computing space, so most of what we needed for a ROS/robotics application was present, and the remainder wasn't too bad to just package ourselves.

That said, I think the node story overall is still pretty rough. There are several competing tools/workflows each with different tradeoffs. My frontend team did a brief evaluation and basically just noped out of it— there's so much tooling in the node world that just gets you directly from your lockfiles right to a deployable container, it's harder to see the value of a Nix closure as an intermediate build object; the case is a lot less clear for it than for, say, Python or C++ stuff.
I agree; your interpretation is reasonable and plausible. But it's disappointing to have this ambiguously, since the license file has a whole section for "Definitions" and yet it fails to define what "forking" means in this context.
We likely overestimate AI's short-term impact, and there might even be a financial bubble about to pop. But I also think we underestimate the long-term impact. We're building absolutely amazing capabilities faster than many would have thought possible only a few years ago - I especially think applications to science and engineering will be huge and transformative.
I think Apple rightly gets the most criticism since their marketing is among mind-control levels and they are fine with doing unethical things (Lying in ads, using fake customers to pretend to have popularity, astroturfing/upvote farms to control narratives, making people status insecure)

Once you realize how dirty Apple's marketing is, its quite off-putting. I have a similar aversion to Samsung, Nintendo, Disney.

Maybe Google does mind control, but I didn't catch them. Apple, Samsung, Nintendo, Disney, these companies have no qualms making you feel pain to get a sale.
That does not sound viable to me at all.

How would you distinguish between the government coercing a demographic into suicide and that demographic just having a higher-than-average predisposition for it? E.g. people with depression or chronic illness/pain.
This isn’t compression, they are throwing features of the original stream out.
This review is so long I may as well just buy the book. Perhaps it's for people who already read it and want to see what other people thought of it.
I tried it.

o1 cannot do my job, and hallucinated immediately.
You can't scan a QR code without photography. But the QR code app won't just write "oh we need the camera to capture some photons".
Well that's where it gets tricky -- what variables are you allowed to control for in this analysis? Not to spoil anyone, but this is what Soylent Green is about: people on the edges of society aren't actively coerced into euthenasia, but the presence of a more abstract level of coercion is made clear.

In terms of contemporary Canada, what if First Nations people end up using it much more often because they have much higher rates of poverty and drug abuse in their communities? On an individual bodily autonomy level that feels like fair game, but on a societal level the injustice is blatant.
They are either going to have to submit a ton of DMCA requests to GitHub and get their own repo taken down by GitHub, or they will be at risk of losing their copyright and will take it off GitHub themselves.

Forking is a fundamental feature of GitHub. Forking policy may only be set on private repos, but this is a public repo. The license doesn’t permit forking. There are already 6 forks.

Typically, copyright is not lost through selective enforcement (unlike trademark), but in this case the rights holder is making license violations both trivial and has full access to the list of violators. I suspect the courts will laugh them out of the room unless they vigorously defend their rights.

In that case, I certainly wouldn’t want to deal with it if I was GitHub. It is a terrible user experience, where a user clicking one of the most popular buttons on the platform suddenly becomes a legal problem.
When’s the next cohort? It doesn’t seem to say on the page.
Elliott Management calls and CEOs and boards listen. Southwest's line is ringing
>Second, because despite the constant threat of automation levied against working class people, we really do seem to be hitting the limits, at least in present technology, of what we can make machines do.

This is the real problem society has, especially with subdued and declining fertility rates.

Most societies have promised people benefits based on 7%+ annual returns, and those returns need to come from somewhere. Without the high fertility rate, the returns were coming from automation and massive economies of scale.

However, there has been a plateau in automation for many high touch businesses (food, healthcare, construction/trades), so those cost increases are being as political fighting over who gets what from society’s productive. And old people control most of the political and economic capital, as they, along with their heirs, have an interest in maintaining their expected share of the economy’s productivity, even though it means younger people get less.
Creativity is a mixture of imitation, recombination and revolution. Very rarely does something novel spring forth from a vacuum. I think AI is very good at the first two. However, the third is something else. It takes an artist/engineer/scientist decades of work to come up with worthwhile and novel concepts. Usually inspired by a lifetime of personal experience.

I think, if an AI can reach that point, we will see an explosion of astounding scientific and artistic progress.
Says the hotchips keynote - https://www.youtube.com/watch?v=rsxCZAE8QNA&t=2480s

- data that is moved is about 100x higher power than data that is local

You have a good point about intermediate data. This would not apply to all algorithms.
You understand that this is an entirely separate argument about an entirely separate issue right? Even if Apple did do that, presumably it wouldn’t change their process for listing things on their curated App Store.
Floppy vs. Stiff Concepts
If you're using dynamic linking, the following two tools will come in very handy:

- pldd (https://man7.org/linux/man-pages/man1/pldd.1.html) shows the actual dynamic libs linked into a running process. (Contrast this with ldd, which shows what the dynamic libs would be based on the current shell environment).

- libtree (https://github.com/haampie/libtree) which shows dependencies similarly to ldd, but in tree format.
How much time do you think the lowly non-Apple employee contractors get for reviewing each app?
Publishing the Same App Once Every 4 Years: The Electoral College Calculator
A vision of the future of software with AI craftsmen
AdGuard Browser Extension for Chrome MV3
100% keep sponsorship separate from paid support.
Life for Haitian Immigrants: Jobs Nobody Wants and Sleeping on the Floor
Book Review: On the Edge: The Gamblers
Actually just nailed down the date to Oct 6th!
Moreover, what if I don't want Google or Apple to know about my {Islamic LGBT app, Chinese Democracy app, etc.} ?

Why do they have to know or control me or my audience?
Presumably the prohibition is around creating a forked release, with the language being intentionally a bit vague to cover their bases. Unfortunate that that's how these things are, though.
The second link is a 404
Situations like this are exactly why trucks carry containers. You don’t want to reuse the containers for those two things but you can absolutely reuse the trucks.

The trucks cost on the order of six figures, the containers an order of magnitude less.
Sleep-tracking devices are wiring the world for the study of sleep
Eh - I actually like developing on OpenBSD first, because of restrictions like this. If it runs on OpenBSD, you are likely to have fewer bugs around things like malloc.

OpenBSD is also really good about upstreaming bug fixes, which is a good thing. Firefox used to be a dumpster fire of core dumps on OpenBSD, and many issues were uncovered and fixed that way.
Which CAD tool did you use?
An Outsider Critiqued Meta's Smart Glasses
Wait until they have to spell the name of the character stat that determines if they are strong or not.
Replace "maybe" with "OBVIOUSLY". Keeping useless-but-hazardous "features" in any language is as idiotic as keeping a heap of oily rags in the furniture factory warehouse.
Windows native C/C++ desktop development (and non-gaming)? I actually think this is becoming a niche now, comparing to other desktop devs, especially if you don't use QT.
This is, of course, exactly what Nextcloud does. It will most certainly refuse to run and break your system. And yes, it also refused that 3-4 years ago.

Not saying it never breaks anything, but since 2016 we for example check PHP versions and other infra to not update to a broken system. We rewrote the updater in 2016 for this purpose. It's possible this has had a bug at some point of course - but it is more likely that the original poster who had this issue had this in the ownCloud times before 2016.
Well, certainly don't rely on forums to get your legal info. Feel free to consult someone versed with data protection regulations in countries where your app is available.
If anything, government regulation would make the App Store submission process even more onerous. Instead of new hire apple/google contractors you’ll be getting cranky government staff who probably have less agency than the former contractors ever had.

Be careful what you wish for.
Some men tend to jump straight to innuendoes: dating app users on why they quit
You see teens/low income people with a new iphone and its their identity.

I had a teacher call me poor for having an Android. I made 4x more money than her in a year, and decided to let her know that.

I also let her know that a phone I can get for $30/mo isnt much of a status symbol. Unemployed teens are able to afford it somehow.
You also see intelligent folks suffer from the curse of knowledge when discussing the topic.

They assume that half the population isn’t below average when it comes to intelligence.

It’s similar to the analogy that crime would go down if every human had a gun, but the analogy fails because of human flaws.

Assisted suicide will always be abused; mentally ill will be killed; kids who want more tax savings will push the button, etc.
Instagram's new under-18 rules met with skepticism
Somewhat related, I think, I am always surprised at how often we don't have non-critical paths in jobs. Half the reason stress is so high, it seems, is we have backed ourselves into a situation where things have to succeed.
That's besides the point though. Yes, having prebuilt binaries is very helpful. But what happens if Fastly decides against renewing next time and there is nobody else willing to sponsor? The cost is through the sky for the PSF to handle. Where does PyPI go?
Hard links are to deduplicate identical tiles, right? How much does that save and how close is the tile with most links (empty one(s)?) to the filesystem limits? Inquiring minds want to know...
as a former yc data integration startup employee... this is a very very very challenging business. i'd consider a different business if i were you. being "x but open source" isn't all it is cracked up to be. i dont really care enough to elaborate but please do feel free to tell me if i am wrong in five years.
I was a huge fan of Winamp back in the day, but the way they handled the software completely soured me towards it. Winamp 3 was a clusterfuck, Winamp 5 was fine but felt like bloat, and then it was passed around like a hot potato, then abandoned on and off, and then the open sourcing feels like it was also around for quite some time. And now it's not even that, just a meager source-available. I know they don't owe me anything, but I feel disappointed.
Someone making a Docker image from this. Instead of using Fabric's commands like c.sudo('git clone ...') it'd use the RUN commands.

I think it would be quite a straightforward task to transform it into a Docker file. I'd be happy to link to it on GitHub.
Memory safety is a very small part of security.

Indeed.
> if Google had done this

I’m coming fresh off weeks of app rejections that turned out to be I included the word “review” in the description of my app on the Google Play Store, and best I can tell was an automated rejection based on keyword matching and entirely unhelpful to explanatory text, so let us not pretend Google is running a tighter ship here.
Terry Pratchett came to Switzerland to help film a documentary on the topic:

https://en.wikipedia.org/wiki/Terry_Pratchett:_Choosing_to_D...
In truth, it's usually the opposite when our bodies are fueled properly.
Lots of people are using generative AI for roleplay - don't know if this is a significant contributor to OpenAI's revenue, but it's a (the?) major non-corporate use.
That's not what the OP said. He said, "Try things quickly, and abandon the ones that don't pan out." Nothing in there about destroying things that are working.
I think I define Finish differently. My projects are commonly scratching an itch or building what could be a business/product (eg SaaS MVP). What I usually find is, scratching an itch is satisfying in it's own right. I don't need to publish it or seek further validation than seeing that I brought this thing to life or achieved the hairbrained hack I imagined. Likewise, usually when building an MVP, along the build process I realize that I actually have no interest in running/promoting/dedicating time to the actual operation of this theoretical business. If it already existed maybe I'd be a customer, but also maybe not. So while both of those things are technically unfinished, I took them as far as I wanted to. So to me, that's Finished.
I signed up, and it's a beautiful UI, with impeccable results for the PDF or Markdown flavors in particular. Speed was impressive on a video that had subtitles off. Bundling all formats into a zip is a stroke of genius.

Does your tool work on 3 hour vodcasts? There are quite a few long series I would far prefer to read than listen.
You can’t compare kiloton with megaton weapons. This is insincere.

Moreover what strikes me is we have so many people handwringing about Hiroshima and Nagasaki and wondering if it was morally right… but the same kind of people are cavalier about having thousands of weapons tens of times more energetic getting launched.

It’s mindboggling.
It should be possible to make it by milling, even if that would waste a lot of material.

For casting, the initial mold must be made by milling anyway (or 3D printing), even if some intermediate molds could be made by casting themselves.
1. I believe you that it works well

2. Plausible != Correct
- ie, would someone notice if they were reading a slightly different but still logical story?
(looks around)

Nope, not seeing anyone defending Apple on this (at least in the top hundred or so comments at time of writing). Even if you can find one, the posts ITT remarking on how common ridiculous Apple defenses are likely outnumber the actual comments defensive of Apple. Y’all may want to adjust your priors.
It can take responsibility for production code and get fired when it produces sub-standard work?
> As for how the orange peels were able to regenerate the site so effectively in just 16 years of isolation, nobody's entirely sure.

Well, the first thing that comes to my mind is: Maybe it wasn't only the orange peels. Perhaps there were other factors that contributed to the turn around. And given that this was a one-off they need to reproduce this experiment again, ideally two more times.

Once is not a pattern. Even twice isn't a pattern. Three times? Now we can begin to identify and consider there might be a causation-worthy pattern.

To often we want a single causation, and more often than not it's not that simple.
Because I don't see it mentioned elsewhere, I wanted to plug OpenTimelineIO, as a lot of the industry is building support around it as a format right now, and it would be great for any new video editor to support.

https://opentimelineio.readthedocs.io/en/stable/
The AI Detection Dilemma: Navigating Authenticity in an AI-Augmented World