Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Hardware purchase request: AVX512-capable laptop
Date: Mon, 15 Jan 2024 18:01:36 +0200
Message-ID: <3268331.aeNJFYEL58@basile.remlab.net> (raw)
In-Reply-To: <NoCceYC--3-9@lynne.ee>

Le maanantaina 15. tammikuuta 2024, 16.59.40 EET Lynne a écrit :
> I've been pinging this for a week now and he hasn't reiterated
> his position again or made it clearer.

I think my position was clear. I don't see the point in rereiterating it 
whilst we are evidently not going to reach an agreement. Besides, you have 
previously complained that my explanations were unnecessarily long.

But since you bring it up and to sum up, I find completely reasonable for 
FFmpeg to provision hardware with the feature necessary to test your work, 
such as AVX-512 and Vulkan video decoding. But:
1) You already have been provided such hardware in the form of a desktop 
computer (and I am told that it was extremely expensive).
2) In general it makes more sense to get a desktop than a laptop for that 
purpose.

Leaving aside those specific hardware requirements, I think it is completely 
reasonable for you to have a laptop, as most of us probably do. But I also 
think that it is not reasonable for the foundation to pay for personal 
laptops.

Maybe you need a laptop specifically to work on FFmpeg for whatever reason. 
Then a cheap laptop for remote access, as Michael suggested, sounds like a 
reasonable compromise to me. Nevertheless, I think that:
- If your employment requires you to work away from your desktop a lot, then 
your employer should provide the laptop.
- If you want to work from your couch or from the beach (figuratively), that is 
really on you.

-- 
Rémi Denis-Courmont
http://www.remlab.net/



_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2024-01-15 16:01 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  0:56 Lynne
2024-01-03  1:22 ` James Almer
2024-01-03  3:04   ` Lynne
2024-01-03 13:46     ` Michael Niedermayer
2024-01-05 17:36     ` James Almer
     [not found]   ` <NnCGm7x--3-9@lynne.ee-NnCGqE2----9>
2024-01-03  3:30     ` Lynne
2024-01-03  5:28       ` Kieran Kunhya
     [not found]     ` <NnCMnsG--3-9@lynne.ee-NnCMrYP--J-9>
2024-01-09 18:57       ` Lynne
     [not found]       ` <Nnj2jS_--3-9@lynne.ee-Nnj_bOo--3-9>
2024-01-14 17:23         ` Lynne
2024-01-15  8:57           ` Kieran Kunhya
2024-01-15 14:06             ` Paul B Mahol
2024-01-15 16:01               ` Rémi Denis-Courmont
2024-01-15 16:07                 ` Paul B Mahol
2024-01-15 16:10                   ` Nicolas George
2024-01-15 17:30                     ` Michael Niedermayer
2024-01-15 14:59             ` Lynne
2024-01-15 16:01               ` Rémi Denis-Courmont [this message]
2024-01-15 17:36                 ` Lynne
2024-01-15 18:50                   ` Kieran Kunhya
2024-01-15 21:47                     ` Michael Niedermayer
2024-01-16  0:03                     ` Lynne
2024-01-16 10:05                       ` Kieran Kunhya
2024-01-16 11:50                         ` Paul B Mahol
2024-01-16 11:54                           ` Kieran Kunhya
2024-01-16 14:59                         ` Lynne
2024-01-17 13:37                           ` Michael Niedermayer
2024-01-17 15:39                             ` Lynne
2024-01-18  3:28                               ` Michael Niedermayer
2024-01-18  4:07                                 ` Lynne
2024-01-18  8:42                                   ` Steve Williams via ffmpeg-devel
2024-01-18  9:52                                   ` Kieran Kunhya
2024-01-18  9:54                                     ` Paul B Mahol
2024-01-18  9:57                                       ` Kieran Kunhya
2024-01-18 17:19                                         ` Paul B Mahol
2024-01-18 22:59                                         ` Michael Niedermayer
     [not found]                                   ` <25e0763a-4b07-4328-ba93-354d23c8e591@advance-software.com-NoQj7Fn----9>
2024-01-18 15:37                                     ` Lynne
     [not found]                                 ` <NoPk9Ny--3-9@lynne.ee-NoPkD07----9>
2024-01-18 12:32                                   ` Lynne
2024-01-05 17:24 ` Rémi Denis-Courmont
2024-01-05 17:31   ` Kieran Kunhya
2024-01-06 10:38   ` Lynne
2024-01-06 11:09     ` Rémi Denis-Courmont
2024-01-06 16:13       ` Lynne
2024-01-06 17:57         ` Rémi Denis-Courmont
2024-01-06 18:01           ` Lynne
     [not found]       ` <NnUYG5V--3-9@lynne.ee-NnUYKEn----9>
2024-01-06 16:21         ` Lynne
2024-01-06 18:11           ` Rémi Denis-Courmont
2024-01-06 18:26             ` Michael Niedermayer
2024-01-06 20:15               ` Rémi Denis-Courmont
2024-01-06 21:06                 ` Lynne
2024-01-06 23:36                   ` Kieran Kunhya
2024-01-07  0:00                     ` Lynne
2024-01-07  0:40                       ` Kieran Kunhya
2024-01-07  1:55                         ` Lynne
2024-01-07  3:14                           ` Kieran Kunhya
2024-01-06 17:59       ` Michael Niedermayer
2024-01-06 18:21         ` Rémi Denis-Courmont
2024-01-06 18:28           ` Lynne
2024-01-06 17:42 ` Michael Niedermayer
2024-01-10  2:31   ` Michael Niedermayer
2024-01-10  2:56     ` Lynne
2024-01-10 13:06       ` Paul B Mahol
2024-01-10 17:58       ` Michael Niedermayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3268331.aeNJFYEL58@basile.remlab.net \
    --to=remi@remlab.net \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git