Re: [Seaside Commits] Seaside 3.0 LGPL: Seaside-FileSystem-pmm.25.mcz

> marschal uploaded a new version of Seaside-FileSystem to project Seaside 3.0 LGPL:
> http://www.squeaksource.com/Seaside30LGPL/Seaside-FileSystem-pmm.25.mcz
>
> ==================== Summary ====================
>
> Name: Seaside-FileSystem-pmm.25
> Author: pmm
> Time: 1 November 2010, 10:15:18 pm
> UUID: b1d0622c-509e-49b5-bf9e-8283172b5427
> Ancestors: Seaside-FileSystem-pmm.24
>
> - FUCK YOU RB!
>
>
> _______________________________________________
> commits mailing list
> To unsubscribe, email [hidden email]
> http://lists.seaside.st/listinfo/commits
>

> 2010/11/2 Julian Fitzell <[hidden email]>:
>> please....?
>
> I hate RB, I really do. I don't understand how people can use it. It
> makes my code look really ugly. If I didn't care how my code looked, I
> used brainfuck. I don't understand how people are allowed to walk
> around and lie "we have the best tools". Honestly search and replace
> would be better than RB, because it doesn't reformat the code. Maybe
> we need a C library that we can call out to that solves this hard
> problem for us.
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>

> 1. RB does only reformat if necessary.
>
> 2. RB has a highly configurable reformatter: Settings > Refactoring
> Browser > Configurable Formatter.
>
> 3. RB shows each change before applying, you can even fix it there if
> you want. Accepting the proposed changes is like signing the EULA, it
> is your problem from the on.
>
> 4. RB can also do plain search and replace: Refactor > Source Regex.

> 2010/11/2 Julian Fitzell<[hidden email]>:
>> please....?
>
> I hate RB, I really do. I don't understand how people can use it. It
> makes my code look really ugly. If I didn't care how my code looked, I
> used brainfuck. I don't understand how people are allowed to walk
> around and lie "we have the best tools". Honestly search and replace
> would be better than RB, because it doesn't reformat the code. Maybe
> we need a C library that we can call out to that solves this hard
> problem for us.
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

> On 11/01/2010 11:00 PM, Philippe Marschall wrote:
>>
>> 2010/11/2 Julian Fitzell<[hidden email]>:
>>>
>>> please....?
>>
>> I hate RB, I really do. I don't understand how people can use it. It
>> makes my code look really ugly. If I didn't care how my code looked, I
>> used brainfuck. I don't understand how people are allowed to walk
>> around and lie "we have the best tools". Honestly search and replace
>> would be better than RB, because it doesn't reformat the code. Maybe
>> we need a C library that we can call out to that solves this hard
>> problem for us.
>>
>> Cheers
>> Philippe
>> _______________________________________________
>> seaside-dev mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
> Philippe,
>
> I mentioned this idea to a few folks at ESUG (and Lukas even wrote the code)
> ...
>
> Since it is impossible to satisfy everyone with a standard format, my idea
> is that the code browsing tools should reformat everything using a
> formatter/style that is chosen by the user ... all code should be stored
> without regard to format and all code comparison tools should format, then
> compare ...

> 2010/11/2 Dale Henrichs<[hidden email]>:
>> On 11/01/2010 11:00 PM, Philippe Marschall wrote:
>>>
>>> 2010/11/2 Julian Fitzell<[hidden email]>:
>>>>
>>>> please....?
>>>
>>> I hate RB, I really do. I don't understand how people can use it. It
>>> makes my code look really ugly. If I didn't care how my code looked, I
>>> used brainfuck. I don't understand how people are allowed to walk
>>> around and lie "we have the best tools". Honestly search and replace
>>> would be better than RB, because it doesn't reformat the code. Maybe
>>> we need a C library that we can call out to that solves this hard
>>> problem for us.
>>>
>>> Cheers
>>> Philippe
>>> _______________________________________________
>>> seaside-dev mailing list
>>> [hidden email]
>>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>> Philippe,
>>
>> I mentioned this idea to a few folks at ESUG (and Lukas even wrote the code)
>> ...
>>
>> Since it is impossible to satisfy everyone with a standard format, my idea
>> is that the code browsing tools should reformat everything using a
>> formatter/style that is chosen by the user ... all code should be stored
>> without regard to format and all code comparison tools should format, then
>> compare ...
>
> We had a pretty consistent formatting across the whole Seaside code
> base until we let tools wreck it.
>
>> It does assume that each individual can teach a formatter to format the code
>> to their liking...
>>
>> The end result is that when each user reads and edits code, it is
>> automatically formatted to their liking ...
>
> I believe it when I see it.