room topic changed to CGCC Blog Chat: For discussion around CGCC's site blog [blog] [cgcc-blog]

Looks like top suggetion is: Language design and development

I think a good way of doing the multiple posts thing would be to have an "index" post with links to each new post

I would like to be part of this historic /transcripts/1 page

It also had a ton of people signing up for it, so it would be a good introductory one

@cairdcoinheringaahing I think this is a good idea

yay reposts ftw

We could reuse the what should we write about thing for it

Although the tag should work as a directory

I see no need for a separate question specifically to do what a built-in feature does

true

room topic changed to CGCC Blog Chat: For discussion around CGCC's site blog and for drafting the posts [blog] [cgcc-blog]

Current top answer is Language design and development. Users who added their usernames are @YepIregratit, @Lyxal, @cairdcoinheringaahing, @hyper-neutrino

@RedwolfPrograms Fair enough

I think that one is going to be an extra good one to start with since so many people signed up for it it'd be a very community style thing

tbh it's pretty broad and should probably be split up

imo a broad approach is a good start

I don't think it's too broad, we already have some more specific ones proposed for later posts

it makes it more approachable as a first post, and we can specify in later posts if necessary

Should the tag be blog or cgcc-blog?

well it's broad enough that we'll want multiple posts under it and multiple people will want to write it

We'd have to rename the current blog for the first one, but it's cleaner.

I vote for blog

[blog] could go to [blog-discussion] and we reuse [blog]

That sounds good

What should the title format be? Blog Post #n: Title?

or maybe CGCC Blog #n: Title

I like the second one I think

CGCC Blog #n: Title (date)?

I think the date is kind of cluttered

idk if the date is necessary since we have the time posted on the post itself already

I think we mostly all agree on the second though

@cairdcoinheringaahing do we need the CGCC

SE needs a chat feature like discord's :thumpsup:

^

@YepIregratit Blog #n: Title seems too short and vague

^

@RedwolfPrograms and it might be confused for SE's official blog

I guess the next thing to do is to come up with a rough plan for the layout of CGCC Blog #1

how are we dividing the writing? from the looks of it i think it would make sense for each week to have one main author that writes the main entry and then the smaller additions that i proposed like "this week/period's underappreciated answers" could just be a collaboration of everyone else adding on a couple of other things

@RedwolfPrograms #0 >:|

1 indexing please :P

I think since this one had so many people sign up, we could divide it into sections and each take a few

i agree with 1-indexing here :p

Especially as this is broad enough, we could probably have one person do the main "intro" section and the rest be sectionals about specific parts of language design and dev

fine, compromise, the #1 post will be about languages and the #0 post will state all the objectively better things about 0-indexing

Wezl, you wrote the proposal, do you want to write the intro?

@RedwolfPrograms I actually didn't

Oh you didn't?

It was a repost from 2016

Oh

but I can write it if necessary

Let's list some sections we could include:

Memory models (stack/tacit/funtional/etc.)

ninja'd :p

Golfing vs. non golfing (what makes them different n'stuff)

compiling vs interpreting

and transpiling

Important aspects of existing popular languages (potentially by other CGCCers)

why you shouldn't use python :P

Non obvious, important builtins to include

Data types, maybe? (number types could also be an important part of that)

point free style

How an SBCS works

Or should that be for the golfing one

not sure if there'd be anything in this category, but maybe things to watch out for / avoid that would make your life unnecessarily harder as development goes on?

That's a good one

@RedwolfPrograms I think that's more relevant to the golfing language one

from my cs courses i know a bit of stuff about like how exactly memory management works with stack frames, the heap, etc, and other weird stuff like faking tail recursion with a trampoline, but idk if that'd be particularly on-topic for what we want here :P

That could be specific enough for its own blog post honestly

yeah that's a good point

@hyper-neutrino I don't care if it's on-topic, write that post please

We can afford to have some more technical and detailed posts, I'm sure everyone here's fine with learning way too much info on some super specific aspect of programming :p

a lot of (eso|golfing )langs don't do any optimization or memory management at all though

that's fair enough, super niche and weird technical things is pretty on-topic here actually :P

So, I think a good idea would be to create a shared document (e.g. a gist or google doc, preferably something that uses markdown) so that once we all know what we're writing about, we can just go ahead and write/edit it

hack.allmende.io/2wvZOGgmTrikRYtukJnCfw

is this like rip-off hackmd or smth

or did this come first, or are both rip-offs of something else, or ?

it's open source hackmd

oh nice

hedgedoc.org

suo

sup*

(screwed up the introduction)

You can edit your messages in chat (see?)

Pres the up arrow, or click the down arrow next to the message and select "edit"

Okay so to clarify: am I writing anything yet?

if you want

Asking because I don't want to accidentally not write content when I was expected to do so

no one's set a deadline

(yet)

@Lyxal You put your name down, but it's 100% up to you if you want to contribute

I'm gonna contribute but I don't know who's writing what

What did we decide?

Nobody does :p

Oh

Right

We haven't figured out how and who is writing the first post

Very excellent

We're doing language design, but what exactly we'll all be writing isn't decided yet

Should we create a g doc for blog writing?

Sure

NO

A gist?

besides, I already made a codimd/hedgedoc

The editor on that is very painful to use

why?

The font and color scheme are very annoying

You're right

gist//github repo would be best imo

No google doc

userscript time

I'd support a repo

@cairdcoinheringaahing add ons can bring MD support

But yes repo good

Should I make one?

I'll create a repo, and we can basically just use it for all drafts?

Oh, ok. You can do it.

New folder for a post, and we just upload our individual sections to edit there?

Sounds good

github.com/cairdcoinheringaahing/CGCC-Blog-drafts

Is there a way to request write access to a repo?

you can at least add collaborators through settings

Or do I have to grant people access by searching for them?

You have to I believe

let it be known that I object to github too by the way :)

I'll submit a PR with a folder and a planning md file

Then you can give me write access

(along with the others)

Good call

Should it just be blog_1/...?

yeah, that's a good format

Proposed

@RedwolfPrograms no, how about blog_0/... >:|

Not sure if that made a PR or not

There's no open PRs

Okay, I had to click a button

Done

This is the repo for collecting drafts for blog posts. If you'd like write access, either submit a PR, or comment on this issue with your CGCC username

I'll collect all of our proposed sections into the planning file

@Wezl Why's that?

@RedwolfPrograms the same reasons I object to google, except they fixed the light theme

@Wezl I think it's going to be impossible to find a system we all agree on, aside from SE (and we don't all agree on that), but this works

@Wezl Why's that?

I'll be happy to edit in any drafts that people want if they don't want to sign up for github. Email oldsandboxposts@gmail.com (yes, I'm reusing it, I cba to set up another one) with a reasonable format

@RedwolfPrograms proprietary, popular, evil companies, no vi keybindings

Why's popular bad?

fwiw I disagree with gmail

Popular is a good thing IMO

@Wezl You don't have to use it, just email to it :P

And I think GH being proprietary is unfortunate, but it's almost certainly benefitted the open source community considerably more than it's harmed it

Github good because I have more followers than y'all

:p

And vi keybindings are exactly what userscripts are for

And pretty much everything's owned by a company, how long it takes for them to become evil is just a function of how easily they can pretend not to be evil

evil being common doesn't justify it

fwiw Microsoft isn't a particularly evil company IMO

We're all going to fall victim to an overly capitalistic and consumerist society eventually, might as well accept the nihilism and do what you want

they're evil because they made github :P

In my opinion very few companies are actually evil; I was mostly joking in the above comment.

"Evil" is too strong, but "strongly dislikeable" can be applied to quite a few

@Wezl yesnt

And most large companies will grow to a point where it's impossible to keep up the human factor that makes companies strongly likeable

I regret giving Lyxal a way to email me :/

And you can't even use RO powers to stop me

I will enjoy this :p

@Lyxal why did you change transpilation to transpiration

wouldn't it make more sense for us to have posted our GH usernames here instead of the other way around

Or was that autocorrect

@hyper-neutrino That doesn't notify me

@RedwolfPrograms auto probably

Plus it means that we can advertise the repo on blog posts so that people who want to contribute don't have to go through here. It's just another equalivalent alternative

Who should write the introduction?

Or should we wait until the sections are done?

@RedwolfPrograms but we can still talk about water movement though if you'd like. ⌍P

Transpiration is a really nice word, it has a nice color

@RedwolfPrograms I'll be happy to do it if @Wezl isn't up for it

Maybe we could divide it into two parts: an introductory paragraph to the blog as a whole, and one for the post itself.

Introductpry

I can take one of the two if you want

Yeah, that's a good idea

Do you mind which one?

Not really

Given I revived the idea of the blog, I'd be fine writing up a paragraph or two about it

I'll do the one about the post itself then

Sounds good

When should we plan to have this done? Maybe by the weekend?

imagine having plans

Oh hey that reminded me I have a math test I almost forgot

Let's try and have it good for posting on Fri/Sat/Sun

Sounds good

@RedwolfPrograms Yeah, just incompetent. I keep getting a BSOD ever since I got the vaccine, none of that promised 5G :P

Are we going to merge all the parts into a single post or have them as different subsections?

And then how are we going to say who wrote which part?

We'll probably have them under subheadings

Like ## Golfing Languages

Are we allowed to use personal pronouns in our sections?

i would say yes

Because I'm wanting to reference the tips question I asked for the post

makes it more of a blog post rather than an article about some topic or smth

We can have something like <small>Written by [Lyxal]</small> for every subheading

That way it doesn't get confusing