Recent submissions

Comment · 1 year ago
what you describe reminds me pretty much of a binary blob that is loaded into a machine or software.

additionally modifying data in binary form was a longtime practice last time I looked, but I might not remember correctly.

Comment · 1 year ago
Free Software is not the same as expropriation. It's perhaps more the social-democratic smoke mirror kind of thing than lifting the dependency.

Regardless of free software, capitalists control the means of production and obtain profits by exploiting the surplus labor time of workers.

Free software may make it more obvious though, at least for some.

Comment · 1 year ago
A better way to differentiate might be to say how many watts have been used for an answer.

> Humans reason

Are you sure? They reason in a way to match others predictions, right? The problem of humans transporting information from one individual to another remains. All reason can effectively only be prediction, as it requires two persons at minimum. And there is a lot of noise to filter.

> LLM predict.

Well, there is a human that needs to reason with what the LLM has predicted. So from that perspective, it should suffice already for the moment.

Comment · 2 years ago
Messaging is very simple, but made hard so that the benefit is not on your side. Business opportunities, yay!
Comment · 3 years ago
Isn't using GPU and hardware acceleration considered experimental in browsers and the safe default to disable such features for day-to-day use?

Not saying to make this achievement smaller than it is, quite the opposite, it's important there is more such research.

Comment · 3 years ago
> We are the collective voice of the game development industry—developers, game designers, artists, and business minds. Passionate about our craft, we've invested years in shaping an industry that touches the lives of millions worldwide.

Clearly the "our craft" is "business minds" and the problem with increased Unity fees is that their add business is at risk despite all these "business minds" invested years to shape their model.

What an excellent shit-show.

Comment · 3 years ago
While I'm able to understand your argument, IMHO the MIT license is not displaying that well. Community is plural, and fork with MIT could be like Windows: Closed source. End of the (fork) line.

Given the project itself is still strong, this might not be a problem, but then I see no reason why it has chosen it in the first place if not for that specific option.

Comment · 3 years ago
see exec builtin in the bash shell. otherwise man execvp etc.
Comment · 3 years ago
Everything was reverted with 48 hours, your arguments might all apply theoretically but given scope, size, practice and handling, I wonder - apart from the theory - what your opinion is how they practically apply for this case.
Comment · 3 years ago
Isn't community plural? Perhaps they meant their own community but didn't say specifically which one?
Comment · 3 years ago
Comment · 3 years ago
The only question that remains then perhaps is, whether this statement was from the inside or the outside.
Comment · 3 years ago
No wonder, the tab bar is open only. Managing multiple tabs is a no-go with it, or lets say, a wonderful journey into Firefox UI.
Comment · 3 years ago
Thanks, that better helped me to understand your comment. Additionally I was not aware if that was with pull-requests or more with regular code-reviews as part of the development process. That was an additional insight, thanks for sharing.

Nevertheless, things can be different, e.g. if CI passes, it merges already, no need to have a request for merge, which are often a blocker to keep a steady development flow. Naturally, this benefits from tests that are already run during development, if not driving the development.

And I didn't read you're against testing nor aligning white space and comments at all, more the localization. Actually the points you raise are looking important to me, because if alignment comes in late, this can cause a lot of erosion, which can hinder any review if not even provoke merge conflicts which are stopping the process quite early and require re-iteration.

Your approach should also work towards non-release blocking code reviews, a property I personally like, as I've seen teams struggle with code reviews, becoming more and more of a burden, even after practicing it has found its way. But that is only a subjective comment of mine, every project is different, which makes it an interesting topic for me.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton