101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

485
active users

#perforce

0 posts0 participants0 posts today
Overlook InfraTech<p>So much for being developer first. <a href="https://fosstodon.org/tags/Perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Perforce</span></a> has sequestered away the <a href="https://fosstodon.org/tags/PDK" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PDK</span></a>, just like they did to <a href="https://fosstodon.org/tags/Puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Puppet</span></a>. It's an odd strategic move to make it harder for the best module authors in the <a href="https://fosstodon.org/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>community</span></a> to build content for your platform... <a href="https://overlookinfratech.com/2025/06/12/so-much-for-being-developer-first/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">overlookinfratech.com/2025/06/</span><span class="invisible">12/so-much-for-being-developer-first/</span></a></p>
Alanna 🏳️‍🌈🏳️‍⚧️<p>The next person who advocates that "Perforce is more user friendly than Git and better for artists." to my face will get a custard pie in response. It really isn't any different to any other VCS is terms of complexity and arguing that it is "user friendly" compared to git is just lies.</p><p><a href="https://mastodon.ie/tags/versioncontrol" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>versioncontrol</span></a> <a href="https://mastodon.ie/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>git</span></a> <a href="https://mastodon.ie/tags/perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>perforce</span></a> <a href="https://mastodon.ie/tags/software_engineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>software_engineering</span></a></p>
anarcat<p><a href="https://kolektiva.social/tags/perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>perforce</span></a> is forking <a href="https://kolektiva.social/tags/puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>puppet</span></a> into a closed source version <a href="https://github.com/OpenPuppetProject/planning/discussions/11" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/OpenPuppetProject/p</span><span class="invisible">lanning/discussions/11</span></a></p>
anarcat<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@genebean" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>genebean</span></a></span> they're doing a serious mistake, and everyone is telling them so, but at this point, i don't care about <a href="https://kolektiva.social/tags/perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>perforce</span></a> at all, i'm more worried about <a href="https://kolektiva.social/tags/puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>puppet</span></a>. if other projects are any reference, however, this will hurt the community (and destroy the name puppet), but we will prevail</p>
anarcat<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@genebean" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>genebean</span></a></span> <a href="https://kolektiva.social/tags/perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>perforce</span></a> has been explicit in asking the community to maintain the opensource version and produce binary packages for <a href="https://kolektiva.social/tags/puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>puppet</span></a>, so we're actually doing what they want, in a sense, maybe not in the way they expect</p>
anarcat<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@genebean" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>genebean</span></a></span> my perspective on this is that we're not forking <a href="https://kolektiva.social/tags/Puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Puppet</span></a>, <a href="https://kolektiva.social/tags/perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>perforce</span></a> is forking puppet, and refusing the community the use of their brand name</p>
GeneBean<p>After <a href="https://fosstodon.org/tags/Perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Perforce</span></a> Software pulled the crap recently with the community Slack, I was afraid they were up to no good. Sadly, it seems I was correct. Fortunately, <span class="h-card" translate="no"><a href="https://hachyderm.io/@binford2k" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>binford2k</span></a></span> is on top of things and it seems he and <a href="https://fosstodon.org/tags/VoxPupuli" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VoxPupuli</span></a> are working on a truly <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> path forward for <a href="https://fosstodon.org/tags/Puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Puppet</span></a>. </p><p><a href="https://overlookinfratech.com/2024/11/08/sequestered-source/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">overlookinfratech.com/2024/11/</span><span class="invisible">08/sequestered-source/</span></a></p>
Troed Sångberg<p>Don't use centralized services for community projects, part 3451.</p><p><a href="https://infosec.exchange/@isotopp/113310756647450391" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">infosec.exchange/@isotopp/1133</span><span class="invisible">10756647450391</span></a></p><p><a href="https://ioc.exchange/tags/Slack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Slack</span></a> <a href="https://ioc.exchange/tags/Matrix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Matrix</span></a> <a href="https://ioc.exchange/tags/Puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Puppet</span></a> <a href="https://ioc.exchange/tags/Perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Perforce</span></a></p>
Jonathan Arnold<p><span class="h-card" translate="no"><a href="https://mastodon.gamedev.place/@grumpygamer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>grumpygamer</span></a></span> have you checked out <a href="https://social.sdf.org/tags/Perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Perforce</span></a>? It's used by lots of game companies.</p>
Jonathan Arnold<p>The <a href="https://social.sdf.org/tags/saltmine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>saltmine</span></a> continues to be pretty great, although I am still struggling with the git workflow. We swapped to <a href="https://social.sdf.org/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>git</span></a> at my previous job (from my beloved <a href="https://social.sdf.org/tags/Perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Perforce</span></a>) because "everyone knows it" but it occurred to me that it doesn't help, because everyone (and I mean everyone) uses it a different way, so there is as much training as if you were using a completely new SCCS. So annoying.</p>
Matthew Martin<p><span class="h-card" translate="no"><a href="https://mastodon.gamedev.place/@DevteamLife" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>DevteamLife</span></a></span> Why blame yourself? You didn't make you use <a href="https://mastodon.social/tags/Perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Perforce</span></a>.</p>
Eva Winterschön<p>Having successfully allocated Saturday afternoon's patience buffer to blobject restoration processing for a corrupted <a href="https://hachyderm.io/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>git</span></a> repo, I decided to be productive and vaccum the house! :ablobfoxbongo: </p><p>Might be time to migrate personal repos back to <a href="https://hachyderm.io/tags/Mercurial" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mercurial</span></a>, or perhaps revisit the glory of <a href="https://hachyderm.io/tags/Perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Perforce</span></a> ... hmmm decisions 🤔 </p><p><a href="https://hachyderm.io/tags/yesThereWereBackups" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>yesThereWereBackups</span></a> <a href="https://hachyderm.io/tags/yesTheRepoBackupArchivesAlsoHadCorruptGitBLOBS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>yesTheRepoBackupArchivesAlsoHadCorruptGitBLOBS</span></a> <a href="https://hachyderm.io/tags/theFilesystemWasFine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>theFilesystemWasFine</span></a><br><a href="https://hachyderm.io/tags/sixteenYearsOfGitIsTooManyGits" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sixteenYearsOfGitIsTooManyGits</span></a> 🙃</p>
Wilda Software<p>Nie zajmujemy się tworzeniem gier (choć wielu z nas od marzeń o tym zaczynało swoją przygodę z IT), więc umieszczenie poniższego artykułu przez nas może być dziwne. Tym niemniej, pokazuje on, że świat systemów kontroli wersji nie kończy się na Gicie i istnieją też alternatywy, które są dostosowane do różnych przypadków. A wierzcie nam - tworzenie gier wideo jest bardzo specyficznym "kejsem".</p><p><a href="https://social.wildasoftware.pl/tags/SVN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SVN</span></a> <a href="https://social.wildasoftware.pl/tags/Git" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Git</span></a> <a href="https://social.wildasoftware.pl/tags/Perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Perforce</span></a></p><p><a href="https://thenewstack.io/5-version-control-tools-game-developers-should-know-about/" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">thenewstack.io/5-version-contr</span><span class="invisible">ol-tools-game-developers-should-know-about/</span></a></p>
Fell<p>Any <a href="https://ma.fellr.net/tags/GameDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GameDev</span></a> people using <a href="https://ma.fellr.net/tags/Perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Perforce</span></a> out there? I would love a mechanisim that prevents me from checking in (=pushing) my changes as long as a specific keyword (like `__debugbreak`) is present in the code. Is there anything like that?</p><p><span class="h-card"><a href="https://a.gup.pe/u/gamedev" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gamedev</span></a></span> <a href="https://ma.fellr.net/tags/GameDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GameDevelopment</span></a> <a href="https://ma.fellr.net/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DevOps</span></a> <a href="https://ma.fellr.net/tags/Helix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Helix</span></a> <a href="https://ma.fellr.net/tags/P4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P4</span></a> <a href="https://ma.fellr.net/tags/AskFedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AskFedi</span></a> <a href="https://ma.fellr.net/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Programming</span></a></p>
Fell<p><span class="h-card"><a href="https://mastodon.social/@jrsofty" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jrsofty</span></a></span> Honestly? Apart from performance issues I don't see anything wrong with that. </p><p>We use <a href="https://ma.fellr.net/tags/Perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Perforce</span></a>, and I hate it.</p>
TTimo<p><a href="https://mastodon.social/tags/perforce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>perforce</span></a> cli fun: `p4 sync -f` on a file that needs resolving will report that you have latest .. and not tell you it didn't touch the file because it needs resolving ..</p>
Nobody [LinuxWalt (@lnxw48a1)]@<a href="https://nu.federati.net/user/12" class="h-card mention" rel="nofollow noopener" target="_blank">musicman</a> I don’t have any knowledge of #<span class=""><a href="https://nu.federati.net/tag/perforce" rel="nofollow noopener" target="_blank">Perforce</a></span> other than occasionally reading some of your posts. But it is good to see that your problem is solved, even if it meant submitting empty garbage files as part of your bugfix submission.
Nobody [LinuxWalt (@lnxw48a1)]@<a href="https://nu.federati.net/user/12" class="h-card mention" rel="nofollow noopener" target="_blank">musicman</a> @<a href="https://mastodon.social/users/b_cavello" class="h-card mention" rel="nofollow noopener" target="_blank">bcavello</a> Yes, true. If someone is watching socnets for job openings, they're probably going to watch tags corresponding to their interests, such as #<span class=""><a href="https://nu.federati.net/tag/java" rel="nofollow noopener" target="_blank">Java</a></span> #<span class=""><a href="https://nu.federati.net/tag/developer" rel="nofollow noopener" target="_blank">Developer</a></span> or #<span class=""><a href="https://nu.federati.net/tag/perforce" rel="nofollow noopener" target="_blank">Perforce.</a></span> <br><br> I'd expect that more generic tags, like #<span class=""><a href="https://nu.federati.net/tag/job" rel="nofollow noopener" target="_blank">job</a></span>, #<span class=""><a href="https://nu.federati.net/tag/jobs" rel="nofollow noopener" target="_blank">jobs</a></span>, #<span class=""><a href="https://nu.federati.net/tag/jobopening" rel="nofollow noopener" target="_blank">jobopening</a></span>, #<span class=""><a href="https://nu.federati.net/tag/applynow" rel="nofollow noopener" target="_blank">applynow</a></span> would be overfilled with non-interesting job openings and various MLM "business offerings".