HackerTrans
TopNewTrendsCommentsPastAskShowJobs

ddevault

no profile record

comments

ddevault
·4 jaar geleden·discuss
Squashing isn't the problem. What you should be doing is trying to make each commit the smallest possible atomic unit of change. Rebase is a useful tool for achieving this -- squashing, splitting, whatever. git add/commit -p also good for this.
ddevault
·4 jaar geleden·discuss
git bisect imo relies on having good commit discipline to be as useful as possible, so many novice git users will not find it useful (identifying the bad commit among "fix thing" "add stuff" "aasdfasdfljser", all of which are +1000/-1000, is not going to help with much).
ddevault
·4 jaar geleden·discuss
git has a lot of stuff, even the experienced can find something new. Have you heard of git bisect yet?
ddevault
·4 jaar geleden·discuss
>as long as it stays open source

This is the important part.
ddevault
·4 jaar geleden·discuss
Something which hasn't been discussed much in this kerfuffle is the role that copyleft can play in protecting projects from this kind of problem. The MIT license is the "default" for many people but it's honestly pretty irresponsible to use it without thinking these cases through.

I represent a similar project (which I shall leave unnamed) and we use copyleft licenses without asking for a copyright assignment from contributors. The result is that the project's copyright is legally held by its contributors and each one licenses their work to everyone else under copyleft terms, requiring everyone involved to commit to keeping it free and open source. Even the project leadership, as it were, is not allowed to take the code and run off with it. Changing the license would involve getting each contributor to agree to a new license, or rewriting the contributions from anyone who does not agree.

As the saying goes: show me the incentives and I will show you the outcome. Design your incentives with care to achieve the desired outcomes. If you make something valuable without considering this, someone will eventually try to take advantage of that value without you.
ddevault
·4 jaar geleden·discuss
This view omits a lot of nuance. Few people are calling for an immediate, unconditional ban on cars, unaccompanied by other reforms. What's clear -- and well backed by research -- is that cars are the worst form of travel compared to the alternatives. The key, then, is to make those alternatives more realistic by accompanying a ban on cars with a serious increase in investment in better public transit and urban design.

This approach is far better for those who aren't "well-off". Cars are very expensive! If we can free people from that economic burden and reduce the environmental impact and improve the availability of alternate means of transit, then the call to eliminate cars is extremely well justified. An argument which, again, is backed up by a wealth of robust scientific research covering all aspects of the problem, including economic.
ddevault
·4 jaar geleden·discuss
Well, Hare is not a high-level programming language, and the standard library has a specific, finite scope. It's also not generally used in the kinds of situations where this is called for (think C -- there's not really a similar library for C, either). But that's not to say it isn't important -- I definitely think that there should be a library which provides this.
ddevault
·4 jaar geleden·discuss
https://qntm.org/calendar

See also: https://qntm.org/continuous and https://qntm.org/abolish
ddevault
·4 jaar geleden·discuss
I think that would be out of scope for the standard library. We do have an interface which might be helpful for developing such a tool, though:

https://docs.harelang.org/datetime#builder
ddevault
·4 jaar geleden·discuss
We're developing a new date/time library from scratch for Hare. So far I think we're doing a pretty good job. The person leading up this effort (Byron Torres) has written up a blog post about it here:

https://harelang.org/blog/2022-04-17-chronology-in-hare/

To stress test our implementation (and to flex on other languages), we're implementing Martian time in it as well.

https://harelang.org/blog/2022-08-01-martian-time-in-hare/

    // Hare's first commit.
    let hare = mbc::new(chrono::MTC, 0, 0218,10,19, 09,20,53,344357297)!;
    fmt::println(mbc::bsformat(buf, mbc::STELLAR, &hare)!)!;
    // 0218 Perseus 19, Fri 09:20 MTC
My current litmus test goal for it is to get strftime to print out 23:23:60.
ddevault
·5 jaar geleden·discuss
GNOME is a dumpster fire is a personal judgement based on a lot of different factors.

But yes, if GNOME or Sway is missing a feature then you want, then that's on them. It would speak ill of GNOME or Sway. But it usually does not speak ill of Wayland, which is the fallacy many, many, many people make, and then fill my inbox up with hateful shit over stuff that Sway actually supports!
ddevault
·5 jaar geleden·discuss
Problems with GNOME are not a fantasy.

Fantasy: Wayland does not support screen capture.

This criticism is not legitimate. In actual truth, many Wayland compositors do support screen capture.

Not fantasy: GNOME on Wayland does not support server-side decorations.

This is a legitimate criticism of GNOME.
ddevault
·5 jaar geleden·discuss
There aren't any Xorg maintainers left. Xorg was abandoned, by its maintainers, because it's a broken pile of shit. Calling it a broken pile of shit is validating its (ex-)maintainers, not being a dick to them.
ddevault
·5 jaar geleden·discuss
No, it doesn't. What matters is that xclip and vnc aren't broken on Wayland. I mean, xclip is, but it's called xclip for a reason. The use-case is not broken, and is fulfilled instead by a tool called wl-clipboard.
ddevault
·5 jaar geleden·discuss
>But it doesn't work for me (aka. important features are buggy in the gnome/wayland/whatever stack I am using if I select wayland in gdm).

GNOME doesn't work for you. GNOME uses Wayland, but the bugs you experienced are not the fault of Wayland. They're the fault of GNOME.

GNOME is a dumpster fire and its premature roll-out to Fedora, Ubuntu, etc was very badly done. None of that has any bearing on Wayland, except to fuel the flames for spiteful people who choose to use the botched GNOME roll-out to harass anyone who has anything to do with Wayland.
ddevault
·5 jaar geleden·discuss
>I’m out going to engage further with you on that because you called me a shitty consumer and that pisses me off. Fuck me, you don’t want me in your userbase anyways, right?

Yeah. Nvidia is engaging in shitty behavior, and I've outlined my argument for this. It's shitty to reward this behavior by buying their thousand-dollar GPUs. And, yes, I think that doing so anyway makes you a shitty consumer. And, yes, I don't want you in my userbase if you've made that decision. It's not my problem when shit breaks for you because of that.
ddevault
·5 jaar geleden·discuss
Author here.

>so he writes an article about people being assholes about him not writing free extra stuff

I did write that extra free stuff, and I'm arguing that some people are being assholes because they perpetuate the lie that I didn't do the free work, and because feature "foo" doesn't work, project bar must be bad. But feature "foo" does work, and using that falsehood to say project "bar" is bad is a dick move. This is the "horseshit" that's pissing me off.

The Nvidia issue is different: Nvidia goes out of their way to prevent their hardware from being used for this purpose. For example, they use signed firmwares that we simply cannot use for implementing the features we need, relying on cryptography to lock us out of their platform unless we use their driver. Then that driver doesn't support what we need. Nvidia deliberately prevents us from putting in the effort. They have created an artificial monpoloy on the required labor, then refuse to do it.
ddevault
·5 jaar geleden·discuss
Games: yes, albiet mostly through Xwayland, which is a compatibility layer. Most games Just Work through this compatibility layer. OBS works fine, but you need a plugin.

Caveat: this applies only to compositors based on wlroots, list of them here:

https://github.com/swaywm/wlroots/wiki/Projects-which-use-wl...

The most mature compositors from this list are sway, wayfire, hikari, and cage. YMMV with other Wayland compositors, and if you have issues with them, you should speak to them, but not blame Wayland in general. If you have Nvidia hardware, you will also have to use the nouveau driver, and YMMV with that, too. I recommend Intel or AMD GPUs, both companies are much more cooperative with the FOSS community.
ddevault
·5 jaar geleden·discuss
Author of the OP here. What you're describing is a bad experience with GNOME, not with Wayland. Each of your examples works great on most other Wayland compositors.

The ignorance which leads you to blame it on Wayland is a major part of the same frustrations I'm venting in this rant. No one is saying you can go fuck yourself for wanting these use-cases. We're saying you can go fuck yourself because we made these use-cases work for you, and you still blame it on Wayland when GNOME is the one not playing ball.
ddevault
·7 jaar geleden·discuss
I disagree in this case, I think it's more Unix-style to use grep when appropriate. You should learn a lot of generally applicable tools, not the intricate details of a few specialized tools. The "useless cat" case can be represented as, instead of grep foo filename, grep foo < filename.